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.
Category Archives: TNS Database Error Messages
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.
TNS-01110: Mismatch – password unchanged
TNS-01110: Mismatch - password unchanged
Cause: New password and re-entered new password are different.
Action: Re-enter the listener password, make sure that New password and re-entered 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 Support Services.
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.
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: Shut down 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/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.