Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-26518: push queue synchronization error detected
- 1 Answers
- 3641 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: Client tried to repush a transaction has already been
committed at the master site. A common cause of this problem
is an error at the local site in initializing or updating
the local site transaction sequence mechanism.
Action: Verify that transaction data that RepAPI was
attempting to repushed to the master site exists at the
master table and is valid and consistent with the local
site. If this error occurs, redundantly identified
transactions are ignored and then purged from the local
updatable materialized view logs. Check that the local site
is correctly assigning new transactionIDs and is not
accidently generating non-unique values.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
ORA-28025: missing or null external name
ORA-24129: table name string does not start with string prefix
RMAN-06552: newname for datafile number was set to NEW, but file was not restored
ORA-28577: argument string of external procedure string has unsupported datatype string
ORA-00981: cannot mix table and system auditing options
ORA-25156: old style outer join (+) cannot be used with ANSI joins
ORA-27453: %s is an invalid job or program argument name.
TNS-00267: Navigator: Internal Error
ORA-31649: Master process string violated startup protocol.
ORA-16955: Unknown error during SQL analyze.
ORA-32586: multiple specification of a supplemental logging attribute
PCC-00068: Host and indicator variables may not have the same name.
Oracle Errors 
