Rolling back from POM 4.1 to 4.0.2 or 4.0.2 service packs or patches

Last Updated : Sep 26, 2025 |

About this task

Use this procedure to change the state of the POM database to a pre-upgrade state after an upgrade of the database fails.

If an upgrade of the POM database fails due to a power outage, restart the POM server.

There is no data loss while changing the state of the POM database to a pre-upgrade state.

Procedure

  1. Ensure that the system displays the following console message:
    POM Upgrade Failed! System can be restored to pre-upgrade version [POM.04.00.02.00.00.xxx].
    Upon POM.04.00.02.00.00.xxx restore completion, it is recommended user to restore the POM database manually.
    Do you want to continue with restore [y/n]? (y/n)
  2. To rollback, type y.
    The system begins to restore the pre-upgrade POM version and displays the following message:
    ------------------------------------------
    POM 4.0.2 restore process completed successfully.
    ------------------------------------------------
    Please restore the POM Database.
    Moving installation log files to: /opt/Avaya/avpom/POManager/logs
    
    ======================================================================
    
    If you are using an external application server and you have installed the POM DD/AAOD
    Application package while installing POM, you need to:
    a--> Copy the *.war files from $POM_HOME/DDapps to $CATALINA_HOME/webapps of the external application server
    b--> Copy files from $POM_HOME/DDapps/lib/* to $CATALINA_HOME/lib of your external application server.
    c--> Enable the SSL configurations for application server.
    d--> Restart the external application server.
    
    ======================================================================
    Please restart the system now!
    
  3. Reboot the system.