Release 8.0.4
A58312-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8 Error Messages Release 8.0.4 A58312-01 |
|
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.
Cause: The 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.
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.
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.
Cause: The function nau_ini() was passed a null pointer as the pointer to the context that it is supposed to use.
Action: Call nau_ini() with a pointer to a context structure.
Cause: An authentication context structure does not contain a string that describes the authentication service being used.
Action: If it is possible, enable tracing and attempt to reproduce the problem. In any event, contact Worldwide Customer Support.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: A native service attempted 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.
Cause: The key returned by negotiation was smaller than the size requested by some service (either encryption or crypto-checksumming).
Action: The error is not normally visible. If the error persists, enable tracing to reproduce the problem and contact Worldwide Customer Support.
Cause: An error occurred while the two sides of the connection were negotiating an encryption or crypto-checksumming key.
Action: The error is not normally visible. If the error persists, enable tracing to reproduce the problem and contact Worldwide Customer Support.
Cause: No appropriate 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.
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"
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.
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.
Cause: The SNS system detected an error while running tests on the active encryption or checksumming algorithm.
Action: Contact Customer Support.
Cause: The authentication type selected by the server does not match that picked by the client.
Action: Contact Worldwide Customer Support
