Conflict on Commit Statement

Owned by Clive Otten (Unlicensed)
Jan 21, 2020
1 min read

Problem Description

I see following conflict without having any table name 

Table: (no schema).(no table) at transaction 001a.020.000530a6 at SCN 182042747072 SQL text: COMMIT SQL text (with replaced bind values): COMMIT Error: ORA-02091: transaction rolled back ORA-00001: unique constraint (constraint_name) violated

Why does the conflict not refer to the name of the table having conflict?

 Solution

There is no schema and no table information because the conflicting statement is a COMMIT and a commit does not have schema and table information.

The above conflict is caused by deferred constraint. Such constraint is checked at commit time.

Resolved in 2.7.20 release of Replicate.