Resolver Reports Menu (Replicator Manager)

The Resolver Reports Menu appears when you select the Resolver option on the Replicator Manager main menu. From this window you can choose reports, which are useful as tools to maintain the consistency and integrity of your replicated databases.

Note: For the equivalent functionality using Visual DBA, see Replication Monitoring Using Visual Performance Monitor or Visual DBA.

The Resolver Reports Menu has the following options:

Collision
Provides a list of collision conflicts between the local database and all the targets that have pending transactions in the distribution queue.
Integrity
Provides a comparison of a replicated table between the local database and another database.
Distrib Config
Provides a Distributed Configuration Checker Report that details any significant differences between the local database and remote database configurations. These database differences include registered tables and columns, database number, name, node, and so on.
Databases
Provides a listing of the replicated databases defined in the local database.
CDDS
Provides a listing of all CDDSs defined in the local database and their propagation paths.
Tables
Provides registration status of the tables and columns defined in the local database.

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.

Table Integrity Report Window

The Table Integrity Report window appears when you select the Integrity option from the Resolver Reports Menu window. This window allows you to define a report that compares a table in the local database against the same table in a different database.

You specify the criteria for the comparison based on transaction begin and end time, and if desired, a CDDS value to designate a particular horizontal partition. You can also designate the sort order of the report by replicated column or transaction time.

The Table Integrity Report window has the following items:

Compare contents of table
Specifies the replicated table for the first and second database that you want to compare.
for owner
Identifies the owner of the table. If only one user owns a table by that name, this field is automatically filled in. For tables with multiple owners, a pop-up table appears, which lets you select the appropriate owner.
in Consistent Distributed Data Set (optional)
(Optional) Identifies the value of the CDDS number to be reported. If the table is not horizontally partitioned, this field is automatically filled in with the CDDS number under which the table is registered.

For horizontally partitioned tables, enter a CDDS number from the CDDS lookup table. You can use ListChoices to view a list of acceptable values.
in Database Number 1
Identifies the number of the local database. This field is automatically filled in.
and Database Number 2
Identifies the number of the other database that you want to compare with the local database.
Begin
(Optional) Specifies the beginning of a date range in standard Ingres date and time format.
End
(Optional) Specifies the end of a date range in standard Ingres date and time format.
Column Name
Displays the names of all registered columns for the specified table. A trans_time column also appears representing the transaction time.
Order
Lets you display rows in a specific order. Enter values (in numerical sequence starting with 1) beside each column name.
Go
Executes the report.

How the Table Integrity Report Is Created

When you execute the report, the Integrity option checks whether the table structure or a secondary index force the table keys to be unique. If the keys are not unique, this information appears in the report. The Integrity option compares the shadow tables of the selected table and reports any rows that are present in one but not in the other.

This comparison is performed on the entire row. If there is a row that differs in only one column, it appears in the report as having one set of data missing from the second database, and the slightly different data is reported as missing from the local database. The report shows which database holds the data and all of the columns and values.

The following is an example of the Table Integrity Report:

Ingres Replicator

Table Integrity Report
For table 'rep_dba.emp' in 'nyc::hq'
And table 'euro_dba.emp' in 'lon::europe'
Row only in 'nyc::hq', not in 'lon::europe'
database no: 10, transaction id: 811660429, sequence no: 1.
     *name: Doe, John
      manager: Jones, Ashley
      hourly_rate:               23.000
      title: Programmer
Row only in 'nyc::hq', not in 'lon::europe'
database no: 10, transaction id: 811660837, sequence no: 1.
     *name: Doe, Jane
      manager: Wolfe, Neal
      hourly_rate:               47.000
      title: Sr Programmer
Row only in 'lon::europe', not in 'nyc::hq'
database no: 20, transaction id: 811660329, sequence no: 1.
     *name: Doe, John
      manager: Wolfe, Neal
      hourly_rate:               25.000
      title: Programmer
Row only in 'lon::europe', not in 'nyc::hq'
database no: 20, transaction id: 811660780, sequence no: 1.
     *name: Doe, Jane
      manager: Ashley, Jones
      hourly_rate:               45.000
      title: Sr Programmer

Distributed Configuration Checker Report

The Distributed Configuration Checker Report verifies that the configuration information in a local database and its remote counterparts is identical where necessary. The report pinpoints any significant differences between the database objects and the configurations of those objects.

We recommend that you run this report after installing or reconfiguring Ingres Replicator as a way to ensure that you have no configuration errors.

The Distributed Configuration Checker Report checks the following items:

Replicated database information
CDDS information
Propagation path information
All tables registered for replication
All registered columns

The report is created when you choose the DistribConfig option from the Resolver Reports Menu window.

Following is an example of the Distributed Configuration Checker Report:

Ingres Replicator

Distributed Configuration Checker Report

From local database 'hq'

28-feb-2003 09:24:00

Report on remote database sfo::west (11):

DD_CDDS ERROR:

Record for CDDS no 3, CDDS name 'Accounting'

not found in remote database.

DD_REGIST_TABLES ERROR:

Support tables not created for local table no 4, table name 'tab1',

table owner 'testenv'.

Report on remote database lon::europe (20):

DD_CDDS ERROR:

CDDS no 0 has local collision mode of 0,

but remote collision mode of 2.

DD_CDDS ERROR:

Record for CDDS no 3, CDDS name 'Accounting'

not found in remote database.

DD_PATHS_ERROR:

Record for CDDS no 0, localdb no 10, sourcedb no 10,

targetdb no 11 not found in remote database.

