If there is an error at the Runtime, you can first notice it on the Summary tab of the Administration Site. The status on the Runtime Overview panel provides information about the error and the component (Agent or DE Runtime Service) where it occurred.
If the Runtime Service Status is Error, you can inspect the Runtime Service log file.
To get more information about the sequence of the errors or events, you can inspect the Administrative Service log.
You can look for the Runtime error in one of the following log files:
| Log File | Used to... |
| DataExchangeRuntimeServiceLog.txt | log the errors encountered by the Runtime Service while performing a transformation. |
| DataTransformErrorLog.txt | log any data truncations or rejections encountered during transformation processing. |
| LongTransactionLog.txt | log long transactions. LongTransactionFragmentSize is the maximum number of record updates you can have in one target transaction / message. You can configure this value in the Runtime Service configuration file. The default is 10000 record updates. If a source transaction has more record updates than the configured value, it is called a long transaction. For optimal use of memory, the long transaction is split into fragments and serialized. These fragments are then deserialized while committing to the target. This is applicable only for a CDT. |
| TargetCommitErrorLog.txt | log the errors encountered while committing data to the target data store, irrespective of whether the transformation is stopped due to the error or it is continued by ignoring the error. |
| TransactionLog.txt | logs the last command in each transaction committed to the target data store if TransactionLoggingOn is set to True in Data Exchange Runtime Service<version_number>.exe.config and the TransactionLogger level is changed in ServiceLoggingConfig.config. See Configuring Log Files for more information on configuring log files. |
| DataExchangeRuntimeAdministrativeServiceLog.txt | log the errors that cause a transformation to stop. |
| TransactionTracerLog.txt | It logs the audit information to track the record from the time Data Exchange reads the record till it is committed to the target. In case of Kafka target, it also logs the receipt from the Kafka server. It does not log any user data. In Info mode (default mode) it logs the messages read and a success or failure message for each transaction committed to one or more targets. Note: If one transaction has record updates to multiple target tables, then it results in multiple commit messages, one per target table. In Debug mode it logs messages from Info level and a message for each message that Data Exchange reads, processes, and commits to the target. |
Events
All user and system actions that occur during a transformation are logged on the Events page on the Administration Site. The types of errors you can find here include:
The errors set to stop in the Data Transform Error Handling Policy in DDW.
The recovery errors handled by the Recovery options on the Administration Site.
The errors set to stop in the Target Commit Error Handling Policy on the Administration Site.
However, the errors that are set to be ignored in the error handling policy are not logged on the Events page because they do not cause the transformation to stop, but are logged in the respective log file.
Windows Events Log
All the events that are logged on the Events page are also logged in the Windows events log.