VisiTransact Guide : Error codes

Error codes
This chapter provides information about error codes for VisiTransact.
VisiTransact common error codes
The following table lists common error codes for VisiTransact.
Start the Smart Agent using the osagent command. See the VisiBroker ORB documentation for details.
VisiTransact Transaction Service error codes
The following table lists the error codes for the VisiTransact Transaction Service.
The request to shutdown the instance of the VisiTransact Transaction Service was issued without the -immediate argument, allowing the instance to let outstanding transactions enter the completion stage before exiting.
The request to shutdown the instance of the VisiTransact Transaction Service was issued with the -immediate argument, allowing the instance to shutdown without letting outstanding transactions enter the completion stage.
Session Manager error codes
The table lists the error codes for the Session Manager.
The transaction context did not exist when getConnection() was invoked because begin() was not called before it.
Make sure your program invokes begin() before calling getConnection().
An invalid value was specified for the SMconnection_idle_timeout attribute.
A negative value was specified for SMconnection_idle_timeout.
The getInfo() invocation in your program is passing an incorrect infotype.
See getInfo() in the VisiBroker for C++ API Reference for common infotypes accepted by the getInfo() method. See “XA Session Manager for Oracle OCI, version 9i Client” and “DirectConnect Session Manager for Oracle OCI, version 9i Client” for database-specific infotypes that are accepted.
The hold() operation is not supported.
The application called hold() on a connection which does not support that operation.
Use isSupported() to determine connections for which this operation is valid.
See “Problem determination” for troubleshooting tips.
Previous hold() call has timed out; connection must be released.
The timeout value supplied to the hold() call has expired and the connection object may no longer be used.
Call release() on this connection and call getConnection() again if still required.
VisiTransact transaction log error codes
The following table lists error codes for the VisiTransact transaction log.