Troubleshooting database deployment

When you deploy the Maximo® Manage application, issues that are related to the database deployment might cause the deployment process to fail.

To prevent or solve some database configuration issues that might result in issues during the Maximo Manage deployment, follow these practices:

  • Review the database settings that you used to configure Maximo Manage. If something is wrong with the values, edit your database configuration on the Manage Status page and activate it again.
  • Ensure that the JDBC URL format and details are correct and are using the correct JDBC protocol, database URL, name, and port. Test your connection to the database by using a database tool.
  • If you are using the SSL-enabled database and port, verify that you selected the SSL option.
  • To ensure that your database is ready, verify that you are using the correct username, password, schema name, tablespace name, and index tablespace name.
  • Do not skip preparation steps. For example, the deployment process for Maximo Manage databases does not work if you skip the step to set its table organization to be row-based instead of column-based.
  • If you plan to deploy languages, ensure that your database is properly configured. Set the configuration to support Maximo Manage or SQL for the language that is used for the databases.
  • Confirm that you used the correct database certificate for the database in the Maximo Manage configuration and that the certificate is not expired.
  • If you are deploying Maximo Manage and reusing a database that was previously used by Maximo Manage, pass the encryption keys that are saved from the previous deployment. Otherwise, the process generates new keys, which do not match the ones that are used to encrypt the database, and the deployment process does not proceed.
    • For example, you deactivated Maximo Manage and deleted the application. Now, you are redeploying the Maximo Manage application and activating it again, but you are still using the previously deployed Maximo Manage database.
  • To deploy multiple Maximo Manage components at the same time, if you are using IBM® Db2® Warehouse databases or other Db2 versions, increase the APPHEAPSZ value to at least 16384 to avoid failures during the database deployment. Alternatively, you can deploy fewer components simultaneously by deploying Maximo Manage components one at a time.
  • Save your database in the same location as Maximo Manage. If the location of your database is different, the chances of database failures during the Maximo Manage deployment due to connection issues and latency are higher.

During the Maximo Manage deployment, database update interruptions might occur due to a situation, such as lost connection. The Maximo Manage operator reconciliation process usually resolves the problem.

If the failure persists, make sure that your database connection is working correctly. Before you remove, re-create the database, and retry the Maximo Manage deployment, you can try the following procedures:
  1. Select the Bypass upgrade version checkbox and then reactivate the Maximo Manage application. If you select this option, the deployment can run, regardless of the current version of the installed database. It skips version validations that might be preventing the deployment to progress.
  2. If the failure persists, review the log files to assess the situation and note the script number for the failed deployment. To review the log files, complete the following steps:
    1. In the Red Hat® OpenShift® console, from the side navigation menu, click Workloads > Pods.
    2. From the Project list, select the Manage project.
    3. On the Pods page, select the administrative pod. The administrative pod includes manage-maxinst in the pod name , as shown in the following example:
      env-managedev-manage-maxinst-7fd3c77492-kmj6z
    4. To review the logs, on the Pod details page, click the Logs tab. If you want to view all the logs, click the Terminal tab and view the logs in the /opt/IBM/SMP/maximo/tools/maximo/log directory.
    5. After you review the log files, manually correct the problems and run the database installation again.