Fix 'Unable to determine the Maximo Home' in UpdateDB

Before you begin: UpdateDB changes the Maximo database. Stop the Maximo application server, take a database backup and confirm that the properties file points to the intended database before running it.

UpdateDB can stop immediately with this message:

Unable to determine the Maximo Home!

This happens when the utility cannot find the maximo.properties file it expects beneath the Maximo installation. The fix is to restore the correct properties file, then rerun UpdateDB from its tools directory.

Check where you are running UpdateDB

Open a command prompt or terminal and change to:

<install-root>\SMP\maximo\tools\maximo

Run the appropriate command for the operating system:

updatedb.bat

./updatedb.sh

IBM's UpdateDB instructions use this directory. If you were already running the command there and still received the error, check the properties file next.

Check for maximo.properties

Look in:

<install-root>\SMP\maximo\applications\maximo\properties

The directory must contain a file named exactly:

maximo.properties

The file contains the database connection and other settings used by Maximo tools. IBM documents both its location and core properties.

Restore the correct properties file

Split deployments sometimes keep separate property files for the user interface, BIRT, integration and cron servers. If maximo.properties is missing but those environment-specific files remain, identify the one that contains the correct settings for the database you intend to update.

Copy that file to maximo.properties. Keep the original environment-specific file in place rather than renaming it:

Copy-Item .\maximo-ui.properties .\maximo.properties

cp ./maximo-ui.properties ./maximo.properties

The filename above is only an example. Use the actual properties filename from your installation.

Before continuing, compare the restored file with your deployment configuration. In particular, verify the database URL, database user and schema-related settings. Choosing the wrong server-specific file can point UpdateDB at the wrong database.

If none of the remaining files contains a known-good configuration, restore maximo.properties from a backup or regenerate it using the configuration process for your Maximo version. Do not assemble database credentials by guesswork.

Run UpdateDB again

Return to <install-root>\SMP\maximo\tools\maximo and run updatedb.bat or updatedb.sh again.

The Unable to determine the Maximo Home message should now be gone. If UpdateDB starts but reports another failure, check the timestamped log under tools\maximo\logs; that is a separate error later in the update process.