NNC-00050: message format error

NNC-00050: message format error

Cause: A corrupted name server message was received by a name server or the name server program interface.

Action: Not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

end-points. NNC-00005: cannot initialization stream subsystem

end-points. NNC-00005: cannot initialization stream subsystem

Cause: The name service stream subsystem could not be started, probably because of a missing TNS error message file.

Action: Check that SQL*Net has been installed properly and that all message files are in their proper locations.

NNC-00004: connection is broken

NNC-00004: connection is broken

Cause: The connection from a name server or client program to another server has been broken, either because that server has shut down, or because the network path to the server has stopped working. This error is usually displayed underneath an error which describes the problem in more detail.

Action: Make sure that the server being connected to is running and listening on the address used, and that there is network connectivity between the two

NNC-00003: error opening stream string

NNC-00003: error opening stream string

Cause: A name server or client program attempted to open a connection to another server and failed, either because the server is down, or because the network path to that server is not working. This error is usually displayed underneath an error which describes the problem in more detail.

Action: Make sure that the server being connected to is listening on the address used, and that there is network connectivity between the two end-points.

NNC-00002: error listening on stream string

NNC-00002: error listening on stream string

Cause: The name server was asked to listen on the specified address, and failed, probably because the address is malformed, or because it uses a SQL*Net protocol adaptor which has not been installed.

Action: Make sure the address is properly formed, and that it uses a protocol adaptor which has been installed on your system.

NNC-00001: maximum number of connections already open

NNC-00001: maximum number of connections already open

Cause: All available name service connections are handling requests.

Action: If the problem occurs when running a name server, increase the values of names.max_open_connections. If the problem occurs in a client program, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

TNS-12699: Native service internal error

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 Customer Support.

TNS-12696: Double Encryption Turned On, login disallowed

TNS-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: Turn OFF either ANO Encryption or the Protocol Adapter Encryption if possible. Refer to Oracle Advanced Security Administrator s Guide on 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 pincode: four, but no more than eight 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.

TNS-12687: Credentials expired.

TNS-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.

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.

Action: This is a programming error and should not normally be visible to the user. If the error does appear, contact Oracle Customer Support.

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 or crypto-checksumming: Diffie-Hellman seed too small

TNS-12684: encryption or crypto-checksumming: Diffie-Hellman seed too small

Cause: The sqlnet.crypto_seed parameter in the SQLNET.ORA parameter file for Oracle Advanced Security is too small.

Action: Add more randomly-chosen text to it, perhaps using Network Manager.

TNS-12683: encryption or crypto-checksumming: no Diffie-Hellman seed

TNS-12683: encryption or crypto-checksumming: no Diffie-Hellman seed

Cause: The sqlnet.crypto_seed parameter is missing from the SQLNET.ORA parameters file for Oracle Advanced Security.

Action: Add this line to SQLNET.ORA: sqlnet.crypto_seed = randomly-chosen text

TNS-12682: Login failed: the SecurID card is in next PRN mode

TNS-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.

TNS-12681: Login failed: the SecurID card does not have a pincode yet

TNS-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.

TNS-12680: Native services disabled but required

TNS-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.

TNS-12679: Native services disabled by other process but required

TNS-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.

TNS-12678: Authentication disabled but required

TNS-12678: Authentication disabled but required

Cause: The configuration parameters that control whether Oracle Advanced Security authentication is disabled or required were both set to TRUE.

Action: Set one or both of the parameters to FALSE.

TNS-12677: Authentication service not supported by database link

TNS-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.

TNS-12676: Server received internal error from client

TNS-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.

TNS-12675: External user name not available yet

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.

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.

TNS-12674: Shared server: proxy context not saved

TNS-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.

TNS-12673: Dedicated server: context not saved

TNS-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.

TNS-12672: Database logon failure

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

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 shared server.

Action: Enable tracing to determine the exact error. Contact Oracle Customer Support if the reason is not obvious.

TNS-12670: Incorrect role password

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

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 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.

TNS-12668: Dedicated server: outbound protocol does not support proxies

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 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.

TNS-12667: Shared server: outbound transport protocol different from inbound

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 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

TNS-12666: Dedicated server: outbound transport protocol different from inbound

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 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.

TNS-12665: NLS string open failed

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 Customer Support.

TNS-12664: Services required by server not available on the client

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

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).

TNS-12662: proxy ticket retrieval failed

TNS-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.

TNS-12661: Protocol authentication to be used

TNS-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.

TNS-12660: Encryption or crypto-checksumming parameters incompatible

TNS-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.

TNS-12659: Error received from other process

TNS-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.

TNS-12658: ANO service required but TNS version is incompatible

TNS-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.

TNS-12657: No algorithms installed

TNS-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.

TNS-12656: Cryptographic checksum mismatch

TNS-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.

TNS-12655: Password check failed

TNS-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.

TNS-12654: Authentication conversion failed

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.

Action: Enable tracing to determine the exact error.

TNS-12653: Authentication control function failed

TNS-12653: Authentication control function failed

Cause: The control function utilized by the authentication service driver failed.

Action: Enable tracing to determine the exact error.

TNS-12652: String truncated

TNS-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.

TNS-12651: Encryption or data integrity algorithm unacceptable

TNS-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.

TNS-12650: No common encryption or data integrity algorithm

TNS-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.

TNS-12649: Unknown encryption or data integrity algorithm

TNS-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.

TNS-12648: Encryption or data integrity algorithm list empty

TNS-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.

TNS-12647: Authentication required

TNS-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.

TNS-12646: Invalid value specified for boolean parameter

TNS-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.

TNS-12645: Parameter does not exist.

TNS-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.

TNS-12643: Client received internal error from server

TNS-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.

TNS-12642: No session key

TNS-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.

TNS-12641: Authentication service failed to initialize

TNS-12641: Authentication service failed to initialize

Cause: The authentication service failed during initialization.

Action: Enable tracing to determine the exact error.

TNS-12640: Authentication adapter initialization failed

TNS-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.

TNS-12639: Authentication service negotiation failed

TNS-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.

TNS-12638: Credential retrieval failed

TNS-12638: Credential retrieval failed

Cause: The authentication service failed to retrieve the credentials of a user.

Action: Enable tracing to determine the exact error.