#31 Data Corruption May Occur When Upgrading to JADE 7.1.03
Posted: Thu Mar 05, 2015 4:58 pm
Some issues have been identified with the 7.1.03 upgrade process which may cause data corruption. This may leave user collection instances and the internal meta-data in the upgraded system in an inconsistent state which will lead to unexpected application behaviour, and could cause future data corruption.
This affects all systems which have been upgraded to 7.1.03, from either 6.3 or 7.0.
Detecting and Resolving the Issue
There are three scenarios all of which must be checked:
1. All environments which have been upgraded to 7.1.03 should use the provided workspace1 to identify if they have incorrect meta-data. If this identifies any issues then please contact JADE Support for advice on resolving it. 2. All environments which were upgraded from 6.3 to 7.1.03 using the InstallShield should run the commands in the provided text file “fix-up_JadeInstallShield.txt” against the 7.1.03 system to fix incorrect meta-data. Please contact JADE Support if you have any issues with the fix-up. 3. All environments which were upgraded using the High Availability Upgrade process (from either 6.3 or 7.0) will have incorrect collection data created during the replay journals phase. These environments should be re-upgraded from a restored 6.3 or 7.0 system once hotfix 7.1.03.009 is made available. This is expected to be released in the next few days. If re-upgrading is not possible please contact JADE Support.
Avoiding the Issue
Hotfix 7.1.03.006, 7.0.03.008 and 7.1.03.009 will fix these issues and should be used for any future migration. These are expected to be released in the next few days once the testing process is complete.
Prior to migrating a database to JADE 7.1, it is crucial to apply these hotfixes to the 7.1\bin directory.
It is recommended that all 7.1 systems be re-upgraded from a restored 6.3 or 7.0 backup using either the new installer which will be made available on the web-site in the next few days, or the manual or high-availability upgrade steps with the latest hotfixes. Refer to the readme.txt included with the installer to be certain you have the correct hotfixes before attempting the migration.
If you have any questions, please also contact Jade Support.
This affects all systems which have been upgraded to 7.1.03, from either 6.3 or 7.0.
Detecting and Resolving the Issue
There are three scenarios all of which must be checked:
1. All environments which have been upgraded to 7.1.03 should use the provided workspace1 to identify if they have incorrect meta-data. If this identifies any issues then please contact JADE Support for advice on resolving it. 2. All environments which were upgraded from 6.3 to 7.1.03 using the InstallShield should run the commands in the provided text file “fix-up_JadeInstallShield.txt” against the 7.1.03 system to fix incorrect meta-data. Please contact JADE Support if you have any issues with the fix-up. 3. All environments which were upgraded using the High Availability Upgrade process (from either 6.3 or 7.0) will have incorrect collection data created during the replay journals phase. These environments should be re-upgraded from a restored 6.3 or 7.0 system once hotfix 7.1.03.009 is made available. This is expected to be released in the next few days. If re-upgrading is not possible please contact JADE Support.
Avoiding the Issue
Hotfix 7.1.03.006, 7.0.03.008 and 7.1.03.009 will fix these issues and should be used for any future migration. These are expected to be released in the next few days once the testing process is complete.
Prior to migrating a database to JADE 7.1, it is crucial to apply these hotfixes to the 7.1\bin directory.
It is recommended that all 7.1 systems be re-upgraded from a restored 6.3 or 7.0 backup using either the new installer which will be made available on the web-site in the next few days, or the manual or high-availability upgrade steps with the latest hotfixes. Refer to the readme.txt included with the installer to be certain you have the correct hotfixes before attempting the migration.
If you have any questions, please also contact Jade Support.