ORA-26518: push queue synchronization error detected
- 1 Answers
- 2952 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 |
DRG-50704: Net8 listener is not running or cannot start external procedures
ORA-24810: attempting to write more data than indicated
ORA-06571: Function string does not guarantee not to update database
RMAN-06575: platform id number found in datafile string header is not a valid platform id
ORA-00126: connection refused; invalid duplicity
ORA-12841: Cannot alter the session parallel DML state within a transaction
ORA-30941: Cannot specify empty URI for non-default namespace 'string'
ORA-08310: sllfop: Bad value for recsize
ORA-27120: unable to removed shared memory segment
ORA-32507: expecting string but found string
RMAN-03001: recovery manager command sequencer component initialization failed
ORA-01776: cannot modify more than one base table through a join view
Oracle Errors 
