Related to this is the possibility that the database and listener are both up but the database has not yet registered with the listener. Service registration can take 60 seconds or more. This may be the case if the server has just been rebooted.
Another reason for this error is that the database you are attempting to connect to is not registered with the listener. This may happen if the instance cannot find the correct listener address in order to register itself. If the LOCAL_LISTENER parameter is set in the init.ora file, the instance will attempt to connect to the listener at that address to register itself. If this parameter is not set, it will attempt to connect to the default listener on port 1521.
Finally, an ORA-12514 can occur if the instance has successfully registered with the listener but the SERVICE_NAME does not match what PMON has registered with the listener. To verify if the service name in tnsnames.ora matches what is registered with the listener, do the following:
- At the DOS prompt, run the listener control utility:
- Set the display mode:
LSNRCTL> set displaymode verbose
- Display the services:
Check that the service name registered with the listener matches what you have defined in the tnsnames.ora file.
Dig Deeper on Oracle database installation, upgrades and patches
Related Q&A from Maria Anderson
Can I use /var/opt/oracle/oratab to specify listener information? Continue Reading
We would like to migrate our database from Oracle 8.1.7 to Oracle 10g. We would like to know the impact for our application developed using Delphi ... Continue Reading
I have been trying to install Oracle 8.1.7 on SUSE Linux 9.0 and got the error: "Error in invoking target install of makefile /opt/oracle/...../*.mk." Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.