Unable to start collector in analytics module of Qlik Enterprise Manager when changing the database

[Steve_Nguyen]

Changing the Qlik Enterprise Manager (QEM) repository connection to a database which already has the QEM schema applied leads to unexpected results, such as the start collector or purger functions being greyed out.

Example:

• The Qlik Enterprise Manager repository connection has been changed from database A to database B.
• Later, the Qlik Enterprise Manager repository connection was changed back from database B to database A, meaning the database already had the QEM schema.

Resolution

A sqlite editor and knowledge on how to use it is required for this change, such as the DB Browser for SQLite: https://sqlitebrowser.org/

To successfully change to a database which already has the QEM schema:

1. Before you begin, take a backup of:
    ~Attunity\Enterprise Manager\data\Java\GlobalRepository.sqlite
2. In the Qlik Enterprise Manager settings, set the repository connection to the database with the schema already included
3. Set the username and password, save, and test the connection

   Do not click Initialize

4. Stop the Qlik Enterprise Manager service
5. Next, we use a SQLite editor (such as DB Browser for SQLite) to open:
   ~Attunity\Enterprise Manager\data\Java\GlobalRepository.sqlite
6. In the SQLite editor:
   1. Click Browse Data
   2. Open the Table dropdown and select Objects
      
      
      
      
   3. Locate and AnalyticsConfiguration 
   4. Click on the json column 
   5. Find the key verifiedConnection 
      
   6. Change "verifiedConnection": false, to "verifiedConnection": true,
      
      
      
      
   7. Apply the change and write the settings
7. Start the Qlik Enterprise Manager service
8. Log back into the Qlik Enterprise Manager, go to Analytics, and review if start collector and start purger are once again available.

Environment

Qlik Enterprise Manager