| 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-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-00029: session is not a user session |
| Written by Administrator | ||||||||
| Friday, 28 March 2008 15:30 | ||||||||
Cause: The session ID specified in an ALTER SYSTEM KILL SESSION command was not a user session (for example, recursive, etc.). Action: Retry with a user session ID. 
Powered by !JoomlaComment 3.25
3.25 Copyright (C) 2007 Alain Georgette / Copyright (C) 2006 Frantisek Hliva. All rights reserved." |
||||||||
| 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.
|
