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 : 25-04-2017
ORA-24772

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

  • ora-19620 : %s is not of string type
  • ora-29315 : tablespace 'string' has been recreated
  • ora-13711 : Some snapshots in the range [string, string] are missing key statistics.
  • ora-24265 : Insufficient privileges for SQL profile operation
  • ora-04016 : sequence string no longer exists
  • ora-02784 : Invalid shared memory ID specified
  • ora-24067 : exceeded maximum number of subscribers for queue string
  • ora-27376 : event condition cannot be NULL
  • ora-29915 : cannot select FOR UPDATE from collection operand
  • ora-23433 : executing against wrong master site string
  • ora-12562 : TNS:bad global handle
  • ora-32584 : missing LOG keyword
  • ora-25257 : consumer must be specified with a multi-consumer queue
  • ora-06131 : NETTCP: user access denied
  • ora-06911 : CMX: t_event returns ERROR
  • ora-24149 : invalid rule name
  • ora-06776 : TLI Driver: error sending parms
  • ora-13233 : failed to create sequence number [string] for R-tree
  • ora-35022 : (QFCHECK03) The analytic workspace and EIF file definitions of workspace object have a mismatched relation.
  • ora-26079 : file "string" is not part of table string.string
  • ora-14520 : Tablespace string block size [string] does not match existing object block size [string]
  • ora-28117 : integrity constraint violated - parent record not found
  • ora-01573 : shutting down instance, no further change allowed
  • ora-06416 : NETCMN: error on test
  • ora-14027 : only one PARTITION clause may be specified
  • ora-01513 : invalid current time returned by operating system
  • ora-27029 : skgfrtrv: sbtrestore returned error
  • ora-22329 : cannot alter a non-object type
  • ora-38903 : DML error logging is not supported for abstract column "string"
  • ora-08463 : overflow converting decimal number to Oracle number
  • 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.