Troubleshooting IBM Optim Data Privacy

Edit online

Use this information to help you understand, isolate, and resolve issues with IBM® Optim Data Privacy.

Collect system information, logs, and error details to help diagnose and resolve issues efficiently.

Before contacting IBM Support about an IBM Optim issue, gather diagnostic information to help engineers understand your environment and reproduce the problem. The specific data you need depends on when the issue occurs:
  • During deployment
  • When the UI fails to start
  • After deployment when running IBM Optim tasks

Collecting deployment details

IBM Support requires specific environment details and error information to diagnose any IBM Optim issue effectively.

To collect environment and configuration details:
  1. Document your IBM Optim Data Privacy version.
  2. Document the Linux® operating system and version where IBM Optim Data Privacy is deployed.
  3. Identify the IBM Optim solution you are deploying (IBM Optim Data Privacy).
  4. Note your license type (Enterprise, Solution, or other).
  5. Document your browser and connection environment. Specify the following details:
    • Your browser type and version.
    • Whether you are connecting from the Linux machine where IBM Optim is deployed.
    • Whether you are using a Microsoft Windows client to connect to the IBM Optim UI.
    • Whether you are using your local environment to access IBM Optim in your local browser.
    • The URL you use to access the IBM Optim UI, such as https://<optim-host-name>:7780.
  6. Capture screenshots or text of all error messages.

Collecting data about deployment issues

When an IBM Optim deployment fails, the console output contains critical diagnostic information about the failure point and underlying cause.

To collect deployment failure data, save the complete console output from the deployment commands to a file. Include all commands run and their output.

Collecting data about UI startup failures

When the IBM Optim UI fails to start, container logs can reveal service initialization problems, configuration errors, and dependency issues.

For information about collecting container logs, see Collecting IBM Optim container logs.

Collecting data about post-deployment task failures

When IBM Optim tasks fail after a successful deployment, job logs and configuration exports can help to identify data processing issues, workflow problems, and configuration errors.

To collect task execution data:
  1. Identify the IBM Optim task that caused the error.

    Examples include connections, workflows, access definitions, subsetting, masking, archives, targets, insert definitions, extract files, or restore operations.

  2. If a job associated with this failure ran, collect the job logs. For information about collecting job logs, see Viewing job details, logs, and process reports.
  3. Export the job configuration as a JSON file.
  4. Download the logs from the IBM Optim UI.
  5. Download the job process report from the IBM Optim UI.