ORA-12600: TNS: string open failed

ORA-12600: TNS: string open failed

Cause: The creation of a string in ORACLE NLS format failed.

Action: This is an internal error, enable tracing and attempt to repeat the error. If it occurs again, contact Oracle Customer Support.

ORA-12599: TNS:cryptographic checksum mismatch

ORA-12599: TNS:cryptographic checksum mismatch

Cause: The data received is not the same as the data sent.

Action: Attempt the transaction again. If error persists, check (and correct) the integrity of your physical connection.

ORA-12598: TNS:banner registration failed

ORA-12598: TNS:banner registration failed

Cause: The registration of a product banner with the Oracle server failed.

Action: This is an error which is not normally visible externally. Enable tracing and attempt to repeat the error. If it occurs again, contact Oracle Customer Support.

ORA-12597: TNS:connect descriptor already in use

ORA-12597: TNS:connect descriptor already in use

Cause: Internal error - illegal use of connect descriptor.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

ORA-12596: TNS:internal inconsistency

ORA-12596: TNS:internal inconsistency

Cause: TNS has detected an internal inconsistency.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Oracle Customer Support.

ORA-12595: TNS:no confirmation

ORA-12595: TNS:no confirmation

Cause: TNS is unable to get requested confirmation acknowledgment from remote partner.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

ORA-12593: TNS:no registered connection

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

ORA-12592: TNS:bad packet

ORA-12592: TNS:bad packet

Cause: An ill-formed packet has been detected by the TNS software.

Action: For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

ORA-12591: TNS:event signal failure

ORA-12591: TNS:event signal failure

Cause: The TNS software is unable to signal an event occurrence.

Action: For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

ORA-12590: TNS:no I or O buffer

ORA-12590: TNS:no I or O buffer

Cause: An attempt to perform an I or O operation failed because no buffer was available.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

ORA-12589: TNS:connection not bequeathable

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

ORA-12585: TNS:data truncation

ORA-12585: TNS:data truncation

Cause: A receive operation has completed with insufficient data to satisfy the user s request.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

ORA-12583: TNS:no reader

ORA-12583: TNS:no reader

Cause: A send operation has been requested but partner has already disconnected.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

ORA-12582: TNS:invalid operation

ORA-12582: TNS:invalid operation

Cause: An internal function received an invalid request.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

ORA-12574: TNS:redirection denied

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

ORA-12571: TNS:packet writer failure

ORA-12571: TNS:packet writer failure

Cause: An error occurred during a data send.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

ORA-12570: TNS:packet reader failure

ORA-12570: TNS:packet reader failure

Cause: An error occurred during a data receive.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

ORA-12569: TNS:packet checksum failure

ORA-12569: TNS:packet checksum failure

Cause: The data received is not the same as the data sent.

Action: Attempt the transaction again. If the error is persistent, turn on tracing and reexecute the operation.

ORA-12566: TNS:protocol error

ORA-12566: TNS:protocol error

Cause: An unexpected TNS protocol error has occurred.

Action: For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

ORA-12564: TNS:connection refused

ORA-12564: TNS:connection refused

Cause: The connect request was denied by the remote user (or TNS software).

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation.

ORA-12562: TNS:bad global handle

ORA-12562: TNS:bad global handle

Cause: Internal error - bad gbh argument passed to TNS from caller. System may have been linked with old libraries.

Action: Not normally visible to the user, contact Oracle Customer Support.

ORA-12561: TNS:unknown error

ORA-12561: TNS:unknown error

Cause: A generic protocol error occurred.

Action: For further details, turn on tracing and reexecute the operation.

ORA-12560: TNS:protocol adapter error

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

ORA-12558: TNS:protocol adapter not loaded

ORA-12558: TNS:protocol adapter not loaded

