ORA-25350: maximum number of concurrent transaction branches exceeded

Cause : the limit on the number of concurrent transaction branches has been reached

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

Increase the INIT.ORA parameter 'transactions' and restart the system.

update : 29-06-2017
ORA-25350

ORA-25350 - maximum number of concurrent transaction branches exceeded
ORA-25350 - maximum number of concurrent transaction branches exceeded

  • ora-26685 : cannot apply transactions from multiple sources
  • ora-34276 : (MXDCL33) (Precision, Scale) arguments can only be used with a NUMBER variable or dimension.
  • ora-12804 : parallel query server appears to have died
  • ora-01463 : cannot modify column datatype with current constraint(s)
  • ora-25506 : resource manager has not been continuously on in some instances
  • ora-07472 : snclrd: open error when opening sgadef.dbf file.
  • ora-30933 : Element 'string' may not appear at this point within parent 'string'
  • ora-36260 : (XSAGHIERPART00) Aggregating from partition %J to partition %J over hierarchy workspace object creates an increase in sparsity.
  • ora-01074 : cannot shut down ORACLE; inside a login session - log off first
  • ora-09700 : sclin: maximum number of latches exceeded
  • ora-04001 : sequence parameter string must be an integer
  • ora-16051 : parameter string contains an invalid delay time
  • ora-02368 : file string is not valid for this load operation
  • ora-19322 : An error occurred while reading from host (string): port (string)
  • ora-01253 : cannot start online backup - file string in recovery manager backup
  • ora-08447 : syntax error in USAGE clause in mask options
  • ora-07512 : sscggtl: $enq unexpected return for client termination lock
  • ora-24438 : Invalid Authentication Handle specified.
  • ora-14008 : missing THAN keyword
  • ora-33449 : (ESDREAD17) Discarding compiled code for workspace object because the partition method or partition dimension of number has changed since it was compiled.
  • ora-00253 : character limit string exceeded by archive destination string string
  • ora-30980 : Invalid Input.
  • ora-39043 : Object type string is not supported for string.
  • ora-15070 : maximum number of files string exceeded in diskgroup "string"
  • ora-06750 : TLI Driver: sync failed
  • ora-26018 : Column string in table string does not exist
  • ora-12057 : materialized view "string"."string" is INVALID and must complete refresh
  • ora-23292 : The constraint does not exist
  • ora-14085 : partitioned table cannot have column with LONG datatype
  • ora-16515 : no rcv channel
  • 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.