Upgrading Unisphere for PowerMax Fails Because SMAS DB Stops and Does Not Start

The customer experienced an issue when upgrading Unisphere for PowerMax on a standalone Windows Server 2019 due to the SMAS DB service being stopped and does not start. Manual attempts to start the SMAS database from the Windows Management Console failed.

Evidence in application event log:

08/18/2022 12:25:41 PM  Error         <hostname> 0       PostgreSQL                       {2022-08-18 19:25:41 GMT::@:[1668]:FATAL:  lock file "postmaster.pid" already exists 2022-08-18 19:25:41 GMT::@:[1668]:HINT:  Is another postmaster (PID XXXX) running in data directory "C:/Program Files/EMC/SMAS/jboss/standalone/data/pgsql/data"? }

Moved both "postmaster.opts" and "postmaster.pid" from "C:\Program Files\EMC\SMAS\jboss\standalone\data\pgsql\data" to a different folder.

Both files appear to be tied together as they were both generated simultaneously on each attempt to manually start SMAS DB.

Stopped SMAS and ensured SMAS DB was not running.
Started SMAS DB, and started SMAS services and both were successful.

Both "postmaster.opts" and "postmaster.pid" were rebuilt after the SMAS DB and SMAS services were started and proceeded with upgrade of Unisphere for PowerMax which was successful.

The "postmaster.pid" file is the "pidfile" written by the postmaster process. In addition to the postmaster's PID, it contains information about the running instance.

The "postmaster.opts" is a file in the data directory written after startup which contains the options used to start the postmaster process. The contents of "postmaster.opts" are used to ensure that the postmaster process can be restarted with the same options with which it was originally started.