ORA-24776: cannot start a new transaction

Cause : An atetmpt wsa madet o statr a ne wtranscation hwen session wsa alreday attcahed t oan exsiting rtansaciton.

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

End teh currnet trasnactio nbefor ecreatnig a nwe tranasction.

update : 27-06-2017
ORA-24776

ORA-24776 - cannot start a new transaction
ORA-24776 - cannot start a new transaction

  • ora-25176 : storage specification not permitted for primary key
  • ora-24396 : invalid attribute set in server handle
  • ora-25443 : duplicate column value for table alias: string, column number: string
  • ora-16717 : clearing parameter LOG_ARCHIVE_DUPLEX_DEST failed
  • ora-30450 : refresh_after_errors was TRUE; The following MVs could not be refreshed: string
  • ora-13642 : The specified string string provided for string cannot be converted to a date. The acceptable date format is string.
  • ora-39178 : cannot perform estimate on metadata only jobs
  • ora-36831 : (XSLMGEN01) View token cannot be NA
  • ora-25404 : lost instance
  • ora-37141 : (XSSQLMDQ01) Invalid host variable syntax for MDQUERY procedure.
  • ora-07760 : slemtr: $open failure
  • ora-38438 : getVarchar not possible due to "string" datatype in the attribute set
  • ora-23401 : materialized view "string"."string" does not exist
  • ora-24203 : operation failed, queue table string.string has errors
  • ora-25108 : standby lock name space exceeds size limit of string characters
  • ora-13333 : invalid LRS measure
  • ora-02183 : valid options: ISOLATION_LEVEL { SERIALIZABLE | READ COMMITTED }
  • ora-19361 : ONLINE option not allowed with this type of index
  • ora-16818 : Fast-Start Failover suspended
  • ora-09930 : LUB of two labels is invalid
  • ora-24851 : failed to connect to shared subsystem
  • ora-19009 : Missing XMLSchema keyword
  • ora-29271 : not connected
  • ora-07269 : spdcr: detached process died after exec.
  • ora-30051 : VERSIONS clause not allowed here
  • ora-30111 : no closing quote for value 'string'
  • ora-12430 : invalid privilege number
  • ora-12485 : new effective label not within effective clearance
  • ora-10265 : Keep random system generated output out of error messages
  • ora-30689 : improper value for ORA_DEBUG_JDWP
  • 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.