After making corrections described in KB 16384-61809, AIK step 3.4 still fails
- Article Type: General
- Product: Aleph
- Product Version: 21
Problem Symptoms:
After making the corrections to tnsnames.ora and listener.ora described in KB 16384-61809 ("Connection to the database aleph21 via listener hasn't been established yet"), AIK step 3.4 still fails.
Cause:
The attempt to connect to the database aleph21 was made before the database had registered itself with the Listener:
Resolution:
Wait until the database has registered itself with the Listener before trying to connect to the database via the Listener.
To be on the safe side, watch the end of the Listener Log File until the message "service_register * aleph21" appears:
$ tail -f /exlibris/app/oracle/diag/tnslsnr/us-elunaaleph/listener/trace/listener.log
Additional Information
According to the log file of the Oracle Listener on server us-elunaaleph the latest unsuccessful attempt to connect to the database aleph21 via the Listener was made on 26 April 2013 at 05:48:16 CDT:
26-APR-2013 05:48:16 * (connect_data=(service_name=aleph21.us-elunaaleph)(server=DEDICATED)(CID=(PROGRAM=sqlplus)(HOST=us-elunaaleph.corp.exlibrisgroup.com)(USER=root))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.100.3.70)(PORT=56282)) * establish * aleph21.us-elunaaleph * 12514
TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
This was only 49 seconds after the Listener had been started:
2013-04-26 05:47:27.200000 -05:00
[...]
Started with pid=14929
However, the attempt to connect to the database aleph21 was made 10 seconds before the database had registered itself with the Listener:
26-APR-2013 05:48:26 * service_register * aleph21 * 0
The Oracle Listener was not aware of the database aleph21 when the connection was attempted.
Category: Installation
Subject: New Installation
- Article last edited: 10/8/2013