Home » RDBMS Server » Server Utilities » Re: Strange error ORA-12514
Re: Strange error ORA-12514 [message #155447 is a reply to message #155444] Mon, 16 January 2006 05:36 Go to next message
Frank Naude
Messages: 4579
Registered: April 1998
Senior Member
See if you can connect after issuing an "ALTER SYSTEM REGISTER;".
Re: Strange error ORA-12514 [message #155605 is a reply to message #155447] Tue, 17 January 2006 11:16 Go to previous message
Gerardo Fernandez Herrera
Messages: 58
Registered: January 2006
Location: Montevideo, Uruguay
Member
See note 235562.1, Issues affecting Automatic Service Registration from Metalink.
The following abstract may help you:

Quote:


2.1 ORA-12514 errors connecting to registered instances
-------------------------------------------------------

When attempting to connect to Oracle8i using a connect descriptor containing a SERVICE_NAME entry, you may receive the following error:

ORA-12514: TNS:listener could not resolve SERVICE_NAME given in connect descriptor

The error means that the client has connected to the Listener but is requesting a connection to SERVICE_NAME that the Listener does not have a service handler for. This is usually not a problem with Service Registration, but since the SERVICE_NAME entry that the client is attempting to connect to is almost always a dynamically registered service, it needs to be addressed
here.
There are several reasons that error ORA-12514 might occur:

1) The instance that the client is attempting to connect to is not registered with the Listener because the instance cannot locate the correct Listener address in order to register itself.
If the LOCAL_LISTENER parameter is present in the INIT.ORA file, it will attempt to resolve to an address. The instance will attempt to connect to a Listener on that address to register itself.
If the LOCAL_LISTENER parameter is not present in the INIT.ORA file, the instance will attempt to connect to the Default Listener using the default address of TCP/IP port 1521 or IPC key PNPKEY.

2) The instance has registered with the listener, but the SERVICE_NAME that the client is attempting to connect to does not match the SERVICE that PMON has registered with the Listener.

The following steps show which SERVICE_NAME is registering with the Listener:

- Run the listener control utility (lsnrctl).
- At the LSNRCTL prompt, type "set displaymode verbose" and press Enter.
- At the LSNRCTL prompt, type "services" and press Enter.

Ensure that the TNSNAMES.ORA entry for the SERVICE_NAME parameter exactly matches a service that is registered with the Listener.

3) The instance is down.

One of the benefits of using service registration is that the Listener is aware of the state of the instance.
When the instance is up, it registers itself with the Listener, allowing the Listener to service incoming requests for it.
When the instance is down, it will not be registered with the Listener. If the instance is not registered with the Listener, the Listener will refuse incoming requests for it, and clients receive error ORA-12514.


4) The instance and Listener are both up, but the instance has not yet registered with the Listener.
When the instance is started, it attempts to connect to register with the local Listener. It continues to check for the Listener about once every 60 seconds.

If the Listener is up when the instance is started, service registration should take place as the instance starts. If the Listener comes up after the instance, it will take up to a minute or so for the instance to register itself with the Listener. This is usually not an issue, but if the Listener is stopped then started, users may fail to connect until the
the instance successfully re-registers with the Listener.

You can check to see whether the instance has registered itself using the lsnrctl commands described in 2).

To resolve the ORA-12514 errors, you need to either resolve the registration problems, resolve the problems with the SERVICE_NAME not matching what the name that is actually registering with the listener, or define a static service
handler in the LISTENER.ORA file and modify the TNSNAMES.ORA file to connect to the newly defined SID instead of the SERVICE_NAME.



Previous Topic: HELP!How to convert Tamino XML DB Server to Oracle XML DB Server and/or Ora
Next Topic: commit to the end of the load
Goto Forum:
  


Current Time: Fri Mar 29 09:31:07 CDT 2024