| 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-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-01019: unable to allocate memory in the user side |
| Written by Administrator | ||||||||
| Friday, 28 March 2008 15:16 | ||||||||
Problem: The user side memory allocator returned error. Solution: Increase the processes heap size or switch to the old set of calls. 
Powered by !JoomlaComment 3.25
3.25 Copyright (C) 2007 Alain Georgette / Copyright (C) 2006 Frantisek Hliva. All rights reserved." |
||||||||
| Last Updated ( Friday, 28 March 2008 15:16 ) | ||||||||
| 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. |
