Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-26518: push queue synchronization error detected
- 1 Answers
- 3501 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-00507: Connection closed
ORA-30747: cannot create substitutable tables or columns of non final type string.string
ORA-01627: rollback segment number 'string' is not online
PCC-00032: Invalid option "string"
O2F-00324: Unable to convert from the database character set to the compiler character set
ORA-16225: Missing LogMiner session name for Streams
ORA-24141: rule set string.string does not exist
PCC-01511: Identifier on line number in file string too long for code generated in file string
SQL-02127: Precompiler/SQLLIB version mismatch
ORA-23437: template authorization already exists for user
ORA-25130: cannot modify primary key - primary key not defined for table
ORA-00356: inconsistent lengths in change description
Oracle Errors 
