Sunday, March 24, 2013

ORA-00162 External dbid Length String is Greater than Maximum

ErrorCode
ORA-00162

Description
External dbid length string is greater than maximum (string).

Cause
Possible cause of this error is, an external database name with too large a length field was passed in.

Action
To fix this error, report the problem to your external transaction coordinator vendor.

reference

ORA-00161 Transaction Branch Length String is Illegal

Error Code
ORA-00161

Description
Transaction branch length string is illegal (maximum allowed string).

Cause
Possible cause of this error is, an external transaction branch ID with a length either too large or 0 was passed in.

Action
To fix this error, report the problem to your external transaction coordinator vendor.

reference

Saturday, March 23, 2013

ORA-00160 Global Transaction Length String is Greater than Maximum

Error Code
ORA-00160

Description
Global transaction length string is greater than maximum (string).

Cause
Possible cause of this error is, an external global transaction ID with a too large length field was passed in.

Action
To fix this error, report the problem to your external transaction coordinator vendor.

reference

ORA-00155 Cannot Perform Work Outside of Global Transaction

Error Code
ORA-00155

Description
Cannot perform work outside of global transaction.

Cause
Possible cause of this error is, 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
To fix this error, 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.

reference

Sunday, March 3, 2013

ORA-00154 Protocol Error in Transaction Monitor

Error Code
ORA-00154

Description
Protocol error in transaction monitor.

Cause
Possible cause of this error is, the transaction monitor returned TMJOIN on an AX_REG call but the transaction was locally suspended.

Action
To fix this error, contact the transaction monitor customer support.

reference