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 : 26-07-2017
ORA-02091

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

  • ora-02077 : selects of long columns must be from co-located tables
  • ora-10647 : Tablespace other than SYSTEM, string, string not found in read only mode
  • ora-16096 : ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY
  • ora-19759 : block change tracking is not enabled
  • ora-22927 : invalid LOB locator specified
  • ora-03201 : the group number specification is invalid
  • ora-22278 : must update the LOB only through the LOB buffers
  • ora-12400 : invalid argument to facility error handling
  • ora-06773 : TLI Driver: error reading command
  • ora-36673 : (XSDPART11) Use simple leaf values to identify concat dimension values in a VALUES LESS THAN clause, rather than the format.
  • ora-19001 : Invalid storage option specified
  • ora-01755 : Must specify an extent number or block number
  • ora-06810 : TLI Driver: could not set the IPX ethernet SAP at init
  • ora-24341 : bad mode specified
  • ora-36179 : (XSNOAGM) No AGGMAP was specified for VARIABLE workspace object.
  • ora-31477 : could not detach LogMiner session during cleanup
  • ora-12986 : columns in partially dropped state. Submit ALTER TABLE DROP COLUMNS CONTINUE
  • ora-29280 : invalid directory path
  • ora-16536 : unknown object type
  • ora-32641 : invalid expression in MODEL rule ORDER BY clause
  • ora-25016 : cannot specify column list for insert into nested table view column
  • ora-38601 : FI Not enough memory for frequent itemset counting: string
  • ora-24385 : Application context size or index is not valid
  • ora-12710 : CREATE CONTROLFILE character set is not known
  • ora-28342 : integrity check fails on column key
  • ora-24320 : unable to initialize a mutex
  • ora-27160 : process requested to perform operation
  • ora-36843 : (XSLMGEN13) Dimension string.string!string hierarchy string is missing a PHYSICALNAME property value
  • ora-15055 : unable to connect to ASM instance
  • ora-09321 : slzdtb: unable to convert zoned decimal to binary
  • 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.