Resolving installation verification program issues

Edit online

The installation verification program (IVP) script is designed to identify issues with the product installation. This section provides guidance to help isolate and resolve problems encountered while running the IVP.

Procedure

Before running the installation verification program
  • Review and confirm all parameters, both default and customized, displayed by the IVP script before starting the process.
  • If necessary, adjust the size of your terminal window to ensure optimal readability.
Resolving subsystem registration error

If you get any error during the subsystem registration using the IVP script:

  • Customize and save the provided ssid.NAME.json template file before using it with the IVP script.
  • Ensure that the ssid.NAME.json file exists and is named correctly.
    The second node in the file name (NAME) must match the Db2 SSID name.
  • Ensure the file includes valid values as mentioned in the ssid.<ssid-name>.json file attributes table.
Troubleshooting issues during script execution

To diagnose issues during the IVP execution:

  • Review error messages.
    • Note any error messages displayed by the script.
    • Use your output viewing tool, such as SDSF, to locate related batch jobs for further diagnostics.
  • Check the status of a component with any error in the UI.
    • Start the Db2® CI/CD Expert UI.
    • Navigate to the affected component (such as subsystems, environments, teams, or paths)
    • Locate the corresponding component and check for error indicators.
    • If available, review the Status messages link for additional information or output references.
  • If a subsystem is in the error state, use the UI to remove it.
    Note: To remove a subsystem, ensure that it is not assigned to any environments and that it is currently active.