ORA-26518: push queue synchronization error detected
- 1 Answers
- 2747 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 |
RMAN-06515: archived logs required to recover from this copy will expire when this copy expires
ORA-01646: tablespace 'string' is not read only - cannot make read write
PCB-00108: Unable to open list file "string"
PCC-00117: Invalid ARRAYLEN length variable type
SQL*Loader-00459: error fetching numeric value for sequence on column (string)
ORA-28024: must revoke grants of external roles to this role/user
ORA-37018: (XSACQUIRE03) Multiwriter operations are not supported for object workspace object.
PCC-00118: Use of host variable initialization not supported by ANSI SQL
ORA-07626: smsget: sga already mapped
ORA-28650: Primary index on an IOT cannot be rebuilt
NNL-00905: NOT AUTHORITY responses sent: number
ORA-36378: (XSAGTHRWEIGHT) While running AGGREGATE with multiple threads, the weight variable workspace object specified by your ARGS variable workspace object must exist in the same analytic workspace as your AGGMAP workspace object.
Oracle Errors 
