Queue Collision Report
The Queue Collision Report lists collision conflicts that exist on the local database. By reviewing the report, you can decide if you want to manually or automatically resolve each collision.
The report lists all collisions found from the distribution queue. It reports the type of collision (insert, update, delete) and the values of the columns in the local database, followed by the remote database where the collision occurred (number, node, name) and the values of the columns in the remote database. The end of the report displays the total number of collisions found.
Following is an example of the Queue Collision Report:
Ingres Replicator
Queue Collision Report
Local Database: 10 hq
INSERT Collision for table rep_dba.book_list
Local database
Source DB: 10 Transaction ID: 811660429 Sequence No: 1
*name: Doe, John
manager: Jones, Ashley
hourly_rate: 23.000
title: Programmer
Remote Database Number 20 Node: lon, Name: europe
*name: Doe, John
manager: Wolfe, Neal
hourly_rate: 25.000
title: Programmer
INSERT Collision for table rep_dba.book_list
Local database
Source DB: 10 Tansaction ID: 811660837 Sequence No: 1
*name: Doe, Jane
manager: Wolfe, Neal
hourly_rate: 47.000
title: Sr Programmer
Remote Database Number 20 Node: lon, Name: europe
*name: Doe, Jane
manager: Ashley, Jones
hourly_rate: 45.000
title: Sr Programmer
2 collision(s) found.
How the Queue Collision Report Is Created
When you select the Collision option from the Resolver Reports Menu window, and there are records in the distribution queue, the Collision Report is created.
When you execute the report, the distribution queue of the local database is read and the following searches are conducted to determine if there are any collisions:
• For insert operations, the remote base table is searched using the table key. If found, both records are displayed in the report.
• For update operations, the remote shadow table is searched using the replicated transaction key of the previous operation that manipulated the row. If not found, the collision is displayed with the local replicated transaction key. If the table key exists in the remote table, both records are displayed.
• For delete operations, the remote shadow table is searched using the replicated transaction key of the previous operation that manipulated the row. If not found, the collision is displayed with the local replicated transaction key.
Last modified date: 11/28/2023