ORA-12670: Incorrect role password

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-12669: Shared server: outbound protocol does not support proxies

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-12668: Dedicated server: outbound protocol does not support proxies

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-12667: Shared server: outbound transport protocol different from inbound

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-12666: Dedicated server: outbound transport protocol different from inbound

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-12665: NLS string open failed

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-12664: Services required by server not available on the client

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-12663: Services required by client not available on the server

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-12662: proxy ticket retrieval failed

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-12661: Protocol authentication to be used

ORA-12661: Protocol authentication to be used

Cause: The Oracle Advanced Security authentication service has determined that the Oracle Net transport protocol in use is to be utilized to authenticate a user s identity.

Action: This error is used solely to communicate information between the authentication service and the Oracle Net session layer and should not normally be visible. If the error is seen, contact Oracle Worldwide Support.

ORA-12660: Encryption or crypto-checksumming parameters incompatible

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-12659: Error received from other process

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-12658: ANO service required but TNS version is incompatible

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-12657: No algorithms installed

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-12656: Cryptographic checksum mismatch

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-12655: Password check failed

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-12654: Authentication conversion failed

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-12653: Authentication control function failed

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-12652: String truncated

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-12651: Encryption or data integrity algorithm unacceptable

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-12650: No common encryption or data integrity 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-12649: Unknown encryption or data integrity algorithm

ORA-12649: Unknown encryption or data integrity algorithm

Cause: An Oracle Advanced Security 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-12648: Encryption or data integrity algorithm list empty

ORA-12648: Encryption or data integrity algorithm list empty

Cause: An Oracle Advanced Security 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-12647: Authentication required

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-12646: Invalid value specified for boolean parameter

ORA-12646: Invalid value specified for boolean parameter

Cause: The value specified for a parameter was set to a value other than true or false or on or off.

Action: Correct the value of the parameter.

ORA-12645: Parameter does not exist.

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-12643: Client received internal error from server

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-12642: No session key

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-12641: Authentication service failed to initialize

ORA-12641: Authentication service failed to initialize

Cause: The authentication service failed during initialization.

Action: Enable tracing to determine the exact error.

ORA-12640: Authentication adapter initialization failed

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-12639: Authentication service negotiation failed

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-12638: Credential retrieval failed

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-12637: Packet receive failed

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-12636: Packet send failed

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-12635: No authentication adapters available

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-12634: Memory allocation failed

ORA-12634: Memory allocation failed

Cause: Process was unable to allocate memory.

Action: Terminate other processes in order to reclaim needed memory.

ORA-12633: No shared authentication services

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-12632: Role fetch failed

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-12631: Username retrieval failed

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-12630: Native service operation not supported

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-12629: TNS:no event test

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-12628: TNS:no event callbacks

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-12626: TNS:bad event type

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-12625: TNS:missing argument

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-12624: TNS:connection is already registered

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-12623: TNS:operation is illegal in this state

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-12622: TNS:event notifications are not homogeneous

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-12620: TNS:requested characteristic not available

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-12619: TNS:unable to grant requested service

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-12618: TNS:versions are incompatible

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-12616: TNS:no event signals

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-12615: TNS:preempt error

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-12612: TNS:connection is busy

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-12611: TNS:operation is not portable

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-12609: TNS: Receive timeout occurred

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-12608: TNS: Send timeout occurred

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-12607: TNS: Connect timeout occurred

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-12606: TNS: Application timeout occurred

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-12602: TNS: Connection Pooling limit reached

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-12601: TNS:information flags check failed

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.