ORA-24790: cannot mix OCI_TRANS_RESUME and transaction isolation flags

Cause : An attempt was made to change the isolation level of an existing transaction.

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

No action required

update : 23-04-2017
ORA-24790

ORA-24790 - cannot mix OCI_TRANS_RESUME and transaction isolation flags
ORA-24790 - cannot mix OCI_TRANS_RESUME and transaction isolation flags

  • ora-24502 : codepoint length overflows
  • ora-30938 : No prefix defined for namespace 'string' (particle string)
  • ora-02071 : error initializing capabilities for remote database string
  • ora-40253 : no target counter examples were found
  • ora-36686 : (XSDPART24) Value number is not in partition number.
  • ora-29339 : tablespace block size string does not match configured block sizes
  • ora-13122 : invalid topo_geometry specified
  • ora-29817 : non-supported option with disassociate statement
  • ora-26013 : List allocated may not be big enough
  • ora-15121 : ASM file name 'string' contains an invalid diskgroup name
  • ora-27484 : Argument names are not supported for jobs without a program.
  • ora-14617 : cannot add/drop values to DEFAULT subpartition
  • ora-38776 : cannot begin flashback generation - flash recovery area is disabled
  • ora-07681 : sou2os: An error occurred while initializing Oracle
  • ora-16051 : parameter string contains an invalid delay time
  • ora-14645 : STORE IN clause cannot be specified for Range List objects
  • ora-12334 : database (link name string) is still open
  • ora-16579 : bad Data Guard NetSlave state detected
  • ora-13838 : invalid ADDRESS value
  • ora-35276 : (SNSYN163) The format of the ALLOCATE command is: ALLOCATE varname [SOURCE svarname] [BASIS bvarname [ACROSS dimname]] [TARGET tvarname [TARGETLOG logvarname]] [ USING aggmap ]
  • ora-30928 : Connect by filtering phase runs out of temp tablespace
  • ora-16621 : database name for ADD DATABASE must be unique
  • ora-12324 : cannot use the ROM: link type on a private database link
  • ora-13210 : error inserting data into the index table
  • ora-27004 : invalid blocksize specified
  • ora-00490 : PSP process terminated with error
  • ora-28662 : IOT index and overflow segments must share the same LOGGING attribute
  • ora-14609 : Tablespace was not specified for the previous lob segments of column string in template but is specified for string
  • ora-16082 : logical standby is not initialized correctly
  • ora-01269 : Destination parameter string is too long
  • 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.