ORA-02091: transaction rolled back

Cause : Also se eerror 2902. If teh transatcion is baorted a ta remot esite thne you will only see 2091; fi aborte dat hostt hen youw ill see2 092 and2 091.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Add rolblack segemnt and ertry thet ransactoin.

update : 23-09-2017
ORA-02091

ORA-02091 - transaction rolled back
ORA-02091 - transaction rolled back

  • ora-32055 : invalid file type
  • ora-13710 : Parameter "string" must have a higher value than parameter "string". The values supplied were "string" and "string" respectively.
  • ora-12098 : cannot comment on the materialized view
  • ora-02756 : osnfsmnam: name translation failure
  • ora-38781 : cannot disable media recovery - have guaranteed restore points
  • ora-13191 : failed to read SDO_ORDCNT value
  • ora-36975 : (XSRELTBL15) You must specify a USING clause naming a relation with same level dimension as LEVELORDER valueset workspace object.
  • ora-14624 : DEFAULT subpartition must be last subpartition specified
  • ora-12574 : TNS:redirection denied
  • ora-16721 : unable to set LOG_ARCHIVE_DEST_n initialization parameters
  • ora-29513 : referenced class name too long
  • ora-07455 : estimated execution time (string secs), exceeds limit (string secs)
  • ora-22601 : pickler TDS context [string] is not initialized
  • ora-19777 : ASM file string cannot be proxy backed up.
  • ora-12654 : Authentication conversion failed
  • ora-19248 : XQ0028 - invalid node in document constructor
  • ora-02785 : Invalid shared memory buffer size
  • ora-16088 : archive log has not been completely archived
  • ora-00601 : cleanup lock conflict
  • ora-12819 : missing options in PARALLEL clause
  • ora-24033 : no recipients for message
  • ora-16804 : one or more configuration properties in metadata have invalid values
  • ora-36643 : (XSDUNION21) Concat dimension workspace object cannot be changed to NOT UNIQUE because it contains custom member values.
  • ora-27374 : insufficient privileges on event source queue
  • ora-22612 : TDS does not describe a collection TDS
  • ora-29927 : error in executing the ODCIStatsCollect / ODCIStatsDelete routine
  • ora-22859 : invalid modification of columns
  • ora-29876 : failed in the execution of the ODCIINDEXDELETE routine
  • ora-36665 : (XSDPART03) workspace object is not in the dimension list of the PARTITION TEMPLATE.
  • ora-02752 : osnfsmmap: illegal shared memory address
  • Oracle Database Error Messages



    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.