TNS-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 Support Services.
Category Archives: TNS Database Error Messages
TNS-12696: Double Encryption Turned On, login disallowed
TNS-12696: Double Encryption Turned On, login disallowed
Cause: A Secure Protocol Adapter was used that has Encryption turned ON as well as ASO Encryption.
Action: Turn OFF either ASO Encryption or the Protocol Adapter Encryption if possible. Refer to the Oracle Advanced Security Administrator's Guide for information about how to do this.
TNS-12690: Server Authentication failed, login cancelled
TNS-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.
TNS-12689: Server Authentication required, but not supported
TNS-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.
TNS-12688: Login failed: the SecurID server rejected the new pincode
TNS-12688: Login failed: the SecurID server rejected the new pincode
Cause: There are a number of reasons why the SecurID server would refuse a pin code: The user might not have permission to make up his own pin code. The pin code was either too short or too long. Valid pin codes consist of minimal four, but no more than eight characters. The pin code contains any non alpha-numeric characters.
Action: Re-execute the operation and make sure to use a pin code 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.
TNS-12687: Database link failed: credentials expired
TNS-12687: Database link failed: credentials expired
Cause: The credentials that are used to authenticate the user for the requested database link have expired.
Action: Renew your credentials. Refer to the documentation specific for your Network Authentication Adapter on how to do this.
TNS-12686: Invalid command specified for a service
TNS-12686: Invalid command specified for a service
Cause: An operation which does not exist was specified for a native service. This is a programming error and should not normally be visible to the user.
Action: Contact Oracle Support Services.
TNS-12685: Native service required remotely but disabled locally
TNS-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.
TNS-12684: encryption/crypto-checksumming: Diffie-Hellman seed too small
TNS-12684: encryption/crypto-checksumming: Diffie-Hellman seed too small
Cause: The sqlnet.crypto_seed parameter in the SQLNET.ORA parameter file for SQL*Net is too small.
Action: Add more randomly-chosen text to it, perhaps using Network Manager.
TNS-12683: encryption/crypto-checksumming: no Diffie-Hellman seed
TNS-12683: encryption/crypto-checksumming: no Diffie-Hellman seed
Cause: The sqlnet.crypto_seed parameter is missing from the SQLNET.ORA parameters file for SQL*Net.
Action: Add this line to SQLNET.ORA: sqlnet.crypto_seed = "randomly-chosen text"