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-09-2017

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

  • ora-01280 : Fatal LogMiner Error.
  • ora-06434 : ssaio: read error, unable to read requested block from database file.
  • ora-00381 : cannot use both new and old parameters for buffer cache size specification
  • ora-19758 : failed to enable/disable block change tracking: out of SGA memory
  • ora-30569 : data type of given column is not supported in a log group
  • ora-26507 : null master connection
  • ora-24408 : could not generate unique server group name
  • ora-04032 : pga_aggregate_target must be set before switching to auto mode
  • ora-30732 : table contains no user-visible columns
  • ora-09746 : smscre: shared memory attach address incorrect.
  • ora-38712 : Corrupt flashback log record header: block string, offset string.
  • ora-10929 : trace name context forever
  • ora-28046 : Password change for SYS disallowed
  • ora-13911 : Threshold not found
  • ora-29278 : SMTP transient error: string
  • ora-24083 : cannot specify remote subscribers for string QUEUE string
  • ora-30567 : name already used by an existing log group
  • ora-10284 : simulate zero/infinite asynch I/O buffering
  • ora-10946 : trace name context forever
  • ora-04045 : errors during recompilation/revalidation of string.string
  • ora-12486 : effective max labels and min labels cannot be changed
  • ora-19576 : datafile string not defined in control file
  • ora-39316 : call to DBMS_SCHEMA_COPY.CLEAN_UP is not legal
  • ora-23354 : deferred RPC execution disabled for "string" with "string"
  • ora-40209 : setting % is invalid for % function
  • ora-01792 : maximum number of columns in a table or view is 1000
  • ora-06314 : IPA: Event set up failure
  • ora-00108 : failed to set up dispatcher to accept connection asynchronously
  • ora-01949 : ROLE keyword expected
  • ora-31621 : error creating master process
  • 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.