Oracle Error Messages: 11/22/11

TNS-01151: Missing listener name, string, in LISTENER.ORA

TNS-01151: Missing listener name, string, in LISTENER.ORA

Cause: The listener could not find the listener name specified.

Action: Make sure valid addresses on which to listen are specified for the listener name in LISTENER.ORA.

TNS-01150: The address of the specified listener name is incorrect

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

TNS-01116: Listener alias name given as connect identifier is too long

TNS-01116: Listener alias name given as connect identifier is too long

Cause: The listener alias name you were attempting to resolve was too long.

Action: The maximum length of a listener alias name is 255 bytes; this limit has been exceeded. Use a smaller listener alias name.

TNS-01115: OS error string creating shared memory segment of string bytes with key string

TNS-01115: OS error string creating shared memory segment of string bytes with key string

Cause: The shared memory segment could not be created as requested. For example, a segment with the provided key may already exist, or the size may be outside of system allowed range.

Action: Use the error code to determine the exact cause of the problem. In certain cases the problem may be resolved by adjusting the system-imposed limits such as the maximum number of allowed shared memory segments, or their maximum and minimum sizes. In other cases, resources need to be freed up first for the operation to succeed.

TNS-01114: LSNRCTL could not perform local OS authentication with the listener

TNS-01114: LSNRCTL could not perform local OS authentication with the listener

Cause: LSNRCTL failed to obtain system resources (heap memory, or shared memory) needed to perform local OS authentication with the listener.

Action: Make sure that system resources like shared memory and heap memory are available for LSNRCTL tool to execute properly.

TNS-01113: save_config_on_stop can either be ON or OFF

TNS-01113: save_config_on_stop can either be ON or OFF

Cause: Failed to specify a valid value for the LSNRCTL save_config_on_stop command.

Action: Specify one of ON or OFF. Type LSNRCTL help set save_config_on_stop for more information.

TNS-01112: Plug and play can either be ON or OFF

TNS-01112: Plug and play can either be ON or OFF

Cause: Failed to specify a valid value for the LSNRCTL use_plugandplay command.

Action: Specify one of ON or OFF. Type LSNRCTL help set use_plugandplay for more information.

TNS-01111: Log status can either be ON or OFF

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-01110: Mismatch - password unchanged

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-01109: Listener password encryption failed

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 Oracle Customer Support.

TNS-01108: Listener password prompt failed

TNS-01108: Listener password prompt failed

Cause: Password not entered via tty

Action: Enter the listener password on a tty device

TNS-01107: A valid trace level was not specified

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, ADMIN, or SUPPORT. Type LSNRCTL help trace for more information or consult Chapter 2 of this manual for an introduction to the concepts of tracing.

TNS-01106: Listener using listener name string has already been started

TNS-01106: Listener using listener name string 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-01103: Protocol specific component of the address is incorrectly specified

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 or 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-01102: TNS application contacted was not the listener

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-01101: Could not find service name string

TNS-01101: Could not find service name string

Cause: The ervice 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-01100: TNS returned error number when attempting to start the listener

TNS-01100: TNS returned error number when attempting to start the listener

Cause: d 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.

Action: If NS error code 12538 is also returned then the BEQ driver is not installed; call Oracle Worldwide Support as the BEQ driver should always be installed. If this is not the problem then the error is probably

TNS-01099: %s * string * string * string * number

TNS-01099: %s * string * string * string * number

Cause: Listener logging message.

Action: None.

TNS-01098: TIMESTAMP * CONNECT DATA * ADDRESS * (PRESENTATION ( COMMAND ERROR TIMESTAMP * (INSTANCE NAME ( (ADDRESS ( (PRESENTATION ( COMMAND ERROR

TNS-01098: TIMESTAMP * CONNECT DATA * ADDRESS * (PRESENTATION *( COMMAND * ERROR TIMESTAMP * (INSTANCE NAME *( (ADDRESS *( (PRESENTATION *( COMMAND * ERROR

Cause: Listener logging message.

Action: None.

TNS-01097: TIMESTAMP * CONNECT DATA (* PROTOCOL INFO( * EVENT (* SID( * RETURN CODE

TNS-01097: TIMESTAMP * CONNECT DATA (* PROTOCOL INFO( * EVENT (* SID( * RETURN CODE

Cause: Listener logging message.

Action: None.

TNS-01096: %s * string * string * string * string * number

TNS-01096: %s * string * string * string * string * number

Cause: Listener logging message.

Action: None.

TNS-01095: %s * string * string * number

TNS-01095: %s * string * string * number

Cause: Listener logging message.

Action: None.

TNS-01094: %s * number

TNS-01094: %s * number

Cause: Listener logging message.

Action: None.

TNS-01093: %s * string * number

TNS-01093: %s * string * number

Cause: Listener logging message.

Action: None.

TNS-01090: No longer listening on: string

TNS-01090: No longer listening on: string

Cause: Listener logging message.

Action: None.

TNS-01082: Running in PROXY mode

TNS-01082: Running in PROXY mode

Cause: Listener starting message.

Action: None.

TNS-01081: Started with pid=string

TNS-01081: Started with pid=string

Cause: Listener starting message.

Action: None.

TNS-01080: Listener failed to start. See the error message(s) above...

TNS-01080: Listener failed to start. See the error message(s) above...

Cause: Listener starting message.

Action: None.

TNS-01079: Attempted to bequeath: string

TNS-01079: Attempted to bequeath: string

Cause: Listener starting message.

Action: None.

TNS-01078: Opened name lookup file: string

TNS-01078: Opened name lookup file: string

Cause: Listener starting message.

Action: None.

TNS-01077: Opened parameter file: string

TNS-01077: Opened parameter file: string

Cause: Listener starting message.

Action: None.

TNS-01076: Opened trace file: string

TNS-01076: Opened trace file: string

Cause: Listener starting message.

Action: None.

TNS-01075: Opened log file: string

TNS-01075: Opened log file: string

Cause: Listener starting message.

Action: None.

TNS-01074: Error listening on: string

TNS-01074: Error listening on: string

Cause: Listener starting message.

Action: None.

TNS-01073: Listening on: string

TNS-01073: Listening on: string

Cause: Listener starting message.

Action: None.

TNS-01072: Started at string

TNS-01072: Started at string

Cause: Listener starting message.

Action: None.

TNS-01071: %s is set to string

TNS-01071: %s is set to string

Cause: Listener starting message.

Action: None.

TNS-01070: Starting string: please wait...

TNS-01070: Starting string: please wait...

Cause: Listener starting message.

Action: None.

TNS-01067: Service display mode is string

TNS-01067: Service display mode is string

Cause: Control program general message.

Action: None.

TNS-01066: Presentation: string

TNS-01066: Presentation: string

Cause: Listener starting message.

Action: None.

TNS-01065: Raw mode is string

TNS-01065: Raw mode is string

Cause: Control program general message.

Action: None.

TNS-01064: Listener configuration changes will not be persistent

TNS-01064: 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