12C ORA-错误汇总10 ORA-12500 to ORA-19400

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-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-12503: TNS:listener received an invalid REGION from client
Cause: Invalid REGION was passed to the listener.
Action: Check the REGION name specified in the CONNECT_DATA component
of the connect descriptor.
ORA-12504: TNS:listener was not given the SERVICE_NAME in CONNECT_DATA
Cause: The listener was not configured with a default service and SERVICE_
NAME was missing from the CONNECT_DATA received by the listener.
Action: Possible solutions are:
- Configure DEFAULT_SERVICE parameter in LISTENER.ORA with a valid
service name. Reload the listener parameter file using reload [<listener_name>].
This should be done by the LISTENER administrator.
- If using a service name, Check that the connect descriptor corresponding to the
service name in TNSNAMES.ORA has a SERVICE_NAME or SID component in
the CONNECT_DATA.
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.
12-2 Oracle Database Error Messages
Action:
- Wait a moment and try to connect a second time.
- Check which instances are currently known by the listener by executing: lsnrctl
services <listener name>
- Check that the SID parameter in the connect descriptor specifies an instance
known by the listener.
- Check for an event in the listener.log file.
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-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-12510: TNS:database temporarily lacks resources to handle the request
Cause: The dispatchers appear to be busy handling other requests.
Action: Attempt the connection again. If error persists, ask the DBA to increase
the number of dispatchers and/or dispatchers' limit on number of
connections/sessions that they can accept.
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 ask him to increase the number of dispatchers.
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-12514: TNS:listener does not currently know of service requested in connect
descriptor
Cause: The listener received a request to establish a connection to a database or
other service. The connect descriptor received by the listener specified a service
name for a service (usually a database service) that either has not yet dynamically
registered with the listener or has not been statically configured for the listener.
This may be a temporary condition such as after the listener has started, but before
the database instance has registered with the listener.
Action:
- Wait a moment and try to connect a second time.
- Check which services are currently known by the listener by executing: lsnrctl
services <listener name>
ORA-12500 to ORA-12699 12-3
- Check that the SERVICE_NAME parameter in the connect descriptor of the net
service name used specifies a service known by the listener.
- If an easy connect naming connect identifier was used, check that the service
name specified is a service known by the listener.
- Check for an event in the listener.log file.
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-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-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-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-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-12521: TNS:listener does not currently know of instance requested in connect
descriptor
Cause: The listener received a request to establish a connection to a database or
other service. The connect descriptor received by the listener specified in addition
to the service name an instance name for an instance (usually a database instance)
that either has not yet dynamically registered with the listener or has not been
statically configured for the listener. This may be a temporary condition such as
after the listener has started, but before the database instance has registered with
the listener.
Action:
- Wait a moment and try to connect a second time.
12-4 Oracle Database Error Messages
- Check which instances are currently known by the listener by executing: lsnrctl
services <listener name>
- Check that the INSTANCE_NAME parameter in the connect descriptor specifies
an instance name known by the listener.
- Check for an event in the listener.log file.
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-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-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-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-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-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.
ORA-12500 to ORA-12699 12-5
Action: Attempt the connection again. If error persists, then contact the database
administrator to check the status of the instances.
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-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-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-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-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-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-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-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.
12-6 Oracle Database Error Messages
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-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-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-12540: TNS:internal limit restriction exceeded
Cause: Too many TNS connections open simultaneously.
Action: Wait for connections to close and re-try.
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-12542: TNS:address already in use
Cause: Specified listener address is already being used.
Action: Start your listener with a unique address.
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-12544: TNS:contexts have different wait/test functions
Cause: Two protocol adapters have conflicting wait/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-12545: Connect failed because target host or object does not exist
Cause: The address specified is not valid, or the program being connected to does
not exist.
Action: Ensure the ADDRESS parameters have been entered correctly; the most
likely incorrect parameter is the node name. Ensure that the executable for the
server exists (perhaps "oracle" is missing.) If the protocol is TCP/IP, edit the
TNSNAMES.ORA file to change the host name to a numeric IP address and try
again.
ORA-12500 to ORA-12699 12-7
ORA-12546: TNS:permission denied
Cause: User has insufficient privileges to perform the requested operation.
Action: Acquire necessary privileges and try again.
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-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-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-12550: TNS:syntax error
Cause: The supplied connect descriptor contains illegal syntax.
Action: Check the syntax of the connect descriptor in TNSNAMES.ORA.
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-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-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-12555: TNS:permission denied
Cause: User has insufficient privileges to perform the requested operation.
Action: Acquire necessary privileges and try again.
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-12557: TNS:protocol adapter not loadable
Cause: On some platforms (such as OS/2) protocol adapters are loaded at
run-time. If the shared library (or DLL) for the protocol adapter is missing or one
of its supporting libraries is missing then this error is returned.
12-8 Oracle Database Error Messages
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-12558: TNS:protocol adapter not loaded
Cause: On some platforms (such as OS/2) protocol adapters are loaded at
run-time. If the shared library (or DLL) for the protocol adapter has not been
loaded, then this error is returned.
Action: For further details, turn on tracing and reexecute the operation. The trace
file will have the name of the shared library (or DLL) that has not been loaded.
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-12561: TNS:unknown error
Cause: A generic protocol error occurred.
Action: For further details, turn on tracing and reexecute the operation.
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-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-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-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-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-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-12574: TNS:redirection denied
ORA-12500 to ORA-12699 12-9
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-12575: TNS:dhctx busy
Cause: The handoff over a dhctx failed as dhctx was already busy with an
ongoing handoff.
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-12576: TNS:handoff not supported for this session
Cause: Handoff of a established session was attempted which either had tcps as
its transport or NA options were enabled for this session.
Action: Check the transport setting as well as NA options. If error persists, contact
Oracle Customer Support.
ORA-12578: TNS:wallet open failed
Cause: An error was encountered while trying to open the specified wallet.
Action: For further details, turn on tracing and re-execute the 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-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-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-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-12590: TNS:no I/O buffer
Cause: An attempt to perform an I/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-12591: TNS:event signal failure
Cause: The TNS software is unable to signal an event occurrence.
12-10 Oracle Database Error Messages
Action: For further details, turn on tracing and reexecute the operation. If error
persists, contact Oracle Customer Support.
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-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-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-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-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-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-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-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-12601: TNS:information flags check failed
Cause: The TNS information flags set by the process prior to connection
negotiation were not present after the negotiation was finished.
Action: This is an internal error. Enable tracing and attempt to repeat the error. If
it occurs again, contact Oracle Customer Support.
ORA-12500 to ORA-12699 12-11
ORA-12602: TNS: Connection Pooling limit reached
Cause: The operation failed because maximum active current connections has
been reached. It may not be a real error when the Connection Pooling feature is
enabled. It is possible that the application later reissues the operation and
successfully grabs the connection pool slot and proceeds.
Action: This is an internal error. Enable tracing and attempt to repeat the error. If
it occurs again, contact Oracle Customer Support.
ORA-12606: TNS: Application timeout occurred
Cause: A network session did not reach an application-defined stage within the
allowed time interval.
Action: This is an error which does not normally appear at the high level. The
action to take is application specific, and is detailed in the higher level error
description.
ORA-12607: TNS: Connect timeout occurred
Cause: A network session did not reach a predefined connect stage within the
allowed time interval.
Action: This is an error which does not normally appear at the high level. The
action to take is application specific, and is detailed in the higher level error
description.
ORA-12608: TNS: Send timeout occurred
Cause: The send or write operation did not complete within the allowed time
interval.
Action: Check if the peer host is available. Increase the send timeout value if
necessary.
ORA-12609: TNS: Receive timeout occurred
Cause: The receive or read operation did not complete within the allowed time
interval.
Action: Check if the peer host is available. Increase the receive timeout value if
necessary.
ORA-12611: TNS:operation is not portable
Cause: Attempted operation is not portable.
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-12612: TNS:connection is busy
Cause: Attempted operation failed because it conflicts with an ongoing
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-12615: TNS:preempt error
Cause: A request to service an event failed because no event notification has yet
been posted.
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-12616: TNS:no event signals
Cause: The operation failed because the type of data specified is unknown.
12-12 Oracle Database Error Messages
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-12618: TNS:versions are incompatible
Cause: The two machines are running incompatible versions of TNS.
Action: Check the version numbers, and upgrade the machine with the smaller
one.
ORA-12619: TNS:unable to grant requested service
Cause: The connect request failed because requested service could not be
provided by the local TNS software.
Action: If appropriate, reexecute with reduced service requirements.
ORA-12620: TNS:requested characteristic not available
Cause: The connect request failed because a requested transport characteristic
could not be supported by the remote TNS software.
Action: If appropriate, reexecute with reduced requirements.
ORA-12622: TNS:event notifications are not homogeneous
Cause: An attempt to register a connection for event notification failed because
the event notification type conflicts with existing registrations.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation and contact Oracle Customer Support.
ORA-12623: TNS:operation is illegal in this state
Cause: Connection is half-duplex and a full-duplex operation was attempted.
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-12624: TNS:connection is already registered
Cause: An attempt to register a connection for event notification failed because
the connection is already registered.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation and contact Oracle Customer Support.
ORA-12625: TNS:missing argument
Cause: An operation failed because an argument was missing"
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation and contact Oracle Customer Support.
ORA-12626: TNS:bad event type
Cause: An attempt to register a connection for event notification failed because
the event type is unknown.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation and contact Oracle Customer Support.
ORA-12628: TNS:no event callbacks
Cause: An attempt to register a connection for event notification failed because
asynchronous callbacks are not available.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation and contact Oracle Customer Support.
ORA-12500 to ORA-12699 12-13
ORA-12629: TNS:no event test
Cause: An attempt to register a connection for event notification failed because
the ability to test for events is not available.
Action: Not normally visible to the user. For further details, turn on tracing and
reexecute the operation and contact Oracle Customer Support.
ORA-12630: Native service operation not supported
Cause: An operation requested by a user is not supported by the native services
component.
Action: This may be an internal error if the operation should have been
supported.
ORA-12631: Username retrieval failed
Cause: The authentication service failed to retrieve the name of a user.
Action: Enable tracing to determine which routine is failing.
ORA-12632: Role fetch failed
Cause: The authentication service failed to retrieve one of the user's roles.
Action: Enable tracing to determine which routine is failing.
ORA-12633: No shared authentication services
Cause: The list of authentication services specified by the user does not match
those supported by the process.
Action: Either specify another list or relink the executable with the desired
services.
ORA-12634: Memory allocation failed
Cause: Process was unable to allocate memory.
Action: Terminate other processes in order to reclaim needed memory.
ORA-12635: No authentication adapters available
Cause: The executable was not linked with any authentication service adapters
but the sqlnet.ora parameter that determines whether or not authentication is
required was set to true.
Action: Either disable the parameter or relink the executable with service
adapters.
ORA-12636: Packet send failed
Cause: A process was unable to send a packet to another process. Possible causes
are:
1. The other process was terminated.
2. The machine on which the other process is running went down.
3. Some other communications error occurred.
Action: If the cause is not obvious, contact Oracle Customer Support.
ORA-12637: Packet receive failed
Cause: A process was unable to receive a packet from another process. Possible
causes are:
1. The other process was terminated.
2. The machine on which the other process is running went down.
12-14 Oracle Database Error Messages
3. Some other communications error occurred.
Action: If the cause is not obvious, contact Oracle Customer Support.
ORA-12638: Credential retrieval failed
Cause: The authentication service failed to retrieve the credentials of a user.
Action: Enable tracing to determine the exact error.
ORA-12639: Authentication service negotiation failed
Cause: No match was found between the types of authentication services that the
client supports and those that the server is using.
Action: Possible solutions:
1. Change the entry in sqlnet.ora that determines which services are to be used.
2. Relink the client with at least one of the authentication service adapters that the
server supports.
3. Relink the server with at least one of the authentication service adapters that the
client supports.
4. Disable authentication on both the client and server.
ORA-12640: Authentication adapter initialization failed
Cause: The function specified in the authentication table entry for the service
failed.
Action: Enable tracing to determine the exact error.
ORA-12641: Authentication service failed to initialize
Cause: The authentication service failed during initialization.
Action: Enable tracing to determine the exact error.
ORA-12642: No session key
Cause: A process has no session key associated with it because the authentication
service being used does not use one.
Action: If a session key is required, use another authentication service.
ORA-12643: Client received internal error from server
Cause: The client process received an error from the server that indicated that an
internal Oracle Net native services error had occurred.
Action: Enable tracing on both processes and attempt to recreate the problem. If
successful in recreating the problem, contact Oracle Customer Support.
ORA-12645: Parameter does not exist.
Cause: A sqlnet.ora parameter from which a value was needed does not exist.
Action: Set the parameter in the parameter file.
ORA-12646: Invalid value specified for boolean parameter
Cause: The value specified for a parameter was set to a value other than
true/false or on/off.
Action: Correct the value of the parameter.
ORA-12647: Authentication required
Cause: The parameter that controls whether authentication is required was set to
true, but the executable does not have an authentication service linked in.
ORA-12500 to ORA-12699 12-15
Action: Either re-link the executable with an authentication service adapter or
disable the parameter.
ORA-12648: Encryption or data integrity algorithm list empty
Cause: A list-of-algorithms parameter was empty, e.g. "()".
Action: Change the list to contain the name of at least one installed algorithm, or
remove the list entirely if every installed algorithm is acceptable.
ORA-12649: Unknown encryption or data integrity algorithm
Cause: A list-of-algorithms parameter included an algorithm name that was not
recognized.
Action: Either remove that algorithm name, correct it if it was misspelled, or
install the driver for the missing algorithm.
ORA-12650: No common encryption or data integrity algorithm
Cause: The client and server have no algorithm in common for either encryption
or data integrity or both.
Action: Choose sets of algorithms that overlap. In other words, add one of the
client's algorithm choices to the server's list or vice versa.
ORA-12651: Encryption or data integrity algorithm unacceptable
Cause: The algorithm the server chose to use for encryption or data integrity was
not one of the choices acceptable to the client. This is either the result of an internal
error, of a network data transmission error, or of deliberate tampering with the
transmitted data.
Action: For further details, turn on tracing, re-execute the operation, and contact
Oracle Customer Support.
ORA-12652: String truncated
Cause: Not enough memory was allocated for a string so it had to be truncated
Action: If it is OK that the string is truncated, then it is not an error. Otherwise,
call the routine that reported the error again with a larger string buffer.
ORA-12653: Authentication control function failed
Cause: The control function utilized by the authentication service driver failed.
Action: Enable tracing to determine the exact error.
ORA-12654: Authentication conversion failed
Cause: The authentication service was unable to convert the credentials of a user
from the format specific to the format into the ORACLE format.
Action: Enable tracing to determine the exact error.
ORA-12655: Password check failed
Cause: The authentication service being used was unable to verify the provided
password.
Action: Enable tracing to determine the exact error.
ORA-12656: Cryptographic checksum mismatch
Cause: The cryptographic checksum received with a packet of incoming data
didn't match the checksum computed by the receiving end. This indicates that the
packet was tampered with or otherwise corrupted in transit.
12-16 Oracle Database Error Messages
Action: Look for sources of data corruption, perhaps including deliberate
tampering.
ORA-12657: No algorithms installed
Cause: The near side of the connection required the use of a service (either
encryption or checksumming) when no algorithms for that service were installed.
Action: Remove the "ON" requirement for that service.
ORA-12658: ANO service required but TNS version is incompatible
Cause: A client process that is running an earlier version of TNS attempted to
connect but the connection failed because the server process required that an ANO
service (authentication, encryption, etc.) be used.
Action: Relink the calling executable and retry the connection or eliminate the
requirement that the service be used on the server side.
ORA-12659: Error received from other process
Cause: An error was received by one or more services from the process on the
other side of the connection.
Action: Enable tracing to determine the exact error(s). The error(s) is (are) not
returned directly because an error generated by a server may not make sense on
the client side and vice-versa.
ORA-12660: Encryption or crypto-checksumming parameters incompatible
Cause: One side of the connection specified "REQUIRED" for encryption or
crypto-checksumming, while the other side specified "REJECTED".
Action: Change the "REQUIRED" side to "REQUESTED" if the you want
encryption or crypto-checksumming to be optional, or change the "REJECTED"
side to "ACCEPTED" if you do not want the service to be optional.
ORA-12661: Protocol authentication to be used
Cause: The authentication service has determined that the Oracle Net transport
protocol in use is to be utilized to authenticate a user's identity.
Action: This error is used solely to communicate information between the
authentication service and the Oracle Net session layer and should not normally
be visible. If the error is seen, contact Oracle Worldwide Support.
ORA-12662: proxy ticket retrieval failed
Cause: The authentication adapter used by Oracle Net failed to retrieve the
credentials needed to authenticate a database link.
Action: Enable tracing to determine the exact error.
ORA-12663: Services required by client not available on the server
Cause: Service(s) that was (were) required by the client process were not available
on the server process.
Action: Configure the server with the services required by the client (best
solution) or delete the requirement from the configuration file of the client (least
secure).
ORA-12664: Services required by server not available on the client
Cause: Service(s) that was (were) required by the server process were not
available on the client process.
ORA-12500 to ORA-12699 12-17
Action: Configure the client with the services required by the server (best
solution) or delete the requirement from the configuration file of the server (least
secure).
ORA-12665: NLS string open failed
Cause: A native service was unable to make a string available for use by the
National Language Support component.
Action: Make sure the National Language Support component has been properly.
If it has, enable tracing and report the problem to Customer Support.
ORA-12666: Dedicated server: outbound transport protocol different from inbound
Cause: The protocol specified for an externally-identified outbound connection
from a dedicated server (database link) was not the same as that used for the
inbound connection. It is not possible for Oracle Net to authenticate a proxy
connection that uses a protocol that is different from that which was used for the
connection to the dedicated server.
Action: Specify the same protocol in the Oracle Net connect descriptor for the
outbound connection as that used for the inbound connection.
ORA-12667: Shared server: outbound transport protocol different from inbound
Cause: The protocol specified for an externally-identified outbound connection
from a shared server (database link) was not the same as as that used for the
inbound connection. It is not possible for Oracle Net to authenticate a proxy
connection that uses a protocol that is different from that which was used for the
connection to the shared server.
Action: Specify the same protocol in the Oracle Net connect descriptor for the
outbound connection as that used for the inbound connection
ORA-12668: Dedicated server: outbound protocol does not support proxies
Cause: The protocol specified to perform an externally-identified proxy
connection (database link) from a dedicated server does not support proxy
connections.
Action: Specify a protocol in the Oracle Net connect descriptor used for the
connection that does support externally-authenticated proxy connections. NOTE:
Because of a limitation in Oracle Net, the protocol used for the proxy connection
must the same as that used for the connection from the client to the server.
ORA-12669: Shared server: outbound protocol does not support proxies
Cause: The protocol specified to perform an externally-identified proxy
connection (database link) from a shared server does not support proxy
connections.
Action: Specify a protocol in the Oracle Net connect descriptor used for the
connection that does support externally-authenticated proxy connections. NOTE:
Because of a limitation in Oracle Net, the protocol used for the proxy connection
must the same as that used for the connection from the client to the server.
ORA-12670: Incorrect role password
Cause: A password supplied for a role could not be validated by the
authentication service.
Action: Supply the correct password.
ORA-12671: Shared server: adapter failed to save context
12-18 Oracle Database Error Messages
Cause: The adapter for the authentication service failed when it tried to save the
data needed for proxy connections (database links) through the shared server.
Action: Enable tracing to determine the exact error. Contact Oracle Customer
Support if the reason is not obvious.
ORA-12672: Database logon failure
Cause: The authentication service adapter in use encountered an error it
attempted to validate the logon attempt of a user.
Action: Enable tracing to determine the exact error encountered by the adapter.
ORA-12673: Dedicated server: context not saved
Cause: A connection was marked as being a proxy connection (database link)
from a dedicated server but no inbound context was present.
Action: This error should not normally be visible to the user. Contact Oracle
Customer Support.
ORA-12674: Shared server: proxy context not saved
Cause: A connection was marked as being a proxy connection (database link)
from a shared server but no inbound context was present.
Action: This error should not normally be visible to the user. Contact Oracle
Customer Support.
ORA-12675: External user name not available yet
Cause: The authentication service in use was not able to return the external name
of a user of the ORACLE server because it is not available to the service yet.
Action: This is just an informational message and should not normally be visible
to the user. If the error does appear, contact Oracle Customer Support.
ORA-12676: Server received internal error from client
Cause: The server process received an error from the client which indicated that
an internal Oracle Net native services error had occurred.
Action: Enable tracing on both processes and attempt to recreate the problem. If
the problem recurs, contact Oracle Customer Support.
ORA-12677: Authentication service not supported by database link
Cause: The authentication service used by the proxy process (database link) was
unable to find the adapter being used by the client in its list of authentication
mechanisms.
Action: Specify an authentication adapter that is shared by the client and the
server being used for the database link.
ORA-12678: Authentication disabled but required
Cause: The configuration parameters that control whether authentication is
disabled or required were both set to TRUE.
Action: Set one or both of the parameters to FALSE.
ORA-12679: Native services disabled by other process but required
Cause: The remote process has disabled native services but the local process
requires them.
Action: Enable native services on the remote process or disable them locally.
ORA-12680: Native services disabled but required
ORA-12500 to ORA-12699 12-19
Cause: The process has disabled native services but at least one service is
required.
Action: Enable native services or change the configuration file so that none of the
available services are required.
ORA-12681: Login failed: the SecurID card does not have a pincode yet
Cause: The SecurID card that is used to logon to Oracle, does not have a pincode
assigned to it.
Action: Use one of the programs supplied by Security Dynamics to assign a
pincode to the card.
ORA-12682: Login failed: the SecurID card is in next PRN mode
Cause: The SecurID card and the SecurID server are out of sync and the server
requires the next cardcode to resynchronize the card.
Action: Use one of the programs supplied by Security Dynamics to resynchronize
the SecurID card.
ORA-12683: encryption/crypto-checksumming: no Diffie-Hellman seed
Cause: The "sqlnet.crypto_seed" parameter is missing from the SQLNET.ORA
parameters file.
Action: Add this line to SQLNET.ORA: sqlnet.crypto_seed = "randomly-chosen
text"
ORA-12684: encryption/crypto-checksumming: Diffie-Hellman seed too small
Cause: The "sqlnet.crypto_seed" parameter in the SQLNET.ORA parameter file is
too small.
Action: Add more randomly-chosen text to it, perhaps using Network Manager.
ORA-12685: Native service required remotely but disabled locally
Cause: A native service is required by the remote process but native services have
been disabled locally.
Action: Enable native services locally or change the configuration parameters on
the remote host so that no native services are required.
ORA-12686: Invalid command specified for a service
Cause: An operation which does not exist was specified for a native service.
Action: This is a programming error and should not normally be visible to the
user. If the error does appear, contact Oracle Customer Support.
ORA-12687: Credentials expired.
Cause: The credentials that are used to authenticate the user for the requested
connection have expired.
Action: Renew your credentials. Refer to the documentation specific for your
Network Authentication Adapter on how to do this.
ORA-12688: Login failed: the SecurID server rejected the new pincode
Cause: There are a number of reasons why the SecurID server would refuse a
pincode:
- The user might not have permission to make up his own pincode.
- The pincode was either too short or too long. Valid pincodes consist of minimal
four, but no more than eight characters.
12-20 Oracle Database Error Messages
- The pincode contains any non alphanumeric characters.
Action: Reexecute the operation and make sure to use a pincode that satisfies the
above requirements. If the problem persists, turn on tracing at the Oracle Server
side of the connection and examine the trace file for the exact error.
ORA-12689: Server Authentication required, but not supported
Cause: Server Authentication is required for this connection, but not supported by
both sides of the connection.
Action: Make sure both sides of the connection have the correct version of
Advanced Networking Option, and that the Authentication Adapter supports
Server Authentication.
ORA-12690: Server Authentication failed, login cancelled
Cause: Server Authentication is required, but the server's credentials were found
invalid by the client.
Action: Make sure that the server has a valid set of credentials. Refer to your
authentication adapter specific documentation on how to do this.
ORA-12696: Double Encryption Turned On, login disallowed
Cause: The user is using a Secure Protocol Adapter that has Encryption turned
ON as well as ANO Encryption.
Action: Turn OFF either ANO Encryption or the Protocol Adapter Encryption if
possible. Refer to the Administrator's Guide on how to do this.
ORA-12699: Native service internal error
Cause: An internal error occurred in the native services component.
Action: Enable tracing to determine the exact error. Contact Oracle Customer
Support.
ORA-12700 to ORA-19400 3 1
ORA-12700: invalid NLS parameter value (string)
Cause: An invalid or unknown NLS configuration parameter was specified.
Action: None
ORA-12701: CREATE DATABASE character set is not known
Cause: The character set specified when creating the database is unknown.
Action: None
ORA-12702: invalid NLS parameter string used in SQL function
Cause: An unknown parameter name or invalid value is specified in a NLS
parameter string.
Action: None
ORA-12703: this character set conversion is not supported
Cause: The requested conversion between two character sets in the CONVERT
function is not implemented
Action: None
ORA-12704: character set mismatch
Cause: One of the following:
- The string operands(other than an nlsparams argument) to an operator or
built-in function do not have the same character set.
- An nlsparams operand is not in the database character set.
- String data with character set other than the database character set is passed to a
built-in function not expecting it.
- The second argument to CHR() or CSCONVERT() is not CHAR_CS or NCHAR_
CS.
- A string expression in the VALUES clause of an INSERT statement, or the SET
clause of an UPDATE statement, does not have the same character set as the
column into which the value would be inserted.
- A value provided in a DEFAULT clause when creating a table does not have the
same character set as declared for the column.
- An argument to a PL/SQL function does not conform to the character set
requirements of the corresponding parameter.
Action: None
13-2 Oracle Database Error Messages
ORA-12705: Cannot access NLS data files or invalid environment specified
Cause: Either an attempt was made to issue an ALTER SESSION command with
an invalid NLS parameter or value; or the environment variable(s) NLS_LANG,
ORA_NLSxx, or ORACLE_HOME was incorrectly specified, therefore the NLS
data files cannot be located.
Action: Check the syntax of the ALTER SESSION command and the NLS
parameter, correct the syntax and retry the statement, or specify the correct
directory path/values in the environment variables.
ORA-12706: this CREATE DATABASE character set is not allowed
Cause: It is not allowed to create a database on a native ASCII-based machine
using an EBCDIC-based character set, and vice versa.
Action: None
ORA-12707: error while getting create database NLS parameter string
Cause: Internal error
Action: None
ORA-12708: error while loading create database NLS parameter string
Cause: Internal error
Action: None
ORA-12709: error while loading create database character set
Cause: Internal error
Action: None
ORA-12710: CREATE CONTROLFILE character set is not known
Cause: The character set specified when creating the control file is unknown.
Action: None
ORA-12711: this CREATE CONTROLFILE character set is not allowed
Cause: It is not allowed to create a control file on a native ASCII-based machine
using an EBCDIC-based character set, and vice versa.
Action: None
ORA-12712: new character set must be a superset of old character set
Cause: When you ALTER DATABASE ... CHARACTER SET, the new character set
must be a superset of the old character set. For example, WE8ISO8859P1 is not a
superset of the WE8DEC.
Action: Specify a superset character set.
ORA-12713: Character data loss in NCHAR/CHAR conversion
Cause: When character set conversion happens between CHAR and NCHAR
either implicitly or explicitly, some characters are lost due to no mapping
characters in the destination character set.
Action: Make sure all the characters can be mapped to destination character set or
set NLS_NCHAR_CONV_EXCP to be FALSE.
ORA-12714: invalid national character set specified
Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national
character set
Action: Ensure that the specified national character set is valid
ORA-12700 to ORA-19400 13-3
ORA-12715: invalid character set specified
Cause: The character set specified is not allowed for this operation or is invalid
Action: Ensure that the specified character set is valid
ORA-12716: Cannot ALTER DATABASE CHARACTER SET when CLOB data
exists
Cause: CLOB data changes representation to Unicode when converting to a
multibyte character set and must be migrated
Action: Remove CLOB data as listed in the alert file. CLOB data can be migrated
by methods such as import/export
ORA-12717: Cannot issue ALTER DATABASE NATIONAL CHARACTER SET
when NCLOB, NCHAR or NVARCHAR2 data exists
Cause: NCLOB, NCHAR or NVARCHAR2 data changed the representation to
Unicode when converting to a multibyte character set and must be migrated.
Action: Remove NCLOB, NCHAR or NVARCHAR2 data as listed in the alert file.
The above type data can be migrated by methods such as import/export.
ORA-12718: operation requires connection as SYS
Cause: This command can only be run when connecting as SYS
Action: Connect as SYS to run this command
ORA-12719: operation requires database is in RESTRICTED mode
Cause: This command can only be run when the database is in RESTRICTED
mode
Action: Ensure that the system is in RESTRICTED mode
ORA-12720: operation requires database is in EXCLUSIVE mode
Cause: This command can only be run when the database is in EXCLUSIVE mode
Action: Ensure that the system is in EXCLUSIVE mode
ORA-12721: operation cannot execute when other sessions are active
Cause: This command can only be run when there are no other sessions active
Action: Ensure there are no other connections to the database
ORA-12722: regular expression internal error
Cause: A regular expression internal error occurred.
Action: This is an internal error. Contact Oracle Support Services.
ORA-12723: regular expression too complex
Cause: The regular expression was too complex and could not be parsed.
Action: This is an internal error. Contact Oracle Support Services.
ORA-12724: regular expression corrupt
Cause: The regular expression contained an incorrect sequence of metacharacters.
Action: Ensure the metacharacters are correctly positioned.
ORA-12725: unmatched parentheses in regular expression
Cause: The regular expression did not have balanced parentheses.
Action: Ensure the parentheses are correctly balanced.
ORA-12726: unmatched bracket in regular expression
13-4 Oracle Database Error Messages
Cause: The regular expression did not have balanced brackets.
Action: Ensure the brackets are correctly balanced.
ORA-12727: invalid back reference in regular expression
Cause: A back references was found before a sub-expression.
Action: Ensure a valid sub-expression is being referenced.
ORA-12728: invalid range in regular expression
Cause: An invalid range was found in the regular expression.
Action: Ensure a valid range is being used.
ORA-12729: invalid character class in regular expression
Cause: An unknown character class was found in the regular expression.
Action: Ensure a valid characters class is being used.
ORA-12730: invalid equivalence class in regular expression
Cause: An unknown equivalence class was found in the regular expression.
Action: Ensure a valid equivalence class is being used.
ORA-12731: invalid collation class in regular expression
Cause: An unknown collation class was found in the regular expression.
Action: Ensure a valid collation class is being used.
ORA-12732: invalid interval value in regular expression
Cause: An invalid interval value was found in the regular expression.
Action: Ensure a valid interval value is being used.
ORA-12733: regular expression too long
Cause: The operation failed because the regular expression it used exceeds the
maximum supported size.
Action: Use a shorter regular expression.
ORA-12734: Instant Client Light: unsupported client national character set string
Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national
character set. Instant Client Light has only minimal character sets.
Action: Do not use Instant Client Light for this character set
ORA-12735: Instant Client Light: unsupported client character set string
Cause: The character set specified is not allowed for this operation or is invalid.
Instant Client Light has only minimal character sets.
Action: Do not use Instant Client Light for this character set
ORA-12736: Instant Client Light: unsupported server national character set string
Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national
character set. Instant Client Light has only minimal character sets.
Action: Do not use Instant Client Light for this character set
ORA-12737: Instant Client Light: unsupported server character set string
Cause: The character set specified is not allowed for this operation or is invalid.
Instant Client Light has only minimal character sets.
Action: Do not use Instant Client Light for this character set
ORA-12700 to ORA-19400 13-5
ORA-12738: Express Instant Client: unsupported client national character set string
Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national
character set. Instant Client has only minimal character sets.
Action: Do not use Express Instant Client for this character set
ORA-12739: Express Instant Client: unsupported client character set string
Cause: The character set specified is not allowed for this operation or is invalid.
Express Instant Client has only minimal character sets.
Action: Do not use Express Instant Client for this character set
ORA-12740: Express Instant Client: unsupported server national character set string
Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national
character set. Instant Client has only minimal character sets.
Action: Do not use Express Instant Client for this character set
ORA-12741: Express Instant Client: unsupported server character set string
Cause: The character set specified is not allowed for this operation or is invalid.
Express Instant Client has only minimal character sets.
Action: Do not use Express Instant Light for this character set
ORA-12742: unable to create the collation key
Cause: The character argument of a collation-sensitive operator was too long or it
had too many decomposable characters to create a collation key for it in the
available buffer space.
Action: Shorten the argument value or, if using a UCA-based collation, increase
the ratio of characters with short or no Unicode decomposition to characters with
long Unicode decomposition in the value.
ORA-12743: internal LX error code, arguments: [string], [string], [string]
Cause: This is an internal error in a globalization support function.
Action: Contact Oracle Support Services.
ORA-12744: Character set string is not allowed as a database character set.
Cause: An attempt was made to create or alter a database using a client-only or
conversion-only character set.
Action: Specify a supported database character set.
ORA-12752: An instance-critical process has terminated.
Cause: An unexpected error was encountered by an instance-critical process.
Action: Contact Oracle Support Services.
ORA-12753: The Oracle home user ID does not match the effective user ID of the
local client which connected to the Oracle instance.
Cause: The user ID that is the owner of the Oracle home directory was not the
same as the effective user ID of the local client that connected to the Oracle
instance.
Action: Run the local client that connects to Oracle instance with the same user ID
as the owner of the Oracle home.
ORA-12800: system appears too busy for parallel query execution
Cause: load on system is too high to perform parallel queries.
Action: re-execute serially or wait until system load is reduced.
13-6 Oracle Database Error Messages
ORA-12801: error signaled in parallel query server string
Cause: A parallel query server reached an exception condition.
Action: Check the following error message for the cause, and consult your error
manual for the appropriate action.
ORA-12802: parallel query server lost contact with coordinator
Cause: A parallel query server lost contact with the foreground (coordinator)
process/thread.
Action: Check your system for anomalies and reissue the statement. If this error
persists, contact Oracle Support Services.
ORA-12803: parallel query server lost contact with another server
Cause: A parallel query server lost contact with another server.
Action: Check your system for anomalies and reissue the statement. If this error
persists, contact Oracle Support Services.
ORA-12804: parallel query server appears to have died
Cause: Cannot find process information for a parallel query server thread.
Action: Check your system for anomalies and reissue the statement. If this error
persists, contact Oracle Support Services.
ORA-12805: parallel query server died unexpectedly
Cause: A parallel query server died unexpectedly, PMON cleaning up the process.
Action: Check your system for anomalies and reissue the statement. If this error
persists, contact Oracle Support Services. See trace file for more details.
ORA-12806: could not get background process to hold enqueue
Cause: Internal error.
Action: This error should not normally occur. If it persists, contact Oracle Support
Services.
ORA-12807: process queue could not receive parallel query message
Cause: Internal error.
Action: This error should not normally occur. If it persists, contact Oracle Support
Services.
ORA-12808: cannot set string_INSTANCES greater than number of instances string
Cause: An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES
using the ALTER SYSTEM command to a value larger than the number of
available instances.
Action: See the accompanying message for the current allowable maximum value,
or set SCAN_INSTANCES / CACHE_INSTANCES to ALL.
ORA-12809: cannot set string_INSTANCES when mounted in exclusive mode
Cause: An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES
using the ALTER SYSTEM command while the database was mounted in
exclusive mode.
Action: SCAN_INSTANCES / CACHE_INSTANCES may not be set unless
running Oracle Real Application Clusters mounted in CLUSTER_DATABASE
mode.
ORA-12810: PARALLEL_MAX_SERVERS must be less than or equal to string
ORA-12700 to ORA-19400 13-7
Cause: An attempt was made to set the PARALLEL_MAX_SERVERS parameter to
a value higher than the maximum allowed by the system.
Action: Set PARALLEL_MAX_SERVERS to a value less than or equal to the
maximum specified in the accompanying message and retry.
ORA-12811: PARALLEL_MIN_SERVERS must be less than or equal to PARALLEL_
MAX_SERVERS, string
Cause: An attempt was made to set the PARALLEL_MIN_SERVERS parameter to
a value higher than PARALLEL_MAX_SERVERS.
Action: Set PARALLEL_MIN_SERVERS to a value less than or equal to
PARALLEL_MAX_SERVERS (indicated in the accompanying message) and retry.
ORA-12812: only one PARALLEL or NOPARALLEL clause may be specified
Cause: PARALLEL was specified more than once, NOPARALLEL was specified
more than once, or both PARALLEL and NOPARALLEL were specified in a
CREATE TABLE, CLUSTER, or INDEX or in an ALTER TABLE or CLUSTER
statement, or in a RECOVER command.
Action: Remove all but one of the PARALLEL or NOPARALLEL clauses and
reissue the statement.
ORA-12813: value for PARALLEL or DEGREE must be greater than 0
Cause: PARALLEL 0 or DEGREE 0 was specified in a CREATE TABLE, CLUSTER,
or INDEX or in an ALTER TABLE or CLUSTER statement.
Action: Specify a degree of parallelism greater than 0 or specify default
parallelism using PARALLEL with no degree or using DEGREE DEFAULT within
a PARALLEL clause.
ORA-12814: only one CACHE or NOCACHE clause may be specified
Cause: CACHE was specified more than once, NOCACHE was specified more
than once, or both CACHE and NOCACHE were specified in a CREATE TABLE or
CLUSTER, or in an ALTER TABLE or CLUSTER statement.
Action: Remove all but one of the CACHE or NOCACHE clauses and reissue the
statement.
ORA-12815: value for INSTANCES must be greater than 0
Cause: PARALLEL parameter specifying number of instances must be a positive
integer or DEFAULT
Action: specify a positive integer or DEFAULT for INSTANCES if parallelism
across instances is desired.
ORA-12817: parallel query option must be enabled
Cause: A parallel query option feature has been invoked but this option has not
been enabled.
Action: Enable the parallel query option.
ORA-12818: invalid option in PARALLEL clause
Cause: an unrecognized option was used within a PARALLEL clause.
Action: specify any combination of DEGREE { <n> | DEFAULT } and
INSTANCES { <n> | DEFAULT } within the PARALLEL clause.
ORA-12819: missing options in PARALLEL clause
Cause: PARALLEL clause cannot be empty.
13-8 Oracle Database Error Messages
Action: specify any combination of DEGREE { <n> | DEFAULT } and
INSTANCES { <n> | DEFAULT } within the PARALLEL clause.
ORA-12820: invalid value for DEGREE
Cause: invalid value for DEGREE was specified within a PARALLEL clause.
Action: specify a positive integer or DEFAULT for the DEGREE option within a
PARALLEL clause.
ORA-12821: invalid value for INSTANCES
Cause: invalid value for INSTANCES was specified within a PARALLEL clause.
Action: specify a positive integer or DEFAULT for the INSTANCES option within
a PARALLEL clause.
ORA-12822: duplicate option in PARALLEL clause
Cause: DEGREE or INSTANCES was specified more than once within a
PARALLEL clause.
Action: specify each desired PARALLEL clause option only once.
ORA-12823: default degree of parallelism may not be specified here
Cause: the PARALLEL keyword was used alone or DEGREE DEFAULT was
specified in the PARALLEL clause of an ALTER DATABASE RECOVER command.
Action: respecify with an explicit degree of parallelism.
ORA-12824: INSTANCES DEFAULT may not be specified here
Cause: INSTANCES DEFAULT was specified in the PARALLEL clause of an
ALTER DATABASE RECOVER command
Action: respecify with an explicit value for INSTANCES or omit the INSTANCES
option if single instance recovery is desired.
ORA-12825: explicit degree of parallelism must be specified here
Cause: the DEGREE option was omitted from an ALTER DATABASE RECOVER
command.
Action: respecify with an explicit degree of parallelism.
ORA-12826: hung parallel query server was killed
Cause: parallel query server was hung and subsequently killed.
Action: re-execute query and report suspicious events in trace file to Oracle
Support Services if error persists.
ORA-12827: insufficient parallel query slaves (requested string, available string,
parallel_min_percent string)
Cause: PARALLEL_MIN_PERCENT parameter was specified and fewer than the
minimum number of slaves were acquired
Action: Either reexecute the query with a lower PARALLEL_MIN_PERCENT or
wait until some running queries are completed, thus freeing up slaves
ORA-12828: Can't start parallel transaction at a remote site
Cause: PDML transaction cannot be started because we are not in the coordinator
site of the distributed transaction.
Action: Do not use PDML at remote sites.
ORA-12829: Deadlock - itls occupied by siblings at block string of file string
ORA-12700 to ORA-19400 13-9
Cause: parallel statement failed because all itls in the current block are occupied
by siblings of the same transaction.
Action: increase MAXTRANS of the block or reduce the degree of parallelism for
the statement. Reexecute the statement. Report suspicious events in trace file to
Oracle Support Services if error persists.
ORA-12830: Must COMMIT or ROLLBACK after executing parallel
INSERT/UPDATE/DELETE
Cause: After executing a parallel INSERT/UPDATE/DELETE statement, a
command other than COMMIT or ROLLBACK was issued.
Action: Execute COMMIT or ROLLBACK before issuing another SQL command.
ORA-12831: Must COMMIT or ROLLBACK after executing INSERT with APPEND
hint
Cause: After executing an INSERT statement with an APPEND hint, a command
other than COMMIT or ROLLBACK was issued.
Action: Execute COMMIT or ROLLBACK before issuing another SQL command.
ORA-12832: Could not allocate slaves on all specified instances
Cause: After executing a query on a global v$ fixed view, one or more instances
failed to allocate a slave to process query
Action: To allow results to be returned by sucessfully allocated slaves, execute
ALTER SESSION SET ALLOW_PARTIAL_SN_RESULTS=TRUE statement, or
check parameters of instances
ORA-12833: Coordinator's instance not a member of parallel_instance_group
Cause: The coordinator's instance must be a member of the parallel_instance_
group in which this operation will be run.
Action: Either add the coordinator's instance to the current parallel_instance_
group or change parallel_instance_group.
ORA-12834: Instance group name, 'string', too long, must be less than string
characters
Cause: The instance group name is too long.
Action: Either shorten the name or get rid of the instance group.
ORA-12835: No instances are active in the GLOBAL_VIEW_ADMIN_GROUP
Cause: There must be at least one instance in the GLOBAL_VIEW_ADMIN_
GROUP in order to execute a query on global views
Action: Change the value of GLOBAL_VIEW_ADMIN_GROUP
ORA-12838: cannot read/modify an object after modifying it in parallel
Cause: Within the same transaction, an attempt was made to add read or
modification statements on a table after it had been modified in parallel or with
direct load. This is not permitted.
Action: Rewrite the transaction, or break it up into two transactions: one
containing the initial modification and the second containing the parallel
modification operation.
ORA-12839: cannot modify an object in parallel after modifying it
Cause: Within the same transaction, an attempt was made to perform parallel
modification operations on a table after it had been modified. This is not
permitted.
13-10 Oracle Database Error Messages
Action: Rewrite the transaction or break it up into two transactions: one
containing the parallel modification and the second containing the initial
modification operation.
ORA-12840: cannot access a remote table after parallel/insert direct load txn
Cause: Within a transaction, an attempt was made to perform distributed access
after a PDML or insert direct statement had been issued.
Action: Commit/rollback the PDML transaction first, and then perform the
distributed access, or perform the distributed access before the first PDML
statement in the transaction.
ORA-12841: Cannot alter the session parallel DML state within a transaction
Cause: Transaction in progress
Action: Commit or rollback transaction and then re-execute
ORA-12842: Cursor invalidated during parallel execution
Cause: The cursor was invalidated during the parse phase of deferred parallel
processing, e.g. when set operands are parallelized.
Action: Depends on why the cursor was invalidated. Possible causes include DDL
on a schema object and shared pool being flushed.
ORA-12843: pdml lock not held properly on the table
Cause: The coodinator crashed or released the lock on the partition which the
slave is trying to aquire currently.
Action: Check if the coordinator or some of the other slaves died. Also check that
the lock has not been corrupted. Issue the pdml again.
ORA-12844: cluster reconfiguration in progress
Cause: Internal error
Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT
NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR
INTERNAL ERROR.
ORA-12845: failed to receive interinstance parallel execution message
Cause: OS or interconnect problem receiving interinstance message
Action: Check OS specific diagnostics
ORA-12850: Could not allocate slaves on all specified instances: string needed,
string allocated
Cause: When executing a query on a gv$ fixed view, one or more instances failed
to allocate a slave to process query.
Action: Check trace output for instances on which slaves failed to start. GV$
query can only proceed if slaves can be allocated on all instances.
ORA-12851: PARALLEL_MAX_SERVERS must be greater than or equal to
PARALLEL_MIN_SERVERS, string
Cause: An attempt was made to set the PARALLEL_MAX_SERVERS parameter to
a value less than PARALLEL_MIN_SERVERS.
Action: Set PARALLEL_MAX_SERVERS to a value greater than or equal to
PARALLEL_MIN_SERVERS value specified in the accompanying message and
retry.
ORA-12852: PARALLEL_MIN_SERVERS must be less than PROCESSES, string
ORA-12700 to ORA-19400 13-11
Cause: An attempt was made to set the PARALLEL_MIN_SERVERS parameter to
a value higher than PROCESSES.
Action: Set PARALLEL_MIN_SERVERS to a value less than PROCESSES value
specified in the accompanying message and retry.
ORA-12853: insufficient memory for PX buffers: current stringK, max needed
stringK
Cause: Insufficient SGA memory for PX buffers
Action: Reconfigure sga to include at least (max - current) bytes of additional
memory
ORA-12854: Parallel query is not supported on temporary LOBs
Cause: The parallel query statement produced a temporary LOB.
Action: Turn off parallelism for the query or underlying table
ORA-12855: cannot run parallel or insert direct load in a loopback
Cause: A loopback was created in the transaction before this operation.
Action: Do not use loopback when using pdml or insert direct load.
ORA-12856: cannot run parallel query on a loopback connection
Cause: A table or index in a parallel query is referenced via a loopback
connection.
Action: Do not use loopback connection when running a query in parallel.
ORA-12872: First slave parse gave different plan
Cause: First hard parse on slave given QC-supplied environment and parameters
gave different plan from QC. Try again with outline.
Action: No external action. Internally used for outline-based reparse.
ORA-12874: parallel execution monitor terminated with error
Cause: The parallel execution monitor process died.
Action: Wait for the process to restart.
ORA-12899: value too large for column string (actual: string, maximum: string)
Cause: An attempt was made to insert or update a column with a value which is
too wide for the width of the destination column. The name of the column is
given, along with the actual width of the value, and the maximum allowed width
of the column. Note that widths are reported in characters if character length
semantics are in effect for the column, otherwise widths are reported in bytes.
Action: Examine the SQL statement for correctness. Check source and destination
column data types. Either make the destination column wider, or use a subset of
the source column (i.e. use substring).
ORA-12900: must specify a default temporary tablespace for a locally managed
database
Cause: a locally managed database must have a temporary tablespace other than
SYSTEM tablespace
Action: specify the default temporary tablespace when creating a locally managed
database
ORA-12901: default temporary tablespace must be of TEMPORARY type
13-12 Oracle Database Error Messages
Cause: in a locally managed database, default temporary tablespace must be
TEMPORARY type
Action: None
ORA-12902: default temporary tablespace must be SYSTEM or of TEMPORARY
type
Cause: in a dictionary managed database, default temporary tablespace must be
SYSTEM or TEMPORARY type
Action: None
ORA-12910: cannot specify temporary tablespace as default tablespace
Cause: attempt to assign a temporary tablespace to be a user's default tablespace
Action: assign a permanent tablespace to be the default tablespace
ORA-12911: permanent tablespace cannot be temporary tablespace
Cause: attempt to assign a permanent tablespace to be a user's temporary
tablespace
Action: assign a temporary tablespace to be user's temporary tablespace
ORA-12912: Dictionary managed tablespace specified as temporary tablespace
Cause: attempt to assign a dictionary managed tablespace to be a user's
temporary tablespace
Action: Assign a locally managed temporary tablespace to be user's temporary
tablespace
ORA-12913: Cannot create dictionary managed tablespace
Cause: Attemp to create dictionary managed tablespace in database which has
system tablespace as locally managed
Action: Create a locally managed tablespace.
ORA-12914: Cannot migrate tablespace to dictionary managed type
Cause: Attemp to migrate locally managed tablespace to dictionary managed type
when the database has locally managed system tablespace.
Action: Command cannot be issued.
ORA-12915: Cannot alter dictionary managed tablespace to read write
Cause: Attemp to alter dictionary managed tablespace to read write in database
which has system tablespace as locally managed. This tablespace can only be
dropped.
Action: Command cannot be issued.
ORA-12916: cannot shrink permanent or dictionary managed tablespace
Cause: An attempt was made to shrink a permanent tablespace or a dictionary
managed tablespace.
Action: Check the tablespace type and issue the statement only on locally
managed temporary tablespaces.
ORA-12918: Invalid tablespace type for default permanent tablespace
Cause: The tablespace is either dropped, temporary or undo
Action: Check the tablespace type and reissue the statement
ORA-12919: Can not drop the default permanent tablespace
ORA-12700 to ORA-19400 13-13
Cause: An attemp was made to drop the default permanent tablespace
Action: Make a different tablespace as the default permanent tablespace and
reissue the drop
ORA-12920: database is already in force logging mode
Cause: ALTER DATABASE FORCE LOGGING command failed because the
database is already in force logging mode.
Action: None
ORA-12921: database is not in force logging mode
Cause: ALTER DATABASE NO FORCE LOGGING command failed because the
database is not in force logging mode.
Action: None
ORA-12922: concurrent ALTER DATABASE [NO] FORCE LOGGING command is
running
Cause: There is a concurrent ALTER DATABASE FORCE LOGGING or ALTER
DATABASE NO FORCE LOGGING command running in the system.
Action: Contact the database administrator who is responsible for the concurrent
command.
ORA-12923: tablespace string is in force logging mode
Cause: An attempt to alter the specified tablespace temporary failed because the
tablespace is in force logging mode.
Action: Put the tablespace out of force logging mode by ALTER TABLESPACE
NO FORCE LOGGING command.
ORA-12924: tablespace string is already in force logging mode
Cause: An attempt to alter the specified tablespace into force logging mode failed
because it is already in force logging mode.
Action: None
ORA-12925: tablespace string is not in force logging mode
Cause: An attempt to alter the specified tablespace out of force logging mode
failed because it is not in force logging mode.
Action: None
ORA-12926: FORCE LOGGING option already specified
Cause: In CREATE TABLESPACE, the FORCE LOGGING option was specified
more than once.
Action: Remove all but one of the FORCE LOGGING options.
ORA-12927: RETENTION option already specified
Cause: In CREATE TABLESPACE, the RETENTION option was specified more
than once.
Action: Remove all but one of the RETENTION options.
ORA-12928: ENCRYPTION option already specified
Cause: In CREATE TABLESPACE, the ENCRYPTION option was specified more
than once.
Action: Remove all but one of the ENCRYPTION options.
13-14 Oracle Database Error Messages
ORA-12931: FORCE LOGGING or SET STANDBY NOLOGGING already
specified
Cause: FORCE LOGGING or SET STANDBY NOLOGGING options were
specified more than once.
Action: Remove all but one of the FORCE LOGGING or SET STANDBY
NOLOGGING options.
ORA-12940: Not enough space in DBVerify text buffer
Cause: DBVerify ran out of text buffer. The error was trapped internally by the
system. DBVerify would return the result in text buffer and then resume checking.
Action: None
ORA-12941: DBVerify exception
Cause: DBVerify encountered run-time error. The error signal was trapped
internally by the system.
Action: None
ORA-12950: SYSTEM tablespace specified as default permanent tablespace
Cause: SYSTEM tablespace was specified as the default permanent during
database creation.
Action: If default permanent tablespace is not specified,then SYSTEM will
implicitly become the default permanent tablespace. Specify an alternate
tablespace or omit the default tablespace clause and reissue the CREATE
DATABASE statement
ORA-12951: Attempt to change default permanent tablespace to temporary
Cause: It is incorrect to alter the default permanent tablespace of a database to
temporary type
Action: None
ORA-12980: checkpoint option not allowed with SET UNUSED
Cause: An attempt was made to specify checkpoint option with SET UNUSED.
Action: Remove checkpoint option.
ORA-12981: cannot drop column from an object type table
Cause: An attempt was made to drop a column from an object type table.
Action: This action is not allowed.
ORA-12982: cannot drop column from a nested table
Cause: An attempt was made to drop a column from a nested table.
Action: This action is not allowed.
ORA-12983: cannot drop all columns in a table
Cause: An attempt was made to drop all columns in a table.
Action: Make sure at least one column remains in the table after the drop column
operation.
ORA-12984: cannot drop partitioning column
Cause: An attempt was made to drop a column used as the partitioning key.
Action: This action is not allowed.
ORA-12985: tablespace 'string' is read only, cannot drop column
ORA-12700 to ORA-19400 13-15
Cause: An attempt was made to drop column from a partition/subpartition on a
read only tablespace.
Action: Set the tablespace to read write and resubmit statement.
ORA-12986: columns in partially dropped state. Submit ALTER TABLE DROP
COLUMNS CONTINUE
Cause: An attempt was made to access a table with columns in partially dropped
state (i.e., drop column operation was interrupted).
Action: Submit ALTER TABLE DROP COLUMNS CONTINUE to complete the
drop column operation before accessing the table.
ORA-12987: cannot combine drop column with other operations
Cause: An attempt was made to combine drop column with other ALTER TABLE
operations.
Action: Ensure that drop column is the sole operation specified in ALTER TABLE.
ORA-12988: cannot drop column from table owned by SYS
Cause: An attempt was made to drop a column from a system table.
Action: This action is not allowed
ORA-12989: invalid value for checkpoint interval
Cause: An invalid checkpoint interval specified in statement. Checkpoint interval
must be between 0 and (2^31-1).
Action: Correct checkpoint interval and resubmit statement
ORA-12990: duplicate option specified
Cause: Duplicate option specified in statement.
Action: Remove the duplicate option and resubmit statement.
ORA-12991: column is referenced in a multi-column constraint
Cause: An attempt was made to drop a column referenced by some constraints.
Action: Drop all constraints referencing the dropped column or specify
CASCADE CONSTRAINTS in statement.
ORA-12992: cannot drop parent key column
Cause: An attempt was made to drop a parent key column.
Action: Drop all constraints referencing the parent key column, or specify
CASCADE CONSTRAINTS in statement.
ORA-12993: tablespace 'string' is offline, cannot drop column
Cause: An attempt was made to drop a column from a partition/subpartition on
an offline tablespace.
Action: Bring the tablespace online and resubmit statement.
ORA-12994: drop column option only allowed once in statement
Cause: An attempt was made to repeat the drop column option in a single
statement.
Action: Separate drop column options into different statements and resubmit
statements.
ORA-12995: no columns in partially dropped state
13-16 Oracle Database Error Messages
Cause: An attempt was made to submit DROP COLUMNS CONTINUE statement
while there are no partially dropped columns.
Action: Cannot submit this statement.
ORA-12996: cannot drop system-generated virtual column
Cause: An attempt was made to drop a virtual column generated by the system.
Action: None
ORA-12997: cannot drop primary key column from an index-organized table
Cause: An attempt was made to drop a primary key column from an indexorganized table.
Action: This action is not allowed.
ORA-12999: cannot DROP or SET UNUSED a column that has been set unused
Cause: An attempt was made to DROP or SET UNUSED a column that has
already been 'set unused'.
Action: Use the DROP UNUSED COLUMNS option to remove the column.
ORA-13000: dimension number is out of range
Cause: The specified dimension is either smaller than 1 or greater than the
number of dimensions encoded in the HHCODE.
Action: Make sure that the dimension number is between 1 and the maximum
number of dimensions encoded in the HHCODE.
ORA-13001: dimensions mismatch error
Cause: The number of dimensions in two HHCODEs involved in a binary
HHCODE operation do not match.
Action: Make sure that the number of dimensions in the HHCODEs match.
ORA-13002: specified level is out of range
Cause: The specified level is either smaller than 1 or greater than the maximum
level encoded in an HHCODE.
Action: Verify that all levels are between 1 and the maximum number of levels
encoded in the HHCODE.
ORA-13003: the specified range for a dimension is invalid
Cause: The specified range for a dimension is invalid.
Action: Make sure that the lower bound (lb) is less than the upper bound (ub).
ORA-13004: the specified buffer size is invalid
Cause: The buffer size for a function is not valid.
Action: This is an internal error. Contact Oracle Support Services.
ORA-13005: recursive HHCODE function error
Cause: An error occurred in a recursively called HHCODE function.
Action: This is an internal error. Contact Oracle Support Services.
ORA-13006: the specified cell number is invalid
Cause: The cell identifier is either less than 0 or greater than (2^ndim - 1).
Action: Make sure that the cell identifier is between 0 and (2^ndim - 1).
ORA-13007: an invalid HEX character was detected
ORA-12700 to ORA-19400 13-17
Cause: A character that is not in the range [0-9] or [A-F a-f] was detected.
Action: Verify that all characters in a string are in [0-9] or [A-F a-f].
ORA-13008: the specified date format has an invalid component
Cause: Part of specified date format is invalid.
Action: Verify that the date format is valid.
ORA-13009: the specified date string is invalid
Cause: The specified date string has a bad component or does not match the
specified format string.
Action: Make sure that the components of the date string are valid and that the
date and format strings match.
ORA-13010: an invalid number of arguments has been specified
Cause: An invalid number of arguments was specified for an SDO function.
Action: Verify the syntax of the function call.
ORA-13011: value is out of range
Cause: A specified dimension value is outside the range defined for that
dimension.
Action: Make sure that all values to be encoded are within the defined dimension
range.
ORA-13012: an invalid window type was specified
Cause: An invalid window type was specified.
Action: Valid window types are RANGE, PROXIMITY, POLYGON.
ORA-13013: the specified topology was not INTERIOR or BOUNDARY
Cause: A topology was specified that was not INTERIOR or BOUNDARY.
Action: Make sure that INTERIOR or BOUNDARY is used to describe an
HHCODE's topology.
ORA-13014: a topology identifier outside the range of 1 to 8 was specified
Cause: A topology identifier outside the range of 1 to 8 was specified.
Action: Specify a topology in the range of 1 to 8.
ORA-13015: the window definition is not valid
Cause: The number of values used to define the window does not correspond to
the window type.
Action: Verify that the number of values used to defined the window is correct for
the window type and number of dimensions.
ORA-13016: specified topology [string] is invalid
Cause: The specified topology did not exist in the database, or some components
of the topology were missing from the database.
Action: Check the specified topology by executing the SDO_TOPO.validate_
topology function.
ORA-13017: unrecognized line partition shape
Cause: The shape of a 2-D line partition could not be determined.
Action: This is an internal error. Contact Oracle Support Services.
13-18 Oracle Database Error Messages
ORA-13018: bad distance type
Cause: The specified distance type is invalid.
Action: The only supported distance functions are EUCLID and MANHATTAN.
ORA-13019: coordinates out of bounds
Cause: Vertex coordinates lie outside the valid range for specified dimension.
Action: Redefine vertex coordinates within specified boundaries.
ORA-13020: coordinate is NULL
Cause: A vertex coordinate has a NULL value.
Action: Redefine vertex coordinate to have non-NULL value.
ORA-13021: element not continuous
Cause: The coordinates defining a geometric element are not connected.
Action: Redefine coordinates for the geometric element.
ORA-13022: polygon crosses itself
Cause: The coordinates defining a polygonal geometric element represent
crossing segments.
Action: Redefine coordinates for the polygon.
ORA-13023: interior element interacts with exterior element
Cause: An interior element of a geometric object interacts with the exterior
element of that object.
Action: Redefine coordinates for the geometric elements.
ORA-13024: polygon has less than three segments
Cause: The coordinates defining a polygonal geometric element represent less
than three segments.
Action: Redefine the coordinates for the polygon.
ORA-13025: polygon does not close
Cause: The coordinates defining a polygonal geometric element represent an open
polygon.
Action: Redefine the coordinates of the polygon.
ORA-13026: unknown element type for element string.string.string
Cause: The SDO_ETYPE column in the <layer>_SDOGEOM table contains an
invalid geometric element type value.
Action: Redefine the geometric element type in the <layer>_SDOGEOM table for
the specified geometric element using one of the supported SDO_ETYPE values.
See the Oracle Spatial documentation for an explanation of SDO_ETYPE and its
possible values.
ORA-13027: unable to read dimension definition from string
Cause: There was a problem reading the dimension definition from the <layer>_
SDODIM table.
Action: Verify that the <layer>_SDODIM table exists and that the appropriate
privileges exist on the table. Address any other errors that might appear with the
message.
ORA-13028: Invalid Gtype in the SDO_GEOMETRY object
ORA-12700 to ORA-19400 13-19
Cause: There is an invalid SDO_GTYPE in the SDO_GEOMETRY object.
Action: Verify that the geometries have valid gtypes.
ORA-13029: Invalid SRID in the SDO_GEOMETRY object
Cause: There is an invalid SDO_SRID in the SDO_GEOMETRY object. The
specified SRID may be outside the valid SRID range.
Action: Verify that the geometries have valid SRIDs.
ORA-13030: Invalid dimension for the SDO_GEOMETRY object
Cause: There is a mismatch between the dimension in the SDO_GTYPE and
dimension in the SDO_GEOM_METADATA for the SDO_GEOMETRY object.
Action: Verify that the geometries have valid dimensionality.
ORA-13031: Invalid Gtype in t

再分享一下我老师大神的人工智能教程吧。零基础！通俗易懂！风趣幽默！还带黄段子！希望你也加入到我们人工智能的队伍中来！http://www.captainbed.net