2019030522PM-How to Use uPatch

uPatch Installation

================================================================================================

How to install uPatch on EMS DB and refresh to current label

Step-by-step guide

The uPatch documentation is located at uPatch Installation and Removal.  It's pretty good documentation and worth reading.

Short list of commands is below:

Setup:

1. mkdir $HOME/upatchconfig

2. ln -s /net/slcai797.us.oracle.com/scratch/upatch/LATEST/bin $HOME/upatchbin
3. In your .cshrc or other shell config file, add $HOME/upatchbin to your PATH environment variable and open a new terminal for the change to take effect in.

4. From within a view on your desired label, do this command and save the FAINTEG label:

$ ade showdepprods | grep FAINTEG
DEP_LABEL             : FAINTEG_MAIN_PLATFORMS_181228.2301

Install uPatch:

1. uPatchManager BUILD_EMS_CONFIG  -UPATCH_CONFIG=$HOME/upatchconfig/mydbconfig -EMS_ENV_NAME=<your DB name> -UPATCH_FRIENDLY_NAME="<whatever name you like>" -ADMIN_EMAIL_ADDR=<your email>
2. uPatchManager BOOTSTRAP -UPATCH_CONFIG=$HOME/upatchconfig/mydbconfig -APPLTOP_INSTALL_SOURCE=<FAINTEG label from above>
3. Wait some time for completion, maybe half an hour or less.

Increase EMS env size:

EMS DB default size is set based on the template, for me it was 26GB.  This was enough to patch but uncomfortably tight afterwards.  I recommend increasing to 30GB using the "Resize Environment" action from the EMS portal.  **DO NOT ABUSE THIS** Don't increase your space unless you need it.  EMS is chronically short on space, if we use up too much then we will not have room for the DBs we need in our team and others.

Patch to a label:

1. You can now access uPatch on your DB through the URL: http://fre2.us.oracle.com:7777/cgi-bin/uiPatch (enter your DB connect details there) or directly via your DB URL e.g. http://fre2.us.oracle.com:7777/cgi-bin/uiPatch?env=slcak357.us.oracle.com:1590/aaulick
2. In the uPatch URL, choose: Submit Request -> APPLY_FA_LABEL
3. Enter your label
4. **Important**: set the "Family Filter" to "CRM,FSCM" to restrict updates to CRM and setup files.  If you try to apply the whole label across all teams you will take 14+ hours and then run out of space.
5. Enter role password – by default same as role but lower-case e.g. RESTRICTED / restricted
6. Click Submit button and watch progress.
   1.   It's best to do this at the end of the day.  My request for CRM alone (missed FSCM) from a recent template took 3 hours, 17 minutes. Including FSCM and/or applying to an older template will take longer.

Patch your current transaction changes to your DB:

From inside your active ADE view with DB schema or seed data changes:

1. check in all files
2. uPatchSubmit -INSTANCE=<your DB machine:port/SID>

================================================================================================

Patch your current transaction changes to your DB

Please find the steps to apply uPatch in your transaction.

1. cd /net/slcai797/scratch/upatch/v2.0.0/bin
2. ./uPatchManager BUILD_PATCH_FROM_VIEW -DESTINATION_DIR=/scratch
3. ./uPatch -INSTANCE=//slcao830.us.oracle.com:1547/finbigbr -ROLE=admin -ROLE_PASSWORD=admin
4. APPLY_PATCH -PATCH=/scratch/<zip_file_name> -NOTIFY_EMAIL=puneet.p.kumar@oracle.com,varun.jain@oracle.com

In step 3 →  replace slcao830.us.oracle.com:1547/finbigbr with your DB. Please make sure your DB has uPatch installed.

In step 4 → step2 will generate a zip file like  9148775774509.zip . Replace<zip_file_name> with zip file name.

You can check status of uPatch from http://fre2.us.oracle.com:7777/cgi-bin/uiPatch?env=slcao830.us.oracle.com:1547/finbigbr  (Please replace DB details in URL if you are using some other DB with uPatch installed in DB).