Question:
Here's my issue, causing a ORA-12514: TNS: listener
could not resolve SERVICE_NAME error:
CODE
|
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount
ORACLE instance started.
ORA-12514: TNS:listener could not
resolve SERVICE_NAME given in connect
descriptor |
I'm using Oracle 10g on Windows 2000.
What's cause of this error and how to resolve it?
Answer by Edward Stoever:
ORA-12514: TNS:listener does not currently know of
service requested in connect descriptor
Cause: The listener received a request to
establish a connection to a database or other
service. The connect descriptor received
by the listener specified a service name for a
service (usually a database service) that either has
not yet dynamically registered with the listener or
has not been statically configured for the listener.
This may be a temporary condition such as after the
listener has started, but before the database
instance has registered with the listener.
Action:
-
Wait a moment and try to connect a second time.
- Check which services are currently known by
the listener by executing:
lsnrctl services <listener name>
- Check that the SERVICE_NAME parameter in the
connect descriptor of the net service name used
specifies a service known by the listener.
- If an easy connect naming connect identifier
was used, check that the service name specified
is a service known by the listener.
- Check for an event in the listener.log file.
I avoid using a listener connection when I startup
or shutdown, as a matter of practice. I realize that
cannot always be done. Are you physically on the
machine? Can you ssh or telnet in and run sqlplus on
the box? Then connect like so:
CODE
|
export ORACLE_SID=mydb ###Unix/Linux
sqlplus sys as sysdba
[no password needed - just hit return ]
SQL> startup mount
... |
do not connect with the @mydb to avoid the listener. |