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-04-2017
ORA-25350

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

  • ora-16209 : Logical standby dictionary build failed to complete.
  • ora-01946 : DEFAULT TABLESPACE already specified
  • ora-14194 : only one subpartition may be rebuilt
  • ora-29395 : cannot set the initial consumer group to string
  • ora-01867 : the interval is invalid
  • ora-14640 : add/coalesce index partition operation is valid only for hash partitioned global indexes
  • ora-30695 : JDWP message format problem
  • ora-02194 : event specification syntax error string (minor error string) near 'string'
  • ora-32810 : foreign queue string is not registered
  • ora-16501 : the Data Guard broker operation failed
  • ora-00027 : cannot kill current session
  • ora-30006 : resource busy; acquire with WAIT timeout expired
  • ora-39060 : table(s) dropped because of conflict with master table
  • ora-00569 : Failed to acquire global enqueue.
  • ora-02728 : osnfop: access error on oracle executable
  • ora-01292 : no log file has been specified for the current LogMiner session
  • ora-07753 : slemcf: fseek before write failure
  • ora-12420 : required procedures and functions not in policy package "string"
  • ora-22331 : cannot alter an incomplete type
  • ora-29855 : error occurred in the execution of ODCIINDEXCREATE routine
  • ora-00256 : cannot translate archive destination string string
  • ora-07744 : slemcl: invalid error message file handle
  • ora-24058 : cannot downgrade QUEUE_TABLE that has propagation in a prepared state
  • ora-06028 : NETASY: unable to intialise for logging
  • ora-01298 : conflicting dictionary option
  • ora-06920 : CMX: getbrkmsg illegal datatype
  • ora-19738 : cannot find language information for character set: 'string'
  • ora-29283 : invalid file operation
  • ora-12515 : TNS:listener could not find a handler for this presentation
  • ora-07495 : spwat: lm_wait failed.
  • 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.