Troubleshooting database deployment

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

Both to prevent or solve some database configuration issues that might result in stuck or failed Maximo Health deployment, you can follow these best practices:

  • Review the database settings that you used to configure Maximo Health. If something is wrong with the values, edit your database configuration on the Health Status page and activate 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 whether 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 preparations steps. For example, the deployment process on Maximo Health databases will not work if you skip the step to set its table organization to be row-based instead of column-based.
  • Make sure you configured your database properly if you plan to deploy languages. Set the configuration to support Maximo Health, SQL, or Maximo Health for the language that is used for the databases.
  • Confirm that you put the correct database certificate for the database in the Maximo Health configuration and that is not expired.
  • If you are running a Maximo Health deployment and reusing a database that hadMaximo Health previously, make sure you passed the encryption keys that are saved from the previous deployment. Otherwise, the process generates new keys, which will not match the ones that are used to encrypt the database, and the deployment process will not proceed.
    • For example, you deactivated Maximo Health and deleted its application. Now you are redeploying the Maximo Health application and activating it again, but you are still using the previously deployed Maximo Health database.
  • For the best Maximo Health deployment performance, the ideal location for your database is the same as the one for your Maximo Health. If the location site of your database is different, the chances of database failures during the Maximo Health deployment due to connection issues and latency are higher.

If the update of your database during the Maximo Health deployment is interrupted by a situation, such as lost connection, the problem is usually automatically resolved by the Maximo Health operator reconciliation process.

If the failure persists, make sure that your database connection is working correctly. Before you remove, re-create the database, and retry the Maximo Health deployment, you can try the following procedures:
  1. Select the Bypass upgrade version checkbox and then reactivate the Maximo Health 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 deployment to progress.
  2. If the failure still 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, expand Workloads and select Pods.
    2. In the Project field, select the Maximo Health project.
    3. In the Pods window, select the administrative pod. The administrative pod includes maxinstin the pod name.
    4. To review the logs, in the Pod Details window, first select the Logs tab for the maxinst pod to look at the messages. If you want to look at all the logs, select the Terminal tab for the maxinst pod and look at the logs in the /opt/IBM/SMP/maximo/tools/maximo/log directory.
    5. After you review the log files, manually correct the problem or problems and run the database installation again.