ORA-26518: push queue synchronization error detected
- 1 Answers
- 2976 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-02038: Partition Change Tracking (PCT) is enabled
ORA-06745: TLI Driver: listener already running
ORA-32018: parameter cannot be modified in memory on another instance
PCC-01003: Invalid continuation at line number in file string
ORA-19506: failed to create sequential file, name="string", parms="string"
ORA-30938: No prefix defined for namespace 'string' (particle string)
ORA-19901: database needs more recovery to create new incarnation
ORA-01673: data file string has not been identified
ORA-01925: maximum of string enabled roles exceeded
KUP-04035: beginning enclosing delimiter not found
ORA-01583: unable to get block size of controlfile to be backed up
ORA-31057: Display Name of the element being inserted is null
Oracle Errors 
