{"id":1108,"date":"2023-03-02T03:25:36","date_gmt":"2023-03-02T03:25:36","guid":{"rendered":"https:\/\/craftcookcode.com\/?p=1108"},"modified":"2024-07-10T02:33:25","modified_gmt":"2024-07-10T02:33:25","slug":"qlik-enterprise-manager-upgrading-from-2021-05-to-2022-11","status":"publish","type":"post","link":"https:\/\/craftcookcode.com\/?p=1108","title":{"rendered":"Qlik Enterprise Manager – Upgrading from 2021.05 to 2022.11"},"content":{"rendered":"\n

As a business requirement of developers wanting to take advantage of new features in Qlik Enterprise Manager (QEM); we had to upgrade our system from 2021.05 to 2022.11.<\/p>\n\n\n\n

This was not a smooth process and encountered several issues on the way.<\/p>\n\n\n\n

First Attempt – Straight Upgrade<\/h2>\n\n\n\n

Simple to upgrade?<\/p>\n\n\n\n

Just download the latest installer from Qlik’s website and kick it off?<\/p>\n\n\n\n

Unfortunately when I gave developers keys to our dev QEM box to do the upgrade before Christmas as I was busy with other tasks.  <\/p>\n\n\n\n

They gave it a go without a backout plan.  <\/p>\n\n\n\n

Couple of days later I tried logging into the QEM console and couldn’t get on.<\/p>\n\n\n\n

The AttunityEnterpriseManager service kept restarting every minute and the following errors were in the\u00a0\u00a0C:\\Program Files\\Attunity\\Enterprise Manager\\data\\logs\\EnterpriseManager.log<\/p>\n\n\n

\n[START: 2023-03-01 09:40:18 Attunity EnterpriseManager Version: 2022.11.0.335]\n1 2023-01-02 09:40:18 [Command ] [INFO ] Executing ServiceRunCommand command.\n6 2023-01-02 09:40:19 [Host ] [INFO ] Setting up web host\n6 2023-01-02 09:40:20 [Host ] [INFO ] The server will listen on the following location: http:\/\/xxxxxxx.xxx.xxx\/attunityenterprisemanager\n6 2023-01-02 09:40:20 [Host ] [INFO ] The server will listen on the following location: https:\/\/xxxxxx.xxx.xxx\/attunityenterprisemanager\n6 2023-01-02 09:40:20 [Host ] [ERROR] Object reference not set to an instance of an object.\n6 2023-01-02 09:40:20 [Host ] [INFO ] Stopping service on error...\n<\/pre><\/div>\n\n\n
I tried the usual desperation tricks of restarting the service and then restarting the box.<\/p>\n\n\n\n
In the end I had to uninstall QEM and reinstall 2021.05 as there was no backout plan.<\/p>\n\n\n\n
The developers were then subsequently banned from doing anymore work on the QEM upgrade<\/p>\n\n\n\n
Second attempt – Two jump upgrade<\/h2>\n\n\n\n
Next attempt was upgrading to 2022.05 and then jumping to 2022.11.<\/p>\n\n\n\n
This time I took a backup of C:Program FilesAttunityEnterprise Managerdata so I could easily backout the change if I had problems.<\/p>\n\n\n\n
The upgrade from 2021.05 to 2022.05 went smoothly; but when jumping from 2022.05 to 2022.11 the same error occurred.<\/p>\n\n\n\n
I then raised a case with Qlik and also posted on their forum asking if anyone else had come across this problem<\/a>.<\/p>\n\n\n\n
Final Success<\/h2>\n\n\n\n
With help from Qlik support we developed a upgrade work around.  Qlik said that there is a patch in the works as other users have had the same problem.<\/p>\n\n\n\n
If you follow along – note that this method might differ for your system.  In the three upgrades I have done internally; they all differed slightly.<\/p>\n\n\n\n
Make sure you TEST and HAVE A BACKOUT PLAN<\/p>\n\n\n\n
Upgrade Perquisites<\/h3>\n\n\n\n
This upgrade was done on a Windows 2019 server.<\/p>\n\n\n\n
You will need:<\/p>\n\n\n\n
    \n
  • Admin rights to QEM’s server<\/li>\n\n\n\n
  • Licenses for QEM and Analytics<\/li>\n\n\n\n
  • Username\/Password that AEM connects to the analytics database<\/li>\n\n\n\n
  • Privilege user account for to the analytics database<\/li>\n\n\n\n
  • Password for the user that you use to connect QR nodes to QEM<\/li>\n\n\n\n
  • A SQLite database client<\/li>\n\n\n\n
  • Handy to have – an editor that can validate json format<\/li>\n<\/ul>\n\n\n\n
    Method<\/h3>\n\n\n\n
      \n
    1. Log on to QEM console<\/li>\n\n\n\n
    2. For each server under the server tab – Right click and go to “Stop Monitoring”<\/li>\n\n\n\n
    3. Remote desktop to the QEM server<\/li>\n\n\n\n
    4. Stop the AttunityEnterpriseManager<\/em> service<\/li>\n\n\n\n
    5. Back up C:\\Program Files\\Attunity\\Enterprise Manager\\data<\/li>\n\n\n\n
    6. Run the upgrade to QEM 2022.05<\/li>\n\n\n\n
    7. Once the upgrade is done; log onto QEM and ensure that version 2022.05 is working correctly<\/li>\n\n\n\n
    8. Back up C:Program FilesAttunityEnterprise Managerdata again<\/li>\n\n\n\n
    9. Stop the AttunityEnterpriseManager<\/em> service again<\/li>\n\n\n\n
    10. Run following command from the command line:
      cd \"C:\\Program Files\\Attunity\\Enterprise Manager\\bin\"
      aemctl repository export -f C:\\temp\\qem_repo_202205.json -w<\/pre>
      <\/li>\n\n\n\n
    11. Script out the postgres database with the following commands:
      cd C:\\Program Files\\PostgreSQL10\\bin
      pg_dump -U <username><\/em> -s -C -c <analyticdbname><\/em> > C:\\temp\\analyticdbname.sql<\/pre>
      <\/li>\n\n\n\n
    12. Edit C:\\temp\\cdcanalyticsp.sql.\u00a0 Find and replace “<analyticdbname><\/em>” with “cdcanalytics_2022_11_p”.\u00a0 Save the file<\/li>\n\n\n\n
    13. Run the following command to create a new temporary database on the postgres server:
      psql -d postgres -U <username><\/em> -f C:\\temp\\cdcanalyticsp.sql<\/pre>
      <\/li>\n\n\n\n
    14. This is where the problem lies in our instance.\u00a0 Open up C:tempqem_repo_202205.json
      Find any code blocks with “type”: “AttunityLicense” in it and remove the whole code block.\n
        \n
      1. On our dev system it was the section with “name”: “Replication Analytics”, but in prod it was section with “name”: “Replication Management”.\u00a0\u00a0<\/li>\n\n\n\n
      2. You may need to experiment to find the correct section<\/li>\n<\/ol>\n<\/li>\n\n\n\n
      3. Go to Add\/Remove and uninstall Enterprise manager<\/li>\n\n\n\n
      4. Once remove – delete the the folder C:\\Program Files\\Attunity\\Enterprise Manager\\data<\/li>\n\n\n\n
      5. Install QEM 2022.11.\u00a0 When prompted do not install Postgres<\/li>\n\n\n\n
      6. Log into QEM and check that it is up and running correctly.<\/li>\n\n\n\n
      7. Stop the AttunityEnterpriseManager<\/em> service again<\/li>\n\n\n\n
      8. Run the following command:
        aemctl repository import -f C:\\temp\\qem_repo_202205_Fix.json -w<\/pre>
        <\/li>\n\n\n\n
      9. Start the AEM service and check that it is running correctly<\/li>\n\n\n\n
      10. Re-add the QEM and Analytics license\u00a0<\/li>\n\n\n\n
      11. Go to Settings -> Repository connections.
        Enter in username password set the database as cdcanalytics_2022_11_p<\/li>\n\n\n\n
      12. Intialize the repository and start the connector<\/li>\n\n\n\n
      13. Stop the AttunityEnterpriseManager<\/em> service again<\/li>\n\n\n\n
      14. Open up C:\\Program Files\\Attunity\\Enterprise Manager\\data\\Java\\GlobalRepository.sqlite in an SQLite editor<\/li>\n\n\n\n
      15. Browse the table objects
        Look for name = “AnalyticsConfiguration” and modify the json value “cdcanalytics_2022_11_p” to the original analytics database name<\/li>\n\n\n\n
      16. Save SQLite database<\/li>\n\n\n\n
      17. Start the AEM service and check that it is running correctly<\/li>\n\n\n\n
      18. Go to the server tab.\u00a0 Edit each server and re-add the password.\u00a0 Click on the button “Monitor this server’s tasks and messages”.\u00a0 Test the connection and click OK<\/li>\n\n\n\n
      19. PVT QEM<\/li>\n<\/ol>\n\n\n\n
        If things go wrong<\/h3>\n\n\n\n
        Backout process<\/p>\n\n\n\n
          \n
        1. Uninstall QEM<\/li>\n\n\n\n
        2. Delete the folder C:\\Program Files\\Attunity\\Enterprise Manager\\data<\/li>\n\n\n\n
        3. Reinstall either QEM 2021.05 or QEM 2022.05<\/li>\n\n\n\n
        4. Stop the\u00a0AttunityEnterpriseManager<\/em>\u00a0service<\/li>\n\n\n\n
        5. Restore the appropriate backed up data folder to C:\\Program Files\\Attunity\\Enterprise Manager\\data<\/li>\n\n\n\n
        6. Restart the AEM service<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"
          As a business requirement of developers wanting to take advantage of new features in Qlik Enterprise Manager (QEM); we had to upgrade our system from 2021.05...<\/p>\n","protected":false},"author":1,"featured_media":1076,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[16],"tags":[36],"class_list":["post-1108","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-qlik-replicate","tag-qlikreplicate"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t