ORA-26518: push queue synchronization error detected
- 1 Answers
- 2574 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-22278: must update the LOB only through the LOB buffers
PLS-00533: Tables of non_queryable types are not supported.
QSM-02004: grouping column omitted from SELECT list
DRG-11813: Moved Temporarily
ORA-23321: Pipename may not be null
PCC-00073: Cursor is declared but never OPENed at line number in file string.
ORA-14156: invalid number of subpartitions specified in [SUBPARTITIONS | SUBPARTITION TEMPLATE] clause
ORA-06930: CMX: error when checking ORACLE_SID
PCC-02438: Arrays of collection objects are not allowed
ORA-08175: discrete transaction restriction violated (string)
TNS-04016: Connecting to string
KUP-00561: invalid length for binary integer field string
Oracle Errors 
