ORA-26518: push queue synchronization error detected
- 1 Answers
- 3767 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 |
TNS-00220: Pump Breakdown --------------
ORA-12811: PARALLEL_MIN_SERVERS must be less than or equal to PARALLEL_MAX_SERVERS, string
NNO-00084: domain "string" is not in the authoritative domain list
PCC-02355: Invalid or obsolete option, ignored
ORA-19717: for non-OMF search the pattern must be specified
ORA-12494: cannot insert or delete a level, category, or release category
ORA-13632: The user cancelled the current operation.
O2U-00202: Invalid data passed to function
imp-00038: could not convert to environment character set's handle error occurs while importing oracle 10g data into oracle 9i database.
IMP-00029: cannot qualify table name by owner (string), use FROMUSER parameter
ORA-27201: skgfpcm: sbtpccommit returned error
ORA-10642: Found rollback segments in dictionary managed tablespaces
Oracle Errors 
