Upgrade Steps for QAD BI Metadata
Preparation
1 Plan for a couple of hours of down time.
2 Ensure that there are no loads currently in progress. All jobs must be completed.
3 Put all scheduled jobs On Hold until the upgrade is complete. Shut down the scheduler.
Important: Take a backup of the current warehouse database and the current portal database.
Upgrade Steps
1 Unzip the metadata for the Common module and any other modules you have installed. Because the metadata files are now segregated by module, it is only necessary to install the modules that are needed.
2 Perform the Common upgrade first. The other upgrades can be done in any order.
3 Run the Common metadata upgrade application.
a If you process any of the Order Management (Sales) fact_om_* tables, install the Order Management (OM) upgrade application.
b If you process Inventory, Purchase Order, or Capacity Planning/Operations Efficiency tables, install the Operations module upgrade application.
c If you process any Financial tables, install the Financials module upgrade application.
d If you have an EAM source, install the EAM module upgrade application.
4 Log in to Setup Administrator.
5 Choose Tools|Start Logging. Select a name and location for your log file and save.
6 Load the Common Module Upgrade Application as follows:
a Set your application directory to the new metadata/common folder.
b Load application upgradeCom by right-clicking on the file and choosing Install Application.
c From the drop-down list, select the ODBC DSN for your DWD instance.
d The system prompts you to proceed. Click OK.
e You can cancel the installation here to review the list of new and modified objects. To continue with the load, right-click in the window and choose Proceed with Load Application.
f The next dialog box is Application Load Properties. Verify that the default values are correct. Make any changes if necessary:
• On the left, select Dimension. On the right, click the box next to Existing Dimension objects will be and select Altered.
• On the left, select Dimension View. On the right, click the box next to Existing Dimension View objects will be and select Recreated.
• On the left, select Stage Table. On the right, click the box next to Existing Stage table objects will be and select Recreated.
• On the left, select Permanent Stage Table. On the right, click the box next to Existing Permanent Stage table objects will be and select Altered.
• On the left, select Fact Table. On the right, click the box next to Existing Fact table objects will be and select Altered.
g Click OK.
7 Repeat for any other modules that must be upgraded.
a Order Management. Change the Application Directory to the metadata/order_management subdirectory and install application upgradeOM. The upgrade application installations take some time as the load process alters and re-creates various objects.
b Operations. Change the Application Directory to the metadata/operations subdirectory and install application upgradeOps.
c Financials. Change the Application Directory to the metadata/financials subdirectory and install application upgradeFin. The upgrade application installations take some time as the load process alters and re-creates various objects.
d EAM. Change the Application Directory to the metadata/eam subdirectory and install application upgradeEAM.
8 Start the Scheduler. Make sure that all jobs are still suspended.
9 If the upgrade affects any customized tables, reapply your customizations. For a list of new and modified tables, see
Data Warehouse Tables Changed.
10 If there were any customizations previously added to any of the modified jobs, update the job to include those extra parts. You can double check what was in the job by looking at the newly renamed <jobname>_1. The jobs that changed in this release are:
|
• CLEANUP_OM_TABLES
|
• HIST_OM_PROCESS_CHAINED
|
|
• DAILY_COMMON_PROCESS_CHAINED
|
• POSTPROCESS_OM_SUMMARY
|
|
• DAILY_OM_PERM_CHAINED
|
• PREPROCESS_FIN_TRUNCATE
|
|
• DAILY_OM_PROCESS_CHAINED
|
• PREPROCESS_OM_LOADS
|
|
• DAILY_OP_PO_PROCESS_CHAINED
|
• PREPROCESS_OM_TRUNCATE
|
|
• HIST_OM_PERM_CHAINED
|
|
11 Make sure the INITIAL_JOB_SETUP_ENABLED parameter is set to Y and run INITIAL_JOB_SETUP to rebuild the daily and historical job chains.
12 Run the upgrade jobs for BI 3.9:
a Edit your INITIAL_JOB_SETUP_CONNECTION_xx_DAILY_MODULES parameter values to ensure that there are no spaces in the comma-separated list. For example, if your DAILY_MODULES parameter currently lists "COM, OM, OP" change it to "COM,OM,OP".
b Order Management Module. Run the UPGRADE_381_to_39_ OM job.
c Operations module. Run the UPGRADE_381_to_39_OP job.
d Financials SE Module. Run the UPGRADE_381_to_39_FINSE job.
e Financials EE Module. Run the UPGRADE_381_to_39_ FINEE job. Note: This is for Financials EE modules that are at 3.8.2. If you are at 3.8.1 or earlier, you must run a full History load of your Financials module.
13 Run the Daily load.
Note: If you have the Order Management module, set the SALES_PROCESS_DAYS to 5000 for the first daily run after the upgrade. This setting ensures that all sales records are processed properly and that the first daily load runs longer than a normal daily load. After the first daily load has run successfully, you can set the SALES_PROCESS_DAYS parameter back to its normal value for your standard processing.