ORA-00162: external dbid length string is greater than maximum (string)
Cause: An external database name with too large a length field was passed in.
Action: Report the problem to your external transaction coordinator vendor.
ORA-00162: external dbid length string is greater than maximum (string)
Cause: An external database name with too large a length field was passed in.
Action: Report the problem to your external transaction coordinator vendor.
ORA-00161: transaction branch length string is illegal (maximum allowed string)
Cause: An external transaction branch ID with a length either too large or 0 was passed in.
Action: Report the problem to your external transaction coordinator vendor.
ORA-00160: global transaction length string is greater than maximum (string)
Cause: An external global transaction ID with a too large length field was passed in.
Action: Report the problem to your external transaction coordinator vendor.
ORA-00155: cannot perform work outside of global transaction
Cause: The application tried to perform some work on either an Oracle 7.3 server or an Oracle8 server with local transactions disabled while outside of a global transaction.
Action: Check if the application is connected to an Oracle 7.3 server. The Transaction monitor must not return a NULL XID on an AX_REG call when the resource manager is Oracle 7.3. If the application is connected to an Oracle8 server, either set nolocal=f in the xa_open string or start a global transaction prior to attempting the work.
ORA-00154: protocol error in transaction monitor
Cause: The transaction monitor returned TMJOIN on an AX_REG call but the transaction was locally suspended.
Action: Contact the transaction monitor customer support
ORA-00153: internal error in XA library
Cause: The XA library could not access thread-specific pointers.
Action: Contact customer support.
ORA-00152: current session does not match requested session
Cause: The current session is not the same as the session that was passed into a upixado() call.
Action: Check your application.
ORA-00151: invalid transaction ID
Cause: The specified transaction ID does not correspond to an existing valid transaction.
Action: Check your application.
ORA-00150: duplicate transaction ID
Cause: Attempted to start a new transaction with an ID already in use by an existing transaction.
Action: Check your application
ORA-00134: invalid DISPATCHERS specification #string
Cause: The syntax for the n-th DISPATCHERS specification was incorrect.
Action: Refer to the Oracle Reference Manual for the correct syntax.