Process to follow when a Qlik Visibility repository database is moving to another server

[Nanda_Ravindra]

Environment

• Qlik Visibility
• Databases: Oracle and DB@

The below steps need to be followed when a Qlik Visibility repository database is moving to another server.

1. Update the $VISIBILITY_HOME/server/config/server.properties file for the repository sections to reflect the new server information – see below for the parameter that you need to adjust.

   For Oracle, Verify that the TNS entry is updated that you can connect from the Process Server to the Visibility Repository and that ORACLE_HOME has been set for the Visibility OS account.

    For DB2, Catalog the new Visibility Repository database on the Process Server and verify that you can connect from the Process Server to the Visibility Repository and that INSTHOME and DB2INSTANCE have been set for the Visibility OS account.

   Server.Repository.Database=

2.  Verify ORACLE_HOME and the  INSTHOME and DB2INSTANCE  is correct on the Visibility process server.  If it is changing, make sure it is updated in the same in the following files:

    .profile / .bash_profile,

    $VISIBILITY_HOME/ env_server

   $VISIBILITY_HOME/server/bin/ analyzer_daemon

   $VISIBILITY_HOME/server/bin/collector_daemon

   $VISIBILITY_HOME/server/bin/populator_daemon

   $VISIBILITY_HOME/server/bin/purger_daemon

3.  Restart all the 4 daemons to pick up the new TNS entry/INSTHOME/ DB2INSTANCE

    cd $VISIBILITY_HOME/server/bin

   ./ analyzer_daemon restart

   ./collector_daemon restart

   ./populator_daemon restart

   ./purger_daemon restart

4.  Update the Tomcat config (visibility. config) file to point to the new repository, restart Tomcat and then verify that it can connect to the Visibility URL

   repository.name=NEW_TNS(INSTHOME)_HERE