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

ORA-30116: syntax error at 'string' following 'string'

1 Answers  

---

DRG-12507: stop word string already exists in this stoplist

1 Answers  

---

ORA-39128: unexpected DbmsJava error number from statement string

1 Answers  

---

DRG-50701: error in listener.get_cmd()

1 Answers  

---

KUP-11001: files not from the same unload operation

1 Answers  

---

DRG-11851: Cache Related Warning

1 Answers  

---

ORA-30654: missing DEFAULT keyword

1 Answers  

---

TNS-00302: Connection Manager: Unknown Request

1 Answers  

---

ORA-31600: invalid input value string for parameter string in function string

1 Answers  

---

ORA-00291: numeric value required for PARALLEL option

1 Answers  

---

NMP-00009: SNMP initialization failure

1 Answers  

---

ORA-09978: skxfqhdel: Error Disconnecting from another endpoint.

1 Answers  

---