Troubleshooting
This topic describes how to troubleshoot issues and errors that you might encounter when working with BMC AMI SQL Assurance for Db2.
- To use an older version of the BMC AMI SQL Assurance for Db2 plug-in, do the following:
- Manually reinstall the .hpi file of the older version.
- Restart the Jenkins server when no jobs are running.
You cannot downgrade the BMC AMI DevOps Common and BMC AMI SQL Assurance for Db2 plug-ins from the Jenkins web user interface because it is a private plug-in.
- If you do not enter input for a required field of a build step during configuration:
- BMC AMI SQL Assurance for Db2 displays an error.
- You can still build the project. However, the project fails.
- If your job build fails with java.lang.OutOfMemoryError: Java heap space: increase the java heap size in your Jenkins configuration.
- If your job build fails with S80A error: include the REGION=0M parameter in the job card.
- If the job build fails with the error message: BMCAMA00074E - Maximum Job Wait Time exceeded, perform any one of the following steps:
- Go to the mainframe to see the job log and validate the output.
Rerun the job build after increasing the Maximum Job Wait Time to the elapsed time.
- If you want to build a project with multiple Plans or Packages by using 2 or more BMC AMI SQL Assurance for Db2 - Analyze Static SQL plug-in steps, we recommend you to use one of the following methods:
Configure a single project by using Object List File in the plug-in step. This will enable you to specify up to 100 Plans or Packages.
- Configure separate projects with a single plug-in step in each project. Build the projects using a single pipeline.
- (BMC.DB2.SPE2204)If you add two consecutive authentication steps in a project, the last authentication step will be considered, along with a warning message.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*