App Visibility - Standby High Availability Application Visibility Portal/Collector will not start due to corrupted database

Version 1
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    TrueSight App Visibility Manager Server


    COMPONENT:

    App Visibility Portal


    APPLIES TO:

    High Availability Application Visibility Portal - All Versions High Availability Application Visibility Collector - All Versions



    PROBLEM:

    When the standby High Availability (HA) Application Visibility Manger Portal or Collector are started, they make a connection to the active component and start to copy over the active database.  If at any point in time during this copy, the standby Component or Standby PostGres Database are stopped, then the copy will not complete and the database will become corrupted.  At this point, the standby Portal/Collector will not start up properly.


    SOLUTION:

    Reinstall the standby Application Visibility Manager Portal/Collector.  This will force the component to have a blank copy of the database and allow the component to start.  The component will then connect back to the active component and start the copying the active database.  Do not stop any of the components during this period.  Below are the steps to follow to confirm that the stand by component comes back successfully:

    1.  Reinstall the standby Portal/Collector and allow the installer to start the component.
    NOTE - The FQDN's for all components are case sensitive. 

    2.  To confirm that the standby Portal/Collector started successfully, review the Portal.log/Collector.log for the following lines:

       
    • Starting to copy primary node data dir
    •  
    • Primary node data dir copied successfully
    •  
    • Configured database server as [HA_STANDBY]
       NOTE - It may take several minutes to a few hours for the database to copy over. It will depend on the size of the database.  While this copy is happening, do not stop any of the services. The components will  be starting and stopping on their own.  It is important that this process is not interfered with.

    3.  Once the line "Configured database server as [HA_STANDBY]" appears, this means that the standby Portal/Collector is running and the database has successfully copied over.  If this line appears in the standby Portal.log/Collector.log:
      
       
    • Configured database server as [HA_ACTIVE]
       Then this means the standby Portal/Collector did not make a successful connection with the active component and now thinks it needs to be the active component.  If this happens, then stop the App Visibility Portal/Collector (not the database) and determine what caused both components to not connect.



      

     


    Article Number:

    000168121


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles