Release 8.0.4
A58312-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8 Error Messages Release 8.0.4 A58312-01 |
|
Cause: An operation requested by a user is not supported by the native services component.
Action: This may be an internal error if the operation should have been supported.
Cause: The authentication service failed to retrieve the name of a user.
Action: Enable tracing to determine which routine is failing.
Cause: The authentication service failed to retrieve one of the user's roles.
Action: Enable tracing to determine which routine is failing.
Cause: The list of authentication services specified by the user does not match those supported by the process.
Action: Either specify another list or relink the executable with the desired services.
Cause: Process was unable to allocate memory.
Action: Terminate other processes in order to reclaim needed memory.
Cause: The executable was not linked with any authentication service adapters but the SQLNET.ORA parameter that determines whether or not authentication is required was set to true.
Action: Either disable the parameter or relink the executable with service adapters.
Cause: A process was unable to send a packet to another process. Possible causes are: 1. The other process was terminated. 2. The machine on which the other process is running went down. 3. Some other communications error occurred.
Action: If the cause is not obvious, contact Worldwide Customer Support.
Cause: A process was unable to receive a packet from another process. Possible causes are: 1. The other process was terminated. 2. The machine on which the other process is running went down. 3. Some other communications error occurred.
Action: If the cause is not obvious, contact Worldwide Customer Support.
Cause: The authentication service failed to retrieve the credentials of a user.
Action: Enable tracing to determine the exact error.
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.
Cause: The function specified in the authentication table entry for the service failed.
Action: Enable tracing to determine the exact error.
Cause: The authentication service failed during initialization.
Action: Enable tracing to determine the exact error.
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.
Cause: The client process received an error from the server that indicated that an internal SQL*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 Worldwide Customer Support.
Cause: The routine called to initialize the authentication adapter failed.
Action: Enable tracing to determine the exact error. A likely cause is that memory is exhausted.
Cause: A SQLNET.ORA parameter from which a value was needed does not exist.
Action: Set the parameter in the parameter file.
Cause: The value specified for a parameter was set to a value other than true/false or on/off.
Action: Correct the value of the parameter.
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.
Cause: A SQL*Net 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.
Cause: A SQL*Net 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.
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.
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 Worldwide Customer Support.
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.
Cause: The control function utilized by the authentication service driver failed.
Action: Enable tracing to determine the exact error.
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.
Cause: The authentication service being used was unable to verify the provided password.
Action: Enable tracing to determine the exact error.
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.
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.
Cause: A process that is running an earlier version of TNS attempted to connect but the connection failed because the server process required that a native 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.
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.
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.
Cause: The SQL*Net authentication service has determined that the SQL*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 SQL*Net session layer and should not be visible to the user. If the error is seen, contact Worldwide customer support.
Cause: The authentication adapter used by SQL*Net failed to retrieve the credentials needed to authenticate a database link.
Action: Enable tracing to determine the exact error.
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).
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).
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.
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 SQL*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 SQL*Net connect string or alias for the outbound connection as that used for the inbound connection
Cause: The protocol specified for an externally-identified outbound connection from a shared server (database link) was not the same as that used for the inbound connection. It is not possible for SQL*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 SQL*Net connect string or alias for the outbound connection as that used for the inbound connection
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 SQL*Net connect string or alias used for the connection that does support externally-authenticated proxy connections. NOTE: Because of a limitation in SQL*Net, the protocol used for the proxy connection must the same as that used for the connection from the client to the server.
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 SQL*Net connect string or alias used for the connection that does support externally-authenticated proxy connections. NOTE: Because of a limitation in SQL*Net, the protocol used for the proxy connection must the same as that used for the connection from the client to the server.
Cause: A password supplied for a role could not be validated by the authentication service.
Action: Supply the correct password.
Cause: The adapter for the authentication service failed when it tried to save the data needed for proxy connections (database links) through the multi-threaded server.
Action: Enable tracing to determine the exact error. Contact Worldwide Customer Support if the reason is not obvious.
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.
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
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
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 information message and should not normally be visible to the user. If the error does appear, contact Worldwide Customer Support.
Cause: The server process received an error from the client which indicated that an internal SQL*Net native services error had occurred.
Action: Enable tracing on both processes and attempt to recreate the problem. If the problem recurs, contact Worldwide Customer Support.
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.
Cause: The configuration parameters that control whether SQL*Net authentication is disabled or required were both set to TRUE.
Action: Set one or both of the parameters to FALSE.
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.
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.
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.
Cause: The SecurID card and the SecurID server are out of sync and the server requires the next cardcode to re-synchronize the card.
Action: Use one of the programs supplied by Security Dynamics to re-synchronize the SecurID card.
Cause: The "sqlnet.crypto_seed" parameter is missing from the SQLNET.ORA parameters file for SQL*Net.
Action: Add this line to SQLNET.ORA: 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: 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.
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 Worldwide Customer Support.
Cause: The credentials that are used to authenticate the user for the requested database link have expired.
Action: Renew your credentials. Refer to the documentation specific for your Network Authentication Adapter on how to do this.
Cause: There are a number of reasons why the SecurID server would refuse a pincode: - The user might not have permission to make up his own pincode. - The pincode was either too short or too long. Valid pincodes consist of minimal four, but no more than eight characters. - The pincode contains any non alpha-numeric 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.
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 Secure Network Services, and that the Authentication Adapter supports Server Authentication.
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.
Cause: An internal error occurred in the native services component.
Action: Enable tracing to determine the exact error. Contact Worldwide Customer Support.
