2.2.4 upgrade to 3.0.2 Still need database cleanup script run?

[stvegerton]

I’m about to make the jump to 3.0.2 from 2.2.4 today. This section from the 3.0 install doc is missing from the install doc for 3.0.2, which makes me wonder if it’s necessary.

Perform a database cleaning before migrating to 3.0

It is recommended that customers with large amount of users or applications performs a database cleaning before migrating from 2.0.x to 3.0.

After performing an upgrade in a multi-node environment, it can take very long time for newly created database items (such as sheets, applications, bookmarks, or tags) to appear on all nodes. This is caused by long synchronization queues between the nodes, as a result of the upgrade. All new items will be at the end of these queues. From Sense 2.2 the repository database is stored in RAM to improve the performance, for users with very large databases the database can become larger than the available RAM on the server which results in an error during startup. If you are running a large installation (users or apps) we recommend that you perform the steps described below before performing the upgrade.

Workaround: Synchronization queues will eventually finalize by themselves, but in very large environments this can take several hours. If you import a large Active Directory, it is recommended to do the following before upgrade to reduce upgrade synchronization queues:

 Make sure that you applied best practices for User Directory connectors: https://community.qlik.com/docs/DOC-14708

 If a large Active Directory has been imported without filters, do the following:

1. Setup LDAP import filters, according to the best practice guide, to reduce size of imported user attributes.

2. Remove users and perform a new import of the Active Directory.

3. Run the Database Cleanup Script, provided by Qlik, to clean the repository database before upgrading. To acquire the Database Cleanup Script, log in to the Support Portal and search for article “17620”. The title of the article is “Qlik Sense Database Cleanup Script 2.2.x”.

4. Restart the system and start the upgrade.

[vlad_komarov]

Actually, it's recommended to do a Repository cleanup periodically anyway...

I am doing it once every 4-5 weeks.

Maybe the script is not supporting the 3.0.x version yet (I did not try it in 3.0.1, upgraded just couple weeks ago)?

VK

[korsikov]

Yes, Vladimir is right. You need  performs a database cleaning before migrating from 2.0.x to 3.0.

[stvegerton]

Qlik better hurry and add this to the 3.0.2 install documentation.  

[amien]

This is still not in install documentation. Plus this should be done automatically when doing an installation if this is really needed.

I'm having some strange behavior after upgrading to 3.1.1. What should i do. I didn't run the tool. All is on 1 server. Is this tool even then needed? Would it make sense to run the tool post installation of 3.1.1?

Thanks

[vlad_komarov]

How your apps' porting went? Do you have any apps with "Migration Failed" status?

And what kind of "strange behavior" you are talking about?

VK

[amien]

I have 1 app where the migration failed. That is the monitoring app.

Strange behavior : on the migrated app, the security rules don't apply. And strange behavior on new published apps:

for example :

when i change the security rules and publish a new app. the rules apply perfectly. When i change after that any security rules (or a custom property of a user) and check the document again, it keeps the old security logic. And therefor the new security is not applied. After that re-publish the same app again and the current security rules are applied correctly.

[vlad_komarov]

About migration failure:

Did you stop all tasks before upgrade? I do not know your tasks' schedule, but it might be running at the same time you've tried to upgrade... Which usually requires services shutdown, which usually caused the app's corruption, if the reload process is running on the same app.

Learned it the hard way few upgrades ago...

About the strange security rules behaviour: sounds like a bug... I've experienced another issue with migrating and publishing apps from older version, and it was accepted as a bug after my call to support.

I would suggest you report this issue....

VK