| 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-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-00069: cannot acquire lock -- table locks disabled for string |
 |
Cause: A command was issued that tried to lock the table indicated in the message. Examples of commands that can lock tables are: LOCK TABLE, ALTER TABLE... ADD (...), and so on. Action: Use the ALTER TABLE... ENABLE TABLE LOCK command, and retry the command.
Powered by !JoomlaComment 3.25
3.25 Copyright (C) 2007 Alain Georgette / Copyright (C) 2006 Frantisek Hliva. All rights reserved."
|
|||||||||||
| 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. |
