Table 8. Source Data Details
| Components | Description |
| Database Name Note: This field is applicable only for an Enterprise Database Server database and a SQL Server database. | The name of the transformation source that is created in the Enterprise Database Server and SQL Server. For Enterprise Database Server, the name includes the user ID and the pack name. |
| Application Group Note: This field is applicable only for an RDMS schema. | The name of the Application Group that is created on the OS 2200 host. |
| Data Manager Type Note: This field is applicable only for an Enterprise Database Server database and a SQL Server database. | The DBMS that the transformation source is using. For example, for Enterprise Database Server DBMS, the Data Manager Type is DMSII; for SQL Server DBMS, the Data Manager Type is SQL Server. |
| SQL Instance Note: This field is applicable only for a SQL Server database. | The instance of the SQL Server. |
| Host Name | The name or the IP address of the host where the DBMS is running. |
| Host Type | The type of the host where the DBMS is running. If the DBMS is running on an MCP host, then the Host Type is MCP. |
Table 9. Status of Runtime Components on the Data Exchange Runtime Overview Pane
| Components | Status | Description |
|---|---|---|
| Data Exchange Status | Error | Either the MCP Agent or the Runtime Service is not running, or it resulted in an error the last time it was run. See the event log for more details. |
| Stopped | Components are ready to perform a changed data transformation or a bulk data transformation. | |
| Changed Data Transformation Running | Components are performing a changed data transformation. | |
| Recovering | An error occurred after initiating a changed data transformation. Data Exchange is trying to restart the changed data transformation or waiting for the next retry attempt. | |
| Bulk Data Transformation Running | Components are performing a bulk data transformation. | |
| Bulk Data Transformation Completed | The bulk data transformation is completed. | |
| Starting | This is an intermediate status. | |
| Stopping | This is an intermediate status. | |
| Agent Status | Connection Failed | Connection to the Agent failed because either the Agent TCP port is incorrect or a firewall is blocking the connection. Connection could also have failed if the MCP host, network, or the Agent is down. |
| Application Error | An application error occurred in the Agent. | |
| Audit Error | The Agent experienced an issue reading the Audit file or the CDC tables. | |
| Data Exchange Disabled | The DASDL file for the source database is not enabled for use in Data Exchange. | |
| Handshake Failed | The handshake reply from the Agent was not valid. | |
| Configuration Error | The configuration of the Agent is out of date. | |
| Product Version Mismatch | The version of the Agent does not match with the version of the Administrative Service. | |
| Error | An unexpected error occurred. | |
| Reserved by Another Administrative Service | More than one Administrative Service tried to connect to the same MCP Agent. | |
| Source Database Unavailable | The MCP database is in unusable status. | |
| Invalid License | The outbound license key was not provided during installation. | |
| Runtime Service Status | Product Version Mismatch | The version of the Runtime Service does not match the version of the Administrative Service. |
| Transform Error | An error occurred when the Runtime Service was loading or processing a transformation. | |
| Initialization Error | An error occurred while initializing the Runtime Service. | |
| Transformation Target Update Error | There was an error when the Runtime Service was updating a transformation target. | |
| Tracking DB Error | There was an error when the Runtime Service was updating the tracking DB. | |
| Schema Mismatch | The schema of the source database changed since it was loaded into the DDW and the transformation was deployed. | |
| Connection Failed | The connection to the Runtime Service failed. | |
| Error | An unexpected error occurred. | |
| SQL Server Connection Error | The Runtime Service was unable to connect to the SQL Server. | |
| DMSII Connection Error | The Runtime Service was unable to connect to the Enterprise Database Server. | |
| Transformation Details (Bulk Data Transformation and Changed Data Transformation) | Not Run | The transformation is not yet run. |
| In Progress | The transformation is in progress. | |
| Completed | The transformation completed. |
The Transformation Overview pane provides the status of the transformations available on the selected transformation source.
Table 10. Status of Transformations on the Transformation Overview Pane
| Status | Description |
|---|---|
| Active | The transformation is active and is currently used or ready to be used for a changed data transformation or a bulk data transformation. |
| Inactive | This is the default status of a transformation when it is deployed from the DDW. You must activate the transformation to run a changed data transformation or bulk data transformation. |
| Out of Sync | A newer version of the same transformation is deployed from the DDW while the older version is currently used in a changed data transformation or a bulk data transformation. To use the newer version, you must stop the transformation that is running. |
| Migration Required | This is applicable after upgrading Data Exchange to a newer
version. This is the status if the transformations are deployed from
an older version of the DDW. You need to update these transformations in the DDW and redeploy them to the Administration Site. If the transformations exist in a DDW Repository, the newer version of the DDW can automatically update the transformations. If the transformations are not available in any DDW Repository, you can download them from the Administration Site into .xml files and import them into the newer version of the DDW. |
The Transformation Source Information pane provides information about the transformation source.
The Schema Information pane provides basic information about the schema.
Table 11. RDMS Schema Information
| Name | Description |
|---|---|
| Schema Name | The name of the schema that you selected. |
| Data Manager Type | The Data Manager Type is RDMS. |
| Application Group | The name of the Application Group that the schema is associated with. |
| Host Name | The host name of the OS 2200 Server where the RDMS is running. |
| Host Type | The host type is OS 2200. |
The Bulk Data Transformation Details pane provides information about the most recent bulk data transformation.
Table 12. Bulk Data Transformation Details: General Information
| Components | Description | |
|---|---|---|
| Status | Completed | Bulk data transformation for a transformation source is completed. |
| Not Run | Bulk data transformation for a transformation source is not initiated. | |
| Incomplete | Bulk data transformation stopped abruptly because of some error, but the status shows as completed. | |
| Running | Bulk data transformation is currently in progress. | |
| Start Time | The time when the bulk data transformation was started. | |
| Completion Time | The time when the bulk data transformation completed. | |
The Bulk Data Transformation Settings pane provides general information about the most recent or currently running bulk data transformation.
Table 13. Bulk Data Transformation Settings (for Enterprise Database Server as the Transformation Source)
| Components | Description |
| Host Name | The name of the host where the DBMS is running. |
| Database Name | The name of the transformation source that was created in the source DBMS. Note that for an Enterprise Database Server, the source can be the clone of the original transformation source. |
| User | The usercode of the database user. If in the MCP host the user is associated with an accesscode or a chargecode or both, then the accesscode and/or chargecode is also displayed. |
| No.Of Processors. | The number of processing threads allocated for performing the bulk data transformation. |
Table 14. Bulk Data Transformation Settings (for Application Group as the Transformation Source)
| Components | Description |
| User Name | The user name of the OS 2200 host. |
| Profile Name | The name of the Profile that was defined in the OS 2200 host. |
| No. of Extraction Thread(s) | The number of processing threads used by the OS 2200 Agent for extracting data from the RDMS transformation source. The value ranges between 1 and 10. |
| No.Of Processors. | The number of processing threads used by the Runtime components for loading the data that is extracted by the OS 2200 Agent. The value ranges between 1 and 10. |
| AIS Connection Name | The name of the connection defined in the AIS Configuration Utility. |
Table 15. Bulk Data Settings (for SQL Server as the Transformation Source)
| Components | Description |
| User Name | The user name of the SQL Server. |
| No.Of Processors. | The number of processing threads that was allocated for performing the bulk data transformation. |
| Select Records | This shows if the tables from the source database used for the bulk data transformation were locked for updates or not indicated with the value “With Update Lock” or “With No Lock” respectively. |
The Bulk Data Transformation Details: Totals pane provides information about the records that are transformed, updated, truncated, and rejected once a bulk data transformation is completed.
Table 16. Bulk Data Transformation Details: Totals
| Name | Description |
| Datasets / Tables Processed | The number of datasets or tables that have been read from the transformation source during a bulk data transformation. |
| Records Processed | The number of records that have been read from the transformation source during the bulk data transformation. |
| Transformation Target | The full name of the transformation targets in the <host name>\<database name> format. |
| Transactions | The number of transactions that have been committed to the transformation target. |
| Record Updates | The 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. This is applicable only when SQL Server is the transformation target. |
| Truncations | The number of target data columns that have been truncated according to the runtime error handling policy that you have defined in the DDW. |
| Rejections | The number of records that have been rejected according to the runtime error handling policy that you have defined in the DDW. |