출처 http://docs.oracle.com/cd/B19306_01/server.102/b14219/tnsus.htm#TNS-12535
오라클 리스너 관련 에러 간략한 설명들
43 TNS-00000 to TNS-12699
- TNS-00002: INTCTL: error while starting the Interchange
- Cause: of the problem. Be sure to turn tracing off when the problem has been rectified.
- Action: Check the Interchange configuration files (INTCHG.ORA, TNSNET.ORA and TNSNAV.ORA) for errors and confirm that no other programs are using the ADDRESS(es) specified. If error continues, turn on tracing in the Interchange components and examine the trace files to determine the
- TNS-00003: INTCTL: error while sending request to the Interchange
- Cause: Improper command sent to the Interchange or the Interchange is not responding. Not normally visible to the user.
- Action: Verify that the command sent to the Interchange is valid. Also check that the Interchange is running by using the INTCTL STATUS command. If necessary, start the Interchange using the INTCTL START command.
- TNS-00004: INTCTL: error while starting the Navigator
- Cause: The Navigator could not be started.
- Action: Check to make sure that executables for the Navigator (navgatr) are present in the ORACLE executable directory on your platform. Check the configuration files TNSNET.ORA and TNSNAV.ORA for errors. If error continues, turn on tracing in the Interchange components and examine the trace files to determine the cause of the problem. Be sure to turn tracing off when the problem has been rectified.
- TNS-00005: INTCTL: error while sending request to the Navigator
- Cause: The Navigator is not responding. Either the Navigator is not running or another process is responding.
- Action: Check that the Navigator is running by using the STATUS command of the Interchange Control Utility. Verify that the correct addresses are listed in the TNSNAMES.ORA, TNSNET.ORA, and TNSNAV.ORA configuration files.
- TNS-00008: INTCTL: could not contact destination Navigator
- Cause: Connection could not be properly established to a Navigator. This may be because the Navigator specified is not running or the Navigator addresses are incorrect.
- Action: Check that the Navigator is running by using the STATUS command of the Interchange Control Utility; if necessary, start the Navigator using the START command of the Interchange Control Utility. If it is running and the error persists, contact Oracle Customer Support.
- TNS-00009: INTCTL: could not contact destination Connection Manager
- Cause: Connection could not be properly established to a Connection Manager. This may be because the Connection Manager (Interchange) specified is not running or the Connection Manager addresses are incorrect.
- Action: Make sure the Connection Manager is running by using the STATUS command of the Interchange Control Utility; if necessary, start the Connection Manager using the START command of the Interchange Control Utility. If it is running and the error persists, contact Oracle Customer Support.
- TNS-00011: INTCTL: error while starting the Connection Manager
- Cause: The Connection Manager could not be started.
- Action: Assure that the executable can be found in the standard Oracle executable area. Check the configuration file INTCHG.ORA for errors and confirm that no other process is using the ADDRESS(es) for this Connection Manager as specified in TNSNET.ORA. Tracing can also be turned on in the Connection Manager and detailed information about the reason for the error determined. Consult the MultiProtocol Interchange Administrator"s Guide and Chapter 2 of this manual for how to turn on tracing.
- TNS-00012: INTCTL: error while processing Connection Manager request
- Cause: An improper command was sent to the Connection Manager or it is not responding. Not normally visible to the user.
- Action: Verify that the correct addresses are listed in the TNSNAMES.ORA, TNSNET.ORA, and TNSNAV.ORA configuration files. Also check that the Connection Manager is running by using the STATUS command of the Interchange Control Utility. If the error persists, contact Oracle Customer Support.
- TNS-00024: INTCTL: Unable to contact Navigator to obtain Connection Manager address
- Cause: The Navigator is not running.
- Action: Verify that the Navigator is running by doing a status request on the Navigator (use the Interchange Control Utility command STATUS). If necessaary, start the Navigator using the Interchange Control Utility. Verify that the network is properly configured; if the error persists, contact Worldwide Customer Support.
- TNS-00025: INTCTL: The ORACLE environment is not set up correctly
- Cause: The ORACLE environment is incorrectly set up.
- Action: Refer to the Oracle operating system specific documentation for your platform for information on how the ORACLE environment should be set. Correct it and rerun INTCTL. Make sure the ORACLE environment includes the correct directories.
- TNS-00026: INTCTL: TNS_ADMIN directory set, and is being used
- Cause: The TNS_ADMIN environment variable is set properly. INTCTL will use the TNS_ADMIN directory. This is only an informative message. If you do not want it to be used, and want the default directory to be used instead, then unset TNS_ADMIN and reexecute.
- Action: None.
- TNS-00028: INTCTL: Could not resolve Connection Manager"s name/address
- Cause: The Connection Manager"s name does not have a definition that the Navigator knows about, nor is the name/address available in the TNSNAMES.ORA file. The name may also be incorrect in the INTCHG.ORA file.
- Action: Verify that the Connection Manager"s name is in the TNSNET.ORA file read by the Navigator or in the TNSNAMES.ORA file. Be sure that INTCHG.ORA is correct.
- TNS-00035: INTCTL: error while constructing full file name
- Cause: Problem while constructing the full path for a file name because the path name to the file or the environment variables are incorrect. Files looked up include TNSNAMES.ORA, TNSNAV.ORA, INTCHG.ORA and the error files for the Navigator and Connection Manager.
- Action: Check that all environment variables are defined correctly and that all configuration files exist in their correct places.
- TNS-00036: INTCTL: error reading from Navigator or Connection Manager error files
- Cause: Problem while reading from Navigator or Connection Manager error files generated by the Navigator or Connection Manager when they fail to start.
- Action: Check that a standard Network Error directory exists and that all privileges on the directory are appropriate.
- TNS-00038: INTCTL: Poorly formed address or command string
- Cause: An unacceptable string was encountered while attempting to send a message to either the Navigator or Connection Manager. The addresses provided for either the Navigator or Connection Manager may be incorrectly constructed.
- Action: Check all address strings in configuration files (TNSNAMES.ORA, TNSNAV.ORA or TNSNET.ORA) and assure that they are properly formed. Regenerate the files, if possible. If all is correct, please contact Worldwide Customer Support.
- TNS-00039: INTCTL: error while spawning a process
- Cause: An error was encountered while spawning a process due to an internal operating system dependent problem. Machine resources may be limited.
- Action: Retry command. Check permissions on Interchange executables and the current setting of the search path. If necessary, terminate other applications to free up machine resources. If the error persists, contact Oracle Customer Support.
- TNS-00040: INTCTL: failed to initialize trace context- Continuing anyway
- Cause: Problem while opening specified trace file because of errors in INTCHG.ORA or because the user has incorrect privileges, or the file does not exist.
- Action: Check the privileges on the configuration files and ensure that all of them exist in their proper locations.
- TNS-00043: The CMANAGER has active connections, do you still want to stop it (y/n)?
- Cause: The CMANAGER that is being stopped has active connections going through. This is the confirmation message.
- Action: Respond by pressing y or n. Answering y will cause the active database connection to be dropped; this is not generally recommended.
- TNS-00044: INTCTL: You must have an INTCHG.ORA file to contact the Connection Manager
- Cause: There was an attempt to contact a default Connection Manager (Interchange) where there was no INTCHG.ORA present in the correct directory.
- Action: Create an INTCHG.ORA file. Make sure it is placed in the correct directory and includes the correct name for the Connection Manager you wish to contact.
- TNS-00046: INTCTL: Could not contact the CMANAGER on address
- Cause: There was an attempt to contact a CMANAGER on a specific address which is not responding.
- Action: Verify that the TNSNET.ORA file contains that address. Also check that the CMANAGER is actually listening on that address by using the INTCTL STATUS command. If necessary, start the Connection Manager using the INTCTL START command.
- TNS-00060: INTCTL: Bad command: only the STATUS command can be used on remote Interchanges
- Cause: The user entered a command that does not exist, or the user tried to make a request other than STATUS to a remote Interchange.
- Action: Check the MultiProtocol Interchange Administrator"s Guide for a list of INTCTL commands or type HELP for a list of valid commands.
- TNS-00063: INTCTL: Failed to allocate memory for buffers
- Cause: INTCTL was unable to allocate memory for internal buffers.
- Action: Check the amount of available memory on your machine to ensure that there is enough memory to run this executable. If necessary, free up memory by running fewer programs, then try again.
- TNS-00103: Parameter file load error
- Cause: Parameter file process failed.
- Action: Check to make sure that all parameter files necessary for the Interchange are present (TNSNAV.ORA, TNSNET.ORA and INTCHG.ORA). If these files are present and properly configured, turn on tracing and repeat the operation. Turn off tracing when the trace is complete. Look in the trace file for errors in the parameter loading process. If error persists contact Oracle Customer Support.
- TNS-00113: Failed to open error log file
- Cause: Could not open log file during startup of Navigator or Connection Manager due to read or write permission problems or non-existent error directory.
- Action: Create the standard error directory or assure that if one is present the Interchange executables can write to it.
- TNS-00116: Pump failed during initial bequeath
- Cause: d by insufficient machine resources.
- Action: Attempt the connection again. The pump should recover from such a failure. If machine resources appear to be the problem, add more resources // or shut down some active applications. If problem persists, contact Oracle Customer Support.
- TNS-00123: Unable to perform a listen on configured ADDRESS(es)
- Cause: Another process is already listening on this address or the ADDRESS is incorrectly defined.
- Action: Check the ADDRESS(es) defined in TNSNET.ORA (for the Connection Manager) for errors. Verify that another program is not using them.
- TNS-00129: Internal error - Failed to create new community
- Cause: Internal Error. Should not normally occur. There may be a resource limitation problem on the machine.
- Action: Stop and restart Interchange. If possible, make more memory available on the machine. If problem persists, contact Oracle Customer Support.
- TNS-00142: Community mismatch in TNSNAV.ORA
- Cause: The communities in the LOCAL_COMMUNITIES entry in TNSNAV.ORA do not correspond with all the communities in the NAVIGATOR_ADDRESSES entry.
- Action: Assure that all communities in the NAVIGATOR_ADDRESSES correspond to those in the LOCAL_COMMUNITIES component.
- TNS-00143: Illegal PREFERRED_CMANAGERS entry in TNSNAV.ORA
- Cause: PREFERRED_CMANAGERS entry in the TNSNAV.ORA used by the Connection Manager. There should only be a PREFERRED_NAVIGATORS entry in the TNSNAV.ORA on an Interchange.
- Action: Remove the PREFERRED_CMANAGERS entry from TNSNAV.ORA and assure that either no PREFERRED_NAVIGATORS entry is present or that it is correct.
- TNS-00201: Unable to read answer connection data :string:
- Cause: Improperly formed connect data sent to the Interchange listener.
- Action: If problem persists, check the application using the Interchange (it may be closing down or crashing). Call Oracle Customer Support if the problem cannot be located.
- TNS-00202: Failure in redirecting call : Original to string Redirect to string
- Cause: Internal - error could not redirect call to a pump or other Interchange listener. The cause may be insufficient network or machine resources.
- Action: Add resources or close some running applications in order to free up resources. If error persists, call Oracle Customer Support.
- TNS-00227: Unable to contact pump; Connection Manager declared pump dead
- Cause: A pump became an orphaned process. A protocol adapter is not working properly or machine network resources are being over used.
- Action: This error is not immediately fatal; the orphaned pump may continue to function. Restart the Interchange when convenient. If the problem persists, call Oracle Customer Support.
- TNS-00230: Cannot start new pump process: string string Protocol Adapter errors:number
- Cause: Unable to create a new process; possibly there are too many processes on the machine.
- Action: Free machine resources by exiting other applications on the Interchange machine. If the problem continues you may need more memory on the machine. If you believe there are sufficient resources on the machine but the problem persists, contact Oracle Customer Support.
- TNS-00316: Ran out of data buffers in the pump
- Cause: The Interchange is resource limited by having too few data buffers in the pump.
- Action: If the problem persists (that is, there are a lot of log messages), increase the number of pump buffers by increasing the value of the parameter PUMP_BUFFERS in INTCHG.ORA. Then shutdown and restart the Interchange to make the changes take effect.
- TNS-00503: Illegal ADDRESS parameters
- Cause: An illegal set of protocol adapter parameters was specified.
- Action: Check the parameters within the ADDRESS section of the TNSNAMES.ORA file. It may be helpful to turn on tracing and look at the addresses specified in the trace file, checking for spelling or other errors. Be sure to turn tracing off when the trace is complete.
- TNS-00504: Operation not supported
- Cause: An internal function received a request to perform an operation that is not supported (on this machine).
- 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-00511: No listener
- Cause: The connect request could not be completed because no application is listening on the address specified, or the application is unable to service the connect request in a sufficiently timely manner.
- Action: Ensure that the supplied destination address matches one of the addresses used by the listener - compare the TNSNAMES.ORA entry with appropriate LISTENER.ORA file (or TNSNAV.ORA if the connection is to go by way of an Interchange. Start the listener on the remote machine.
- TNS-00515: Connect failed because target host or object does not exist
- Cause: The address specified is not valid, or the program being connected to does not exist.
- Action: Ensure the ADDRESS parameters have been entered correctly; the most likely incorrect parameter is the node name. Ensure that the executable for the server exists (perhaps "oracle" is missing.)
- TNS-00527: Protocol Adapter not loadable
- Cause: On some platforms (for example OS/2) protocol adapters are loaded at run-time. If the shared library (or DLL) for the protocol adapter is missing or one of its supporting libraries is missing, then this error is returned.
- Action: For further details, turn on tracing and reexecute the operation. The trace file will have the name of the shared library (or DLL) that could not be loaded.
- TNS-00528: Protocol Adapter not loaded
- Cause: On some platforms (for example OS/2) protocol adapters are loaded at run-time. If the shared library (or DLL) for the protocol adapter has not been loaded, then this error is returned.
- Action: For further details, turn on tracing and reexecute the operation. The trace file will have the name of the shared library (or DLL) that has not been loaded.
- TNS-00542: SSL Handshake failed
- Cause: The SSL protocol adapter was unable to connect to another process.
- Action: This error can be caused by a variety of problems including the termination of the peer process. Enable Oracle Net tracing and attempt the connection again. The trace file should give some clues as to what the exact problem is.
- TNS-00560: extraction of name from Entrust certificate failed
- Cause: An error occurred while attempting to extract a name from an Entrust certificate.
- Action: This error is not normally visible to users. Enable Oracle Net tracing and attempt to reproduce the error. If it occurs, contact Oracle customer support.
- TNS-00580: Read failed due to closed or invalid transport connection
- Cause: Read attempt was made on a transport connection which was previously terminated or is somehow deemed to be invalid.
- Action: Indicates a substantial transport level failure. Check the O/S configuration for the particular transport or contact the transport provider. For further details, turn on tracing and reexecute the operation.
- TNS-00581: Send failed due to timeout
- Cause: The send operation did not complete within the allowed time interval.
- Action: Error is informational. Note, repeated receipt of this error could indicate an attempted Denial-Of-Service attack. Also, if the receipt of this error interferes w/ a customer"s normal operations, the customer may wish to lengthen the timeout.
- TNS-00582: Receive failed due to timeout
- Cause: The receive operation did not complete within the allowed time interval.
- Action: Error is informational. Note, repeated receipt of this error could indicate an attempted Denial-Of-Service attack. Also, if the receipt of this error interferes w/ a customer"s normal operations, the customer may wish to lengthen the timeout.
- TNS-00583: Valid node checking: unable to parse configuration parameters
- Cause: Valid node checking was unable to parse the configuration due to syntactical errors.
- Action: Ensure that the configuration syntax matches the Oracle reference manual documented syntax. For further details, turn on tracing and reexecute the operation.
- 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-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-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-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-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-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-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.
- 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: <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 Oracle9i Net Services Reference Guide should be used. For example, SID_LIST_LISTENER = (SID_LIST=(SID_DESC=(SID_NAME=<sid>)(ORACLE_HOME=<oracle_home>)))
- TNS-01155: Incorrectly specified SID_LIST_string parameter in LISTENER.ORA
- Cause: SID_LIST_<listener_name> 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=<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, 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)))) Add or correct these parameters in the LISTENER.ORA file
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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=<sid>)(PRESPAWN_MAX=15)(ORACLE_HOME=<oracle_home>)(PRESPAWN_DESC=(PROTOCOL=tcp)(POOL_SIZE=10)(TIMEOUT=30)))) Add or correct these parameters in the LISTENER.ORA file
- 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=<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)))) Add or correct these parameters in the LISTENER.ORA file
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- TNS-01187: No proxy service handler available
- Cause: One of the following conditions has occurred:
- the proxy service was not registered
- the proxy service was registered, but was blocking new connections
- all of the registered proxy service handlers were blocking new connections
- 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-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.
- 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.
- 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.
- 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.
- 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_<listener_name> on the left side of the equation. For example, SID_LIST_LISTENER =(SID_LIST=(SID_DESC=(SID_NAME=<sid>)(ORACLE_HOME=<oracle_home>)))
- 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-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 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 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-02502: Authentication: unable to find initialization function
- Cause: The native authentication service was unable to call the initialization function for the specified service because it does not exist.
- Action: If this service adaptor came directly from Oracle, contact Oracle Customer Support, as this error should never happen. Otherwise, add an initialization function for the service being used.
- TNS-02507: Encryption: algorithm not installed
- Cause: After picking an algorithm, the server was unable to find an index for it in its table of algorithms. This should be impossible because the algorithm was chosen (indirectly) from that list.
- 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-02513: Requested data type does not match retrieved type
- Cause: A service requested data whose type does not match that of the segment which was sent from the other process.
- Action: If it is possible, enable tracing and attempt to reproduce the problem. In any event, contact Oracle Customer Support.
- TNS-02515: Encryption/crypto-checksumming: unknown control type
- Cause: An encryption or crypto-checksumming algorithm "control" function was called, but did not recognize the "type" argument it was given.
- 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-02516: No data available
- Cause: A native service attempted to retrieve data but no data was available to be received.
- Action: The error is not normally visible as it usually is only used to signal the end of a data stream. If the error becomes visible, enable tracing to reproduce the problem and contact Oracle Customer Support.
- TNS-02517: key smaller than requested size
- Cause: The key returned by negotiation was smaller than the size requested by some service (either encryption or crypto-checksumming).
- Action: The error is not normally visible. If the error persists, enable tracing to reproduce the problem and contact Oracle Customer Support.
- TNS-02519: no appropriate key-negotiation parameters
- Cause: No appopriate key-negotiation parameters are available for the key size requested either by encryption or by crypto- checksumming.
- Action: The error is not normally visible. Enable tracing to reproduce the problem and contact Oracle Customer Support.
- TNS-02524: Authentication: privilege check failed
- Cause: An error occurred when the Oracle Advanced Security authentication service attempted to verify that a user had a specific database privilege.
- Action: This error should not happen normally. Enable tracing and attempt to repeat the error. Contact Customer Support.
- TNS-03503: Could not initialize NL
- Cause: The network library could not be initialized.
- Action: This is an internal error which should not normally be visible. Ensure that memory is available to run the application and that there are no other operating system problems, and then attempt the command again.
- TNS-03505: Failed to resolve name
- Cause: The service name you provided could not be found in TNSNAMES.ORA, an Oracle Names server, or a native naming service.
- Action: Verify that you entered the service name correctly. You may need to ensure that the name was entered correctly into the network configuration.
- TNS-03506: Failed to create address binding
- Cause: The TNSPING utility found the requested address or service name, but received an internal error when trying to use it.
- Action: This is an internal error which should not normally be visible. Ensure that memory is available to run the application and that there are no other operating system problems, and then attempt the command again.
- TNS-03507: Failure looking for ADDRESS keyword
- Cause: The TNS address did not contain an ADDRESS keyword.
- Action: If you entered the TNS address on the command line, be sure that the syntax is correct. If you entered a service name on the command line, the address contains the wrong information. You should verify that the information was entered correctly.
- TNS-03508: Failed to create address string
- Cause: The TNSPING utility received an internal error when generating an address.
- Action: This is an internal error which should not normally be visible. Ensure that memory is available to run the application and that there are no other operating system problems, and then attempt the command again.
- TNS-04012: Unable to start Oracle Connection Manager instance.
- Cause: CMCTL was unable to start the Oracle Connection Manager instance. Some of the possible reasons include: cmadmin not present in ORACLE_HOME/bin, Invalid parameter in configuration repository, wrong parameter values, or log directory not present.
- Action: 1. Check whether log directory is present, and is writable. Log directory can be found at ORACLE_HOME/network/log, or as specified by the LOG_DIRECTORY parameter in CMAN.ORA.
2. Turn on logging or tracing to get more information about this error.
3. Correct any parameter errors (or mismatched paranthesis), and retry starting Oracle Connection Manager.
4. If the problem persists, contact Oracle Support Services.
- TNS-04065: The number of remote CMCTL sessions exceeds (MAX_CMCTL_SESSIONS-1)
- Cause: The Oracle Connection Manager instance already has (MAX_CMCTL_SESSIONS-1) number of remote CMCTL sessions connected to it.
- Action: Use an already connected CMCTL, or, use a higher value for the parameter MAX_CMCTL_SESSIONS in the CMAN.ORA file.
- TNS-04070: Cannot administer a remote Oracle Connection Manager instance which is not yet started.
- Cause: An attempt was made to administer a remote Oracle Connection Manager instance which is not yet started.
- Action: Use a local CMCTL session to start the Oracle Connection Manager instance before trying to administer it remotely.
- TNS-04072: Unable to suspend atleast one of the gateways.
- Cause: CMCTL was unable to suspend one or more gateways. Possible reason could be suspending a gateway that was already suspended or suspending a gateway that was not present.
- Action: Turn on tracing and logging, retry operation. Information in the log files would help.
- TNS-04077: WARNING: No password set for the Oracle Connection Manager instance.
- Cause: A connection to the Oracle Connection Manager instance was made with no password from the user.
- Action: Ignore the warning if the Oracle Connection Manager is secure enough. Otherwise, use SET PASSWORD command to set a new password for the instance.
- TNS-04078: Unable to resume atleast one of the gateways.
- Cause: CMCTL was unable to resume one or more gateways. Possible reason could be resuming a gateway that was ready for connections, or resuming a gateway that was not present.
- Action: Turn on tracing and logging, retry operation. Information in the log files would help.
- TNS-04079: Cannot administer Oracle Connection Manager with no CMAN.ORA, and port = number.
- Cause: CMAN.ORA is not present or address not configured in CMAN.ORA, and the net service name in the TNSNAMES.ORA contains a nondefault Oracle Connection Manager port.
- Action: Either change the TNSNAMES.ORA entry to use the default port, or configure the CMAN.ORA file with the Oracle Connection Manager"s address.
- TNS-04084: WARNING: Non-reloadable parameters have retained their values.
- Cause: Values of non-reloadable parameters were changed, or, one or more non-reloadable parameters having non-default values were added to the parameter file.
- Action: See Oracle Net Services documentation for a list of non-reloadable parameters.
- TNS-12154: TNS:could not resolve the connect identifier specified
- Cause: A connection to a database or other service was requested using a connect identifier, and the connect identifier specified could not be resolved into a connect descriptor using one of the naming methods configured. For example, if the type of connect identifier used was a net service name then the net service name could not be found in a naming method repository, or the repository could not be located or reached.
- Action:
- If you are using local naming (TNSNAMES.ORA file):
- Make sure that "TNSNAMES" is listed as one of the values of the NAMES.DIRECTORY_PATH parameter in the Oracle Net profile (SQLNET.ORA)
- Verify that a TNSNAMES.ORA file exists and is in the proper directory and is accessible.
- Check that the net service name used as the connect identifier exists in the TNSNAMES.ORA file.
- Make sure there are no syntax errors anywhere in the TNSNAMES.ORA file. Look for unmatched parentheses or stray characters. Errors in a TNSNAMES.ORA file may make it unusable.
- If you are using directory naming:
- Verify that "LDAP" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA).
- Verify that the LDAP directory server is up and that it is accessible.
- Verify that the net service name or database name used as the connect identifier is configured in the directory.
- Verify that the default context being used is correct by specifying a fully qualified net service name or a full LDAP DN as the connect identifier
- If you are using easy connect naming:
- Verify that "EZCONNECT" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA).
- Make sure the host, port and service name specified are correct.
- Try enclosing the connect identifier in quote marks. See the Oracle Net Services Administrators Guide or the Oracle operating system specific guide for more information on naming.
- TNS-12159: TNS:trace file not writeable
- Cause: The trace file to be generated is not writeable by this user.
- Action: If the user does not have write permissions in the directory to which the trace file will be written, contact an administrator to get the proper permissions or set the TRACE_DIRECTORY_CLIENT parameter in the net profile (SQLNET.ORA file) to a directory the user can write to.
- TNS-12162: TNS:net service name is incorrectly specified
- Cause: The connect descriptor corresponding to the net service name in TNSNAMES.ORA or in the directory server (Oracle Internet Directory) is incorrectly specified.
- Action: If using local naming make sure there are no syntax errors in the corresponding connect descriptor in the TNSNAMES.ORA file. If using directory naming check the information provided through the administration used for directory naming.
- TNS-12163: TNS:connect descriptor is too long
- Cause: The connect descriptor corresponding to the net service name specified as the connect identifier is too long. The maximum length for a connect descriptor is 512 bytes and this limit has been exceeded.
- Action: Check the net service name"s connect descriptor in the local naming file (TNSNAMES.ORA) or in the directory server (Oracle Internet Directory). Use a smaller connect descriptor. If this is not possible, contact Worldwide Customer Support.
- TNS-12165: TNS:Trying to write trace file into swap space.
- Cause: Oracle Trace doesn"t allow writing trace information into your swap space.
- Action: Oracle Trace cannot write trace information into swap space so either disable tracing or redirect trace files to be written to another area of your disk.
- TNS-12168: TNS:Unable to contact LDAP Directory Server
- Cause: Cannot contact LDAP directory server to get Oracle Net configuration.
- Action: Verify that the directory server is up and accessible from the network. Verify that directory access configuration is correct. For more information see the Oracle Internet Directory Administrators Guide or the Oracle Net Administrators Guide.
- TNS-12169: TNS:Net service name given as connect identifier is too long
- Cause: The net service name you are attempting to resolve is too long.
- Action: The maximum length of a net service name is 255 bytes; this limit has been exceeded. Use a smaller net service name. If this is not possible, contact Worldwide Customer Support.
- TNS-12170: TNS:Connect timeout occurred
- Cause: The server shut down because connection establishment or communication with a client failed to complete within the allotted time interval. This may be a result of network or system delays; or this may indicate that a malicious client is trying to cause a Denial of Service attack on the server.
- Action: If the error occurred because of a slow network or system, reconfigure one or all of the parameters SQLNET.INBOUND_CONNECT_TIMEOUT, SQLNET.SEND_TIMEOUT, SQLNET.RECV_TIMEOUT in sqlnet.ora to larger values. If a malicious client is suspected, use the address in sqlnet.log to identify the source and restrict access. Note that logged addresses may not be reliable as they can be forged (e.g. in TCP/IP).
- TNS-12171: TNS:could not resolve connect identifier: string
- Cause: A connection to a database or other service was requested using a connect identifier, and the connect identifier specified could not be resolved into a connect descriptor using one of the naming methods configured. For example, if the type of connect identifier used was a net service name then the net service name could not be found in a naming method repository, or the repository could not be located or reached.
- Action:
- If you are using local naming (TNSNAMES.ORA file):
- Make sure that "TNSNAMES" is listed as one of the values of the NAMES.DIRECTORY_PATH parameter in the Oracle Net profile (SQLNET.ORA)
- Verify that a TNSNAMES.ORA file exists and is in the proper directory and is accessible.
- Check that the net service name used as the connect identifier exists in the TNSNAMES.ORA file.
- Make sure there are no syntax errors anywhere in the TNSNAMES.ORA file. Look for unmatched parentheses or stray characters. Errors in a TNSNAMES.ORA file may make it unusable.
- If you are using directory naming:
- Verify that "LDAP" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA).
- Verify that the LDAP directory server is up and that it is accessible.
- Verify that the net service name or database name used as the connect identifier is configured in the directory.
- Verify that the default context being used is correct by specifying a fully qualified net service name or a full LDAP DN as the connect identifier
- If you are using easy connect naming:
- Verify that "EZCONNECT" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA).
- Make sure the host, port and service name specified are correct.
- Try enclosing the connect identifier in quote marks. See the Oracle Net Services Administrators Guide or the Oracle operating system specific guide for more information on naming.
- TNS-12198: TNS:could not find path to destination
- Cause: Could not navigate a path through Interchanges to the destination. This error occurs if an invalid community is in the address string, or the address includes a protocol that is not available or the TNSNAV.ORA file does not have a correct CMANAGER address specified or the Interchange is down.
- Action: Assure that Interchanges necessary to get to the desired destination are up and have available capacity for an additional connection. Also check that the correct community and protocol have been specified in the CMANAGER address used.
- TNS-12203: TNS:unable to connect to destination
- Cause: Invalid address specified or destination is not listening. This error can also occur because of underlying network or network transport problems.
- Action: Verify that the net service name you entered was correct. Verify that the ADDRESS portion of the connect descriptor which corresponds to the net service name is correct. Ensure that the destination process (for example the listener) is running at the remote node.
- TNS-12204: TNS:received data refused from an application
- Cause: The application using Connection Manager refused the connection at the listener.
- Action: Make sure that the application listener at the destination is functioning correctly. If it is and the problem persists, contact Worldwide Customer Support.
- TNS-12209: TNS:encountered uninitialized global
- Cause: Application calling navigation routine has not properly configured the global variables. There are no TNSNAV.ORA files available, or they are defective.
- Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.
- TNS-12212: TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA
- Cause: The PREFERRED_CMANAGERS binding in the client"s TNSNAV.ORA file does not have a CMANAGER_NAME specified.
- Action: Define the CMANAGER_NAME as part of the PREFERRED_CMANAGERS binding. Use of the Oracle Network Manager should eliminate this error.
- TNS-12217: TNS:could not contact PREFERRED_CMANAGERS in TNSNAV.ORA
- Cause: There is a syntax error in the PREFERRED_CMANAGERS entry, or addresses specified are wrong, or the intended Connection Managers are unavailable.
- Action: Check the PREFERRED_CMANAGERS entries in the client"s TNSNAV.ORA file and correct them or talk with your network administrator to determine if the specified Connection Managers are available. Verify that the Interchanges are active by using the INTCTL STATUS command.
- TNS-12218: TNS:unacceptable network configuration data
- Cause: Poorly formed network configuration data. For example, a PREFERRED_CMANAGERS entry may have an incorrect CMANAGER_NAME in the client"s TNSNAV.ORA file. Or an Interchange downtime parameter (TIMEOUT_INTERVAL) on the Navigator may be set to zero in INTCHG.ORA.
- Action: Check the entries in TNSNAV.ORA and the Interchange configuration files and correct them. If necessary, talk with your network administrator to determine if the specified Interchanges (Connection Managers) are available and properly configured. Use the Oracle Network Manager to generate the configuration files if necessary.
- TNS-12219: TNS:missing community name from address in ADDRESS_LIST
- Cause: This error occurs when an ADDRESS_LIST has some ADDRESSes in it that have no COMMUNITY component and others that do have a COMMUNITY component.
- Action: Check that in the connect descriptors you are using either all the ADDRESSes have a COMMUNITY component or all do not.
- TNS-12221: TNS:illegal ADDRESS parameters
- Cause: An illegal set of protocol adapter parameters was specified. In some cases, this error is returned when a connection cannot be made to the protocol transport.
- Action: Verify that the destination can be reached using the specified protocol. Check the parameters within the ADDRESS section of TNSNAMES.ORA or in the directory. Legal ADDRESS parameter formats may be found in the Oracle operating system specific documentation or the Oracle Net Administrator"s Guide. Protocols that resolve names at the transport layer are vulnerable to this error if not properly configured or names are misspelled.
- TNS-12222: TNS:no support is available for the protocol indicated
- Cause: The protocol requested in the ADDRESS portion of the connect descriptor identified through the net service name is not available. If the supplied ADDRESS is typographically correct then support for that protocol is not installed.
- Action: Install support for the protocol or correct typographical error, as appropriate. Note: if the supplied address was derived from resolving the net service name, check the address in the appropriate file (TNSNAMES.ORA, LISTENER.ORA) or in the directory server.
- TNS-12224: TNS:no listener
- Cause: The connection request could not be completed because the listener is not running.
- Action: Ensure that the supplied destination address matches one of the addresses used by the listener - compare the TNSNAMES.ORA entry with the appropriate LISTENER.ORA file (or TNSNAV.ORA if the connection is to go by way of an Interchange). Start the listener on the remote machine.
- TNS-12228: TNS:protocol adapter not loadable
- Cause: On some platforms (such as Windows) protocol support is loaded at run-time. If the shared library (or DLL) for the protocol adapter is missing or one of its supporting libraries is missing then this error is returned.
- Action: For further details, turn on tracing and reexecute the operation. The trace file will include the name of the shared library (or DLL) that could not be loaded.
- TNS-12229: TNS:Interchange has no more free connections
- Cause: One or more Interchanges along the path to the destination desired has no more free connections available to be used for this call.
- Action: Try again later when the Interchanges are less busy, or contact your network administrator to have him determine which interchange it is, and increase the number of connections available on that interchange.
- TNS-12230: TNS:Severe Network error occurred in making this connection
- Cause: This error is reported by an interchange which fails to make contact with the destination due to a physical network error while calling a destination.
- Action: Try again later when the network service may have been fixed or report the problem to your Network Administrator so that he may fix the problem.
- TNS-12236: TNS:protocol support not loaded
- Cause: On some platforms (such as Windows) protocol support is loaded at run-time. If the shared library (or DLL) for the protocol adapter has not been loaded, then this error is returned.
- Action: For further details, turn on tracing and reexecute the operation. The trace file will have the name of the shared library (or DLL) that has not been loaded.
- TNS-12500: TNS:listener failed to start a dedicated server process
- Cause: The process of starting up a dedicated server process failed. The executable could not be found or the environment may be set up incorrectly.
- Action: Turn on tracing at the ADMIN level and reexecute the operation. Verify that the ORACLE Server executable is present and has execute permissions enabled. Ensure that the ORACLE environment is specified correctly in LISTENER.ORA. The Oracle Protocol Adapter that is being called may not be installed on the local hard drive. Please check that the correct Protocol Adapter are successfully linked. If error persists, contact Oracle Customer Support.
- TNS-12505: TNS:listener does not currently know of SID given in connect descriptor
- Cause: The listener received a request to establish a connection to a database or other service. The connect descriptor received by the listener specified a SID for an instance (usually a database instance) that either has not yet dynamically registered with the listener or has not been statically configured for the listener. This may be a temporary condition such as after the listener has started, but before the database instance has registered with the listener.
- Action:
- Wait a moment and try to connect a second time.
- Check which instances are currently known by the listener by executing: lsnrctl services <listener name>
- Check that the SID parameter in the connect descriptor specifies an instance known by the listener.
- Check for an event in the listener.log file.
- TNS-12509: TNS:listener failed to redirect client to service handler
- Cause: The dispatcher terminated unexpectedly
- Action: Attempt to connect again and if the same error occurs, contact the DBA to check the state of the dispatchers for this SID. If the problem persists, turn on tracing in the listener to determine the TNS error caused by the redirect.
- TNS-12510: TNS:database temporarily lacks resources to handle the request
- Cause: The dispatchers appear to be busy handling other requests.
- Action: Attempt the connection again. If error persists, ask the DBA to increase the number of dispatchers and/or dispatchers" limit on number of connections/sessions that they can accept.
- TNS-12511: TNS:service handler found but it is not accepting connections
- Cause: The dispatchers notified the listener that they temporarily do not accept new connections.
- Action: Attempt the connection again. If error persists, contact the DBA to check the state of the dispatchers and/or ask him to increase the number of dispatchers.
- TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
- Cause: The listener received a request to establish a connection to a database or other service. The connect descriptor received by the listener specified a service name for a service (usually a database service) that either has not yet dynamically registered with the listener or has not been statically configured for the listener. This may be a temporary condition such as after the listener has started, but before the database instance has registered with the listener.
- Action:
- Wait a moment and try to connect a second time.
- Check which services are currently known by the listener by executing: lsnrctl services <listener name>
- Check that the SERVICE_NAME parameter in the connect descriptor of the net service name used specifies a service known by the listener.
- If an easy connect naming connect identifier was used, check that the service name specified is a service known by the listener.
- Check for an event in the listener.log file.
- TNS-12515: TNS:listener could not find a handler for this presentation
- Cause: None of the listener"s known service handlers are registered as supporting the presentation protocol required by the connecting client.
- Action: Check that the destination service is configured to accept the presentation protocol.
- TNS-12516: TNS:listener could not find available handler with matching protocol stack
- Cause: None of the known and available service handlers for the given SERVICE_NAME support the client"s protocol stack: transport, session, and presentation protocols.
- Action: Check to make sure that the service handlers (e.g. dispatchers) for the given SERVICE_NAME are registered with the listener, are accepting connections, and that they are properly configured to support the desired protocols.
- TNS-12518: TNS:listener could not hand off client connection
- Cause: The process of handing off a client connection to another process failed.
- Action: Turn on listener tracing and re-execute the operation. Verify that the listener and database instance are properly configured for direct handoff. If problem persists, call Oracle Support.
- TNS-12520: TNS:listener could not find available handler for requested type of server
- Cause: None of the known and available service handlers for requested type of server (dedicated or shared) are appropriate for the client connection.
- Action: Run "lsnrctl services" to ensure that the instance(s) have registered with the listener and that the appropriate handlers are accepting connections.
- TNS-12521: TNS:listener does not currently know of instance requested in connect descriptor
- Cause: The listener received a request to establish a connection to a database or other service. The connect descriptor received by the listener specified in addition to the service name an instance name for an instance (usually a database instance) that either has not yet dynamically registered with the listener or has not been statically configured for the listener. This may be a temporary condition such as after the listener has started, but before the database instance has registered with the listener.
- Action:
- Wait a moment and try to connect a second time.
- Check which instances are currently known by the listener by executing: lsnrctl services <listener name>
- Check that the INSTANCE_NAME parameter in the connect descriptor specifies an instance name known by the listener.
- Check for an event in the listener.log file.
- TNS-12522: TNS:listener could not find available instance with given INSTANCE_ROLE
- Cause: There are not any available and appropriate database instances registered with the listener, that are part of the service identified by SERVICE_NAME given in the connect descriptor and that have the specified INSTANCE_ROLE (and INSTANCE_NAME, if specified).
- Action: Check to make sure that the INSTANCE_ROLE specified is correct. Run "lsnrctl services" to ensure that the instance(s) have registered with the listener and that they are ready to accept connections.
- TNS-12523: TNS:listener could not find instance appropriate for the client connection
- Cause: The listener could not find any available (database) instances, that are appropriate for the client connection.
- Action: Run "lsnrctl services" to ensure that the instance(s) are registered with the listener, and have status READY.
- TNS-12525: TNS:listener has not received client"s request in time allowed
- Cause: The listener disconnected the client because the client failed to provide the necessary connect information within the allowed time interval. This may be a result of network or system delays; or this may indicate that a malicious client is trying to cause a Denial of Service attack on the listener.
- Action: If the error occurred because of a slow network or system, reconfigure INBOUND_CONNECT_TIMEOUT to a larger value. If a malicious client is suspected, use the address in listener.log to identify the source and restrict access. Turn on tracing for more information.
- TNS-12526: TNS:listener: all appropriate instances are in restricted mode
- Cause: Database instances supporting the service requested by the client were in restricted mode. The Listener does not allow connections to instances in restricted mode. This condition may be temporary, such as during periods when database administration is performed.
- Action: Attempt the connection again. If error persists, then contact the database administrator to change the mode of the instance, if appropriate.
- TNS-12527: TNS:listener: all instances are in restricted mode or blocking new connections
- Cause: All appropriate database instances supporting the service requested by the client reported that they either were in restricted mode or were blocking the new connections. The Listener does not allow connections to such instances. This condition may be temporary, such as at instance startup.
- Action: Attempt the connection again. If error persists, then contact the database administrator to check the status of the instances.
- TNS-12528: TNS:listener: all appropriate instances are blocking new connections
- Cause: All instances supporting the service requested by the client reported that they were blocking the new connections. This condition may be temporary, such as at instance startup.
- Action: Attempt the connection again. If error persists, then contact the administrator to check the status of the instances.
- TNS-12529: TNS:connect request rejected based on current filtering rules
- Cause: Connection Manager and its listener were configured with filtering rules specifying that the connect request be rejected.
- Action: If this connect request should be allowed, then contact the administrator to modify the filtering rules.
- TNS-12533: TNS:illegal ADDRESS parameters
- Cause: An illegal set of protocol adapter parameters was specified. In some cases, this error is returned when a connection cannot be made to the protocol transport.
- Action: Verify that the destination can be reached using the specified protocol. Check the parameters within the ADDRESS section of TNSNAMES.ORA. Legal ADDRESS parameter formats may be found in the Oracle operating system specific documentation for your platform. Protocols that resolve names at the transport layer (such as DECnet object names) are vulnerable to this error if not properly configured or names are misspelled.
- TNS-12534: TNS:operation not supported
- Cause: An internal function received a request to perform an operation that is not supported (on this machine).
- 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-12535: TNS:operation timed out
- Cause: The requested operation could not be completed within the time out period.
- Action: Look at the documentation on the secondary errors for possible remedy. See SQLNET.LOG to find secondary error if not provided explicitly. Turn on tracing to gather more information.
- TNS-12538: TNS:no such protocol adapter
- Cause: The protocol adapter requested (by way of the "(PROTOCOL=..)" keyword-value pair in a TNS address) is unknown. If the supplied address is typographically correct then the protocol adapter is not installed.
- Action: Install the protocol adapter or correct typographically error, as appropriate. Note: if the supplied address was derived from resolving the service name, check the address in the appropriate file (TNSNAMES.ORA, LISTENER.ORA or SQLNET.ORA).
- TNS-12539: TNS:buffer over- or under-flow
- Cause: Buffer too small for incoming data or too large for outgoing data.
- Action: This restriction (which is associated with CONNECT DATA) is not normally visible to the user. For further details, turn on tracing and reexecute the operation; contact Oracle Customer Support.
- TNS-12541: TNS:no listener
- Cause: The connection request could not be completed because the listener is not running.
- Action: Ensure that the supplied destination address matches one of the addresses used by the listener - compare the TNSNAMES.ORA entry with the appropriate LISTENER.ORA file (or TNSNAV.ORA if the connection is to go by way of an Interchange). Start the listener on the remote machine.
- TNS-12545: Connect failed because target host or object does not exist
- Cause: The address specified is not valid, or the program being connected to does not exist.
- Action: Ensure the ADDRESS parameters have been entered correctly; the most likely incorrect parameter is the node name. Ensure that the executable for the server exists (perhaps "oracle" is missing.) If the protocol is TCP/IP, edit the TNSNAMES.ORA file to change the host name to a numeric IP address and try again.
- TNS-12557: TNS:protocol adapter not loadable
- Cause: On some platforms (such as OS/2) protocol adapters are loaded at run-time. If the shared library (or DLL) for the protocol adapter is missing or one of its supporting libraries is missing then this error is returned.
- Action: For further details, turn on tracing and reexecute the operation. The trace file will include the name of the shared library (or DLL) that could not be loaded.
- TNS-12558: TNS:protocol adapter not loaded
- Cause: On some platforms (such as OS/2) protocol adapters are loaded at run-time. If the shared library (or DLL) for the protocol adapter has not been loaded, then this error is returned.
- Action: For further details, turn on tracing and reexecute the operation. The trace file will have the name of the shared library (or DLL) that has not been loaded.
- TNS-12560: TNS:protocol adapter error
- Cause: A generic protocol adapter error occurred.
- Action: Check addresses used for proper protocol specification. Before reporting this error, look at the error stack and check for lower level transport errors. For further details, turn on tracing and reexecute the operation. Turn off tracing when the operation is complete.
- TNS-12574: TNS:redirection denied
- Cause: The connect request failed because it would have required redirection and the caller has requested no redirections.
- 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-12589: TNS:connection not bequeathable
- Cause: An attempt to hand-off a connection from one process to another has failed because the protocol provider does not support it.
- 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-12593: TNS:no registered connection
- Cause: An attempt to solicit network event activity has failed because no connections are registered for event notification.
- 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-12601: TNS:information flags check failed
- Cause: The TNS information flags set by the process prior to connection negotiation were not present after the negotiation was finished.
- Action: This is an internal error. Enable tracing and attempt to repeat the error. If it occurs again, contact Oracle Customer Support.
- TNS-12602: TNS: Connection Pooling limit reached
- Cause: The operation failed because maximum active current connections has been reached. It may not be a real error when the Connection Pooling feature is enabled. It is possible that the application later reissues the operation and successfully grabs the connection pool slot and proceeds.
- Action: This is an internal error. Enable tracing and attempt to repeat the error. If it occurs again, contact Oracle Customer Support.
- TNS-12606: TNS: Application timeout occurred
- Cause: A network session did not reach an application-defined stage within the allowed time interval.
- Action: This is an error which does not normally appear at the high level. The action to take is application specific, and is detailed in the higher level error description.
- TNS-12607: TNS: Connect timeout occurred
- Cause: A network session did not reach a predefined connect stage within the allowed time interval.
- Action: This is an error which does not normally appear at the high level. The action to take is application specific, and is detailed in the higher level error description.
- TNS-12622: TNS:event notifications are not homogeneous
- Cause: An attempt to register a connection for event notification failed because the event notification type conflicts with existing registrations.
- Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Oracle Customer Support.
- TNS-12624: TNS:connection is already registered
- Cause: An attempt to register a connection for event notification failed because the connection is already registered.
- Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Oracle Customer Support.
- TNS-12629: TNS:no event test
- Cause: An attempt to register a connection for event notification failed because the ability to test for events is not available.
- Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Oracle Customer Support.
- TNS-12635: No authentication adapters available
- Cause: The executable was not linked with any authentication service adapters but the sqlnet.ora parameter that determines whether or not authentication is required was set to true.
- Action: Either disable the parameter or relink the executable with service adapters.
- TNS-12636: Packet send failed
- Cause: A process was unable to send a packet to another process. Possible causes are:
1. The other process was terminated.
2. The machine on which the other process is running went down.
3. Some other communications error occurred.
- Action: If the cause is not obvious, contact Oracle Customer Support.
- TNS-12637: Packet receive failed
- Cause: A process was unable to receive a packet from another process. Possible causes are:
1. The other process was terminated.
2. The machine on which the other process is running went down.
3. Some other communications error occurred.
- Action: If the cause is not obvious, contact Oracle Customer Support.
- TNS-12639: Authentication service negotiation failed
- Cause: No match was found between the types of authentication services that the client supports and those that the server is using.
- Action: Possible solutions:
1. Change the entry in sqlnet.ora that determines which services are to be used.
2. Relink the client with at least one of the authentication service adapters that the server supports.
3. Relink the server with at least one of the authentication service adapters that the client supports.
4. Disable authentication on both the client and server.
- TNS-12643: Client received internal error from server
- Cause: The client process received an error from the server that indicated that an internal Oracle Net native services error had occurred.
- Action: Enable tracing on both processes and attempt to recreate the problem. If successful in recreating the problem, contact Oracle Customer Support.
- TNS-12650: No common encryption or data integrity algorithm
- Cause: The client and server have no algorithm in common for either encryption or data integrity or both.
- Action: Choose sets of algorithms that overlap. In other words, add one of the client"s algorithm choices to the server"s list or vice versa.
- TNS-12651: Encryption or data integrity algorithm unacceptable
- Cause: The algorithm the server chose to use for encryption or data integrity was not one of the choices acceptable to the client. This is either the result of an internal error, of a network data transmission error, or of deliberate tampering with the transmitted data.
- Action: For further details, turn on tracing, re-execute the operation, and contact Oracle Customer Support.
- TNS-12656: Cryptographic checksum mismatch
- Cause: The cryptographic checksum received with a packet of incoming data didn"t match the checksum computed by the receiving end. This indicates that the packet was tampered with or otherwise corrupted in transit.
- Action: Look for sources of data corruption, perhaps including deliberate tampering.
- TNS-12658: ANO service required but TNS version is incompatible
- Cause: A client process that is running an earlier version of TNS attempted to connect but the connection failed because the server process required that an ANO service (authentication, encryption, etc.) be used.
- Action: Relink the calling executable and retry the connection or eliminate the requirement that the service be used on the server side.
- TNS-12659: Error received from other process
- Cause: An error was received by one or more services from the process on the other side of the connection.
- Action: Enable tracing to determine the exact error(s). The error(s) is (are) not returned directly because an error generated by a server may not make sense on the client side and vice-versa.
- TNS-12660: Encryption or crypto-checksumming parameters incompatible
- Cause: One side of the connection specified "REQUIRED" for encryption or crypto-checksumming, while the other side specified "REJECTED".
- Action: Change the "REQUIRED" side to "REQUESTED" if the you want encryption or crypto-checksumming to be optional, or change the "REJECTED" side to "ACCEPTED" if you do not want the service to be optional.
- TNS-12661: Protocol authentication to be used
- Cause: The Oracle Advanced Security authentication service has determined that the Oracle Net transport protocol in use is to be utilized to authenticate a user"s identity.
- Action: This error is used solely to communicate information between the authentication service and the Oracle Net session layer and should not normally be visible. If the error is seen, contact Oracle Worldwide Support.
- TNS-12663: Services required by client not available on the server
- Cause: Service(s) that was (were) required by the client process were not available on the server process.
- Action: Configure the server with the services required by the client (best solution) or delete the requirement from the configuration file of the client (least secure).
- TNS-12664: Services required by server not available on the client
- Cause: Service(s) that was (were) required by the server process were not available on the client process.
- Action: Configure the client with the services required by the server (best solution) or delete the requirement from the configuration file of the server (least secure).
- TNS-12666: Dedicated server: outbound transport protocol different from inbound
- Cause: The protocol specified for an externally-identified outbound connection from a dedicated server (database link) was not the same as that used for the inbound connection. It is not possible for Oracle Net to authenticate a proxy connection that uses a protocol that is different from that which was used for the connection to the dedicated server.
- Action: Specify the same protocol in the Oracle Net connect descriptor for the outbound connection as that used for the inbound connection.
- TNS-12667: Shared server: outbound transport protocol different from inbound
- Cause: The protocol specified for an externally-identified outbound connection from a shared server (database link) was not the same as as that used for the inbound connection. It is not possible for Oracle Net to authenticate a proxy connection that uses a protocol that is different from that which was used for the connection to the shared server.
- Action: Specify the same protocol in the Oracle Net connect descriptor for the outbound connection as that used for the inbound connection
- TNS-12668: Dedicated server: outbound protocol does not support proxies
- Cause: The protocol specified to perform an externally-identified proxy connection (database link) from a dedicated server does not support proxy connections.
- Action: Specify a protocol in the Oracle Net connect descriptor used for the connection that does support externally-authenticated proxy connections. NOTE: Because of a limitation in Oracle Net, the protocol used for the proxy connection must the same as that used for the connection from the client to the server.
- TNS-12669: Shared server: outbound protocol does not support proxies
- Cause: The protocol specified to perform an externally-identified proxy connection (database link) from a shared server does not support proxy connections.
- Action: Specify a protocol in the Oracle Net connect descriptor used for the connection that does support externally-authenticated proxy connections. NOTE: Because of a limitation in Oracle Net, the protocol used for the proxy connection must the same as that used for the connection from the client to the server.
- TNS-12671: Shared server: adapter failed to save context
- Cause: The adapter for the authentication service failed when it tried to save the data needed for proxy connections (database links) through the shared server.
- Action: Enable tracing to determine the exact error. Contact Oracle Customer Support if the reason is not obvious.
- TNS-12675: External user name not available yet
- Cause: The authentication service in use was not able to return the external name of a user of the ORACLE server because it is not available to the service yet.
- Action: This is just an informational message and should not normally be visible to the user. If the error does appear, contact Oracle Customer Support.
- TNS-12676: Server received internal error from client
- Cause: The server process received an error from the client which indicated that an internal Oracle Net native services error had occurred.
- Action: Enable tracing on both processes and attempt to recreate the problem. If the problem recurs, contact Oracle Customer Support.
- TNS-12677: Authentication service not supported by database link
- Cause: The authentication service used by the proxy process (database link) was unable to find the adapter being used by the client in its list of authentication mechanisms.
- Action: Specify an authentication adapter that is shared by the client and the server being used for the database link.
- TNS-12685: Native service required remotely but disabled locally
- Cause: A native service is required by the remote process but native services have been disabled locally.
- Action: Enable native services locally or change the configuration parameters on the remote host so that no native services are required.
- TNS-12688: Login failed: the SecurID server rejected the new pincode
- Cause: There are a number of reasons why the SecurID server would refuse a pincode:
- The user might not have permission to make up his own pincode.
- The pincode was either too short or too long. Valid pincodes consist of minimal four, but no more than eight characters.
- The pincode contains any non alphanumeric characters.
- Action: Reexecute the operation and make sure to use a pincode that satisfies the above requirements. If the problem persists, turn on tracing at the Oracle Server side of the connection and examine the trace file for the exact error.
- TNS-12689: Server Authentication required, but not supported
- Cause: Server Authentication is required for this connection, but not supported by both sides of the connection.
- Action: Make sure both sides of the connection have the correct version of Advanced Networking Option, and that the Authentication Adapter supports Server Authentication.
- TNS-12690: Server Authentication failed, login cancelled
- Cause: Server Authentication is required, but the server"s credentials were found invalid by the client.
- Action: Make sure that the server has a valid set of credentials. Refer to your authentication adapter specific documentation on how to do this.
- TNS-12696: Double Encryption Turned On, login disallowed
- Cause: The user is using a Secure Protocol Adapter that has Encryption turned ON as well as ANO Encryption.
- Action: Turn OFF either ANO Encryption or the Protocol Adapter Encryption if possible. Refer to Oracle Advanced Security Administrator"s Guide on how to do this.
'DB > oralce' 카테고리의 다른 글
| ORA-00942: table or view does not exist (0) | 2015.06.26 |
|---|---|
| hugepages (0) | 2015.06.17 |
| 오라클관련포트 (0) | 2015.06.07 |
| 설치관련 오라클 공식문서 (0) | 2015.06.04 |
| Alert Log (0) | 2015.06.04 |
