Copy of Oracle FAQ | ORACLE RECOVERY without DUL |
Index >
ORACLE Server Parameters >
dispatchers
dispatchersOracle 10.0.1:
Oracle 9.2.0:
Oracle 8.1.7:No such parmeter in Oracle 8.1.7.Oracle 8.0.6:No such parmeter in Oracle 8.0.6.Oracle 7.3.4:No such parmeter in Oracle 7.3.4.Related Error Messages:ORA-00101: invalid specification for system parameter DISPATCHERS
Action: Refer to the manual for correct syntax. ORA-00102: network protocol %s cannot be used by dispatchers
Action: Refer to the manual on network protocols supported by the dispatchers. ORA-00113: protocol name %s is too long
Action: Use a valid protocol name for the DISPATCHERS value. ORA-00134: invalid DISPATCHERS specification #%s
Action: Refer to the Oracle Reference Manual for the correct syntax. ORA-02066: missing or invalid DISPATCHERS text
Action: place the string literal containing the dispatcher's specification after ALTER SYSTEM SET DISPATCHERS ORA-12509: TNS:listener failed to redirect client to service handler
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. ORA-12510: TNS:database temporarily lacks resources to handle the request
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. ORA-12511: TNS:service handler found but it is not accepting 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. ORA-12513: TNS:service handler found but it has registered for a different protocol
Action: Contact the DBA to register a dispatcher on your protocol.
This parameter is documented in the Oracle Server Reference Guide. Search for more info about [ dispatchers ] on the Oracle FAQ.
|