Table of Contents

Search

  1. Preface
  2. Data Replication Overview
  3. Understanding Data Replication
  4. Sources - Preparation and Replication Considerations
  5. Targets - Preparation and Replication Considerations
  6. Starting the Server Manager
  7. Getting Started with the Data Replication Console
  8. Defining and Managing Server Manager Main Servers and Subservers
  9. Creating and Managing User Accounts
  10. Creating and Managing Connections
  11. Creating Replication Configurations
  12. Materializing Targets with InitialSync
  13. Scheduling and Running Replication Tasks
  14. Implementing Advanced Replication Topologies
  15. Monitoring Data Replication
  16. Managing Replication Configurations
  17. Handling Replication Environment Changes and Failures
  18. Troubleshooting
  19. Data Replication Files and Subdirectories
  20. Data Replication Runtime Parameters
  21. Command Line Parameters for Data Replication Components
  22. Updating Configurations in the Replication Configuration CLI
  23. DDL Statements for Manually Creating Recovery Tables
  24. Sample Scripts for Enabling or Disabling SQL Server Change Data Capture
  25. Glossary

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.
  1. In the Data Replication Console, connect to the Server Manager Main server as the idradmin user.
  2. Click
    Tools
    Collect Diagnostic Data
    .
    The
    Collect Diagnostic Data
    dialog box appears.
  3. 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
  4. Optionally, edit the list of SQLite configuration database files that you want to collect for each selected replication configuration. Perform the following substeps:
    1. Click the
      Edit
      icon in the selected configuration row.
      The
      Configuration <configuration_name>
      dialog box appears.
    2. 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.
    3. Click
      OK
      .
  5. 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.
  6. Optionally, edit the list of task types and runs for which you want to collect the log files. Perform the following substeps:
    1. Click the
      Edit
      icon in the selected configuration row.
      The
      Configuration <configuration_name>
      dialog box appears.
    2. Select the types of tasks for which you want to collect execution log files.
    3. Select the target connections for which you want to collect InitialSync and Applier logs.
    4. If you want to include log files only for the task runs that failed, select the
      Collect task logs only for failed runs
      option.
    5. Click
      OK
      .
  7. 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.
  8. To collect the SQLite database SM_stat.db3 file that contains task statistics, select
    Collect statistics file SM_stat.db3
    .
  9. 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.
  10. Optionally, edit the set of intermediate files that you want to include in the diagnostic data. Perform the following substeps:
    1. Click the
      Edit
      icon in the selected configuration row.
      The
      Configuration <configuration_name>
      dialog box appears.
    2. In the
      From
      and
      To
      fields, specify the range of intermediate files that you want to include.
    3. In the list of available database connections, select source and target connections for which you want to collect intermediate files.
    4. Click
      OK
      .
  11. 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.
  12. 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.zip file that contains the collected diagnostic data. By default, Data Replication deletes the Collect Diagnostic Data task after it ends successfully.

0 COMMENTS

We’d like to hear from you!