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 : 24-05-2017
ORA-24772

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

  • ora-32634 : automatic order MODEL evaluation does not converge
  • ora-01501 : CREATE DATABASE failed
  • ora-23414 : materialized view log for "string"."string" does not record rowid values
  • ora-30974 : invalid Path Id Index option for XML Index
  • ora-30373 : object data types are not supported in this context
  • ora-06121 : NETTCP: access failure
  • ora-03200 : the segment type specification is invalid
  • ora-29928 : duplicate default selectivity specified
  • ora-30957 : cannot downgrade because there are XML indexes
  • ora-10284 : simulate zero/infinite asynch I/O buffering
  • ora-23382 : materialized view repgroup "string"."string" is not registered at site string
  • ora-01344 : LogMiner coordinator already attached
  • ora-09805 : conversion of category number to string failed.
  • ora-03262 : the file is non-empty
  • ora-22629 : OCIAnyData is null
  • ora-02401 : cannot EXPLAIN view owned by another user
  • ora-12318 : database (link name string) is already mounted
  • ora-16551 : short string copied
  • ora-01952 : system privileges not granted to 'string'
  • ora-14265 : data type or length of a table subpartitioning column may not be changed
  • ora-09812 : Unable to get user clearance from connection
  • ora-12533 : TNS:illegal ADDRESS parameters
  • ora-19641 : backup datafile checkpoint is SCN string time string
  • ora-10659 : Segment being shrunk is not a lob
  • ora-10627 : Dump the content of the index leaf block
  • ora-01269 : Destination parameter string is too long
  • ora-04092 : cannot string in a trigger
  • ora-22600 : encountered 8.0.2 (Beta) VARRAY data that cannot be processed
  • ora-31408 : invalid value specified for begin_scn or end_scn
  • ora-32588 : supplemental logging attribute string exists
  • 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.