TNS-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.
TNS-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.
TNS-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 multi-threaded server.
Action: Enable tracing to determine the exact error. Contact Oracle Support Services if the reason is not obvious.
TNS-12670: Incorrect role password
Cause: A password supplied for a role could not be validated by the authentication service.
Action: Supply the correct password.
TNS-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 SQL*Net connect string or alias used for the connection that does support externally-authenticated proxy connections. NOTE: Because of a limitation in SQL*Net, the protocol used for the proxy connection must the same as that used for the connection from the client to the server.
TNS-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 SQL*Net connect string or alias used for the connection that does support externally-authenticated proxy connections. NOTE: Because of a limitation in SQL*Net, the protocol used for the proxy connection must the same as that used for the connection from the client to the server.
TNS-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 that used for the inbound connection. It is not possible for SQL*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 SQL*Net connect string or alias for the outbound connection as that used for the inbound connection.
TNS-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 SQL*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 SQL*Net connect string or alias for the outbound connection as that used for the inbound connection.
TNS-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 Oracle Support Services.
TNS-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).
TNS-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).