How to maintain custom specific views and indexes during an upgrade
Customer specific indexes, FK and procedure can cause the system upgrade to fail.
Cause
This document explains how to avoid that customer specific database modifications like indexes or FK are causing a system upgrade to fail.
Solution
During an upgrade the system tries to located the following two files in the ..\APM directory.
customized_pre.ads
customized_post.ads
If found the script customized_pre.ads is executed before running the actual upgrade, after the upgrade it executes customized_post.ads.
To avoid the standard upgrade from failing you can drop or enable the indexes or fk in the customized_pre.ads file and create or activate the index, fk in the customized_post.ads file.
This will ensure that that custom index, fk or stored procedure is not interfering with the standard upgrade.
To solve the error in the screen shot above the following statement* can be added to the customized_pre.ads:
DROP INDEX PW001PYHACCDIM2 ON PW001PYH --GO |
In the customized_post.ads the following statement is added:
CREATE INDEX PW001PYHACCDIM2 ON PW001PYH(ACCOUNTDIM2 ASC) --GO; |
*This is an example and should not be used on your database. Contact Adonis Support if you are uncertain what statements to add.