ORA-26518: push queue synchronization error detected
- 1 Answers
- 2619 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 |
QSM-02091: mv references a non-repeatable or session-sensitive expression
ORA-23313: object group "string"."string" is not mastered at string
RMAN-20506: no backup of archivelog found
ORA-30380: REWRITE_TABLE does not exist
ORA-29324: SET COMPATIBILITY release string format is wrong
ORA-12211: TNS:needs PREFERRED_CMANAGERS entry in TNSNAV.ORA
ORA-22321: method does not return any result
EXP-00094: Could not convert to server national character set's handle
PLS-00049: bad bind variable 'string'
UDI-00051: unable to set NLS_NUMERIC_CHARACTERS to required defaults.
ORA-12571: TNS:packet writer failure
LCD-00219: nested include file [string] is too large
Oracle Errors 
