Collecting Diagnostic Data for Troubleshooting Data Replication Tasks
Collecting Diagnostic Data for Troubleshooting Data Replication Tasks
From the Data Replication Console, the idradmin user can collect diagnostic data for replication tasks. Usually, this information is collected at the request of Informatica Global Customer Support.
In the Data Replication Console, connect to the Server Manager Main server as the idradmin user.
Click
Tools
Collect Diagnostic Data
.
The
Collect Diagnostic Data
dialog box appears.
On the
Configurations
tab, select the check box next to each configuration that you want to include in the diagnostic data collection.
By default, for each selected configuration, Data Replication will include the following SQLite database files:
The
config_name
.db and
config_name
_scn_
connection_object_ID
.db files that are associated with the source database connection
The
config_name
_loader.db and
config_name
_buf.db files from all of the target Server Manager instances for all target connections
Optionally, edit the list of SQLite configuration database files that you want to collect for each selected replication configuration. Perform the following substeps:
Click the
Edit
icon in the selected configuration row.
The
Configuration <configuration_name>
dialog box appears.
Select the connections for which to collect the
config_name
.db,
config_name
_scn_
connection_object_ID
.db,
config_name
_loader.db and
config_name
_buf.db files.
Click
OK
.
On the
Task Logs
tab, select the check box next to each configuration for which you want to include execution logs in the diagnostic data collection.
By default, for each selected configuration, Data Replication will include execution logs for all runs of all task types for the period of time that is defined by the
From
and
To
fields. InitialSync and Applier logs will be included for all targets.
Optionally, edit the list of task types and runs for which you want to collect the log files. Perform the following substeps:
Click the
Edit
icon in the selected configuration row.
The
Configuration <configuration_name>
dialog box appears.
Select the types of tasks for which you want to collect execution log files.
Select the target connections for which you want to collect InitialSync and Applier logs.
If you want to include log files only for the task runs that failed, select the
Collect task logs only for failed runs
option.
Click
OK
.
On the
Server Manager
tab, select the Server Manager instances for which you want to collect Server Manager log files and SQLite SM.db3 files.
To collect the SQLite database SM_stat.db3 file that contains task statistics, select
Collect statistics file SM_stat.db3
.
On the
Intermediate Files
tab, select the check box next to each configuration for which you want to include intermediate files in the diagnostic data collection.
By default, Data Replication includes all of the intermediate files for all connections.
Optionally, edit the set of intermediate files that you want to include in the diagnostic data. Perform the following substeps:
Click the
Edit
icon in the selected configuration row.
The
Configuration <configuration_name>
dialog box appears.
In the
From
and
To
fields, specify the range of intermediate files that you want to include.
In the list of available database connections, select source and target connections for which you want to collect intermediate files.
Click
OK
.
If you want to keep the Collect Diagnostic Data task after it collects the requested data, clear the
Delete task after successful completion
option.
If you keep the Collect Diagnostic Data task, any user can start this task again and collect the same set of diagnostic data. However, a regular user cannot change the data collection settings that were defined for this task.
Click
Collect
.
Data Replication creates a Collect Diagnostic Data task and starts the task with the specified data collection parameters. If the task ends successfully, it generates the diag_
<timestamp>
.zip file that contains the collected diagnostic data. By default, Data Replication deletes the Collect Diagnostic Data task after it ends successfully.