Release 8.0.4
A58312-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8 Error Messages Release 8.0.4 A58312-01 |
|
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 LISTERNER.ORA
Action: Edit LISTENER.ORA setting USE_CKPFILE_LISTENER=true
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.
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.
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.
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.
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.
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.
Cause: Password not entered via tty
Action: Enter the listener password on a tty device
Cause: Possibly garbled password entered
Action: Re-enter the listener password, using valid ASCII characters. If problem persists, contact Worldwide Customer Support.
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
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.
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.
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.
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.
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.
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 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 Worldwide Customer Support. *Comment: Do not include in error manual.
Cause: One of the SIDs was specified in an obsolete format.
Action: Check LISTENER.ORA for a line of the form: <sid> = (SID=(ORACLE_HOME=<oracle_home>)) OR <sid> = (SID_DESC=(ORACLE_HOME=<oracle_home>)) The above format is no longer supported and SID_LIST_<listener_name> format described in the SQL*Net Administrator's Guide should be used. For example, SID_LIST_LISTENER = (SID_LIST=(SID_DESC=(SID_NAME=<sid>)(ORACLE_HOME=<oracle_home>)))
Cause: SID_LIST_<listener_name> in LISTENER.ORA has an error in it.
Action: Be sure this parameter is specified as described in the SQL*Net Administrator's Guide. For example, SID_LIST_LISTENER = (SID_LIST=(SID_DESC=(SID_NAME=<sid>)(ORACLE_HOME=<oracle_home>)))
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=<sid>)(PRESPAWN_MAX=5)(ORACLE_HOME=<oracle_home>)(PRESPAWN_DESC=(PROTOCOL=tcp)(POOL_SIZE=10)(TIMEOUT=30)))) Use the Oracle Network Manager to add or correct these parameters in the LISTENER.ORA file
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: 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.
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 the operation. If error persists, contact Worldwide Customer Support.
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: 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: The security feature of the listener is preventing the intended operation.
Action: Some commands like stopping the listener are only intended to be done 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 with 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.
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 de-allocate 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.
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 de-allocate 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.
Cause: The event detection mechanism broke and caused all listen addresses to be removed.
Action: Error 1170 has occurred and caused all the listen addresses to be de-allocated. 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.
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=<sid>)(PRESPAWN_MAX=15)(ORACLE_HOME=<oracle_home>)(PRESPAWN_DESC=(PROTOCOL=tcp)(POOL_SIZE=10)(TIMEOUT=30)))) Use the Oracle Network Manager to 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=<sid>)(PRESPAWN_MAX=15)(ORACLE_HOME=<oracle_home>)(PRESPAWN_DESC=(PROTOCOL=tcp)(POOL_SIZE=10)(TIMEOUT=30))(PRESPAWN_DESC=(PROTOCOL=ipc)(POOL_SIZE=5)(TIMEOUT=15)))) Use the Oracle Network Manager to add or correct these parameters in the LISTENER.ORA file
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: 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
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: Trace Levelneeds to be set for changing the trace file/directory
Action: use command set trc_level ON to set the trace level
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. *Comment: This error is reported only on Trusted Oracle platforms.
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. *Comment: This error is reported only on UNIX platforms.
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. *Comment: This error is reported only on UNIX platforms.
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. *Comment: This error is reported only on UNIX platforms.
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. *Comment: This error is only reported on UNIX platforms.
