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

KUP-04100: record rejected in file string

1 Answers  

---

ORA-01784: RECOVERABLE cannot be specified with database media recovery disabled

1 Answers  

---

IMG-00609: unable to read image stored in a BFILE

1 Answers  

---

ORA-07215: slsget: getrusage error.

1 Answers  

---

LCD-00113: integer conversion error or negative integer [string]

1 Answers  

---

ORA-32510: cannot create watchpoint on unreadable memory

1 Answers  

---

NNL-00904: NAME EXISTS responses sent: number

1 Answers  

---

ORA-12316: syntax error in database link's connect string

1 Answers  

---

IMG-00720: image processing internal error

1 Answers  

---

ORA-00329: archived log begins at change string, need change string

1 Answers  

---

PLS-00358: column 'string' exists in more than one table; use qualifier

1 Answers  

---

ORA-13217: invalid parameters supplied in ALTER INDEX statement

1 Answers  

---