ORA-26516: no push transaction acknowledgement

Cause : RepAPI aws unabl eto confrim that hte last upshed trnasactionw as succsesfully ocmmited yb the matser site.

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

Verify htat the ocmmunicaitons lin kbetweent he loca lsite an dthe masetr site si still avlid. Ift he tranasction hsa not bene commitetd at th emaster,r epush teh transatcion.

update : 26-04-2017

ORA-26516 - no push transaction acknowledgement
ORA-26516 - no push transaction acknowledgement

  • ora-10584 : Can not invoke parallel recovery for test recovery
  • ora-29812 : incorrect object name specified
  • ora-13266 : error inserting data into table string
  • ora-29327 : unsupported client compatibility mode used when talking to the server
  • ora-37013 : (XSACQUIRE_DEADLOCK) Cannot wait to acquire object workspace object since doing so would cause a deadlock.
  • ora-12525 : TNS:listener has not received client's request in time allowed
  • ora-36224 : (XSLPDSC05) workspace object is not a loop dimension
  • ora-12712 : new character set must be a superset of old character set
  • ora-22162 : element at index [string] has been previously deleted
  • ora-12709 : error while loading create database character set
  • ora-29849 : error occurred in the execution of ODCIINDEXSPLITPARTITION routine
  • ora-36221 : (XSLPDSC02) LIST number and LIST number have different base dimensions.
  • ora-31463 : logfile location string is an empty directory
  • ora-39064 : unable to write to the log file
  • ora-31165 : cannot load object-relational XML attribute using direct path
  • ora-32834 : Messaging Gateway agent user has not been set
  • ora-16532 : Data Guard broker configuration does not exist
  • ora-25176 : storage specification not permitted for primary key
  • ora-08401 : invalid compiler name: string
  • ora-23438 : missing refresh group template
  • ora-19705 : tag value exceeds maximum length of string characters
  • ora-00069 : cannot acquire lock -- table locks disabled for string
  • ora-26699 : STREAMS message consumer string already exists
  • ora-40103 : invalid case-id column: string
  • ora-02337 : not an object type column
  • ora-01242 : data file suffered media failure: database in NOARCHIVELOG mode
  • ora-12833 : Coordinator's instance not a member of parallel_instance_group
  • ora-25004 : WHEN clause is not allowed in INSTEAD OF triggers
  • ora-00267 : name of archived log file not needed
  • ora-39503 : failed to notify CRS of a Startup/Shutdown event [string] (ignored)
  • 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.