ID |
Message text |
Explanation and action |
---|---|---|
1205 |
|
A user command encountered a deadlock in Adaptive Server, or the primary Adaptive Server failed during a user transaction. In the latter case, the connection will be switched to the secondary Adaptive Server and placed in the database that the user was in prior to the failure. In both cases, the last transaction will be rolled back, and the user should reissue the last command. |
2812 |
|
OpenSwitch received a remote procedure call that does not exist in this server. Check the validity of your RPC. |
5701 |
|
This is an informational message indicating the database that is in effect when a cache thread is being reused. |
5703 |
|
This is an informational message indicating a change in language setting. |
5704 |
|
This is an informational message indicating a change in character set setting. |
20005 |
|
This is an informational message for debugging purposes only. |
20008 |
|
When a CM first connects to OpenSwitch, the latter sends this message to the CM indicating that this is a special connection which has been granted the coordinator access role. This is an informational message and is not usually seen by regular users. |
20011 |
|
An error occurred when OpenSwitch was trying to bind to the parameters for the registered procedure. See the OpenSwitch Administration Guide for the correct syntax and parameters to use to execute this registered procedure. |
20012 |
|
An error occurred when OpenSwitch was trying to transfer parameters for the registered procedure from the client. Either the client disconnected abruptly, or a network I/O error occurred. Try rerunning your registered procedure command. |
20013 |
|
An error occurred when OpenSwitch was trying to process the columns of rows returned by the registered procedure. Check the validity of your registered procedure call. Contact Sybase Technical Support if needed. |
20014 |
|
An error occurred when OpenSwitch was trying to transfer results from the registered procedure to the client. Either the client disconnected abruptly, or a network I/O error occurred. Try rerunning your registered procedure command. |
20015 |
|
This is an internal OpenSwitch error. Call Sybase Technical Support. |
20016 |
|
OpenSwitch does not recognize the name of the called registered procedure. Verify the procedure name; see the OpenSwitch Administration Guide for a list of OpenSwitch registered procedures. |
20017 |
|
This is an internal OpenSwitch error. Contact Sybase Technical Support |
20018 |
|
OpenSwitch encountered a memory allocation failure. Reduce the load on this machine, or increase the memory allocated to the OpenSwitch process and restart the OpenSwitch server. |
20019 |
|
OpenSwitch detected a syntax error in the registered procedure call. See the OpenSwitch Administration Guide for the correct syntax to use for this registered procedure. |
20020 |
|
The number of parameters supplied exceeds the maximum number of parameters for this registered procedure. See the OpenSwitch Administration Guide for the correct parameters to pass for this registered procedure. |
20021 |
|
An incorrect parameter type was specified for the registered procedure. Check that the parameters in your registered procedure call use the correct types. |
20022 |
|
This is an internal OpenSwitch error. Call Sybase Technical Support. |
20023 |
|
Registered procedures can only accept parameters in integer type or character (string) type. All other types are invalid. |
20024 |
|
This is an internal OpenSwitch error. Call Sybase Technical Support. |
20025 |
|
OpenSwitch found unmatched double or single quotes in the registered procedure command. Correct your command and try executing again. |
20026 |
|
The configuration file for this OpenSwitch server cannot be found. Check that this file exists before your execute the rp_cfg command. |
20027 |
|
There was an error while OpenSwitch was processing the configuration file during the rp_cfg command. See the error log for details. |
20028 |
|
This is an informational message: The rp_cfg command was successful. |
20029 |
|
This is an internal OpenSwitch error. Contact Sybase Technical Support for assistance |
20030 |
|
rp_debug received an incorrect state parameter. See the OpenSwitch Administration Guide for the valid parameters for rp_debug. |
20031 |
|
rp_debug received an incorrect flag parameter. See the OpenSwitch Administration Guide for the valid parameters for rp_debug. |
20032 |
|
rp_dump received an incorrect what parameter. See the OpenSwitch Administration Guide for the valid parameters for rp_dump. |
20033 |
|
The poolname parameter specified for this registered procedure is incorrect. Run rp_pool_status to check the available pools in this OpenSwitch server, and rerun the command using the correct pool name. |
20034 |
|
OpenSwitch is unable to determine the poolname for the specified spid. Use sp_who to verify that the spid is indeed a client spid and has a server name attached to it. |
20035 |
|
OpenSwitch was unable to kill the thread specified by spid. Check the OpenSwitch error log for details. |
20036 |
|
OpenSwitch was unable to cancel the current request of the thread specified by spid. Check the OpenSwitch error log for details. |
20037 |
|
This is an internal OpenSwitch error. Call Sybase Technical Support. |
20038 |
|
This is an informational message: The rp_kill command was successful. |
20039 |
|
This is an informational message: the rp_cancel command was successful. |
20040 |
|
This is an internal OpenSwitch error. Check the OpenSwitch error log for details, and call Sybase Technical Support. |
20041 |
|
This is an internal OpenSwitch error. Check the OpenSwitch error log for details, and call Sybase Technical Support. |
20042 |
|
This is an internal OpenSwitch error. Check the OpenSwitch error log for details, and call Sybase Technical Support. |
20043 |
|
This is an internal OpenSwitch error. Check the OpenSwitch error log for details, and call Sybase Technical Support. |
20044 |
|
This is an informational message for debugging purposes and can safely be ignored. |
20045 |
|
This is an informational message. The command was successful and has been channeled to the relevant threads. |
20046 |
|
The spid specified for the registered procedure was incorrect. Please verify the spid before rerunning the command. |
20047 |
|
This is an internal OpenSwitch error. Check the OpenSwitch error log for details, and call Sybase Technical Support. |
20048 |
|
The specified pool cannot be set to the status specified by rp_pool_status or rp_pool_cache. Check the status and validity of the pool. Call Sybase Technical Support if needed. |
20049 |
|
This is an internal OpenSwitch error. Check the OpenSwitch error log for details, and call Sybase Technical Support. |
20050 |
|
The user tried to add a pool that already exists in this OpenSwitch server. Run rp_pool_status to see existing pool names. |