System Administration - How to Re-install Patches

This outlines what steps to take if for some reason it is necessary to re-install a patch older than the currently installed patch.

NOTE: This procedure will not reverse a patch install. After re-installing a previous patch, continue installing patches until the system is back up to the starting patch number.

When Patchinstall is run, it updates both the database and the server to indicate that patch X was installed successfully.

The database is updated to the correct patch number by updating the field sys_upgrade_code on the table da.SYSOPT, while the server is updated for the environment by putting a text file with the patch code name in the directory, D:\cm\ias\utility\patchinstall\sucessful_installs\<env>\.

To reinstall a patch:

  1. Remove the file(s) in D:\cm\ias\utility\patchinstall\sucessful_installs\<env>\ that are equal to or greater than the patch that needs to be re-installed.

    For example, if the patch being re-installed is patch V12-012-2, and patch V10-11-2 have already been installed, then all three files must be removed.

  2. Update sys_upgrade_code to be one patch number before the patch to be reinstalled. For example, if the patch to be re-installed is V12-012-2 then update this field to be V12-011-2.

    Copy 
    Update da.sysopt set sys_upgrade_code = ‘V12-011-2’;
    Commit;

  3. Reinstall the patch.

  4. Continue installing patches in sequence until the system is back at the starting point.

Location of Log Files

D:\oracle\midtier\asinst_midtier\

D:\oracle\midtierjsp\asinst_midtierjsp\

D:\oracle\midtierjsp\user_projects\domains\cmicprod\servers\cmicprod_prod_cmic_ca\logs

Installing SVN_Hotfixes

This is an update to a patch to fix certain bugs. The regular hotfix is to be installed only on JSP/Forms/Collab servers. The mobile hotfix is only for Mobile server and not for other app servers. 

The overall Hotfix should run for about 1.5 to 2 hours on average. 

The released Hotfix will be sent by CMiC QA.  

The Hotfix should be copied to the Patches folder in the D:\ drive of the server.

Installation steps:

  1. Extract the .exe file provided by CMiC QA and copy all the files under extracted folders to the respective folders under the D:\cm\v12\ENV\ folder (e.g. D:\cm\V12\PROD), and copy files under jsp and uig/java to the D:\cm\ias\j2ee\ENV\deployment\deploy folder (e.g. D:\cm\ias\j2ee\PROD\deployment\deploy).

  2. Execute the sql script of the SVN Hotfix from D:\cm\v12\ENV\sql (e.g D:\cm\v12\PROD\sql) as the DA user from Command Prompt as an administrator.

This is a database update; we need to run it on only one server. The SQL script must be run as the DA user.

Copy 
D:\cm\v12\ENV\sql>setsqlpath.bat  
D:\cm\v10\ENV\sql>sqlplus da/pwd@ENV 
SQL>@dbdefine
SQL>@V12-012-x-HF-xx.sql

After the execution, the V12-012-x-HF-xx.txt file will be created under the D:\cm\v10\ENV\sql folder. Send it to patchlogs@cmic.ca for review

  1. This is a Jasper and a DB update; so it only needs to be run on one server. 

    Copy 
    D:\patches\ V12-012-x-HF-xx\jasper\bin> loadJasperFixes.cmd PROD

  2. Run the deployment:

    Copy 
    D:\cm\ias\j2ee\ENV\deployment\bin>cmicENV_deploy.cmd

We need to verify if the deployment is done successfully. All the files under D:\cm\ias\j2ee\ENV\deployment\deploy should disappear after the deployment. Also, there should not be any duplicates on the Weblogic. 

During SVN Hotfixes, the workflow engine gets disabled.

If there are some invalids in the OWF_MGR schema, then DBA does not run any startup of the workflow engine.

If there are some invalids in the DA schema with names starting with “DBK_WKF”, then DBA does not run any startup of the workflow engine.

If there are no invalids, run the following in SQL (as the DA user):

Copy 
Start workflow_status.sql;

To restart the Workflow Engine, run the following in SQL (as the DA user):

Copy 
Start workflow_startup.sql;