DD_PATHS_ERROR:

Record for CDDS no 0, localdb no 10, sourcedb no 20,

targetdb no 11 not found in remote database.

DD_PATHS_ERROR:

Record for CDDS no 0, localdb no 10, sourcedb no 30,

targetdb no 11 not found in remote database.

DD_REGIST_TABLES ERROR:

Support tables not created for local table no 4, table name 'tab1',

table owner 'testenv'.

Report on remote database hkg::asia (30):

DD_CDDS ERROR:

CDDS no 0 has local collision mode of 0,

but remote collision mode of 2.

DD_CDDS ERROR:

Record for CDDS no 3, CDDS name 'Accounting'

not found in remote database.

DD_REGIST_TABLES ERROR:

Support tables not created for local table no 4, table name 'tab1',

table owner 'testenv'.

Replicated Databases Report

The Replicated Databases Report lists information about all replicated databases that are defined in the local database. It displays the Database Number, Virtual Node Name, Database Name, DBMS Type, Database Owner, and Remarks.

This report is equivalent to the contents of the Database Summary window.

The report is created when you choose the Databases option from the Resolver Reports Menu window.

Following is an example of the Replicated Databases Report:

28-Feb-2003 09:40:52

Ingres Replicator

Replicated Databases Report

hq 10

-----------------------------------------------------------------------

Database # Virtual Node Name / Database Name DBMS Type

Database Owner / Remarks

-----------------------------------------------------------------------

10 nyc::hq ingres

rep_dba

Headquarters database

11 sfo::west ingres

rep_dba

U.S. Western Region database

12 dal::central ingres

rep_dba

U.S. Central Region database

20 lon::europe ingres

euro_dba

European Region database

30 hkg::asia ingres

rep_dba

Asian Region database

CDDS Data Propagation Paths Report

The CDDS Data Propagation Paths Report displays a listing of the pathways for each CDDS. It displays the CDDS Number, Originating Database, Local Database, and Target Database.

This report is equivalent to the contents of the Propagation Path Definition window.

The report is created when you choose the CDDS option from the Resolver Reports Menu window.

Following is an example of the CDDS Data Propagation Paths Report:

28-Feb-2003 10:04:37

Ingres Replicator

hq 10 CDDS Data Propagation Paths Report

--------------------------------------------------------------------

CDDS No: 1 Inventory

Originating Database

Local Database

Target Database

--------------------------------------------------------------------

10 nyc::hq

11 sfo::west

10 nyc::hq

20 lon::europe

30 hkg::asia

20 lon::europe

10 nyc::hq

11 sfo::west

20 lon::europe

10 nyc::hq

20 lon::europe

30 hkg::asia

10 nyc::hq

20 lon::europe

11 sfo::west

30 hkg::asia

20 lon::europe

10 nyc::hq

30 hkg::asia

20 lon::europe

Registered Tables Report

The Registered Table Report displays the status of all replicated tables. This report is created when you select Tables from the Resolver Reports Menu window.

Following is an example of the Registered Tables Report:

28-Feb-2003 11:35:16

                              Ingres Replicator
                           Registered Tables Report
hq 10

-------------------------------------------------------------------------------
Table                            C S A     Priority Lookup Table
CDDS                                      CDDS Lookup Table
  Column                         Data type                              D K R
-------------------------------------------------------------------------------
book_list                        C S A
  1 Inventory
  book_no                        integer not null with default          1  K  R
  title                          varchar(40) not null with default            R
  author                         varchar(25) not null with default            R
  price                          money not null with default                  R
  category                       varchar(12) not null with default            R
  stock                          smallint not null with default               R
  dist_no                        smallint not null with default               R

book_orders                      C S A
  0 Default CDDS
  order_no                       integer not null with default          1  K  R
  book_no                        integer not null with default          2  K  R
  sale_price                     money with null                              R
  quantity                       smallint with null                           R
  extension                      money with null                              R

cust_info                        C S A
  0 Default CDDS
  cust_no                        integer not null with default 1 K R
  name                           varchar(25) not null with default            R
  company                        varchar(25) with null                        R
  street                         varchar(20) not null with default            R
  city                           varchar(20) not null with default            R
  state                          char(2) not null with default                R
  zip                            char(10) not null with default               R
  card_no                        varchar(30) not null with default            R
  ep_date                        date not null with default                   R
  ship_to                        char(1) not null with default                R

cust_orders                      C S A
  0 Default CDDS
  order_no                       integer not null with default          1  K  R
  cust_no                        integer not null with default                R
  order_date                     date not null with default                   R
  status                         varchar(15) not null with default            R
  order_total                    money with null                              R

C - Columns Registered           D - Table Key Sequence
S - Support Objects Created      K - Replicated Key Column
A - Change Recording Activated R – Replicated Column

The Registered Tables Report has the following items:

Table
The name of the table.
CDDS
The number and name of the CDDS to which the table belongs.
Column
The name of the column.
C (Columns Registered)
Indicates that the columns are registered.
S (Support Objects Created)
Indicates that support objects are created.
A (Change Recording Activated)
Indicates that change recording has been activated.
Data type
The data type and declared length of the column.
Priority Lookup Table
The name of the priority lookup table assigned to the table, if defined.
CDDS Lookup Table
The name of the horizontal partitioning lookup table assigned to the table, if defined.
D (Table Key Sequence)
A number indicates that the column is a key column in the base table structure and indicates the column's sequence in the key.
K (Replicated Key Column)
Indicates that the column is a key column for replication.
R (Replicated Column )
Indicates that the column is registered for replication.