Troubleshooting

Follow these guidelines to troubleshoot issues and errors that you might encounter when working with BMC AMI DevOps for Db2:

  • Do not include locations in the outbound migrate profile that you want to apply before or after a comparison.
  • Do not specify a remote catalog for the Compare1 configuration.
  • Enter unique names for pre-execution and post-execution baselines. If you enter the name of an existing baseline, errors occur when you submit the JCL.
  • If the compare, import, analysis, or JCL generation JES job steps fail, review the output for the error messages that are displayed and perform the appropriate actions. 

  • If the execution JCL JES job step fails when running the worklist, your z/OS Db2 DBA might need to perform the following steps:

    1. Review the output for the error messages that are displayed.
    2. Resolve any issues.
    3. Restart the worklist run from BMC AMI Change Manager for Db2 by using the restart or startover process.

    For more information, see Restart methods.

  • When transferring DDL files to the mainframe, make sure that each record in the DDL file is less than 80 bytes long. This avoids errors in the BMC AMI DevOps Schema Mgmt for Db2 - Schema Change Migration step that might occur for the following reasons:
    • The DDL file might truncate during file transmission.
    • The Change Manager parser might read only the first 80 bytes of any record. 
  • If you add two consecutive authentication steps in a project or pipeline, the last authentication step will be considered, and you receive a warning message.

  • If your project or pipeline execution fails with the error message BMCAMA00074E: Maximum Job Wait Time exceeded, then review the job output on the mainframe to obtain the total elapsed time that the job required and increase the maximum job wait time accordingly.

    Important

    The Maximum wait time is based on the time elapsed from submission until completion and not on the CPU time used by the job. 

    The purpose of this field is to make sure that a build executor is not tied up too long.

Click here if you are using the BMC AMI DevOps for Db2 in Jenkins.

Perform the following steps to avoid errors:

  • If you do not enter input for a required field of a build step during configuration, BMC AMI DevOps displays an error. You can still build the project, but the project fails.

  • To use an older version of the BMC AMI DevOps plug-in in Jenkins, follow these steps:

    1. Manually reinstall the .hpi file of the older version. 
    2. Restart the Jenkins server when no jobs are running.

    You cannot downgrade the BMC AMI DevOps Common and BMC AMI DevOps Schema Management for Db2 plug-ins from the Jenkins web user interface because it is a private plug-in.

  • During configuration, if your input in a field exceeds 8 KB of text, Jenkins displays a Bad Message 414 error in the BMC AMI DevOps Schema Mgmt for Db2 - Schema Change Migration build step. To resolve this issue, increase the Jenkins header size to 32 KB as follows:
    1. Log out of Jenkins.
    2. Navigate to the directory on your system in which Jenkins is installed.
    3. Open the jenkins.xml file.
    4. Save the jenkins.xml file with a different name to create a backup. For example, save the file as jenkins_backup.xml.
    5. Open the original jenkins.xml file.

    6. In the <arguments> statement, add the following parameters with the following values:

      -Dorg.eclipse.jetty.server.Request.maxFormContentSize=500000

      --requestHeaderSize=32768

      The following example illustrates the <arguments> statement in the jenkins.xml file with the required parameters:

      <arguments>-Xrs -Xmx256m -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle
      -Dorg.eclipse.jetty.server.Request.maxFormContentSize=500000 -jar
      "%BASE%\jenkins.war" --httpPort=8087 --requestHeaderSize=32768
      --webroot="%BASE%\war"</arguments>
    7. Log in to Jenkins again.
  • If you have a problem running your Jenkins pipeline with your rule set in the BMC AMI DevOps Schema Mgmt for Db2 - Schema Standards build step, set Violation Response to WARN. This allows the pipeline to run all steps to completion until you can correct your schema definition.
  • If you receive a host variable or SQL error for your rule, you can set your rule to inactive in BMC AMI Command Center for Db2 rule editor. This allows the pipeline or project to run to completion until you can resolve the error with the rule.
