Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-26518: push queue synchronization error detected
- 1 Answers
- 3527 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 |
IMG-00810: boundary queue initialization failed
ORA-06790: TLI Driver: poll failed
NNO-00070: administrative region has changed, reloading domain data
ORA-29318: datafile string is online
ORA-02209: invalid MAXTRANS option value
ORA-15020: discovered duplicate ASM disk "string"
NNO-00801: Error: OCI_SUCCESS_WITH_INFO: string
PLS-00207: identifier 'string', applied to implicit cursor SQL, is not a legal cursor attribute
ORA-31439: subscription is already active
PLS-01424: Non-ANSI order of clauses
ORA-00025: failed to allocate string
ORA-01532: cannot create database; instance being started elsewhere
Oracle Errors 
