Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-26518: push queue synchronization error detected
- 1 Answers
- 3389 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-00227: Unable to contact pump; Connection Manager declared pump dead
ORA-13018: bad distance type
ORA-39727: COMPATIBLE must be set to 10.0.0.0.0 or higher
ORA-19637: backupPieceCreate requires file name when using DISK device
ORA-16808: unable to resolve the full path name
ORA-12421: different size binary labels
DRG-11806: Non-authoritative Information
SQL*Loader-00461: direct path loading of datatype for column string not supported
ORA-10641: Cannot find a rollback segment to bind to
ORA-23414: materialized view log for "string"."string" does not record rowid values
ORA-33066: (XSAGDNGL32) In AGGMAP workspace object, the hierarchy dimension QDR workspace object must be a hierarchy dimension of the relation.
ORA-01561: failed to remove all objects in the tablespace specified
Oracle Errors 
