Message text |
Explanation and action |
---|---|
|
OpenSwitch encountered a memory allocation failure. Reduce the load on this machine, or increase the memory allocated to OpenSwitch and restart the OpenSwitch server. |
|
This is an internal OpenSwitch error. Check the OpenSwitch error log for details. |
|
Verify that the call to ct_dynamic (CS_DEALLOC) in the client application had a valid ID and IDLEN or CS_NULLTERM. See the relevant Sybase documents for your client’s APIs. |
|
Check for failures in the CS_PREPARE statement in the client application, and that the statement was not previously deallocated. If you cannot resolve the problem, call Sybase Technical Support for assistance. |
|
This is an internal OpenSwitch error. Check the OpenSwitch error log for details. |
|
Check that the client application is still running and maintains connectivity with OpenSwitch. If you cannot resolve the problem, call Sybase Technical Support for assistance. |
|
Check that the client application is still running and maintains connectivity with OpenSwitch. If you cannot resolve the problem, call Sybase Technical Support for assistance. |
|
Check that the client application is still running and maintains connectivity with OpenSwitch. If you cannot resolve the problem, call Sybase Technical Support for assistance. |
|
Call to ct_send failed. Check that Adaptive Server is still running and that clients like isql can connect to Adaptive Server from the OpenSwitch host. |
|
This is an internal OpenSwitch error. Check the OpenSwitch error log for details. |
|
The call to ct_cmd_alloc may have failed due to an internal OpenSwitch error. You may also be running out of memory on the OpenSwitch host. Increase the memory available to the OpenSwitch process and restart the OpenSwitch server. If the problem persists, call Sybase Technical Support. |
|
This is an internal OpenSwitch error. Check the OpenSwitch error log for details. |
|
Check that the application passed a valid argument for the buffer in the call to ct_dynamic (CS_EXEC_IMMEDIATE). See the relevant Sybase document for your client’s APIs. |
|
Check that the client did not abruptly disconnect from the OpenSwitch server. Check that the application passed a valid strlen of the buffer (or CS_NULLTERM) in the call to ct_dynamic (CS_EXEC_IMMEDIATE). See the relevant Sybase document for your client’s APIs. |
|
OpenSwitch encountered a memory allocation failure. Reduce the load on this machine, or increase the memory allocated to OpenSwitch and restart the OpenSwitch server. |
|
This error may be due to an abrupt disconnect from the client or loss of network connection between OpenSwitch and the client. Otherwise, this is due to an internal OpenSwitch problem; call Sybase Technical Support for assistance. |
|
Check that the CS_PREPARE statement did not fail. Otherwise, this error is due to an internal OpenSwitch problem; call Sybase Technical Support for assistance. |
|
Check that the CS_PREPARE statement did not fail. Otherwise, this error is due to an internal OpenSwitch problem; call Sybase Technical Support for assistance. |
|
This error may be due to an abrupt disconnect from the client or loss of network connection between OpenSwitch and the client. Otherwise, this is due to an internal OpenSwitch problem; call Sybase Technical Support for assistance. |
|
This error may be due to an abrupt disconnect from the client or loss of network connection between OpenSwitch and the client. Otherwise, this is due to an internal OpenSwitch problem; call Sybase Technical Support for assistance. |
|
This error may be due to an abrupt disconnect from the client or loss of network connection between OpenSwitch and the client. Otherwise, this is due to an internal OpenSwitch problem; call Sybase Technical Support for assistance. |
|
This is an internal OpenSwitch error. A call to ct_con_props (CS_GET, CS_CON_STATUS) failed. Check any previous errors in the OpenSwitch error log. Call Sybase Technical Support for assistance. |
|
This is an internal OpenSwitch error. Check the OpenSwitch error log for details. |
|
A call to ct_send failed. Check that Adaptive Server is still running and that clients like isql can connect to Adaptive Server from the OpenSwitch host. |
|
This is an internal OpenSwitch error. Check the OpenSwitch error log for details. |
|
Verify that the client application passed a valid ID and IDLEN or CS_NULLTERM in the call to ct_dynamic. See the relevant Sybase documents for your client’s APIs. |
|
Check the call to ct_dynamic in the client application Verify for a valid operation type. See the relevant Sybase documents for your client’s APIs. |
|
This may be an internal OpenSwitch error due to which the call to ct_cmd_alloc failed. You may also be running out of memory on the OpenSwitch host. Increase the memory available to the OpenSwitch process and restart the OpenSwitch server. If the problem persists, call Sybase Technical Support. |
|
This is an internal OpenSwitch error. Check the OpenSwitch error log for details. |
|
This is an internal OpenSwitch error. Check the OpenSwitch error log for details. |
|
This is an internal OpenSwitch error. Check the OpenSwitch error log for details. |
|
OpenSwitch encountered a memory allocation failure. Reduce the load on this machine, or increase the memory allocated to OpenSwitch and restart the OpenSwitch server. |
|
OpenSwitch encountered a memory allocation failure. Reduce the load on this machine, or increase the memory allocated to OpenSwitch and restart the OpenSwitch server. |
|
This error may be due to an abrupt disconnect from the client or loss of network connection between OpenSwitch and the client. Otherwise, this is due to an internal OpenSwitch problem; call Sybase Technical Support for assistance. |
|
This error may be due to an abrupt disconnect from the client or loss of network connection between OpenSwitch and the client. Otherwise, this is due to an internal OpenSwitch problem; call Sybase Technical Support for assistance. |
|
This error may be due to an abrupt disconnect from the client or loss of network connection between OpenSwitch and the client. Otherwise, this is due to an internal OpenSwitch problem; call Sybase Technical Support for assistance. |
|
This error may be due to an abrupt disconnect from the client or loss of network connection between OpenSwitch and the client. Otherwise, this is due to an internal OpenSwitch problem; call Sybase Technical Support for assistance. |
|
Check that Adaptive Server is still running and that clients like isql can connect to Adaptive Server from the OpenSwitch host. If the problem persists, call Sybase Technical Support. |
|
Check that Adaptive Server is still running and that clients like isql can connect to the server from the OpenSwitch host. If the problem persists, call Sybase Technical Support. |
|
OpenSwitch encountered a memory allocation failure. Reduce the load on this machine, or increase the memory allocated to OpenSwitch and restart the OpenSwitch server. |
|
Check that the client application passed a valid strlen of the buffer or CS_NULLTERM in the call to ct_dynamic (CS_PREPARE). See the relevant Sybase documents for your client’s APIs. |
|
A call to ct_cmd_alloc failed. You may be running out of memory on the OpenSwitch host. Increase the memory available to the OpenSwitch process and restart the OpenSwitch server. |
|
This is an internal OpenSwitch error. Check the OpenSwitch error log for details. |
|
This is an internal OpenSwitch error. Check the OpenSwitch error log for details. |
|
Call to ct_send failed. Check that Adaptive Server is still running and that clients like isql can connect to the server from the OpenSwitch host. |
|
This is an internal OpenSwitch error. Call Sybase Technical Support for assistance. |
|
An error occurred when OpenSwitch attempted to switch the connections to the companion Adaptive Server of the current HA-Adaptive Server. Check the status of the companion server and verify that it is accepting connections. Also check the OpenSwitch configuration file and the interfaces file to verify that the server names are listed correctly. |
|
An error occurred while OpenSwitch was attempting to switch the connections to the secondary Adaptive Server of the current pool. Check the status of the companion server and verify that it is accepting connections. Also check the OpenSwitch configuration file and the interfaces file to verify that the server names are listed correctly. |
|
This is an internal OpenSwitch error. Call Sybase Technical Support for assistance. |
|
OpenSwitch may have temporarily run out of memory. Check previous errors in the OpenSwitch error log. You may need to allocate more memory to the OpenSwitch process, or reevaluate the load on the OpenSwitch server given the current resources. If the problem persists, call Sybase Technical Support. |
|
OpenSwitch may have temporarily run out of memory. Check previous errors in the OpenSwitch error log. You may need to allocate more memory to the OpenSwitch process, or reevaluate the load on the OpenSwitch server given the current resources. If the problem persists, call Sybase Technical Support. |
|
This is an internal OpenSwitch error. Call Sybase Technical Support for assistance. |
|
This is an internal OpenSwitch error. Call Sybase Technical Support for assistance. |
|
This is an internal OpenSwitch error. Check previous errors in the OpenSwitch error log. |
|
This is an internal OpenSwitch error. Call Sybase Technical Support for assistance. |
|
This is an internal OpenSwitch error. Check previous errors in the OpenSwitch error log. |
|
This is an internal OpenSwitch error. Check previous errors in the OpenSwitch error log. |
|
This is an internal OpenSwitch error. Call Sybase Technical Support for assistance. |
|
This is an internal OpenSwitch error. Call Sybase Technical Support for assistance. |
|
This error is usually raised when a client disconnects abruptly due to time-out or some other reason. If OpenSwitch behavior is not affected, you can safely ignore this error. Otherwise, call Sybase Technical Support for assistance. |
|
This error is usually raised when a client disconnects abruptly due to time-out or some other reason. If OpenSwitch behavior is not affected, you can safely ignore this error. Otherwise, call Sybase Technical Support for assistance. |
|
This is an internal OpenSwitch error. and may be due to insufficient memory or number of file descriptors. Check previous errors in the OpenSwitch error log. Check the total memory on the OpenSwitch host, and any limit on memory usage or file descriptors for OpenSwitch. |
|
This is an internal OpenSwitch error. Call Sybase Technical Support for assistance. |
|
This is an internal OpenSwitch error. Call Sybase Technical Support for assistance. |
|
This is an internal OpenSwitch error. Call Sybase Technical Support for assistance. |
|
This is an internal OpenSwitch error. Call Sybase Technical Support for assistance. |
|
This is an internal OpenSwitch error. Call Sybase Technical Support for assistance. |
|
OpenSwitch encountered a memory allocation failure. Check the total memory on the OpenSwitch host. Increase the memory available to OpenSwitch and restart the OpenSwitch server. |
|
This is an internal OpenSwitch error. Call Sybase Technical Support for assistance. |