NA Internal Messages (TNS-02501 to 03500)

Cause:	When a process attempted to retrieve a role from the authentication service, no more were available.

Action:	None. This error is used internally and occurs in the normal course of events.

TNS-02502 Authentication: unable to find initialization function

Cause:	he native authentication service was unable to call the initialization function for the specified service because it does not exist.

Action:	If this service adaptor came directly from Oracle, contact Worldwide Customer Support, as this error should never happen. Otherwise, add an initialization function for the service being used.

TNS-02503 Parameter retrieval failed

Cause:	The native service layer was unable to retrieve a parameter from a configuration file.

Action:	If it is possible, enable tracing and attempt to reproduce the problem. In any event, contact Worldwide Customer Support.

TNS-02504 Parameter count retrieval failed

Cause:	The native service layer was unable to determine the number of arguments given for a configuration parameter.

Action:	If it is possible, enable tracing and attempt to reproduce the problem. In any event, contact Worldwide Customer Support.

TNS-02505 Authentication: null context pointer provided

Cause:	nau_ini() was passed a null pointer for the context that it is supposed to use.

Action:	Call nau_ini() with a pointer to a context structure.

TNS-02506 Authentication: no type string

Cause:	An authentication context structure does not contain a string that describes the authentication service being used.

Action:	Contact Worldwide Customer Support

TNS-02507 Encryption: algorithm not installed

Cause:	After picking an algorithm, the server was unable to find an index for it in its table of algorithms. This should be impossible because the algorithm was chosen (indirectly) from that list.

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

TNS-0208 Encryption: server negotiation response in error

Cause:	The server's response in negotiation was in error.

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

TNS-02509 Authentication: invalid process state

Cause:	The state in which a process is running does not correspond to any of the values which are valid.

Action:	If it is possible, enable tracing and attempt to reproduce the problem. In any event, contact Worldwide Customer Support.

TNS-02510 Invalid numeric data type

Cause:	The type of a piece of numeric data that was received does not correspond to one of the valid values.

Action:	If it is possible, enable tracing and attempt to reproduce the problem. In any event, contact Worldwide Customer Support.

TNS-02511 Invalid data type

Cause:	The type of a piece of data that was received or to be transmitted did not correspond to any of the correct values.

Action:	If it is possible, enable tracing and attempt to reproduce the problem. In any event, contact Worldwide Customer Support.

TNS-02512 Invalid status received

Cause:	A process received a value as a status flag which was unknown.

Action:	If it is possible, enable tracing and attempt to reproduce the problem. In any event, contact Worldwide Customer Support.

TNS-02513 Requested data type does not match retrieved type

Cause:	A service requested data whose type does not match that of the segment which was sent from the other process.

Action:	If it is possible, enable tracing and attempt to reproduce the problem. In any event, contact Worldwide Customer Support.

TNS-02514 Invalid packet received

Cause:	A process received a data packet which was not meant for the native services layer.

Action:	If it is possible, enable tracing and attempt to reproduce the problem. In any event, contact Worldwide Customer Support.

TNS-02515 Encryption/crypto-checksumming: unknown control type

Cause:	An encryption or crypto-checksumming algorithm "control" function was called, but did not recognize the "type" argument it was given.

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

TNS-02516 No data available

Cause:	A native service attempt to retrieve data but no data was available to be received.

Action:	The error is not normally visible as it usually is only used to signal the end of a data stream. If the error becomes visible, enable tracing to reproduce the problem and contact Worldwide Customer Support.

TNS-02517 Key smaller than requested size

Cause:	The key returned by SNS key negotiation was smaller than the size requested by some service (either encryption or crypto-check-summing).

Action:	The error is not normally visible. If the error persists, enable tracing, reproduce the problem, and contact Worldwide Customer Support.

TNS-02518 key negotiation error

Cause:	An error occurred while the two sides of the connection were negotiating an SNS key.

Action:	he error is not normally visible. If the error persists, enable tracing to reproduce the problem and contact Worldwide Customer Support.

TNS-02519 no appropriate key-negotiation parameters

Cause:	No appopriate key-negotiation parameters are available for the key size requested either by encryption or by crypto-checksumming.

Action:	The error is not normally visible. Enable tracing to reproduce the problem and contact Worldwide Customer Support.

TNS-02520 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, perhaps by using Network Manager: sqlnet.crypto_seed = "randomly-chosen text"

TNS-02521 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-02524 Authentication: privilege check failed

Cause:	An error occurred when the SQL*Net authentication service attempted to verify that a user had a specific database privilege.

Action:	This error should not happen normally. Enable tracing and attempt to repeat the error. Contact Customer Support.

TNS-02525 encryption/crypto-checksumming: self test failed

Cause:	The SNS system detected an error while running tests on the active encryption or checksumming algorithm.

Action:	Contact Customer Support.

TNS-02526 server proxy type does not match client type

Cause:	The authentication type selected by the server does not match that picked by the client.

Action:	Contact Worldwide Customer Support

TNS-03502 Insufficient arguments. Usage: tnsping <address> [<count>]

Cause:	Some required command-line arguments are missing.

Action:	Re-enter the command using the correct arguments.

TNS-03503 Could not initialize NL

Cause:	The network library could not be initialized.

Action:	This is an internal error which should not normally be visible. Ensure that memory is available to run the application and that there are no other operating system problems, and then attempt the command again.

TNS-03504 Service name too long

Cause:	The service name you are attempting to ping is too long.

Action:	Re-enter the command using the correct service name.

TNS-03505 Failed to resolve name

Cause:	The service name you provided could not be found in TNSNAMES.ORA, an Oracle Names server, or a native naming service.

Action:	Verify that you entered the service name correctly. You may need to ensure that the name was entered correctly into the network configuration using Oracle Network Manager.

TNS-03506 Failed to create address binding

Cause:	The TNSPING utility found the requested address or service name, but received an internal error when trying to use it.

Action:	This is an internal error which should not normally be visible. Ensure that memory is available to run the application and that there are no other operating system problems, and then attempt the command again.

TNS-03507 Failure looking for ADDRESS keyword

Cause:	The TNS address did not contain an ADDRESS keyword.

Action:	If you entered the TNS address on the command line, be sure that the syntax is correct. If you entered a service name on the command line, the address contains the wrong information. You should verify that the information was entered correctly with Oracle Network Manager.

TNS-03508 Failed to create address string

Cause:	The TNSPING utility received an internal error when generating an address.

Action:	This is an internal error which should not normally be visible. Ensure that memory is available to run the application and that there are no other operating system problems, and then attempt the command again.

TNS-03509 OK (decimal msec)

Cause:	The operation succeeded, in this amount of time.

Action:	No action necessary.

TNS-03510 Failed doe to I/O error

Cause:	An I/O operation failed perhaps due to resource failure of premature window termination.

Action:	This is an internal error which should not normally be visible. Do not close the TNSPING window before all I/O operations have completed.

TNS-03601 Failed in route information collection

Cause:	The route could either not connect or encountered an unsupported version of SQL*Net.

Action:	Check if SQL*Net along all node is version 2.3 or greater.

TNS-03602 Insufficient arguments. Usage: trcroute address

Cause:	Some required command-line arguments are missing.

Action:	Re-enter the command using the correct arguments.

TNS-03603 Encountered a node with pre-2.3 version of SQL*Net

Cause:	Any version of SQL*Net before 2.3 doesn't support trcroute.

Action:	Find the node that isn't responding to trcroute.