Symptom:
The oam-p service is not restarted after the password change of user omm. As a result, database user omm is locked during the oam-p upgrade.
Diagnosis:
When you access the database, a message is displayed indicating that the database has been locked.
Cause:
After the password change, before you restart the oam-p service, the old password still takes effect.
Solution:
Use PuTTY to log in to the primary FSM node. Ensure that the floating management IP address of the FSM node is used to establish the connection.
Run the su ommdba command to switch to user ommdba.
Run the gsql -U ommdba -d postgres -p 21600 command and enter the user name and password to go to the GaussDB command line. Run the alter user omm account unlock; command to unlock the user.
Switch to user root and run commands sh /root/oam-p-manager_8.0.1/action/appctl.sh stop and sh /root/oam-p-manager_8.0.1/action/appctl.sh start to restart oam-p.
Check After Recovery:
Perform upgrade operations again.
