Resources

Random Errors

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.

 

Random Errors

ORA-00133: value of string is too long

Cause: The value specified for the attribute was too long.

Action: Use shorter names and keywords or remove unneeded blanks.


Designed by:
SiteGround web hosting Joomla Templates
ORA-blog

 

Oracle Error Codes category contains full list of Oracle RDBMS errors supplied in Oracle documentation. Each error is divided in 2 sections CAUSE and ACTION.

 



ORA-00161: transaction branch length string is illegal (maximum allowed string)
Written by Administrator   
Monday, 31 March 2008 10:29

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)
Written by Administrator   
Monday, 31 March 2008 10:29

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-00154: protocol error in transaction monitor
Written by Administrator   
Monday, 31 March 2008 10:27

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-00155: cannot perform work outside of global transaction
Written by Administrator   
Monday, 31 March 2008 10:28

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.

 

Last Updated ( Tuesday, 17 June 2008 10:51 )
 
ORA-32121 Source FILE is null
Written by Administrator   
Friday, 28 March 2008 15:16

Problem: The source FILE instance on which the operation was attempted was null.

Solution: : Use a valid, non-null source FILE instance for this operation.

Last Updated ( Friday, 28 March 2008 15:16 )
 
ORA-00153: internal error in XA library
Written by Administrator   
Monday, 31 March 2008 10:27

Cause: The XA library could not access thread-specific pointers.

Action: Contact customer support.

 
ORA-00152: current session does not match requested session
Written by Administrator   
Monday, 31 March 2008 10:27

Cause: The current session is not the same as the session that was passed into a upixado() call.

Action: Check your application.

 
ORA-32147 Environment not specified
Written by Administrator   
Friday, 28 March 2008 15:16

Problem: The date on which the operation was attempted was null and no environment was specified.

Solution: : Specify a non-null environment or perform the operation on a non null instance.

Last Updated ( Friday, 28 March 2008 15:16 )
 
ORA-00151: invalid transaction ID
Written by Administrator   
Monday, 31 March 2008 10:26

Cause: The specified transaction ID does not correspond to an existing valid transaction.

Action: Check your application.

 
ORA-00022: invalid session ID; access denied
Written by Administrator   
Friday, 28 March 2008 15:25

Cause: Either the session specified does not exist or the caller does not have the privilege to access it.

Action: Specify a valid session ID that you have privilege to access, that is either you own it or you have the CHANGE_USER privilege.

 
ORA-00150: duplicate transaction ID
Written by Administrator   
Monday, 31 March 2008 10:26

Cause: Attempted to start a new transaction with an ID already in use by an existing transaction.

Action: Check your application.

 
ORA-02251: subquery not allowed here
Written by Administrator   
Friday, 28 March 2008 15:16

Problem: Subquery is not allowed here in the statement.

Solution: Remove the subquery from the statement.

Last Updated ( Friday, 28 March 2008 15:16 )
 
ORA-00134: invalid DISPATCHERS specification #string
Written by Administrator   
Monday, 31 March 2008 10:25

Cause: The syntax for the n-th DISPATCHERS specification was incorrect.

Action: Refer to the Oracle Reference Manual for the correct syntax.

 
ORA-30373 object data types are not supported in this context
Written by Administrator   
Friday, 28 March 2008 15:16

Problem: An object data type was encountered in an unsupported context.

Solution: : Re-specify the expression to avoid the use of objects.

Last Updated ( Friday, 28 March 2008 15:16 )
 
ORA-00023: session references process private memory; cannot detach session
Written by Administrator   
Friday, 28 March 2008 15:26

Cause: An attempt was made to detach the current session when it contains references to process private memory.

Action: A session may contain references to process memory (PGA) if it has an open network connection, a very large context area, or operating system privileges. To allow the detach, it may be necessary to close the session's database links and/or cursors. Detaching a session with operating system privileges is always disallowed.

 
ORA-00025: failed to allocate string
Written by Administrator   
Friday, 28 March 2008 15:27

Cause: Out of memory.

Action: Restart with larger sga heap.

 
ORA-00021: session attached to some other process; cannot switch session
Written by Administrator   
Friday, 28 March 2008 15:25

Cause: The user session is currently used by others.

Action: Do not switch to a session attached to some other process.

 
ORA-00133: value of string is too long
Written by Administrator   
Monday, 31 March 2008 10:24

Cause: The value specified for the attribute was too long.

Action: Use shorter names and keywords or remove unneeded blanks.

 
ORA-00030: User session ID does not exist.
Written by Administrator   
Friday, 28 March 2008 15:30

Cause: The user session ID no longer exists, probably because the session was logged out.

Action: Use a valid session ID.

 
ORA-00018: maximum number of sessions exceeded
Written by Administrator   
Friday, 28 March 2008 15:21

Cause: All session state objects are in use.

Action: Increase the value of the SESSIONS initialization parameter.

 

 
<< Start < Prev 1 2 3 4 5 6 7 8 9 10 Next > End >>

Page 1 of 347

Random Errors

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.

Resources

Oracle Database Support, Powered by Joomla! and designed by SiteGround web hosting