Oracle 12c R2 Error Codes and Solution Suggestions from ORA-12150 to ORA-12400
- ORA-12150: TNS:unable to send data
Cause: Unable to send data. Connection probably disconnected.
Action: Reestablish connection. If the error is persistent, turn on tracing and reexecute the operation.
Cause: Internal error.
Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.
Cause: Unable to send break message. Connection probably disconnected.
Action: Reestablish connection. If the error is persistent, turn on tracing and reexecute the operation.
Cause: Not currently connected to a remote host.
Action: Reestablish connection.
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.
Cause: Internal error during break handling.
Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.
Cause: Internal error during break handling.
Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.
Cause: Internal error during network communication.
Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.
Cause: Unable to locate parameter file.
Action: Verify that a valid parameter file exists, and is readable.
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.
Cause: Corrupt error reporting subsystem.
Action: 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 connection may be terminated.
Action: Reconnect and try again. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.
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. If using ORACLE_SID, please check if ORACLE_SID is// set.
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.
Cause: The sqlnet.fdf file doesn’t exist in $ORACLE_HOME/network/admin.
Action: The sqlnet.fdf file is required for Oracle Tracing to occur. Either install the sqlnet.fdf file in $ORACLE_HOME/network/admin or turn off tracing in your ORA file.
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.
Cause: NVstring contained DESCRIPTION/HO.
Action: Call HO agent from integrating 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.
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.
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).
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.
Cause: The navigation layer received an error from TNS.
Action: See the error log file for the specific TNS error.
Cause: The navigation layer received an error while trying to look up a value for a keyword.
Action: Check the syntax of the connect descriptor.
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.
Cause: Out of memory on machine.
Action: Reconfigure machine to have more storage or run fewer applications while the Interchange is running.
Cause: TNS connection buffer supplied by the application was too small to retrieve the data sent back.
Action: Supply a larger connection buffer. If problem persists, call Worldwide Customer Support.
Cause: Internal navigation error.
Action: Not normally visible to the user. For further details contact Worldwide Customer Support.
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.
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.
Cause: Internal navigation error.
Action: Not normally visible to the user. For further details contact Worldwide Customer Support.
Cause: Internal navigation error because of an unexpected TNS error.
Action: Look at the log file to find the TNS error. If necessary, turn on tracing and repeat the operation.
Cause: Improperly configured navigation file TNSNAV.ORA.
Action: Check the syntax of the TNSNAV.ORA file on the application`s machine, and verify that it lists the correct communities.
Cause: Either the ORACLE environment is not set up correctly, or the TNSNAV.ORA file is not present.
Action: Ensure that the ORACLE environment is set up appropriately on your platform and that a TNSNAV.ORA file is present.
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.
Cause: Application calling navigation routine has not properly configured the TNSNAV.ORA file.
Action: Check the syntax of the TNSNAV.ORA file.
Cause: TNSNAV.ORA does not have a PREFERRED_CMANAGERS defined.
Action: Add a PREFERRED_CMANAGERS entry to the TNSNAV.ORA file.
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.
Cause: The PREFERRED_CMANAGERS binding in the client’s TNSNAV.ORA file does not have an ADDRESS specified.
Action: Define the ADDRESS as part of the PREFERRED_CMANAGERS binding.
Cause: There is no LOCAL_COMMUNITIES entry in TNSNAV.ORA.
Action: Define the LOCAL_COMMUNITIES for this node in the TNSNAV.ORA file.
Cause: Address binding for PREFERRED_NAVIGATORS entry is improperly entered. entry.
Action: Check your PREFERRED_NAVIGATORS entry and fix it in TNSNAV.ORA
Cause: Address binding for the PREFERRED_CMANAGERS entry in the client’s TNSNAV.ORA file is improperly entered.
Action: Define the ADDRESS as part of the PREFERRED_CMANAGERS binding.
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.
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.
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.
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.
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.
Cause: Too many TNS connections open simultaneously.
Action: Wait for connections to close and re-try.
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.
Cause: Contact can not be made with remote party.
Action: Make sure the network driver is functioning and the network is up.
Cause: The current user has exceeded the allotted resource assigned in the operating system.
Action: Acquire more operating system resource, or perform a different function.
Cause: The supplied connect descriptor contains illegal syntax.
Action: Check the syntax of the connect descriptor in TNSNAMES.ORA.
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.
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.
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.
Cause: This error is reported by an interchange which fails to find a possible connection along the path to the destination.
Action: Report the problem to your Network Administrator so that he may fix the problem.
Cause: This error is reported by an interchange which fails to find a possible path to the destination.
Action: Report the problem to your Network Administrator so that he may fix the problem.
Cause: This error is reported by an interchange which fails to accept a connection due to a redirect failure.
Action: Report the problem to your Network Administrator so that he may isolate the interchange problem.
Cause: This error is reported by an interchange which determines that this interchange is not the right gateway and needs to redirect the connection to another gateway along the path to the destination.
Action: None
Cause: This error is reported by an interchange which fails to redirect a connection to another interchange along the path to the destination.
Action: Report the problem to your Network Administrator so that he may fix the problem.
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.
Cause: The NT operation is aborted because it is interrupted by upper layer to cleanup the database session.
Action: None
- ORA-12315: database link type is invalid for the ALTER DATABASE statement
Cause: The database link name you specified on the ALTER DATABASE statement is not an ROM: link. You must specify an ROM: link when using the ALTER DATABASE statement to mount or open a secondary database.
Action: Re-issue the ALTER DATABASE statement using a valid ROM: link to the database you want to mount or open. If a valid ROM: link does not exist, create one using the CREATE DATABASE LINK command. See the Trusted ORACLE RDBMS Guide to Security Features for more information about creating database links using the ROM: link type.
Cause: The connect string in the CREATE DATABASE LINK statement has a syntactical error.
Action: Drop the database link and recreate it using valid syntax. See the SQL Language Reference Manual for more information about the connect string portion of the CREATE DATABASE LINK statement.
Cause: There are several possible causes for this error. First, you can get this error if your username (and password, if you are using database instead of operating system authentication) in the secondary database are not identical to your username (and password) in the primary database. Second, you can get this error if your username in the secondary database is invalid (has not been created). Third, you can get this error if the username/password combination specified in the connect string of the database link definition is invalid (either not created or has an invalid password).
Action: In the first case, ensure that the secondary database contains a username (and password, if you are using database authentication) identical to the one you are using in the primary database. In general, you should always use operating system authentication in Trusted ORACLE (see the Trusted ORACLE RDBMS Guide to Security Features for more information about the advantages of OS authentication). In the second case, ensure that your username in the secondary database has been created. In the third case, ensure that the username specified in the connect string has been created in the secondary database.
Cause: You are attempting to mount a secondary database that has already been mounted by your instance.
Action: The database is already mounted, so you need not take additional action to mount it. To establish access, use the ALTER DATABASE linkname OPEN command to open the database.
Cause: You are attempting to open a secondary database that is already open.
Action: The database is open and you need not take additional action to establish access.
Cause: The secondary database that your instance is attempting to mount is not open and automatic mounting has not been enabled.
Action: Manually mount and open the secondary database using ALTER DATABASE linkname with the OPEN and MOUNT options. Alternately, to allow your instance to automatically mount and open secondary databases, set the AUTO_MOUNTING parameter in the parameter file to TRUE.
Cause: This message should be accompanied by additional error messages that indicate the cause of the problem.
Action: Follow the steps outlined in the accompanying error messages to resolve the problem.
Cause: This message should be accompanied by additional error messages that indicate the cause of the problem.
Action: Follow the steps outlined in the accompanying error messages to resolve the problem.
Cause: You can only specify the ROM: link type on a public, not a private, database link.
Action: Determine if there is an existing public database link to the secondary database. If not, and if you wish to establish public access to the secondary database, create a public database link to the secondary database using the CREATE DATABASE LINK command.
Cause: The database you attempted to access is closing, so your operation has been terminated.
Action: Wait until the database has been reopened, or contact the database adminstrator.
Cause: The database you attempted to access is closed, so your operation has been terminated.
Action: Wait until the database is reopened, or contact the database administrator.
Cause: You attempted to open a database that has not been mounted.
Action: Mount the database with the ALTER DATABASE linkname MOUNT command, then re-attempt to open the database.
Cause: You attempted to dismount a database that is still open.
Action: Close the database with the ALTER DATABASE linkname CLOSE command, then re-attempt to dismount the database.
Cause: You attempted to close a database that is not open.
Action: The database is closed; you can proceed with dismounting it.
Cause: You are tyring to login while another user is mounting or dismounting the same database.
Action: Check to see if the database is in the middle of being mounted or opened and try your login again once the database is accessible.
Cause: The number specified on the OPEN_MOUNTS parameter in the parameter file exceeds the maximum allowed (255).
Action: Change the value of this parameter so that it reflects the actual number of possible open mounts to secondary databases. This must be less than 255.
Cause: The number of currently open mounts exceeds the value you specified on the OPEN_MOUNTS parameter.
Action: Increase the value of the OPEN_MOUNTS parameter so that it accommodates the maximum possible number of open mounts to secondary databases.
Cause: There are several possible causes for this message: First, you will get this message if your username in the second database specified was not granted the CREATE SESSION system privilege. Second, you will get this message if the username specified in the connect string of the database link definition was not granted the CREATE SESSION system privilege.
Action: The action you take depends upon the cause of the message: In the first case, ensure that your username in the secondary database was granted the CREATE SESSION system privilege. In the second case, ensure the username specified in the connect string of the database link definition was granted the CREATE SESSION system privilege in the secondary database.
Cause: An attempt was made to drop a ROM: database link that was still mounted and/or opened.
Action: Close and dismount the database and then re-issue the drop statement.
Cause: You tried to create a view which references a remote object which, in turn, references an object on another database. Since the view that you tried to create references a remote object, that object cannot reference an object on another database.
Action: Choose a different object to reference in your view or change the remote object so that it does not reference another database.
Cause: An attempt was made to reference (compile against) an object of a secondary database but the object is invalid and the system cannot validate or recompile it because it is in a secondary database.
Action: Manually recompile the invalid object in the secondary database.
Cause: You tried to either select from a remote view or execute a remote procedure which references an object on another database. Since the remote view or procedure is on a secondary database, an additional reference to another database cannot be done.
Action: Choose a different object to reference or change the remote view or procedure so that it does not reference another database.
Cause: You tried to access a object (for example, a table or view) on a secondary database that was in the process of being dropped.
Action: Repeat the operation. If you receive this message again, try to access the object from the secondary database. If you receive an internal error or a trace file, contact Oracle WorldWide Technical Support.