Unique constraint error

When the gateway tries to insert duplicate records into the reporter_status or reporter_journal table, the transaction will fail due to a Unique Constraint error. The details are written to the gateway's log file.

Examples

Oracle:

22/04/28 03:50:16: Debug: [pool-3-thread-3] pool-3-thread-3: SQL State: 23000
22/04/28 03:50:16: Debug: [pool-3-thread-3] pool-3-thread-3: SQL Error code: 1
22/04/28 03:50:16: Debug: [pool-3-thread-3] pool-3-thread-3: SQL message: ORA-00001: unique constraint (REPORTER.SYS_C0010202) violated

DB2:

22/04/28 01:35:56: Error: [pool-3-thread-2] pool-3-thread-2: SQL State: 23505
22/04/28 01:35:56: Error: [pool-3-thread-2] pool-3-thread-2: SQL Error code: -803
22/04/28 01:35:56: Error: [pool-3-thread-2] pool-3-thread-2: SQL message: Error for batch element #1: DB2 SQL Error: SQLCODE=-803, SQLSTATE=23505, SQLERRMC=1;DB2INST1.REPORTER_JOURNAL, DRIVER=4.31.10

MySQL:

22/04/28 03:45:06: Debug: [pool-3-thread-2] pool-3-thread-2: SQL State: 23000
22/04/28 03:45:06: Debug: [pool-3-thread-2] pool-3-thread-2: SQL Error code: 1062
22/04/28 03:45:06: Debug: [pool-3-thread-2] pool-3-thread-2: SQL message: Duplicate entry '276127-JDBC-2022-04-27 23:52:09-0' for key 'reporter_journal.PRIMARY'

SQL Server:

22/04/28 03:59:18: Debug: [pool-3-thread-3] pool-3-thread-3: SQL State: 23000
22/04/28 03:59:18: Debug: [pool-3-thread-3] pool-3-thread-3: SQL Error code: 2627
22/04/28 03:59:18: Debug: [pool-3-thread-3] pool-3-thread-3: SQL message: Violation of PRIMARY KEY constraint 'PK__REPORTER__80F8C1D2D6CC1DA3'. Cannot insert duplicate key in object 'dbo.REPORTER_JOURNAL'. The duplicate key value is (0, Apr 27 2022 11:52PM, 276127, JDBC).

Note:

This is expected behavior because the gateway has previously inserted the event record into the reporter_status or reporter_journal table and this constraint prevents the gateway from inserting duplicate entries into those tables. This behavior occurs when the gateway cache files are deleted or do not exist due to a new installation, and the Gate.Jdbc.ResyncMode property is set to UNI or NONE and the gateway process is restarted. This behavior will not be seen when Gate.Jdbc.ResyncMode is set to BI as this will rebuild the cache files from the database table.