ORA-12500: TNS:listener failed to start a dedicated server process

Cause: The process of starting up a dedicated server process failed. The executable could not be found or the environment may be set up incorrectly.

Action: Turn on tracing at the ADMIN level and reexecute the operation. Verify that the ORACLE Server executable is present and has execute permissions enabled. Ensure that the ORACLE environment is specified correctly in LISTENER.ORA. The Oracle Protocol Adapter that is being called may not be installed on the local hard drive. Please check that the correct Protocol Adapter are successfully linked. If error persists, contact Oracle Customer Support.

Solution doesn't works for you?
POST your error in our discussion panel here.
Our DBA team will be happy to help you :)
Continue Reading

ORA-12504: TNS:listener was not given the SERVICE_NAME in CONNECT_DATA

Cause: The listener was not configured with a default service and SERVICE_NAME was missing from the CONNECT_DATA received by the listener.

Action: Possible solutions are:
- Configure DEFAULT_SERVICE parameter in LISTENER.ORA with a valid service name. Reload the listener parameter file using reload [<listener_name>]. This should be done by the LISTENER administrator.
- If using a service name, Check that the connect descriptor corresponding to the service name in TNSNAMES.ORA has a SERVICE_NAME or SID component in the CONNECT_DATA.

Solution doesn't works for you?
POST your error in our discussion panel here.
Our DBA team will be happy to help you :)
Continue Reading

ORA-12505: TNS:listener does not currently know of SID given 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 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.

Action:
- Wait a moment and try to connect a second time.
- Check which instances are currently known by the listener by executing: lsnrctl services <listener name>
- Check that the SID parameter in the connect descriptor specifies an instance known by the listener.
- Check for an event in the listener.log file.

Solution doesn't works for you?
POST your error in our discussion panel here.
Our DBA team will be happy to help you :)
Continue Reading

ORA-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 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.

Solution doesn't works for you?
POST your error in our discussion panel here.
Our DBA team will be happy to help you :)
Continue Reading
1 2 3 27