TNS-01406: ID: string
Cause: Control program status message.
Action: None.
Cause: Control program status message.
Action: None.
TNS-01405: Host: string
TNS-01405: Host: string
Cause: Control program status message.
Action: None.
Cause: Control program status message.
Action: None.
TNS-01404: Max Load: string
TNS-01404: Max Load: string
Cause: Control program status message.
Action: None.
Cause: Control program status message.
Action: None.
TNS-01403: Load: string
TNS-01403: Load: string
Cause: Control program status message.
Action: None.
Cause: Control program status message.
Action: None.
TNS-01402: TYPE: string
TNS-01402: TYPE: string
Cause: Control program status message.
Action: None.
Cause: Control program status message.
Action: None.
TNS-01401: Class: string
TNS-01401: Class: string
Cause: Control program status message.
Action: None.
Cause: Control program status message.
Action: None.
TNS-01400: Instance string has number handlers.
TNS-01400: Instance string has number handlers.
Cause: Control program status message.
Action: None.
Cause: Control program status message.
Action: None.
TNS-01307: nt OS err code: number
TNS-01307: nt OS err code: number
Cause: Listener logging message.
Action: None.
Cause: Listener logging message.
Action: None.
TNS-01306: nt secondary err code: number
TNS-01306: nt secondary err code: number
Cause: Listener logging message.
Action: None.
Cause: Listener logging message.
Action: None.
TNS-01305: nt main err code: number
TNS-01305: nt main err code: number
Cause: Listener logging message.
Action: None.
Cause: Listener logging message.
Action: None.
TNS-01304: ns secondary err code: number
TNS-01304: ns secondary err code: number
Cause: Listener logging message.
Action: None.
Cause: Listener logging message.
Action: None.
TNS-01303: ns main err code: number
TNS-01303: ns main err code: number
Cause: Listener logging message.
Action: None.
Cause: Listener logging message.
Action: None.
TNS-01302: nr err code: number
TNS-01302: nr err code: number
Cause: Listener logging message.
Action: None.
Cause: Listener logging message.
Action: None.
TNS-01301: TNS error structure:
TNS-01301: TNS error structure:
Cause: Listener logging message.
Action: None.
Cause: Listener logging message.
Action: None.
TNS-01300: ERROR at string
TNS-01300: ERROR at string
Cause: Listener logging message.
Action: None.
Cause: Listener logging message.
Action: None.
TNS-01204: Unprivileged account (string) is in dba group (string)
TNS-01204: Unprivileged account (string) is in dba group (string)
Cause: The unprivileged account has DBA privileges. The unprivileged account specified by DEFAULT_USER_ACCOUNT in the SID_DESC in LISTENER.ORA is a member of the dba group specified by DBA_GROUP in SID_DESC. The unprivileged account cannot belong to the dba group because this would be a security violation with OPS$ logins.
Action: Remove the unprivileged account from the dba group.
Cause: The unprivileged account has DBA privileges. The unprivileged account specified by DEFAULT_USER_ACCOUNT in the SID_DESC in LISTENER.ORA is a member of the dba group specified by DBA_GROUP in SID_DESC. The unprivileged account cannot belong to the dba group because this would be a security violation with OPS$ logins.
Action: Remove the unprivileged account from the dba group.
TNS-01203: Missing the account (string) specified by DEFAULT_USER_ACCOUNT in SID_DESC
TNS-01203: Missing the account (string) specified by DEFAULT_USER_ACCOUNT in SID_DESC
Cause: The unprivileged OS account is missing from or etc or passwd.
Action: Check the DEFAULT_USER_ACCOUNT parameter in the SID_DESC in LISTENER.ORA and verify it has a valid entry in or etc or passwd. This is the account that the Oracle shadow process will be started with if the the connecting client has database privileges or does not exist on this machine.
Cause: The unprivileged OS account is missing from or etc or passwd.
Action: Check the DEFAULT_USER_ACCOUNT parameter in the SID_DESC in LISTENER.ORA and verify it has a valid entry in or etc or passwd. This is the account that the Oracle shadow process will be started with if the the connecting client has database privileges or does not exist on this machine.
TNS-01202: Missing the dba group (string) specified by DBA_GROUP in SID_ DESC
TNS-01202: Missing the dba group (string) specified by DBA_GROUP in SID_ DESC
Cause: The dba group specified is missing from or ETC or GROUP.
Action: Check the DBA_GROUP parameter in the SID_DESC in LISTENER.ORA and verify it has a valid entry in or ETC or GROUP.
Cause: The dba group specified is missing from or ETC or GROUP.
Action: Check the DBA_GROUP parameter in the SID_DESC in LISTENER.ORA and verify it has a valid entry in or ETC or GROUP.
TNS-01201: Listener cannot find executable string for SID string
TNS-01201: Listener cannot find executable string for SID string
Cause: The executable for the Oracle dedicated server process cannot be found.
Action: Check the appropriate SID_DESC in LISTENER.ORA to make sure that the ORACLE_HOME component is pointing to a valid location. If this component is not set, then check the value of the ORACLE_HOME environment variable.
Cause: The executable for the Oracle dedicated server process cannot be found.
Action: Check the appropriate SID_DESC in LISTENER.ORA to make sure that the ORACLE_HOME component is pointing to a valid location. If this component is not set, then check the value of the ORACLE_HOME environment variable.
TNS-01200: The listener must be suid root
TNS-01200: The listener must be suid root
Cause: The ownership privileges of the TNSLSNR executable are incorrect.
Action: Contact your DBA or system administrator to change the ownership of the file to be suid root and restart the listener. This action is necessary because the user that started the process should claim ownership.
Cause: The ownership privileges of the TNSLSNR executable are incorrect.
Action: Contact your DBA or system administrator to change the ownership of the file to be suid root and restart the listener. This action is necessary because the user that started the process should claim ownership.
TNS-01192: Missing SID_LIST_ value left of equation for SID description in LISTENER.ORA
TNS-01192: Missing SID_LIST_ value left of equation for SID description in LISTENER.ORA
Cause: SID description in LISTENER.ORA had an error in it.
Action: Make sure the lines of code in LISTENER.ORA containing SID_DESC or SID begin with SID_LIST_lamp;lt;lamp;nbsp;listener_namelamp;gt; on the left side of the equation. For example, SID_LIST_LISTENER =(SID_LIST=(SID_DESC=(SID_ NAME=lamp;lt;lamp;nbsp;sidlamp;gt;)(ORACLE_HOME=lamp;lt;lamp;nbsp;oracle_homelamp;gt;)))
Cause: SID description in LISTENER.ORA had an error in it.
Action: Make sure the lines of code in LISTENER.ORA containing SID_DESC or SID begin with SID_LIST_lamp;lt;lamp;nbsp;listener_namelamp;gt; on the left side of the equation. For example, SID_LIST_LISTENER =(SID_LIST=(SID_DESC=(SID_ NAME=lamp;lt;lamp;nbsp;sidlamp;gt;)(ORACLE_HOME=lamp;lt;lamp;nbsp;oracle_homelamp;gt;)))
TNS-01191: Failed to initialize the local OS authentication subsystem
TNS-01191: Failed to initialize the local OS authentication subsystem
Cause: Initialization of the security subsystem failed during listener startup or reload. The listener could not obtain system resources (memory, or file descriptors) needed for local OS authentication security mechanism.
Action: Make sure that system resources like shared memory and heap memory are available for listener to execute properly. For further details, turn on tracing and execute the operation again. If the error persists, contact Oracle Support Services.
Cause: Initialization of the security subsystem failed during listener startup or reload. The listener could not obtain system resources (memory, or file descriptors) needed for local OS authentication security mechanism.
Action: Make sure that system resources like shared memory and heap memory are available for listener to execute properly. For further details, turn on tracing and execute the operation again. If the error persists, contact Oracle Support Services.
TNS-01190: The user is not authorized to execute the requested listener command
TNS-01190: The user is not authorized to execute the requested listener command
Cause: Most of the listener administrative commands are only intended to be issued by privileged users, for example DBAs or system administrators. If the listener password is not set, then the listener only accepts administrative requests from LSNRCTL running with the same OS credentials, or running as a local administrator (also referred to as super user).
Action: If an authorized user is attempting the command, then make sure that LSNRCTL is executed with the same OS user credentials as the running listener, or as a local administrator.
Cause: Most of the listener administrative commands are only intended to be issued by privileged users, for example DBAs or system administrators. If the listener password is not set, then the listener only accepts administrative requests from LSNRCTL running with the same OS credentials, or running as a local administrator (also referred to as super user).
Action: If an authorized user is attempting the command, then make sure that LSNRCTL is executed with the same OS user credentials as the running listener, or as a local administrator.
TNS-01189: The listener could not authenticate the user
TNS-01189: The listener could not authenticate the user
Cause: The user attempted to issue a privileged administrative command, but could not be successfully authenticated by the listener using the local OS authentication mechanism. This may occur due to one of the following reasons: 1. The user is running a version of LSNRCTL that is lower than the version of the listener. 2. The user is attempting to administer the listener from a remote node. 3. The listener could not obtain the system resources needed to perform the authentication. 4. The local network connection between the listener and LSNRCTL was terminated unexpectedly during authentication message exchange, such as if LSNRCTL program was suddenly aborted. 5. The communication between the listener and LSNRCTL is being intercepted by a malicious user. 6. The software that the user is running is not following the authentication protocol, indicating a malicious user.
Action: Make sure that administrative commands are issued using the LSNRCTL tool that is of a version equal or greater than the version of the listener, and that the tool and the listener are running on the same node. You can issue the VERSION command to find out the version of the listener. If a malicious user is suspected, use the information provided in the listener log file to determine the source and nature of the requests. Enable listener tracing for more information. If the error persists, contact Oracle Support Services.
Cause: The user attempted to issue a privileged administrative command, but could not be successfully authenticated by the listener using the local OS authentication mechanism. This may occur due to one of the following reasons: 1. The user is running a version of LSNRCTL that is lower than the version of the listener. 2. The user is attempting to administer the listener from a remote node. 3. The listener could not obtain the system resources needed to perform the authentication. 4. The local network connection between the listener and LSNRCTL was terminated unexpectedly during authentication message exchange, such as if LSNRCTL program was suddenly aborted. 5. The communication between the listener and LSNRCTL is being intercepted by a malicious user. 6. The software that the user is running is not following the authentication protocol, indicating a malicious user.
Action: Make sure that administrative commands are issued using the LSNRCTL tool that is of a version equal or greater than the version of the listener, and that the tool and the listener are running on the same node. You can issue the VERSION command to find out the version of the listener. If a malicious user is suspected, use the information provided in the listener log file to determine the source and nature of the requests. Enable listener tracing for more information. If the error persists, contact Oracle Support Services.
TNS-01188: Listener cannot operate with incompatible transport protocols
TNS-01188: Listener cannot operate with incompatible transport protocols
Cause: Listener was configured with multiple listening addresses with different and incompatible transport protocols. Listener cannot operate efficiently in such configuration.
Action: Modify the existing listener configuration by removing the listening address that caused the error. Configure a separate listener to listen on this address.
Cause: Listener was configured with multiple listening addresses with different and incompatible transport protocols. Listener cannot operate efficiently in such configuration.
Action: Modify the existing listener configuration by removing the listening address that caused the error. Configure a separate listener to listen on this address.
TNS-01187: No proxy service handler available
TNS-01187: No proxy service handler available
Cause: One of the following conditions has occurred:
Action: If the proxy service is not registered it may need to be restarted. If the proxy service handlers are busy and not accepting new connections more of them may need to be started to handle the load.
Cause: One of the following conditions has occurred:
Action: If the proxy service is not registered it may need to be restarted. If the proxy service handlers are busy and not accepting new connections more of them may need to be started to handle the load.
TNS-01186: Client connection was dropped based on a filtering rule
TNS-01186: Client connection was dropped based on a filtering rule
Cause: Listener was configured with a filtering rule which explicitly specified that the client connection should be terminated without returning an error to the client.
Action: Modify the filtering rules if the client should be allowed access to the requested service.
Cause: Listener was configured with a filtering rule which explicitly specified that the client connection should be terminated without returning an error to the client.
Action: Modify the filtering rules if the client should be allowed access to the requested service.
TNS-01185: Registration attempted from a remote node
TNS-01185: Registration attempted from a remote node
Cause: It was determined that the registering instance is not located on the same node as the listener. It is required that the instance be colocated with the listener for this type of service registration.
Action: Check the configuration of the registering instance. Ensure that local_ listener parameter specifies only local listeners. Use remote_listener parameter to specify remote listeners.
Cause: It was determined that the registering instance is not located on the same node as the listener. It is required that the instance be colocated with the listener for this type of service registration.
Action: Check the configuration of the registering instance. Ensure that local_ listener parameter specifies only local listeners. Use remote_listener parameter to specify remote listeners.
TNS-01184: Listener rejected registration or update of service handler string
TNS-01184: Listener rejected registration or update of service handler string
Cause: Received registration or update information could not be processed because it was invalid, or an internal error occurred.
Action: Not normally visible to the user. For further details, turn on tracing and restart the instance. If error persists, contact Oracle Customer Support.
Cause: Received registration or update information could not be processed because it was invalid, or an internal error occurred.
Action: Not normally visible to the user. For further details, turn on tracing and restart the instance. If error persists, contact Oracle Customer Support.
TNS-01183: Listener rejected registration or update of instance string
TNS-01183: Listener rejected registration or update of instance string
Cause: Received registration or update information could not be processed because it was invalid, or an internal error occurred.
Action: Not normally visible to the user. For further details, turn on tracing and restart the instance. If error persists, contact Oracle Customer Support.
Cause: Received registration or update information could not be processed because it was invalid, or an internal error occurred.
Action: Not normally visible to the user. For further details, turn on tracing and restart the instance. If error persists, contact Oracle Customer Support.
TNS-01182: Listener rejected registration of service string
TNS-01182: Listener rejected registration of service string
Cause: Received registration information could not be processed because it was invalid, or an internal error occurred.
Action: Not normally visible to the user. For further details, turn on tracing and restart the instance. If error persists, contact Oracle Customer Support.
Cause: Received registration information could not be processed because it was invalid, or an internal error occurred.
Action: Not normally visible to the user. For further details, turn on tracing and restart the instance. If error persists, contact Oracle Customer Support.
TNS-01181: Internal registration connection limit reached
TNS-01181: Internal registration connection limit reached
Cause: The number of registration connections has reached the maximum. No more registrations are allowed until some of the existing registration connections are completed.
Action: Disconnect existing registration connections if they are no longer needed.
Cause: The number of registration connections has reached the maximum. No more registrations are allowed until some of the existing registration connections are completed.
Action: Disconnect existing registration connections if they are no longer needed.
TNS-01180: Missing listener object string in Directory Server
TNS-01180: Missing listener object string in Directory Server
Cause: The listener could not find the listener object specified.
Action: Make sure the listener object is present in the Directory Server.
Cause: The listener could not find the listener object specified.
Action: Make sure the listener object is present in the Directory Server.
TNS-01179: Listener cannot load instance class string
TNS-01179: Listener cannot load instance class string
Cause: Instance tried to register as a class unknown to listener.
Action: check LISTENER.ORA and or or instance configuration, and reference platform documentation to find the instance classes available for the listener on this platform.
Cause: Instance tried to register as a class unknown to listener.
Action: check LISTENER.ORA and or or instance configuration, and reference platform documentation to find the instance classes available for the listener on this platform.
TNS-01178: Trace Level is 0. Trace file or directory unchanged
TNS-01178: Trace Level is 0. Trace file or directory unchanged
Cause: Trace Level needs to be set for changing the trace file or directory
Action: use command set trc_level ON to set the trace level
Cause: Trace Level needs to be set for changing the trace file or directory
Action: use command set trc_level ON to set the trace level
TNS-01177: Log Status is OFF. Log file or directory unchanged
TNS-01177: Log Status is OFF. Log file or directory unchanged
Cause: Log status needs to be set ON for changing the log file
Action: use command set log_status ON to set the log status of the listener ON.
Cause: Log status needs to be set ON for changing the log file
Action: use command set log_status ON to set the log status of the listener ON.
TNS-01176: Error in loading the new parameter value
TNS-01176: Error in loading the new parameter value
Cause: Illegal values given for the parameters
Action: Make sure that the parameter values are valid refer to the manual for the legal values for paramters
Cause: Illegal values given for the parameters
Action: Make sure that the parameter values are valid refer to the manual for the legal values for paramters
TNS-01175: Password unchanged
TNS-01175: Password unchanged
Cause: Unable to set the new password
Action: Be sure to see that the new password has legal ASCII characters. Try to set the password again.
Cause: Unable to set the new password
Action: Be sure to see that the new password has legal ASCII characters. Try to set the password again.
TNS-01174: The sum of the POOL_SIZEs from each PRESPAWN_DESC is greater than the PRESPAWN_MAX
TNS-01174: The sum of the POOL_SIZEs from each PRESPAWN_DESC is greater than the PRESPAWN_MAX
Cause: The minimum value for PRESPAWN_MAX should be the sum of the POOL_SIZEs.
Action: Be sure the parameters required for PRESPAWN_DESC are specified in each SID_DESC. For example, SID_LIST_LISTENER = (SID_LIST=(SID_ DESC=(SID_NAME=lamp;lt;lamp;nbsp;sidlamp;gt;)(PRESPAWN_MAX=15)(ORACLE_HOME=lamp;lt;lamp;nbsp;oracle_ homelamp;gt;)(PRESPAWN_DESC=(PROTOCOL=tcp)(POOL_ SIZE=10)(TIMEOUT=30))(PRESPAWN_DESC=(PROTOCOL=ipc)(POOL_ SIZE=5)(TIMEOUT=15)))) Add or correct these parameters in the LISTENER.ORA file
Cause: The minimum value for PRESPAWN_MAX should be the sum of the POOL_SIZEs.
Action: Be sure the parameters required for PRESPAWN_DESC are specified in each SID_DESC. For example, SID_LIST_LISTENER = (SID_LIST=(SID_ DESC=(SID_NAME=lamp;lt;lamp;nbsp;sidlamp;gt;)(PRESPAWN_MAX=15)(ORACLE_HOME=lamp;lt;lamp;nbsp;oracle_ homelamp;gt;)(PRESPAWN_DESC=(PROTOCOL=tcp)(POOL_ SIZE=10)(TIMEOUT=30))(PRESPAWN_DESC=(PROTOCOL=ipc)(POOL_ SIZE=5)(TIMEOUT=15)))) Add or correct these parameters in the LISTENER.ORA file
TNS-01173: Missing or inappropriate PRESPAWN_MAX parameter from SID_DESC
TNS-01173: Missing or inappropriate PRESPAWN_MAX parameter from SID_DESC
Cause: PRESPAWN_MAX in each SID_DESC does not have required fields.
Action: Be sure the parameters required for PRESPAWN_DESC are specified in each SID_DESC. For example, SID_LIST_LISTENER = (SID_LIST=(SID_ DESC=(SID_NAME=lamp;lt;lamp;nbsp;sidlamp;gt;)(PRESPAWN_MAX=15)(ORACLE_HOME=lamp;lt;lamp;nbsp;oracle_ homelamp;gt;)(PRESPAWN_DESC=(PROTOCOL=tcp)(POOL_ SIZE=10)(TIMEOUT=30)))) Add or correct these parameters in the LISTENER.ORA file
Cause: PRESPAWN_MAX in each SID_DESC does not have required fields.
Action: Be sure the parameters required for PRESPAWN_DESC are specified in each SID_DESC. For example, SID_LIST_LISTENER = (SID_LIST=(SID_ DESC=(SID_NAME=lamp;lt;lamp;nbsp;sidlamp;gt;)(PRESPAWN_MAX=15)(ORACLE_HOME=lamp;lt;lamp;nbsp;oracle_ homelamp;gt;)(PRESPAWN_DESC=(PROTOCOL=tcp)(POOL_ SIZE=10)(TIMEOUT=30)))) Add or correct these parameters in the LISTENER.ORA file
TNS-01172: Listener has shut down since all listen addresses have been deallocated
TNS-01172: Listener has shut down since all listen addresses have been deallocated
Cause: The event detection mechanism broke and caused all listen addresses to be removed.
Action: Error 1170 has occured and caused all the listen addresses to be deallocated. Since all the listen addresses have been removed, no more connections can be established to this listener so it shuts itself down. This error is not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.
Cause: The event detection mechanism broke and caused all listen addresses to be removed.
Action: Error 1170 has occured and caused all the listen addresses to be deallocated. Since all the listen addresses have been removed, no more connections can be established to this listener so it shuts itself down. This error is not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-01171: Event detection broke for dispatcher: string
TNS-01171: Event detection broke for dispatcher: string
Cause: The event detection mechanism for the dispatcher specified returned an error.
Action: Future attempts to detect events on this dispatcher will fail. The listener will deallocate the dispatcher and connections will no long be redirected to this dispatcher. This error is not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.
Cause: The event detection mechanism for the dispatcher specified returned an error.
Action: Future attempts to detect events on this dispatcher will fail. The listener will deallocate the dispatcher and connections will no long be redirected to this dispatcher. This error is not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-01170: Event detection broke for address: string
TNS-01170: Event detection broke for address: string
Cause: The event detection mechanism for the address specified returned an error.
Action: Future attempts to detect events on this address will fail. The listener will deallocate the listen address and connections will no long be accepted for this address. This error is not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.
Cause: The event detection mechanism for the address specified returned an error.
Action: Future attempts to detect events on this address will fail. The listener will deallocate the listen address and connections will no long be accepted for this address. This error is not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-01169: The listener has not recognized the password
TNS-01169: The listener has not recognized the password
Cause: The listener has the password security mechanism enabled and requires the correct password to execute any command other than VERSION. The user attempted to issue one of the privileged administrative commands, but could not be successfully authenticated with the password provided.
Action: If an authorized user is attempting the command, then use the SET PASSWORD command at the LSNRCTL prompt with the listener password. If you do not know the password, then you are trying to execute an inappropriate command.
Cause: The listener has the password security mechanism enabled and requires the correct password to execute any command other than VERSION. The user attempted to issue one of the privileged administrative commands, but could not be successfully authenticated with the password provided.
Action: If an authorized user is attempting the command, then use the SET PASSWORD command at the LSNRCTL prompt with the listener password. If you do not know the password, then you are trying to execute an inappropriate command.
TNS-01168: Cannot allocate memory
TNS-01168: Cannot allocate memory
Cause: Sufficient memory could not be allocated to perform the desired activity.
Action: Either free some resource for TNS, or add more memory to the machine. For further details, turn on tracing and reexecute the operation.
Cause: Sufficient memory could not be allocated to perform the desired activity.
Action: Either free some resource for TNS, or add more memory to the machine. For further details, turn on tracing and reexecute the operation.
TNS-01167: The command string is not supported by the listener contacted
TNS-01167: The command string is not supported by the listener contacted
Cause: The listener does not recognize the command.
Action: This is caused when a newer version of LSNRCTL contacts an old listener. Upgrade listener if executing this command is important.
Cause: The listener does not recognize the command.
Action: This is caused when a newer version of LSNRCTL contacts an old listener. Upgrade listener if executing this command is important.
TNS-01165: Spawn alias has no program name set in it
TNS-01165: Spawn alias has no program name set in it
Cause: The spawn alias in LISTENER.ORA is incorrectly specified.
Action: This is not seen in normal use of Oracle Net.
Cause: The spawn alias in LISTENER.ORA is incorrectly specified.
Action: This is not seen in normal use of Oracle Net.
TNS-01164: No spawn alias sent to listener
TNS-01164: No spawn alias sent to listener
Cause: The spawn command was issued without an alias.
Action: This is not seen in normal use of Oracle Net.
Cause: The spawn command was issued without an alias.
Action: This is not seen in normal use of Oracle Net.
TNS-01163: Failed to spawn process: string
TNS-01163: Failed to spawn process: string
Cause: The process failed to start correctly.
Action: This is not seen in normal use of Oracle Net.
Cause: The process failed to start correctly.
Action: This is not seen in normal use of Oracle Net.
TNS-01162: Syntax error in the address resolved from the spawn alias: string
TNS-01162: Syntax error in the address resolved from the spawn alias: string
Cause: The alias specified to spawn a program was not a valid NVstring.
Action: This is not seen in normal use of Oracle Net.
Cause: The alias specified to spawn a program was not a valid NVstring.
Action: This is not seen in normal use of Oracle Net.
TNS-01161: Spawn alias string was not found. Check listener parameter file
TNS-01161: Spawn alias string was not found. Check listener parameter file
Cause: The alias specified to spawn a program was not found in LISTENER.ORA.
Action: This is not seen in normal use of Oracle Net.
Cause: The alias specified to spawn a program was not found in LISTENER.ORA.
Action: This is not seen in normal use of Oracle Net.
TNS-01160: Trace level was not specified
TNS-01160: Trace level was not specified
Cause: Failed to specify a trace level for the trace command.
Action: Specify one of OFF, USER, ADMIN, or SUPPORT. Users should not see this error if LSNRCTL is being used.
Cause: Failed to specify a trace level for the trace command.
Action: Specify one of OFF, USER, ADMIN, or SUPPORT. Users should not see this error if LSNRCTL is being used.
TNS-01159: Internal connection limit has been reached; listener has shut down
TNS-01159: Internal connection limit has been reached; listener has shut down
Cause: The internal Oracle Net connection list is full. The listener is configured to use too many Oracle Net connections.
Action: Reduce the number of listen addresses or services connected to the listener. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.
Cause: The internal Oracle Net connection list is full. The listener is configured to use too many Oracle Net connections.
Action: Reduce the number of listen addresses or services connected to the listener. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-01158: Internal connection limit reached, preventing dispatcher from connecting
TNS-01158: Internal connection limit reached, preventing dispatcher from connecting
Cause: The internal Oracle Net connection list is full. Too many dispatchers are connected to the listener; therefore, no more dispatchers are allowed to connect.
Action: For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.
Cause: The internal Oracle Net connection list is full. Too many dispatchers are connected to the listener; therefore, no more dispatchers are allowed to connect.
Action: For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-01157: Can only listen on number addresses - ignoring string
TNS-01157: Can only listen on number addresses - ignoring string
Cause: Too many addresses were given to listen on.
Action: Reduce the number of addresses to listen on and use another listener to listen on the remaining addresses.
Cause: Too many addresses were given to listen on.
Action: Reduce the number of addresses to listen on and use another listener to listen on the remaining addresses.
TNS-01156: Missing or inappropriate PROTOCOL, TIMEOUT or POOL_SIZE parameter from PRESPAWN_DESC
TNS-01156: Missing or inappropriate PROTOCOL, TIMEOUT or POOL_SIZE parameter from PRESPAWN_DESC
Cause: PRESPAWN_DESC in each SID_DESC does not have required fields.
Action: Be sure the parameters required for PRESPAWN_DESC are specified in each SID_DESC. For example, SID_LIST_LISTENER = (SID_LIST=(SID_ DESC=(SID_NAME=lamp;lt;lamp;nbsp;sidlamp;gt;)(PRESPAWN_MAX=5)(ORACLE_HOME=lamp;lt;lamp;nbsp;oracle_ homelamp;gt;)(PRESPAWN_DESC=(PROTOCOL=tcp)(POOL_ SIZE=10)(TIMEOUT=30)))) Add or correct these parameters in the LISTENER.ORA file
Cause: PRESPAWN_DESC in each SID_DESC does not have required fields.
Action: Be sure the parameters required for PRESPAWN_DESC are specified in each SID_DESC. For example, SID_LIST_LISTENER = (SID_LIST=(SID_ DESC=(SID_NAME=lamp;lt;lamp;nbsp;sidlamp;gt;)(PRESPAWN_MAX=5)(ORACLE_HOME=lamp;lt;lamp;nbsp;oracle_ homelamp;gt;)(PRESPAWN_DESC=(PROTOCOL=tcp)(POOL_ SIZE=10)(TIMEOUT=30)))) Add or correct these parameters in the LISTENER.ORA file
TNS-01155: Incorrectly specified SID_LIST_string parameter in LISTENER.ORA
TNS-01155: Incorrectly specified SID_LIST_string parameter in LISTENER.ORA
Cause: SID_LIST_lamp;lt;lamp;nbsp;listener_namelamp;gt; in LISTENER.ORA has an error in it.
Action: Be sure this parameter is specified as described in the Oracle9i Net Services Reference Guide. For example, SID_LIST_LISTENER = (SID_LIST=(SID_ DESC=(SID_NAME=lamp;lt;lamp;nbsp;sidlamp;gt;)(ORACLE_HOME=lamp;lt;lamp;nbsp;oracle_homelamp;gt;)))
Cause: SID_LIST_lamp;lt;lamp;nbsp;listener_namelamp;gt; in LISTENER.ORA has an error in it.
Action: Be sure this parameter is specified as described in the Oracle9i Net Services Reference Guide. For example, SID_LIST_LISTENER = (SID_LIST=(SID_ DESC=(SID_NAME=lamp;lt;lamp;nbsp;sidlamp;gt;)(ORACLE_HOME=lamp;lt;lamp;nbsp;oracle_homelamp;gt;)))
TNS-01154: SID detected in old format that is no longer supported
TNS-01154: SID detected in old format that is no longer supported
Cause: One of the SIDs was specified in an obsolete format.
Action: Check LISTENER.ORA for a line of the form: lamp;lt;lamp;nbsp;sidlamp;gt; = (SID=(ORACLE_ HOME=lamp;lt;lamp;nbsp;oracle_homelamp;gt;)) OR lamp;lt;lamp;nbsp;sidlamp;gt; = (SID_DESC=(ORACLE_HOME=lamp;lt;lamp;nbsp;oracle_ homelamp;gt;)) The above format is no longer supported and SID_LIST_lamp;lt;lamp;nbsp;listener_namelamp;gt; format described in the Oracle9i Net Services Reference Guide should be used. For example, SID_LIST_LISTENER = (SID_LIST=(SID_DESC=(SID_ NAME=lamp;lt;lamp;nbsp;sidlamp;gt;)(ORACLE_HOME=lamp;lt;lamp;nbsp;oracle_homelamp;gt;)))
Cause: One of the SIDs was specified in an obsolete format.
Action: Check LISTENER.ORA for a line of the form: lamp;lt;lamp;nbsp;sidlamp;gt; = (SID=(ORACLE_ HOME=lamp;lt;lamp;nbsp;oracle_homelamp;gt;)) OR lamp;lt;lamp;nbsp;sidlamp;gt; = (SID_DESC=(ORACLE_HOME=lamp;lt;lamp;nbsp;oracle_ homelamp;gt;)) The above format is no longer supported and SID_LIST_lamp;lt;lamp;nbsp;listener_namelamp;gt; format described in the Oracle9i Net Services Reference Guide should be used. For example, SID_LIST_LISTENER = (SID_LIST=(SID_DESC=(SID_ NAME=lamp;lt;lamp;nbsp;sidlamp;gt;)(ORACLE_HOME=lamp;lt;lamp;nbsp;oracle_homelamp;gt;)))
TNS-01153: Failed to process string: string
TNS-01153: Failed to process string: string
Cause: The string specified is not well-formed.
Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.
Cause: The string specified is not well-formed.
Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-01152: All addresses specified for the listener name, string, failed
TNS-01152: All addresses specified for the listener name, string, failed
Cause: The listener failed to listen on any of the specified addresses.
Action: Make sure that another application is not listening on the addresses specified or check that the appropriate protocol adapters are installed. Turn on tracing and execute again for more information.
Cause: The listener failed to listen on any of the specified addresses.
Action: Make sure that another application is not listening on the addresses specified or check that the appropriate protocol adapters are installed. Turn on tracing and execute again for more information.
Subscribe to:
Posts (Atom)