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.