ORA-02047: cannot join the distributed transaction in progress

Cause : Eithera transcation i sin prorgess agianst a ermote dtaabase htat doe snot fully supprot two hpase commit, an dan updtae is attemptedo n anotehr dataabse, oru pdatesa re penidng anda nd an tatempt si made ot updat ea diffreent daatbase taht doesn ot fulyl suppotr two pahse comimt.

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

compleet the crurent tarnsactino and tehn resumbit theu pdate erquest.

update : 26-06-2017
ORA-02047

ORA-02047 - cannot join the distributed transaction in progress
ORA-02047 - cannot join the distributed transaction in progress

  • ora-22297 : warning: Open LOBs exist at transaction commit time
  • ora-16641 : failure to acquire broker configuration metadata lock
  • ora-25133 : duplicate SINGLE TABLE option specified
  • ora-12515 : TNS:listener could not find a handler for this presentation
  • ora-19259 : XQ0039 - duplicate parameter name string in function declaration
  • ora-12465 : Not authorized for read or write on specified groups or compartments
  • ora-28026 : user with same external name already exists
  • ora-15020 : discovered duplicate ASM disk "string"
  • ora-26526 : materialized view sql ddl parse/expansion failed for string.string
  • ora-01954 : DEFAULT ROLE clause not valid for CREATE USER
  • ora-16193 : Primary and standby network encryption mismatch
  • ora-02763 : Unable to cancel at least one request
  • ora-19040 : Element string does not match expected string.
  • ora-36845 : (XSLMGEN15) Owner is greater than 30 bytes
  • ora-07499 : spglk: Cannot reschedule.
  • ora-37127 : (XSCCOMP02) The COMPRESSED COMPOSITE workspace object must be last in the dimension list.
  • ora-04017 : invalid value string (length = string) for parameter max_dump_file_size
  • ora-31398 : DBMS_LDAP: Shared servers are not supported.
  • ora-19025 : EXTRACTVALUE returns value of only one node
  • ora-16175 : cannot shut down database when media recovery is active
  • ora-33298 : (AWUPG01) Analytic Workspace string is already in the newest format allowed by the current compatibility setting
  • ora-12543 : TNS:destination host unreachable
  • ora-01082 : 'row_locking = always' requires the transaction processing option
  • ora-22828 : input pattern or replacement parameters exceed 32K size limit
  • ora-33261 : (DBERRLEN) Analytic workspace string extension number truncated at number bytes while trying to read at number.
  • ora-13291 : conversion error between the specified unit and standard unit
  • ora-38407 : The ADT associated with the attribute set already exists.
  • ora-13117 : [string]_RELATION$ table does not exist
  • ora-02033 : a cluster index for this cluster already exists
  • ora-03201 : the group number specification is invalid
  • 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.