Status on the Statistics Page

The Statistics page is displayed when you click Monitor on the Summary tab. It provides real-time statistical data about a bulk data transformation or a changed data transformation that is being performed currently. The page automatically refreshes every 2 seconds to display the most recent data. You can change the refresh interval on the Settings tab.

Table 17. Statistical Data in the Current Processing Details Pane

NameDescription
Since

For a bulk data transformation, this is the time when the transformation is started.

For a changed data transformation, this is the last time

  • You started the changed data transformation.

  • You reset the transformation statistics totals.

  • Data Exchange recovered from an error.

Datasets Processed / Tables ProcessedDisplays a progress bar of the number of datasets or tables that have been read from the transformation source during a bulk data transformation. It also displays the name of the dataset or table that is being read.
Records Processed / Transactions ProcessedThe number of records or transactions that have been read from the transformation source during a bulk data transformation or a changed data transformation, respectively.
Records ExtractedThe number of records that have been extracted from the transformation source during a bulk data transformation. This is applicable only for transformation with RDMS as the source.
Records PreparedThe number of records the OS 2200 Agent has read from the audit file and written to the OS 2200 data files, during a bulk data transformation. This is applicable only for transformation with RDMS as the source.
Tables PreparedThe number of tables the OS 2200 Agent has read from the audit file and written to the OS 2200 data files, during a bulk data transformation. This is applicable only for transformation with RDMS as the source.
Tables ProcessedThe number of tables the OS 2200 Agent has transferred and committed to the target database, during a bulk data transformation. This is applicable only for transformation with RDMS as the source.

Reading Audit Trail / Latest Audit Trail

The name of the current audit file being read by the MCP Agent / The name of the latest audit file on the source database. This is updated when a new audit file is generated.

Note: This is applicable only for a changed data transformation with Enterprise Database Server as the source.

Last ABSN Read / Latest ABSN

The Audit Block Serial Number (ABSN) of the last audit trail which the MCP Agent has read / The latest ABSN on the source database. The Latest ABSN is updated when the source database is updated.

Notes:

  • This is applicable only for a changed data transformation with an Enterprise Database Server as the source.

  • The ABSN last read by the MCP Agent and the ABSN last committed to the target database can be different as the time taken to read the records and to commit them may be different.

  • If the MCP Agent has read all the source data and there is no new data generated in the source database, the Last ABSN Read is equal to the Latest ABSN. However, this does not mean that all the data read is committed to the target database.

  • When you give the command <mix> HI to the Agent (where <mix> is the task number), the Agent responds with the Audit File number / Audit Block number in use by Enterprise Database Server and Data Exchange, as follows:

    DE_AFN = <integer>, DE_ABSN = <integer>, DM_AFN = <integer>, DM_ABSN = <integer>

  • When you stop and resume a changed data transformation, Data Exchange reads the source database from the ABSN recorded in the Tracking DB and not from the Last ABSN Read.

    For example, assume the source database has data D1, D2, D3, and D4. During changed data transformation, the MCP Agent reads all the data and the Runtime Service commits D1 and D2 to the target database. At this point, if you stop the changed data transformation, the Tracking DB records the last committed data as D2. On resuming the transformation, the MCP Agent starts reading the source database from D3 and not from D4 onwards.

Reading Audit TrailThe name of the audit trail being read by the OS 2200 Agent. This is in the format Qualifier*Filename(cycle number). The audit trail cycle number is also displayed in Events, in the same format, when changed data transformation is resumed.

Note: This is applicable only for a changed data transformation with an RDMS schema as the source.

Last LSN Read / Latest LSN The Log Sequence Number (LSN) of the last audit trail which the DE Agent for SQL Server has read / The latest LSN generated on the source database.

Notes:

  • This is applicable only for a changed data transformation from a SQL Server to an Enterprise Database Server.

  • The LSN last read by the DE Agent for SQL Server and the LSN last committed to the target database can be different as the time taken to read the records and to commit them may be different.

  • If the DE Agent for SQL Server has read all the source data and there is no new data generated in the source database, the Last LSN Read is equal to the Latest LSN. However, this does not mean that all the data read is committed to the target database.

  • When you stop and resume a changed data transformation, Data Exchange reads the source database from the LSN recorded in the Tracking DB and not from the Last LSN Read.

    For example, assume the source database has data D1, D2, D3, and D4. During changed data transformation, the DE Agent for SQL Server reads all the data and the Runtime Service commits D1 and D2 to the target database. At this point, if you stop the changed data transformation, the Tracking DB records the last committed data as D2. On resuming the transformation, the DE Agent for SQL Server starts reading the source database from D3 and not from D4 onwards.

Transformation TargetThe full name of the transformation target in the <host name>\<database name> format.
Transactions

The number of transactions that have been committed to the transformation target.

Record UpdatesThe number of SQL commands committed to the transformation target. The SQL commands are committed in transactions. For example, if the Runtime Service commits 100 SQL commands in a batch, then the Record Updates field shows 100 and the Transactions field shows 1.
Truncations / Feature Values TruncatedThe number of target data columns in which the source data has been truncated according to the Data Transform Error Handling Policy that you have defined in the DDW.
Transform RejectionsThe number of records that have been rejected according to the Data Transform Error Handling Policy that you have defined in the DDW.
Records IgnoredThe number of records that have been ignored while committing the records to the transformation target. The records are ignored according to the settings in the Target Commit Error Handling Policy.


Note: For a changed data transformation, you can reset these values to zero (except the audit file and the ABSN number) by clicking the Reset button on the Changed Data Transformation Statistics pane. An automatic recovery of the changed data transformation resets the values to zero.