Description:
TNS-12643 Client received internal error from server
Cause:
The client process received an error from the server that indicated that an internal SQL*Net native services error had occurred.
ORADB-TNS error
Description:
TNS-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.
ORADB-TNS oracle
Description:
TNS-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.
ORADB-TNS conversion, oracle
Description:
TNS-12687 Database link failed: credentials expired
Cause:
The credentials that are used to authenticate the user for the requested database link have expired.
ORADB-TNS
Description:
TNS-12631 Username retrieval failed
Cause:
The authentication service failed to retrieve the name of a user.
ORADB-TNS oracle tns-12631, tns-12631
Description:
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.
ORADB-TNS
Description:
TNS-12644 Authentication service initialization failed
Cause:
The routine called to initialize the authentication adapter failed.
ORADB-TNS
Description:
TNS-12676 Server received internal error from client
Cause:
The server process received an error from the client which indicated that an internal SQL*Net native services error had occurred.
ORADB-TNS error
Description:
TNS-12655 Password check failed
Cause:
The authentication service being used was unable to verify the provided password.
ORADB-TNS
Description:
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.
ORADB-TNS j, oracle