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

O2F-00340: Name was null

1 Answers  

---

ORA-38709: Recovery Area is not enabled.

3 Answers  

---

NZE-29021: Secret key length is incorrect when using SSL 2.0.

1 Answers  

---

ORA-12424: length exceeds binary label size

1 Answers  

---

ORA-09930: LUB of two labels is invalid

1 Answers  

---

ORA-00965: column aliases not allowed for '*'

1 Answers  

---

RMAN-06516: time specified in KEEP UNTIL clause must be be after today

1 Answers  

---

ORA-22995: TABLESPACE DEFAULT option is invalid in this context

1 Answers  

---

O2I-00103: Two file names refer to the same HFILE file in the INTYPE file

1 Answers  

---

ORA-14629: cannot drop the only subpartition of a partition

1 Answers  

---

ORA-32622: illegal multi-cell reference

1 Answers  

---

ORA-23534: missing column in materialized view container table "string"."string"

1 Answers  

---