TNS-12515: TNS:listener could not find a handler for this presentation
Cause: None of the listener's known service handlers are registered as supporting the presentation protocol required by the connecting client.
Action: Check that the destination service is configured to accept the presentation protocol.
TNS-12514: TNS:listener could not resolve SERVICE_NAME given in connect descriptor
Cause: The SERVICE_NAME in the CONNECT_DATA was not found in the listener's tables.
Action: Check to make sure that the SERVICE_NAME specified is correct.
TNS-12513: TNS:service handler found but it has registered for a different protocol
Cause: The dispatchers registered for this service are connected to the listener by way of a different network protocol than that of the client.
Action: Contact the database administrator to register a dispatcher on your protocol.
TNS-12512: TNS:service handler found but it has not registered a redirect address
Cause: The dispatcher just came up and has not had time yet to register the address that a client should be redirected to.
Action: Attempt the connection again. If the error persists, ask the database administrator to increase the number of dispatchers.
TNS-12511: TNS:service handler found but it is not accepting connections
Cause: The dispatchers notified the listener that they temporarily do not accept new connections.
Action: Attempt the connection again. If the error persists, contact the database administrator to check the state of the dispatchers and/or increase the number of dispatchers.
TNS-12510: TNS:database temporarily lacks resources to handle the request
Cause: The dispatchers appear to be busy handling other requests.
Action: Attempt the connection again. If the error persists, ask the database administrator to increase the number of dispatchers and/or dispatchers' limit on the number of connections/sessions that they can accept.
TNS-12509: TNS:listener failed to redirect client to service handler
Cause: The dispatcher terminated unexpectedly.
Action: Attempt to connect again and if the same error occurs, contact the database administrator to check the state of the dispatchers for this SID. If the problem persists, turn on tracing in the listener to determine the TNS error caused by the redirect.
TNS-12505: TNS:listener could not resolve SID given in connect descriptor
Cause: The SID in CONNECT_DATA was not found in the listener's tables.
Action: Check to make sure that the SID specified is correct. The SIDs that are currently registered with the listener can be obtained by typing "LSNRCTL SERVICES listener_name". These SIDs correspond to SID_NAMEs in TNSNAMES.ORA, or DB_NAMES in the INIT.ORA file.
TNS-12504: TNS:listener was not given the SID in CONNECT_DATA
Cause: The SID was missing from CONNECT_DATA.
Action: Check that the connect descriptor corresponding to the service name in TNSNAMES.ORA has an SID component in CONNECT_DATA.
TNS-12502: TNS:listener received no CONNECT_DATA from client
Cause: No CONNECT_DATA was passed to the listener.
Action: Check that the service name resolved from TNSNAMES.ORA has the CONNECT_DATA component of the connect descriptor.