SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 57097: The Update Host Name References tool in SAS® Deployment Manager builds an invalid JDBC URL and an error message is generated

DetailsHotfixAboutRate It

When you use the SAS Deployment Manager Update Host Name utility, configuration of the SAS Web Infrastructure Platform might fail. With this failure, an invalid Java database connectivity (JDBC) URL is built, and the webinfpltfm_changeHost_date.log file displays the following error:

[echo] url: jdbc:oracle:thin:@//hostname:1521:service name . . .more message lines. . . ORA-12505, TNS:listener does not currently know of SID given in connect descriptor

This problem occurs when the target database is Oracle and the Use Oracle database name as a Service Name selection is checked during the original configuration. This selection causes the database name to be treated as a Service Name rather than as a SID.

The Oracle Real Application Clusters (RAC) database uses a Service Name rather than a SID. As a result, the error occurs when you use this database.

Click the Hot Fix tab in this note to access the hot fix for this issue.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Web Infrastructure PlatformMicrosoft® Windows® for x649.4_M39.4_M49.4 TS1M39.4 TS1M4
Microsoft Windows 8 Enterprise 32-bit9.4_M39.4_M49.4 TS1M39.4 TS1M4
Microsoft Windows 8 Enterprise x649.4_M39.4_M49.4 TS1M39.4 TS1M4
Microsoft Windows 8 Pro 32-bit9.4_M39.4_M49.4 TS1M39.4 TS1M4
Microsoft Windows 8 Pro x649.4_M39.4_M49.4 TS1M39.4 TS1M4
Microsoft Windows 8.1 Enterprise 32-bit9.4_M39.4_M49.4 TS1M39.4 TS1M4
Microsoft Windows 8.1 Enterprise x649.4_M39.4_M49.4 TS1M39.4 TS1M4
Microsoft Windows 8.1 Pro9.4_M39.4_M49.4 TS1M39.4 TS1M4
Microsoft Windows 8.1 Pro 32-bit9.4_M39.4_M49.4 TS1M39.4 TS1M4
Microsoft Windows Server 20089.4_M39.4_M49.4 TS1M39.4 TS1M4
Microsoft Windows Server 2008 R29.4_M39.4_M49.4 TS1M39.4 TS1M4
Microsoft Windows Server 2008 for x649.4_M39.4_M49.4 TS1M39.4 TS1M4
Microsoft Windows Server 2012 Datacenter9.4_M39.4_M49.4 TS1M39.4 TS1M4
Microsoft Windows Server 2012 R2 Datacenter9.4_M39.4_M49.4 TS1M39.4 TS1M4
Microsoft Windows Server 2012 R2 Std9.4_M39.4_M49.4 TS1M39.4 TS1M4
Microsoft Windows Server 2012 Std9.4_M39.4_M49.4 TS1M39.4 TS1M4
Windows 7 Enterprise 32 bit9.4_M39.4_M49.4 TS1M39.4 TS1M4
Windows 7 Enterprise x649.4_M39.4_M49.4 TS1M39.4 TS1M4
Windows 7 Home Premium 32 bit9.4_M39.4_M49.4 TS1M39.4 TS1M4
Windows 7 Home Premium x649.4_M39.4_M49.4 TS1M39.4 TS1M4
Windows 7 Professional 32 bit9.4_M39.4_M49.4 TS1M39.4 TS1M4
Windows 7 Professional x649.4_M39.4_M49.4 TS1M39.4 TS1M4
Windows 7 Ultimate 32 bit9.4_M39.4_M49.4 TS1M39.4 TS1M4
Windows 7 Ultimate x649.4_M39.4_M49.4 TS1M39.4 TS1M4
64-bit Enabled AIX9.4_M39.4_M49.4 TS1M39.4 TS1M4
64-bit Enabled Solaris9.4_M39.4_M49.4 TS1M39.4 TS1M4
HP-UX IPF9.4_M39.4_M49.4 TS1M39.4 TS1M4
Linux for x649.4_M39.4_M49.4 TS1M39.4 TS1M4
Solaris for x649.4_M39.4_M49.4 TS1M39.4 TS1M4
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.