Oracle Errors

Cause: The listener received a request to establish a

connection to a database or other service. The connect

descriptor received by the listener specified in addition to

the service name an instance name for an instance (usually a

database instance) 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.

Cause: The listener could not find any available service

handlers that are appropriate for the client connection.

Action: Run "lsnrctl services" to ensure that the

instance(s) have registered with the listener, and are

accepting connections.

Cause: The process of handing off a client connection to

another process failed.

Action: Turn on listener tracing and re-execute the

operation. Verify that the listener and database instance

are properly configured for direct handoff. If problem

persists, call Oracle Support.

Cause: None of the known and available service handlers for

the given SERVICE_NAME support the client's protocol stack:

transport, session, and presentation protocols.

Action: Check to make sure that the service handlers (e.g.

dispatchers) for the given SERVICE_NAME are registered with

the listener, are accepting connections, and that they are

properly configured to support the desired protocols.

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.

Cause: None of the known and available service handlers for

requested type of server (dedicated or shared) are

appropriate for the client connection.

Action: Run "lsnrctl services" to ensure that the

instance(s) have registered with the listener and that the

appropriate handlers are accepting connections.

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.

Cause: The dispatchers appear to be busy handling other

requests.

Action: Attempt the connection again. If error persists, ask

the DBA to increase the number of dispatchers and/or

dispatchers' limit on number of connections/sessions that

they can accept.

Cause: The dispatcher terminated unexpectedly

Action: Attempt to connect again and if the same error

occurs, contact the DBA 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.

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 DBA to register a dispatcher on your

protocol.

Cause: d by incompatible Oracle Net or Net8 versions. Do not

include in error manual.

Action: This is not seen in normal use of Oracle Net.

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 SID for an

instance (usually a database instance) 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.

Cause: The dispatchers notified the listener that they

temporarily do not accept new connections.

Action: Attempt the connection again. If error persists,

contact the DBA to check the state of the dispatchers and/or

ask him to increase the number of dispatchers.

Cause: The SID was missing from the CONNECT_DATA.

Action: Check that the connect descriptor corresponding to

the service name in TNSNAMES.ORA has an SID component in the

CONNECT_DATA.

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.