Click here if you are using the BMC AMI DevOps for Db2 with Universal Connector.

(BMC.DB2.SPE2304)

You might encounter the following issues and errors:

  • When you create a variable for a Linux directory path, the path value requires a backslash (\) escape character before each forward slash (/) path separator (for example, Azure\/SMPE\/PropertiesFiles\/AMI_DevOps.properties).
  • When you create a variable with one of these special characters in the ($,&) value, the value requires a backslash (\) escape character before either of the special characters (for example, DB\$123, TBL\&A). This is applicable to the 'password' key-value as well.
  • When you create a variable name that is also used in JCL syntax or input keyword and then run the pipeline or workflow, the variable value replaces the syntax or keyword and ultimately causes the step to fail.
  • (BMC.DB2.SPE2307)If you receive this error: unzip: not found, while running the workflow in which you used the unzip step and the first released image, 13.01.00.0001-GA, then either remove the unzip step from the workflow or change the workflow image and rerun the workflow. The first released image did not include the unzip utility and should not be used with new features after the first released image.
  • When you define a pipeline, we recommend that you use the BMC AMI DevOps step as a separate script. Any other bash or shell command after the step might report the script execution result inaccurately in Azure DevOps.

  • The Azure DevOps pipeline might fail with the following message in the Initialize container step because the container does not stay up. Disregard the time stamp and container ID.

    2023-10-05T12:25:21.5544536Z ##[warning]Docker container d83d7db2e08eaf1e401521baef9e8b9a724ced0bec7e4be1656fa4d2fa2ee432 is not in running state.
    2023-10-05T12:25:21.5606939Z ##[command]/usr/bin/docker exec  d83d7db2e08eaf1e401521baef9e8b9a724ced0bec7e4be1656fa4d2fa2ee432 sh -c "command -v bash"
    2023-10-05T12:25:21.6596835Z ##[error]Docker-exec executed: `sh -c "command -v bash"`; container id: `d83d7db2e08eaf1e401521baef9e8b9a724ced0bec7e4be1656fa4d2fa2ee432`; exit code: `255`; command output: `Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.`, `Error: can only create exec sessions on running containers: container state improper`
    2023-10-05T12:25:21.6601435Z ##[section]Finishing: Initialize containers

    If this error occurs, then perform the following steps:

    • Make sure that you are not running the SELinux in enforcing mode. This mode prevents the container from running as root, which BMC AMI DevOps requires.
    • Change the SELinux security mode to permissive mode. This gives a warning when running the container as root, but allows the container to continue to run.
    • Restart the VM.
    • Rerun your pipeline.

  • If your pipeline or workflow has the step command omitted, a shell error of either command not found or not found is displayed. For more information, see the explanation in the following tabs: 

    Suppose that the step command is omitted, as shown in the following example:

    - script: |
        schema_standards_catalogMigrateProfileScope Azure/Test_config.yml
      displayName: 'Schema Standards with Catalog Migrate Profile source'

    The following error is displayed:

    /__w/_temp/700be3f0-9de6-4886-a461-d3543f4b9e33.sh: line 1: schema_standards_catalogMigrateProfileScope: command not found
    ##[error]Bash exited with code '127'.

    To correct this error, add the step command, as shown in the following example:

    - script: |
        step schema_standards_catalogMigrateProfileScope Azure/Test_config.yml
      displayName: 'Schema Standards with Catalog Migrate Profile source'

    Suppose that the step command is omitted, as shown in the following example:

    - name: Schema Standards Migrate Profile source step
            run: |
                schema_standards_catalogMigrateProfileScope GHA/Test_config.yml

    The following error is displayed:

    /__w/_temp/5af6affc-f6be-4bff-856d-943a315601b0.sh: line 1: schema_standards_catalogMigrateProfileScope: not found
    Error: Process completed with exit code 127.

    To correct this error, add the step command, as shown in the following example:

    - name: Schema Standards Migrate Profile source step
            run: |
              step schema_standards_catalogMigrateProfileScope GHA/Test_config.yml

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*