Cause: On some platforms (such as OS or 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.

ORA-12557: TNS:protocol adapter not loadable

ORA-12557: TNS:protocol adapter not loadable

Cause: On some platforms (such as OS or 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.

ORA-12556: TNS:no caller

ORA-12556: TNS:no caller

Cause: TNS detected an incoming connect request but there was no caller.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

ORA-12555: TNS:permission denied

ORA-12555: TNS:permission denied

Cause: User has insufficient privileges to perform the requested operation.

Action: Acquire necessary privileges and try again.

ORA-12554: TNS:current operation is still in progress

ORA-12554: TNS:current operation is still in progress

Cause: An internal operation is still in progress.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

ORA-12552: TNS:operation was interrupted

ORA-12552: TNS:operation was interrupted

Cause: An internal operation was interrupted and could not complete.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

ORA-12551: TNS:missing keyword

ORA-12551: TNS:missing keyword

Cause: The supplied connect descriptor is missing one or more TNS keywords.

Action: Check the syntax, and ensure all required keywords are present.

ORA-12550: TNS:syntax error

ORA-12550: TNS:syntax error

Cause: The supplied connect descriptor contains illegal syntax.

Action: Check the syntax of the connect descriptor in TNSNAMES.ORA.

ORA-12549: TNS:operating system resource quota exceeded

ORA-12549: TNS:operating system resource quota exceeded

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.

ORA-12548: TNS:incomplete read or write

ORA-12548: TNS:incomplete read or write

Cause: A data send or receive failed.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

ORA-12547: TNS:lost contact

ORA-12547: TNS:lost contact

Cause: Partner has unexpectedly gone away, usually during process startup.

Action: Investigate partner application for abnormal termination. On an Interchange, this can happen if the machine is overloaded.

ORA-12546: TNS:permission denied

ORA-12546: TNS:permission denied

Cause: User has insufficient privileges to perform the requested operation.

Action: Acquire necessary privileges and try again.

ORA-12545: Connect failed because target host or object does not exist

ORA-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 or IP, edit the TNSNAMES.ORA file to change the host name to a numeric IP address and try again.

ORA-12544: TNS:contexts have different wait or test functions

ORA-12544: TNS:contexts have different wait or test functions

Cause: Two protocol adapters have conflicting wait or test functions.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

ORA-12543: TNS:destination host unreachable

ORA-12543: TNS:destination host unreachable

Cause: Contact can not be made with remote party.

Action: Make sure the network driver is functioning and the network is up.

ORA-12542: TNS:address already in use

ORA-12542: TNS:address already in use

Cause: Specified listener address is already being used.

Action: Start your listener with a unique address.

ORA-12541: TNS:no listener

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

ORA-12540: TNS:internal limit restriction exceeded

ORA-12540: TNS:internal limit restriction exceeded

Cause: Too many TNS connections open simultaneously.

Action: Wait for connections to close and re-try.

ORA-12539: TNS:buffer over- or under-flow

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

ORA-12538: TNS:no such protocol adapter

ORA-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).

ORA-12537: TNS:connection closed

ORA-12537: TNS:connection closed

Cause: End of file condition has been reached; partner has disconnected.

Action: None needed; this is an information message.

ORA-12536: TNS:operation would block

ORA-12536: TNS:operation would block

Cause: An internal operation did not commence because to do so would block the current process and the user has requested that operations be non-blocking.

Action: None needed; this is an information message.

ORA-12535: TNS:operation timed out

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

ORA-12534: TNS:operation not supported

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

ORA-12533: TNS:illegal ADDRESS parameters

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

ORA-12532: TNS:invalid argument

ORA-12532: TNS:invalid argument

Cause: An internal function received an invalid parameter.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.

ORA-12531: TNS:cannot allocate memory

ORA-12531: TNS:cannot allocate memory

Cause: Sufficient memory could not be allocated to perform the desired activity.

Action: Either free some resource for TNS, or add more memory to the machine. For further details, turn on tracing and reexecute the operation.

ORA-12529: TNS:connect request rejected based on current filtering rules

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

ORA-12528: TNS:listener: all appropriate instances are blocking new connections

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

ORA-12527: TNS:listener: all instances are in restricted mode or blocking new connections

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

ORA-12526: TNS:listener: all appropriate instances are in restricted mode

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

ORA-12525: TNS:listener has not received client s request in time allowed

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

ORA-12524: TNS:listener could not resolve HANDLER_NAME given in connect descriptor

ORA-12524: TNS:listener could not resolve HANDLER_NAME given in connect descriptor

Cause: The HANDLER_NAME in the CONNECT_DATA was not found in the listener s tables for the specified SERVICE_NAME and INSTANCE_NAME.

Action: Check to make sure that the HANDLER_NAME specified is correct.

ORA-12523: TNS:listener could not find instance appropriate for the client connection

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

ORA-12522: TNS:listener could not find available instance with given INSTANCE_ ROLE

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

ORA-12521: TNS:listener does not currently know of instance requested in connect descriptor

ORA-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: services lamp;lt;lamp;nbsp;listener namelamp;gt; an instance name known by the listener.

ORA-12520: TNS:listener could not find available handler for requested type of server

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

ORA-12519: TNS:no appropriate service handler found

ORA-12519: TNS:no appropriate service handler found

Cause: The listener could not find any available service handlers that are appropriate for the client connection.

Action: Run lsnrctl services to ensure that the instance(s) have registered with the listener, and are accepting connections.

ORA-12518: TNS:listener could not hand off client connection

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

ORA-12516: TNS:listener could not find available handler with matching protocol stack

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

ORA-12515: TNS:listener could not find a handler for this presentation

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

ORA-12514: TNS:listener does not currently know of service requested in connect descriptor

ORA-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: services lamp;lt;lamp;nbsp;listener namelamp;gt; service name used specifies a service known by the listener. name specified is a service known by the listener.

ORA-12513: TNS:service handler found but it has registered for a different protocol

ORA-12513: TNS:service handler found but it has registered for a different protocol

Cause: The dispatchers registered for this service are connected to the listener by way of a different network protocol than that of the client.

Action: Contact the DBA to register a dispatcher on your protocol.

ORA-12511: TNS:service handler found but it is not accepting connections

ORA-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 or ask him to increase the number of dispatchers.

ORA-12510: TNS:database temporarily lacks resources to handle the request

ORA-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 or dispatchers limit on number of connections or sessions that they can accept.

ORA-12509: TNS:listener failed to redirect client to service handler

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

ORA-12508: TNS:listener could not resolve the COMMAND given

ORA-12508: TNS:listener could not resolve the COMMAND given

Cause: d by incompatible Oracle Net or Net8 versions. Do not include in error manual.

Action: This is not seen in normal use of Oracle Net.

ORA-12505: TNS:listener does not currently know of SID given in connect descriptor

ORA-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: services lamp;lt;lamp;nbsp;listener namelamp;gt; known by the listener.

ORA-12504: TNS:listener was not given the SID in CONNECT_DATA

ORA-12504: TNS:listener was not given the SID in CONNECT_DATA

Cause: The SID was missing from the CONNECT_DATA.

Action: Check that the connect descriptor corresponding to the service name in TNSNAMES.ORA has an SID component in the CONNECT_DATA.

ORA-12502: TNS:listener received no CONNECT_DATA from client

ORA-12502: TNS:listener received no CONNECT_DATA from client

Cause: No CONNECT_DATA was passed to the listener.

Action: Check that the service name resolved from TNSNAMES.ORA has the CONNECT_DATA component of the connect descriptor.

ORA-12500: TNS:listener failed to start a dedicated server process

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

ORA-12497: maximum combined categories exceeds string

ORA-12497: maximum combined categories exceeds string

Cause: The maximum number of descriptive categories plus release categories supported by the MLS policy was exceeded.

Action: Enter numbers that do not add up to more than the maximum.

ORA-12496: cannot change existing level, category, or release numbers

ORA-12496: cannot change existing level, category, or release numbers

Cause: You attempted to change the number assigned to level, category or releasability category.

Action: Change the character string representations, not the numbers.

ORA-12495: cannot disable an enabled level, category, or release category

ORA-12495: cannot disable an enabled level, category, or release category

Cause: You attempted to disable a level, category, or release category that had previously been enabled. An enabled label definition may be exist in some database label, so cannot be disabled.

Action: If the label definition is no longer valid, change its name to one that identifies it as invalid. When any labels are converted to character strings, the new label definition will be used.

ORA-12494: cannot insert or delete a level, category, or release category

ORA-12494: cannot insert or delete a level, category, or release category

Cause: You attempted to insert or delete a level, category, or release category definition.

Action: If the label definition is no longer valid, change its name to one that identifies it as invalid. When any labels are converted to character strings, the new label definition will be used.

ORA-12493: invalid MLS binary label

ORA-12493: invalid MLS binary label

Cause: The MLS binary label contained an invalid value, was not the correct size, or contained a level, category, or release category that was not enabled.

Action: Check the DBA_MLS_LABELS view for the valid MLS labels.

ORA-12492: DBLOW cannot be changed

ORA-12492: DBLOW cannot be changed

Cause: You attempted to change the value of DBLOW after it had been set to any initial value. DBLOW can only be set once after initial database creation.

Action: To change DBLOW, you have to create a new database, set DBLOW to the new value, and import your data into the new database.

ORA-12491: DBHIGH value does not dominate DBLOW

ORA-12491: DBHIGH value does not dominate DBLOW

Cause: You attempted to enter a value for DBHIGH that did not dominate DBLOW.

Action: Enter a value for DBHIGH that dominates DBLOW.

ORA-12490: DBHIGH cannot be lowered

ORA-12490: DBHIGH cannot be lowered

Cause: You attempted to enter a value for DBHIGH that did not dominate the existing value of DBHIGH.

Action: Enter a value for DBHIGH that dominates the old value.

ORA-12489: default label not within clearance range

ORA-12489: default label not within clearance range

Cause: You attempted to enter a value for a default label that did not dominate the minimum clearance or was not dominated by the maximum clearance.

Action: Enter a default label value within the clearance range.

ORA-12488: maximum label does not dominate minimum label

ORA-12488: maximum label does not dominate minimum label

Cause: You attempted to enter a value for a clearance label that did not preserve the dominance relationship between the minimum and maximum labels.

Action: Enter label values that preserves the dominance relationship between the minimum and maximum.

ORA-12487: clearance labels not between DBHIGH and DBLOW

ORA-12487: clearance labels not between DBHIGH and DBLOW

Cause: You attempted to enter a value for a clearance label that was not dominated by DBHIGH or did not dominate DBLOW.

Action: Enter clearance label values between DBHIGH and DBLOW.

ORA-12486: effective max labels and min labels cannot be changed

ORA-12486: effective max labels and min labels cannot be changed

Cause: You attempted to enter a value for an effective min label or effective max label, but these labels cannot be changed.

Action: Enter NULL values for the effective minimum and maximum labels.

ORA-12485: new effective label not within effective clearance

ORA-12485: new effective label not within effective clearance

Cause: You attempted to enter a value for an effective label that did not dominate the effective min label or was not dominated by the effective max label.

Action: Enter a value between the min and the max labels.

ORA-12484: invalid OS label

ORA-12484: invalid OS label

Cause: The specified label does not exist in the OS host s label definition file.

Action: Use the OS label management tools to define the label.

ORA-12483: label not in OS system accreditation range

ORA-12483: label not in OS system accreditation range

Cause: The specified label is above the OS maximum label or below the OS minimum label.

Action: Use a label that is within the accreditation range for the host OS.

ORA-12482: internal MLS error: string Error: string

ORA-12482: internal MLS error: string Error: string

Cause: An internal MLS policy error occurred.

Action: Contact Oracle Customer Support.

ORA-12481: effective label not within program unit clearance range

ORA-12481: effective label not within program unit clearance range

Cause: The effective label when the program unit was invoked was not within the range authorized for the program unit.

Action: Modify the program unit clearance range or invoke the program unit from a session with an authorized effective clearance.

ORA-12480: specified clearance labels not within the effective clearance

ORA-12480: specified clearance labels not within the effective clearance

Cause: You specified a clearance range that was not within your authorized clearance; you can only specify clearance ranges that are within your clearance.

Action: Specify clearance labels that are within your own clearance range.

ORA-12479: file label string must equal DBHIGH string

ORA-12479: file label string must equal DBHIGH string

Cause: A database file had an OS label that did not match DBHIGH. Either DBHIGH was altered or the OS file was relabeled.

Action: Relabel the file so that its label matches DBHIGH, or alter DBHIGH so that it matches the label on the file.

ORA-12477: greatest lower bound resulted in an invalid OS label

ORA-12477: greatest lower bound resulted in an invalid OS label

Cause: You tried to do an operation that generated a greatest lower bound (GLB) label which is not a valid label on your operating system.

Action: Consult your OS label management documentation for information on invalid label generation.

ORA-12476: least upper bound resulted in an invalid OS label

ORA-12476: least upper bound resulted in an invalid OS label

Cause: You tried to do an operation that generated a least upper bound (LUB) label which is not a valid label on your operating system.

Action: Consult your OS label management documentation for information on invalid label generation.

ORA-12473: The procedure is disabled when Label Security is used with OID.

ORA-12473: The procedure is disabled when Label Security is used with OID.

Cause: Using Label Security with OID disabled this procedure.

Action: Do not use OID with Label Security if this procedure is required to function.

ORA-12472: policy string is being used

ORA-12472: policy string is being used

Cause: The policy which was being dropped due to event propagation from OID was applied to some table or schema.

Action: Drop a policy in OID only if it is not used in any of the databases using the policy.

ORA-12471: Specified compartment or group is not authorized for user

ORA-12471: Specified compartment or group is not authorized for user

Cause: The specified compartment or group is not in user s authorizations or the user does not have read on compartment or group specified for write.

Action: Enter an authorized compartment or group.

ORA-12470: NULL or invalid user label: string

ORA-12470: NULL or invalid user label: string

Cause: The label entered is NULL or not within the user s authorizations.

Action: Enter the authorized labels for the user.

ORA-12469: no user levels found for user string and policy string

ORA-12469: no user levels found for user string and policy string

Cause: No levels have been specified for the user.

Action: Enter the maximum and minimum labels for the user.

ORA-12468: max write level does not equal max read level

ORA-12468: max write level does not equal max read level

Cause: The level in the max write label must equal the level in the max read label.

Action: Enter max read and max write labels with the same level component.

ORA-12467: minimum label can contain a level only

ORA-12467: minimum label can contain a level only

Cause: You included compartments or groups in the minimum label.

Action: Enter only an authorized minimum level as the label.

ORA-12466: default level is greater than the user s maximum

ORA-12466: default level is greater than the user s maximum

Cause: The default level cannot be greater than the user s maximum.

Action: Enter an authorized level.

ORA-12465: Not authorized for read or write on specified groups or compartments

ORA-12465: Not authorized for read or write on specified groups or compartments

Cause: You included groups or compartments that are not in the user s list of groups and compartments authorized for read or write access.

Action: Include read access when authorizing groups or compartments for write access.

ORA-12464: invalid characters in label component string

ORA-12464: invalid characters in label component string

Cause: Label components can contain only alphanumeric characters, blanks, and underscores.

Action: Correct syntax of the label component.

ORA-12463: undefined group string for policy string

ORA-12463: undefined group string for policy string

Cause: The specified group is not defined for the policy.

Action: Correct the group identifier value.

ORA-12462: undefined compartment string for policy string

ORA-12462: undefined compartment string for policy string

Cause: The specified compartment is not defined for the policy.

Action: Correct the compartment identifier value.

ORA-12461: undefined level string for policy string

ORA-12461: undefined level string for policy string

Cause: The specified level is not defined for the policy.

Action: Correct the level identifier value.

ORA-12457: security label exceeded maximum allowable length

ORA-12457: security label exceeded maximum allowable length

Cause: An operation attempted to materialize a security label greater than 4000 bytes in length.

Action: Consult the Oracle Label Security documentation for information on how the length of a security label is calculated. Re-submit the operation once the problem has been corrected.

ORA-12456: label security startup in progress

ORA-12456: label security startup in progress

Cause: You attempted to connect to the database before the Oracle Label Security component was fully initialized.

Action: Wait until the database is fully open before attempting to connect.

ORA-12455: internal error in Label Security MMON cleanup task

ORA-12455: internal error in Label Security MMON cleanup task

Cause: An internal error occurred in the Label Security MMON cleanup task.

Action: Contact Oracle Customer Support.

ORA-12454: label string does not exist for policy string

ORA-12454: label string does not exist for policy string

Cause: The label tag or value you entered did not identify a label for the policy.

Action: Enter a label value or tag that is in use by the policy.

ORA-12453: label string already exists

ORA-12453: label string already exists

Cause: The label value you entered already exists.

Action: No action necessary; alter the label to change its tag or type.

ORA-12452: label tag string already exists

ORA-12452: label tag string already exists

Cause: The label tag value you entered is already in use for another label.

Action: Enter a different value for the label tag.

ORA-12451: label not designated as USER or DATA

ORA-12451: label not designated as USER or DATA

Cause: A label is either a DATA label, a USER label, or both DATA and USER.

Action: Enter TRUE for at least DATA or USER.

ORA-12450: LOB datatype disabled in LBAC initialization file

ORA-12450: LOB datatype disabled in LBAC initialization file

Cause: You tried to specify a LOB datatype for a column or attribute, but the use of the LOB datatype has been disabled.

Action: Change the LBAC initialization file to allow the creation of LOB columns and attributes.

ORA-12449: Labels specified for user must be of type USER

ORA-12449: Labels specified for user must be of type USER

Cause: You tried to set labels for a user, but the labels in the list were not all designated as USER labels.

Action: Alter the labels to be USER labels.

ORA-12448: policy string not applied to schema string

ORA-12448: policy string not applied to schema string

Cause: You tried to alter a schema policy that was not applied.

Action: Correct the policy name or schema name.

ORA-12447: policy role already exists for policy string

ORA-12447: policy role already exists for policy string

Cause: The role named lamp;lt;lamp;nbsp;policylamp;gt;_DBA already exists.

Action: Correct the policy name or delete the existing policy.

ORA-12446: Insufficient authorization for administration of policy string

ORA-12446: Insufficient authorization for administration of policy string

Cause: You tried to perform an administrative function for a policy, but you have not been granted the lamp;lt;lamp;nbsp;policylamp;gt;_DBA role.

Action: Grant the user the lamp;lt;lamp;nbsp;policylamp;gt;_DBA role for the specified policy.

ORA-12445: cannot change HIDDEN property of column

ORA-12445: cannot change HIDDEN property of column

Cause: You tried to specify a different HIDE option for a table with an existing policy column.

Action: Drop the column from the table and reapply the policy with the new HIDE option.

ORA-12444: policy already applied to table

ORA-12444: policy already applied to table

Cause: You tried to apply a policy to a table that was already protected by the policy.

Action: To change the policy options, predicate, or label function, remove the policy from the table and re-apply it.

ORA-12443: policy not applied to some tables in schema

ORA-12443: policy not applied to some tables in schema

Cause: You applied a policy to a schema, and some of the tables in the schema already had the policy applied.

Action: No action necessary; the policy was applied to the remaining tables.

ORA-12442: policy column string already used by an existing policy

ORA-12442: policy column string already used by an existing policy

Cause: You tried to create a policy with the same policy column name as an existing policy.

Action: Use a different name for the policy column or drop the existing policy.

ORA-12441: policy string already exists

ORA-12441: policy string already exists

Cause: You tried to create a policy with the same name as an existing one.

Action: Use a different name or drop the existing policy.

ORA-12440: insufficient authorization for the SYSDBA package

ORA-12440: insufficient authorization for the SYSDBA package

Cause: The use of the SYSDBA package requires the LBAC_DBA role.

Action: Grant the LBAC_DBA role to the database user.

ORA-12439: invalid combination of policy options

ORA-12439: invalid combination of policy options

Cause: A set of contradictory policy options was entered.

Action: Provide a set of compatible policy options.

ORA-12438: repeated policy option: string

ORA-12438: repeated policy option: string

Cause: A policy option was entered more than once in the option string.

Action: Remove the duplicate policy option value.

ORA-12437: invalid policy option: string

ORA-12437: invalid policy option: string

Cause: A value that was not a valid policy option was entered.

Action: Correct the policy option value.

ORA-12436: no policy options specified

ORA-12436: no policy options specified

Cause: A NULL option string was specified, but no default schema or policy option string was found.

Action: Enter a valid option string, or alter the schema or policy to have a valid default option string.

ORA-12435: invalid audit success: string

ORA-12435: invalid audit success: string

Cause: The audit success parameter must be SUCCESSFUL or NOT SUCCESSFUL.

Action: Correct the audit success value.

ORA-12434: invalid audit type: string

ORA-12434: invalid audit type: string

Cause: The audit type must be BY ACCESS or BY SESSION.

Action: Correct the audit type value.

ORA-12433: create trigger failed, policy not applied

ORA-12433: create trigger failed, policy not applied

Cause: The policy could not be applied due to errors during the creation of a DML trigger.

Action: Correct the SQL syntax of the label function specification.

ORA-12432: LBAC error: string

ORA-12432: LBAC error: string

Cause: LBAC enforcement resulted in an error.

Action: Correct the problem identified in the error message.

ORA-12431: invalid audit action

ORA-12431: invalid audit action

Cause: The specified audit action was not a valid audit action.

Action: Correct the audit action number.

ORA-12430: invalid privilege number

ORA-12430: invalid privilege number

Cause: The specified privilege number was not between 1 and 32.

Action: Correct the privilege number.

ORA-12429: label list range exceeded

ORA-12429: label list range exceeded

Cause: The specified index value was not between 1 and 6.

Action: Correct the index value for the label list operation.

ORA-12427: invalid input value for string parameter

ORA-12427: invalid input value for string parameter

Cause: An input parameter was specified incorrectly.

Action: Correct the parameter value.

ORA-12426: invalid audit option

ORA-12426: invalid audit option

Cause: The option specified was not a valid audit option for the specified policy.

Action: Enter a correct audit option.

ORA-12425: cannot apply policies or set authorizations for system schemas

ORA-12425: cannot apply policies or set authorizations for system schemas

Cause: You tried to either apply a policy to the SYS, SYSTEM, or LBACSYS schema or to set user labels or privileges for the SYS, SYSTEM, or LBACSYS user.

Action: Apply policies and set authorizations only for non-system users.

ORA-12424: length exceeds binary label size

ORA-12424: length exceeds binary label size

Cause: The length specified for a binary label operation exceeded the the size of the binary label.

Action: Provide a bit or byte length that is within the label size limits.

ORA-12423: invalid position specified

ORA-12423: invalid position specified

Cause: The position specified for a binary label operation was invalid.

Action: Provide a position that is within the label size limits.

ORA-12422: max policies exceeded

ORA-12422: max policies exceeded

Cause: You tried to create a new policy, but the maximum number of policies for the instance had already been created.

Action: Increase the size of the MAX_LABEL_POLICIES initialization parameter and restart the server.

ORA-12421: different size binary labels

ORA-12421: different size binary labels

Cause: The label sizes for the binary label operation were not equal.

Action: Provide binary labels with the same lengths for the operation.

ORA-12420: required procedures and functions not in policy package string

ORA-12420: required procedures and functions not in policy package string

Cause: The policy package did not contain all of the procedures and functions necessary to enforce the policy.

Action: Consult the label framework documentation for a list of required procedures and functions for a policy package.

ORA-12419: null binary label value

ORA-12419: null binary label value

Cause: A null value was provided for a binary label operation.

Action: Provide a valid binary label for the operation.

ORA-12418: user string not found

ORA-12418: user string not found

Cause: The specified user does not exist in the database.

Action: Correct the user name or create the user.

ORA-12417: database object string not found

ORA-12417: database object string not found

Cause: The specified object was not in the database.

Action: Enter the correct name for the database object.

ORA-12416: policy string not found

ORA-12416: policy string not found

Cause: The specified policy does not exist in the database.

Action: Enter the correct policy name or create the policy.

ORA-12415: A column of another datatype exists on the specified table

ORA-12415: A column of another datatype exists on the specified table

Cause: The datatype of the column present in the table is different from the datatype set for the policy column.

Action: Drop the column on the table or change the datatype for policy column.

ORA-12414: internal LBAC error: string Error: string

ORA-12414: internal LBAC error: string Error: string

Cause: An internal label policy framework error occurred.

Action: Contact Oracle Customer Support.

ORA-12413: labels do not belong to the same policy

ORA-12413: labels do not belong to the same policy

Cause: The labels being compared belong to different policies.

Action: Only compare labels that belong to the same policy.

ORA-12412: policy package string is not installed

ORA-12412: policy package string is not installed

Cause: The policy package does not exist in the database.

Action: Check that the policy package name is correct or install the required policy package.

ORA-12411: invalid label value

ORA-12411: invalid label value

Cause: The specified label value does not exist.

Action: Check the data dictionary views for the policy to identify valid labels.

ORA-12410: internal policy error for policy: string Error: string

ORA-12410: internal policy error for policy: string Error: string

Cause: The policy enforcement encountered an internal error.

Action: Consult the policy documentation for details.

ORA-12409: policy startup failure for string policy

ORA-12409: policy startup failure for string policy

Cause: The policy encountered an error during startup processing; access to the data protected by the policy is prohibited.

Action: Check the alert log for additional information, correct the policy error, and restart the instance.

ORA-12408: unsupported operation: string

ORA-12408: unsupported operation: string

Cause: The specified policy does not support the requested operation.

Action: Consult the policy documentation to determine the supported access mediation operations.

ORA-12407: unauthorized operation for policy string

ORA-12407: unauthorized operation for policy string

Cause: The policy did not authorize the database session to perform the requested operation.

Action: Grant the user or program unit the necessary policy privilege or additional authorizations.

ORA-12406: unauthorized SQL statement for policy string

ORA-12406: unauthorized SQL statement for policy string

Cause: The policy did not authorize the database session to perform the requested SQL statement.

Action: Grant the user or program unit the necessary policy privilege or additional authorizations.

ORA-12405: invalid label list

ORA-12405: invalid label list

Cause: The policy determined that the label list was invalid for its intended use.

Action: Check the policy constraints on the specific list of labels.

ORA-12404: invalid privilege string: string

ORA-12404: invalid privilege string: string

Cause: The policy could not interpret the privilege string.

Action: Specify a privilege string that is supported by the policy.

ORA-12403: invalid internal label

ORA-12403: invalid internal label

Cause: An internal label could not be converted to a valid label for the policy.

Action: Analyze any additional messages on the error stack and consult the policy documentation.

ORA-12402: invalid format string: string

ORA-12402: invalid format string: string

Cause: The format string is not supported by the policy.

Action: Correct the syntax of the format string.

ORA-12401: invalid label string: string

ORA-12401: invalid label string: string

Cause: The policy could not convert the label string to a valid internal label.

Action: Correct the syntax of the label string.

ORA-12400: invalid argument to facility error handling

ORA-12400: invalid argument to facility error handling

Cause: An argument to a facility error handling function exceeded a maximum limit or referred to an invalid product or facility.

Action: Specify a valid facility error handling parameter value.

ORA-12354: secondary object being dropped

ORA-12354: secondary object being dropped

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.

ORA-12353: secondary stored object cannot reference remote object

ORA-12353: secondary stored object cannot reference remote object

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.

ORA-12352: object string.stringstring is invalid

ORA-12352: object string.stringstring is invalid

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.

ORA-12351: cannot create view using a remote object which has a remote object reference

ORA-12351: cannot create view using a remote object which has a remote object reference

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.

ORA-12350: database link being dropped is still mounted

ORA-12350: database link being dropped is still mounted

Cause: An attempt was made to drop a ROM: database link that was still mounted and or or opened.

Action: Close and dismount the database and then re-issue the drop statement.

ORA-12345: user string lacks CREATE SESSION privilege in database link (linkname string)

ORA-12345: user string lacks CREATE SESSION privilege in database link (linkname string)

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.

ORA-12342: open mounts exceeds limit set on the OPEN_MOUNTS parameter

ORA-12342: open mounts exceeds limit set on the OPEN_MOUNTS parameter

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.

ORA-12341: maximum number of open mounts exceeded

ORA-12341: maximum number of open mounts exceeded

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.

ORA-12336: cannot login to database (link name string)

ORA-12336: cannot login to database (link name string)

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.

ORA-12335: database (link name string) is not open

ORA-12335: database (link name string) is not open

Cause: You attempted to close a database that is not open.

Action: The database is closed; you can proceed with dismounting it.

ORA-12334: database (link name string) is still open

ORA-12334: database (link name string) is still open

Cause: You attempted to dismount a database that is still open.

Action: Close the database with the ALTER DATABASE lamp;lt;lamp;nbsp;linknamelamp;gt; CLOSE command, then re-attempt to dismount the database.

ORA-12333: database (link name string) is not mounted

ORA-12333: database (link name string) is not mounted

Cause: You attempted to open a database that has not been mounted.

Action: Mount the database with the ALTER DATABASE lamp;lt;lamp;nbsp;linknamelamp;gt; MOUNT command, then re-attempt to open the database.

ORA-12329: database string is closed; no operations are permitted

ORA-12329: database string is closed; no operations are permitted

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.

ORA-12326: database string is closing immediately; no operations are permitted

ORA-12326: database string is closing immediately; no operations are permitted

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.

ORA-12324: cannot use the ROM: link type on a private database link

ORA-12324: cannot use the ROM: link type on a private database link

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.

ORA-12323: unable to open database (link name string)

ORA-12323: unable to open database (link name string)

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.

ORA-12322: unable to mount database (link name string)

ORA-12322: unable to mount database (link name string)

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.

ORA-12321: database (link name string) is not open and AUTO_ MOUNTING=FALSE

ORA-12321: database (link name string) is not open and AUTO_ MOUNTING=FALSE

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 lamp;lt;lamp;nbsp;linknamelamp;gt; 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.

ORA-12319: database (link name string) is already open

ORA-12319: database (link name string) is already open

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.

ORA-12318: database (link name string) is already mounted

ORA-12318: database (link name string) is already mounted

Cause: You are attempting to mount a secondary database that has already been mounted by your instance.

Action: to mount it. To establish access, use the ALTER DATABASE lamp;lt;lamp;nbsp;linknamelamp;gt; OPEN command to open the database.

ORA-12317: logon to database (link name string) denied

ORA-12317: logon to database (link name string) denied

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 or 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.

ORA-12316: syntax error in database link s connect string

ORA-12316: syntax error in database link s connect string

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.

ORA-12315: database link type is invalid for the ALTER DATABASE statement

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.

ORA-12236: TNS:protocol support not loaded

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

ORA-12235: TNS:Failure to redirect to destination

ORA-12235: TNS:Failure to redirect to destination

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.

ORA-12234: TNS:Redirect to destination

ORA-12234: TNS:Redirect to destination

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.

ORA-12233: TNS:Failure to accept a connection

ORA-12233: TNS:Failure to accept a connection

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.

ORA-12232: TNS:No path available to destination

ORA-12232: TNS:No path available to destination

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.

ORA-12231: TNS:No connection possible to destination

ORA-12231: TNS:No connection possible to destination

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.

ORA-12230: TNS:Severe Network error occurred in making this connection

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

ORA-12229: TNS:Interchange has no more free connections

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

ORA-12228: TNS:protocol adapter not loadable

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

ORA-12227: TNS:syntax error

ORA-12227: TNS:syntax error

Cause: The supplied connect descriptor contains illegal syntax.

Action: Check the syntax of the connect descriptor in TNSNAMES.ORA.

ORA-12226: TNS:operating system resource quota exceeded

ORA-12226: TNS:operating system resource quota exceeded

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.

ORA-12225: TNS:destination host unreachable

ORA-12225: TNS:destination host unreachable

Cause: Contact can not be made with remote party.

Action: Make sure the network driver is functioning and the network is up.

ORA-12224: TNS:no listener

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

ORA-12223: TNS:internal limit restriction exceeded

ORA-12223: TNS:internal limit restriction exceeded

Cause: Too many TNS connections open simultaneously.

Action: Wait for connections to close and re-try.

ORA-12222: TNS:no support is available for the protocol indicated

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

ORA-12221: TNS:illegal ADDRESS parameters

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

ORA-12219: TNS:missing community name from address in ADDRESS_LIST

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

ORA-12218: TNS:unacceptable network configuration data

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

ORA-12217: TNS:could not contact PREFERRED_CMANAGERS in TNSNAV.ORA

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

ORA-12216: TNS:poorly formed PREFERRED_CMANAGERS addresses in TNSNAV.ORA

ORA-12216: TNS:poorly formed PREFERRED_CMANAGERS addresses 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.

ORA-12215: TNS:poorly formed PREFERRED_NAVIGATORS Addresses in TNSNAV.ORA

ORA-12215: TNS:poorly formed PREFERRED_NAVIGATORS Addresses in TNSNAV.ORA

Cause: Address binding for PREFERRED_NAVIGATORS entry is improperly entered. entry.

Action: Check your PREFERRED_NAVIGATORS entry and fix it in TNSNAV.ORA

ORA-12214: TNS:missing local communities entry in TNSNAV.ORA

ORA-12214: TNS:missing local communities entry in TNSNAV.ORA

Cause: There is no LOCAL_COMMUNITIES entry in TNSNAV.ORA.

Action: Define the LOCAL_COMMUNITIES for this node in the TNSNAV.ORA file.

ORA-12213: TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA

ORA-12213: TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA

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.

ORA-12212: TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA

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

ORA-12211: TNS:needs PREFERRED_CMANAGERS entry in TNSNAV.ORA

ORA-12211: TNS:needs PREFERRED_CMANAGERS entry in TNSNAV.ORA

Cause: TNSNAV.ORA does not have a PREFERRED_CMANAGERS defined.

Action: Add a PREFERRED_CMANAGERS entry to the TNSNAV.ORA file.

ORA-12210: TNS:error in finding Navigator data

ORA-12210: TNS:error in finding Navigator data

Cause: Application calling navigation routine has not properly configured the TNSNAV.ORA file.

Action: Check the syntax of the TNSNAV.ORA file.

ORA-12209: TNS:encountered uninitialized global

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

ORA-12208: TNS:could not find the TNSNAV.ORA file

ORA-12208: TNS:could not find the TNSNAV.ORA file

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.

ORA-12207: TNS:unable to perform navigation

ORA-12207: TNS:unable to perform navigation

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.

ORA-12206: TNS:received a TNS error during navigation

ORA-12206: TNS:received a TNS error during navigation

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.

ORA-12205: TNS:could not get failed addresses

ORA-12205: TNS:could not get failed addresses

Cause: Internal navigation error.

Action: Not normally visible to the user. For further details contact Worldwide Customer Support.

ORA-12204: TNS:received data refused from an application

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

ORA-12203: TNS:unable to connect to destination

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

ORA-12202: TNS:internal navigation error

ORA-12202: TNS:internal navigation error

Cause: Internal navigation error.

Action: Not normally visible to the user. For further details contact Worldwide Customer Support.

ORA-12201: TNS:encountered too small a connection buffer

ORA-12201: TNS:encountered too small a connection buffer

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.

ORA-12200: TNS:could not allocate memory

ORA-12200: TNS:could not allocate memory

Cause: Out of memory on machine.

Action: Reconfigure machine to have more storage or run fewer applications while the Interchange is running.

ORA-12198: TNS:could not find path to destination

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

ORA-12197: TNS:keyword-value resolution error

ORA-12197: TNS:keyword-value resolution 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.

ORA-12196: TNS:received an error from TNS

ORA-12196: TNS:received an error from TNS

Cause: The navigation layer received an error from TNS.

Action: See the error log file for the specific TNS error.

ORA-12171: TNS:could not resolve connect identifier: string

ORA-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) accessible. 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). is configured in the directory. 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). Administrators Guide or the Oracle operating system specific guide for more information on naming.

ORA-12170: TNS:Connect timeout occurred

ORA-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 or IP).

ORA-12169: TNS:Net service name given as connect identifier is too long

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

ORA-12168: TNS:Unable to contact LDAP Directory Server

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

ORA-12166: TNS:Client can not connect to HO agent.

ORA-12166: TNS:Client can not connect to HO agent.

Cause: NVstring contained DESCRIPTION or HO.

Action: Call HO agent from integrating server.

ORA-12165: TNS:Trying to write trace file into swap space.

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

ORA-12164: TNS:Sqlnet.fdf file not present

ORA-12164: TNS:Sqlnet.fdf file not present

Cause: The sqlnet.fdf file doesn t exist in $ORACLE_HOME or network or admin.

Action: The sqlnet.fdf file is required for Oracle Tracing to occur. Either install the sqlnet.fdf file in $ORACLE_HOME or network or admin or turn off tracing in your ORA file.