Oracle Network Products Troubleshooting Guide

Contents Index Home Previous Next

Listener Error Messages (TNS-01000 to 02500)

TNS-1064 Listener configuration changes will not be persistent

Cause:Configuration changes to the listener will not be visible when the listener starts up again as the check-pointing has been turned off in listener.ora
Action:Edit LISTENER.ORA setting USE_CKPFILE_LISTENER=true
TNS-01100 TNS returned error num when attempting to start the listener

Cause:The bequeath (BEQ) mechanism that LSNRCTL uses to start the listener failed.
Action:Check to ensure that the BEQ driver is installed - if it is not then the nserror code returned will be 12538 (NSENODRIVER). To fix this, reinstall SQL*Net V2 and make sure that the BEQ driver is selected when it is installed. If this is not the problem then the error is probably caused by the fact that the TNSLSNR executable cannot be found in the place expected in your platform's ORACLE environment. Verify that the full pathname of the TNSLSNR executable as displayed by LSNRCTL is correct.
TNS-01101 Could not find service name string

Cause:The service name could not be resolved by name-lookup.
Action:Verify that the listener name or service name specified to LSNRCTL has the correct name and address defined in LISTENER.ORA or in TNSNAMES.ORA.
TNS-01102 TNS application contacted was not the listener

Cause:Another TNS application such as the Interchange was listening at the address contacted. There may be another TNS application listening at the address contacted and the data returned is not in the appropriate format.
Action:Verify that the listener name or service name specified to LSNRCTL has the correct name and address defined in LISTENER.ORA or in TNSNAMES.ORA.
TNS-01103 Protocol specific component of the address is incorrectly specified

Cause:The ADDRESS used to contact the listener is not correctly specified. This error occurs because the address fails to specify the destination of the listener. The address is well-formed (for example, there are no missing parentheses) but it is missing a protocol specific component. For example, this is the error returned when the HOST component is missing from a TCP/IP address string.
Action:Edit the ADDRESS in LISTENER.ORA to include the required protocol-specific keywords. For more information about the keywords required by different protocol adapters, see the Oracle operating system specific documentation for your platform.
TNS-01106 Listener using listener_name listener_name has already been started

Cause:Another listener is already listening on one of the ADDRESSes specified.
Action:Shutdown the previous listener specified by the listener_name before starting this one.
TNS-01107 A valid trace level was not specified

Cause:Failed to specify a valid trace level for the LSNRCTL trace command.
Action:Specify one of OFF, USER, or ADMIN. Type "lsnrctl help trace" for more information or consult Chapter 2 of this manual for an introduction to the concepts of tracing.
TNS-01108 Listener password prompt failed

Cause:Password not entered via tty.
Action:Enter the listener password on a tty device.
TNS-01109 Listener password encryption failed

Cause:Possibly garbled password entered.
Action:Re-enter the listener password, using valid ASCII characters. If problem persists, contact Worldwide Customer Support.
TNS-01110 Mismatch - password unchanged

Cause:New password and reentered new password are different
Action:Re-enter the listener password, make sure that New password and reentered new password are the same
TNS-01111 Log status can either be ON or OFF

Cause:Failed to specify a log status value for the LSNRCTL log_status command.
Action:Specify one of ON or OFF. Type "LSNRCTL help set log_status" for more information or consult Chapter 2 of this manual for an introduction to the concepts of logging.
TNS-01150 The address of the specified listener name is incorrect

Cause:The address on which the listener attempted to listen contains a syntax error.
Action:For the listener name or service name specified to LSNRCTL, check that the address or connect descriptor is well-formed. You can find the listener name in LISTENER.ORA, or you can access the listener through the service name in TNSNAMES.ORA.
TNS-01151 Missing listener name listener_name in LISTENER.ORA

Cause:The listener could not find the listener name specified.
Action:Make sure that valid addresses on which to listen are specified for the listener name in LISTENER.ORA.
TNS-01152 All addresses specified for the listener name listener_name 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.
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:

TNS-01155 Incorrectly specified SID_LIST_listener_name parameter in LISTENER.ORA

Cause:SID_LIST_listener_name in LISTENER.ORA contains an error.
Action:Be sure this parameter is specified as described in the SQL*Net Administrator's Guide. For example, (SID_LIST_LISTENER = (SID_DESC=(SID_NAME=sid) (ORACLE_HOME=oracle_home))).
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:

TNS-01157 Can only listen on num addresses - ignoring 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-01158 Internal connection limit has been reached, preventing dispatcher from connecting

Cause:The internal SQL*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 Worldwide Customer Support.
TNS-01159 Internal connection limit has been reached; listener has shut down

Cause:The internal SQL*Net connection list is full. The listener is configured to use too many SQL*Net connections.
Action:Reduce the number of listen addresses or services connected to the listener. For further details, turn on tracing and reexecute to operation. If error persists, contact Worldwide Customer Support.
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.
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.
TNS-01169 The listener did not recognize the password

Cause:The security feature of the listener is preventing the intended operation.
Action:Some commands like stopping the listener are only intended to be used by DBAs. A client can only use LSNRCTL to get the status of a listener and the version of the listener software running. The command that the client attempted may not have been appropriate. If a DBA is attempting the command then use the "set password" command at the LSNRCTL prompt to one of the appropriate passwords in the PASSWORDS_listener_name entry in LISTENER.ORA. If you do not know a password then you are trying to execute an inappropriate command.
TNS-01170 Event detection broke for address: addrress

Cause:he 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 Worldwide Customer Support.
TNS-01171 Event detection broke for dispatcher: dispatcher

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 Worldwide Customer Support.
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 Worldwide Customer Support.
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:

TNS-1174 The sum of the POOL_SIZEsfrom each PRESPAWN_DESC is greater than the PRESPAWN_MAX

Cause:The minimum value for PRESPAWN_MAX should be the sum of the POOL_SIZEs in each SID_DESC. For example:

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.
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 parameters.
TNS-01177 Log Status is OFF. Log file/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.
TNS-01178 Trace Level is 0. Trace file/directory unchanged

Cause:Trace Levelneeds to be set for changing the trace file/directory.
Action:Use command set trc_level ON to set the trace level.
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.

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.

TNS-01202 Missing the dba group (string) specified by DBA_GROUP in SID_DESC

Cause:The dba group specified is missing from /ETC/GROUP.
Action:Check the DBA_GROUP parameter in the SID_DESC in LISTENER.ORA and verify it has a valid entry in /ETC/GROUP.

TNS-01203 Missing the account string specified by DEFAULT_USER_ACCOUNT in SID_DESC

Cause:The unprivileged OS account is missing from /ETC/PASSWD.
Action:Check the DEFAULT_USER_ACCOUNT parameter in the SID_DESC in LISTENER.ORA and verify it has a valid entry in /ETC/PASSWD. This is the account that the ORACLE shadow process will be started with if the connecting client has database privileges or does not exist on this machine.

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

Contents Index Home Previous Next