ORA-24772: Cannot mix tightly-coupled and loosely-coupled branches

Cause : Application attempted to start a transaction with a global transaction identifier and a wrong option.

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

Verify that all branches of a global transaction are started with either OCI_TRANS_TIGHT or OCI_TRANS_LOOSE option. If the application is correct and uses distributed updates, contact customer support.

update : 17-08-2017

ORA-24772 - Cannot mix tightly-coupled and loosely-coupled branches
ORA-24772 - Cannot mix tightly-coupled and loosely-coupled branches

  • ora-01903 : EVENTS keyword expected
  • ora-13421 : null or invalid cell value
  • ora-13712 : Cannot perform ADDM analysis on AWR snapshots from previous releases. Snapshot version "string" do not match the database version "string".
  • ora-01513 : invalid current time returned by operating system
  • ora-39137 : cannot specify a TABLE_EXISTS_ACTION of string for a job with no metadata
  • ora-30364 : this level has the same set of columns as another
  • ora-00406 : COMPATIBLE parameter needs to be string or greater
  • ora-33454 : (ESDREAD07) Discarding compiled code for workspace object because number is now string workspace object, whereas it was string workspace object when the code was compiled.
  • ora-30388 : name of the rewrite equivalence is not specified
  • ora-22289 : cannot perform string operation on an unopened file or LOB
  • ora-12319 : database (link name string) is already open
  • ora-31607 : function string is inconsistent with transform.
  • ora-39166 : Object string was not found.
  • ora-30976 : invalid Parent Order Key Index option for XML Index
  • ora-23352 : duplicate destination for deferred transaction
  • ora-06810 : TLI Driver: could not set the IPX ethernet SAP at init
  • ora-17504 : ksfddel:Failed to delete file string
  • ora-00487 : CTWR process terminated with error
  • ora-19599 : block number string is corrupt in string string
  • ora-30433 : 'string.string' is not a summary
  • ora-16511 : messaging error using ksrget
  • ora-15107 : missing or invalid ASM disk name
  • ora-29375 : sum of values string for level string, plan string exceeds string
  • ora-25253 : listen failed, queue string.string is not enabled for dequeue
  • ora-06915 : CMX: unknown t_event in datarq
  • ora-08114 : can not alter a fake index
  • ora-14001 : LOCAL clause contradicts previosly specified GLOBAL clause
  • ora-13144 : target table string not found
  • ora-32006 : %s initialization parameter has been deprecated
  • ora-16783 : instance string not open for read and write access
  • 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.