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 : 22-07-2017

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

  • ora-01986 : OPTIMIZER_GOAL is obsolete
  • ora-01977 : Missing thread number
  • ora-13296 : incorrect coordinate system specification
  • ora-39019 : invalid operation type string
  • ora-31451 : invalid value string for capture_values, expecting: OLD, NEW, or BOTH
  • ora-01261 : Parameter string destination string cannot be translated
  • ora-38954 : Cross platform transport is not supported between source platform identifier string and target platform identifier string
  • ora-16150 : FINISH recovery performed on another, older standby database
  • ora-24330 : internal OCI error
  • ora-10263 : Don't free empty PGA heap extents
  • ora-30361 : unrecognized string type
  • ora-19951 : cannot modify control file until DBNEWID is completed
  • ora-22804 : remote operations not permitted on object tables or user-defined type columns
  • ora-33292 : (DBERR18) insufficient permissions to access analytic workspace string using the specified access mode.
  • ora-08117 : Index Organized Table operation released its block pin
  • ora-13499 : %s
  • ora-01670 : new datafile string needed for standby database recovery
  • ora-36684 : (XSDPART22) You cannot rename values of DIMENSION workspace object because it is the partition dimension of RANGE PARTITION TEMPLATE workspace object
  • ora-24502 : codepoint length overflows
  • ora-26007 : invalid value for SETID or OID column
  • ora-13859 : Action cannot be specified without the module specification
  • ora-07703 : error in archive text: need '/' after device type
  • ora-02436 : date or system variable wrongly specified in CHECK constraint
  • ora-16221 : history table synchronization error
  • ora-09929 : GLB of two labels is invalid
  • ora-12927 : RETENTION option already specified
  • ora-26725 : cannot downgrade apply handlers
  • ora-10265 : Keep random system generated output out of error messages
  • ora-14510 : can specify VALIDATE INTO clause only for partitioned tables
  • ora-01504 : database name 'string' does not match parameter db_name 'string'
  • 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.