ORA-12500 to ORA-12699

81 ORA-12500 to ORA-12699

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.; 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-12506: TNS:listener rejected connection based on service ACL filtering: Cause: The client is not present in Service Access Control List.; Action: Add the client's address in Service ACL.
ORA-12508: TNS:listener could not resolve the COMMAND given: Cause: The COMMAND given to listener is not supported.; 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 - 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. - 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.; 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-12530: TNS:listener: rate limit reached: Cause: Listener has reached connection or service rate limit and hence rejected the connection.; Action: Attempt the connection again. If the error occurs frequently, contact the database administrator to increase connection or service rate limit.
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.
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-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.; 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-12563: TNS:operation was aborted: Cause: NT operation was interrupted by the uppper layer.; Action: None
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:Application generated error: Cause: This error was generated by peer application. Please see secondary errors for the actual cause.; Action: Action should be taken on secondary error.
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-12579: TNS:transport connection failed: Cause: An error was encountered while trying to create transport connection.; Action: Likely reasons include host may be down, outbound transport connection may be blocked by network or any other transport connectivity issue. If error persists, contact Oracle Customer Support.
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.; 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-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 or status of the connection.; 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.; 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-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. 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.; 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.; 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.; 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: 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: 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. - 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-12691: TTC RPC (string) not supported by Oracle Connection Manager in Traffic Director mode: Cause: Oracle Connection Manager in Traffic Director mode does not support the specified Two-Task Common (TTC) Remote Procedure Call(RPC).; Action: Do not use functionality that issues the specified TTC RPC which was disallowed by Oracle Connection Manager in Traffic Director mode
ORA-12692: functionality (string) not supported by Oracle Connection Manager in Traffic Director mode: Cause: Oracle Connection Manager in Traffic Director mode does not support the specified functionality.; Action: Do not use functionality that is not supported by Oracle Connection // Manager in Traffic Director mode.
ORA-12693: PRCP is not configured in Oracle Connection Manager in Traffic Director mode: Cause: The client was attempting to connect using Proxy Resident Connection Pool (PRCP) while PRCP is not configured in Oracle Connection Manager in Traffic Director mode.; Action: The client should use PRCP connections only when PRCP is configured in Oracle Connection Manager in Traffic Director mode.
ORA-12694: non-PRCP connection requested when PRCP is configured in Oracle Connection Manager in Traffic Director mode: Cause: The client was attempting a non Proxy Resident Connection Pool (PRCP) connection while PRCP was configured in Oracle Connection Manager in Traffic Director mode.; Action: The client should only use PRCP connections when PRCP is configured in Oracle Connection Manager in Traffic Director mode.
ORA-12695: This statement cannot be executed with Oracle Connection Manager in Traffic Director mode with PRCP enabled: Cause: The client did not send enough information to execute the statement with Oracle Connection Manager in Traffic Director mode with Proxy Resident Connection Pooling (PRCP) enabled.; Action: This client needs a patch that will fix the issue. Alternatively, it needs to be upgraded to Oracle Database Release 18.1 or later. Contact Oracle Customer Support for the patch.
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: Take one of the following actions: - Turn off ANO encryption. - Set the SQLNET.IGNORE_ANO_ENCRYPTION_FOR_TCPS parameter to TRUE. - Set IGNORE_ANO_ENCRYPTION_FOR_TCPS to TRUE in the SECURITY clause of the client's TNS connect string. Refer to the Database Net Services Reference for more details.
ORA-12697: PRCP: Internal error\n: Cause: Invalid PRCP state detected while collecting statistics; Action: Check with CMAN in Traffice Director mode admin to get more info from traces and sqlnet.log.
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.