Installation Note 41514: SAS® Activity-Based Management installation log contains "Listener refused the connection" when incorrect Oracle database name specified
You might observe an error similar to the following in the SAS Activity-Based Management installation log if you have specified the wrong Oracle Global Database Name during your SAS Activity-Based Management installation:
[echo] java.sql.SQLException: Listener refused the connection with the following error:
[echo] ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
The Oracle Global Database Name typically contains the Service Name (alias) or SID (unique name of the database instance) followed by the domain suffix.
For example, if the Service Name is "orcl" and the domain suffix is "na.test.com", then the correct Global Database Name would be:
However, it is possible to configure the Oracle Global Database Name to be the same as the Service Name or the SID. This is especially true for many default setups for database instances
prior to Oracle 11g R2.
If you use Oracle 11g R2 and you encounter this error, be sure to supply the correct Global Database Name (with the domain suffix) when you are prompted for the "Global Database Name" parameter in the SAS Deployment Wizard.
Operating System and Release Information
| SAS System | SAS Activity-Based Management | Microsoft Windows Server 2003 Datacenter Edition | 7.1 | | | |
| Microsoft Windows Server 2003 Enterprise Edition | 7.1 | | | |
| Microsoft Windows Server 2003 Standard Edition | 7.1 | | | |
| Microsoft Windows Server 2003 for x64 | 7.1 | | | |
| Microsoft Windows Server 2008 | 7.1 | | | |
| Microsoft Windows Server 2008 for x64 | 7.1 | | | |
*
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.
| Type: | Installation Note |
| Priority: | medium |
| Date Modified: | 2010-11-08 11:18:27 |
| Date Created: | 2010-11-05 13:13:35 |
