PATCHING - Blog for DBA, RAC, EBS DBA — Blog for …Patching is one of Jobs Apps DBA do...

transcript

Author – A.Kishore/Sachin

http://appsdba.info

PATCHING

Patch is a program (set of instructions) to fix a particular problem or enhance/ add a particular feature in existing program/product/software. Patching is one of Jobs Apps DBA do frequently, so we should clear with patch basics and process. Like Database patch, we apply using opatch, similarly for Apps patch we will use adpatch. AD Utility & executables relating to patching reside under product AD and is also called as Application DBA product. There are different types of Patches. The major application patches are as follows:

Standalone/One-off Patch - This patch is created to fix/resolve a particular bug.

Minipack Patch - This patch is the collection of one-off patches.It means it contains group of patches to fix bug in a particular group like GL, AP. The alphabetic characters implies the version of minipack version for the module.For an example 11i.GL.E means E version of GL product is released.Minipack patch is cumulative that means 11i.GL.E includes 11i.GL.A, 11i.GL.B…….11i.GL.D,11i.GL.E.

Family Pack Patch - This patch is the collection of minipack patches for a particular family group of application modules.These are usually named as 11i_PF. For an example 11i.SCM_PF.G ,here PF indicates product family pack.

Maintenance Pack – This patch is the collections of family packs that serves as point level release upgrade. Oracle Application 11.5.10 is an example of a Maintenance pack.

http://appsdba.info

PATCHING STEPS

Step 1 : Set Environment Variables by executing APPSORA.env

Login as Oracle user. In R11i we will do as follows: $ cd /d01/oracle/prodappl $. ./APPSORA.env

Step 2 : Stop Apps Services In R11i we will do as follows: $ cd /d01/oracle/prodcomn/admin/scripts/PROD_erp

Execute the following script $./adstpall.sh apps/appspassword The script prompts are shown below for 11i Please Note : Database and Database Listener Should be up.

http://appsdba.info

Step 3 - Enable Maintenance Mode We need to run adadmin to change maintenance mode as shown below.

In R11i we will do as follows: $ cd /d01/oracle/prodappl/ad/11.5.0/bin $./adadmin

http://appsdba.info

After running adadmin, below screen will appear

http://appsdba.info

Enter Password Of SYSTEM and APPS:

http://appsdba.info

ADADMIN main screen will appear now ,as shown below

http://appsdba.info

Select option 5 and press Enter Key to change maintenance mode

http://appsdba.info

Select option 1 and press Enter key to enable maintenance mode

http://appsdba.info

Select option 3 and press Enter key to return to main menu as shown below

http://appsdba.info

Select option 6 and press Enter to exit ADADMIN

http://appsdba.info

Step 4 - Patching using adpatch

Unzip the downloaded patch from metalink.

Open readme.html file from unzipped patch folder.

Read the following readme.html of patch # 6502082 for 11i.

We need to follow the steps mentioned in readme.html of the patch we are going to apply.

Here we have the patch contains the u6502082.drv.Oracle has changed the patch files and now only one file is included that has prefixed as u<patch number> .drv, previously patch had three files to apply with prefixes (c, d, g).

http://appsdba.info

In R11i we will do as follows:

Change directory $ cd /do1/oracle/prodappl/ad/11.5.0/bin $./adpatch

Run adpatch as shown below

http://appsdba.info

The status is showing AutoPatch is complete, as shown above means the patch applied successfully.If there are more than one patches then all patches should be applied before proceeding to the next disabling maintenance mode step.

Step 5 - Disabling Maintenance Mode The disabling steps are just same as enabling maintenance mode as

shown above. Just we need to select 2 instead of 1 to disable maintenance mode, while all other steps are same.Check the below slide.

Step 6 - Start Apps Services In R11i we will do as follows: $ cd /d01/oracle/prodcomn/admin/scripts/PROD_erp $./adstrtal.sh apps/appspassword

http://appsdba.info

Now status showing all application services are up, we can now access oracle apps.

http://appsdba.info

Verify Oracle Apps After Patching Login as sysadmin as shown below

Click on System Administrator as shown below

http://appsdba.info

Click on Concurrent : Manager -> Administer

Above screen showing Internal Manager is up.

http://appsdba.info

Now We need to run a request to verify that Internal Managers are working. Click on Concurrent -> Request as shown below

http://appsdba.info

Below Screen wil be displayed, Select the request button to select the request ‘Active Users’.

http://appsdba.info

Search for Active Users Request and click on Find button as shown below

http://appsdba.info

Select Active Users Request ,as shown below and click on OK button

Click on Submit button as shown below

http://appsdba.info

Click on OK button to Continue

Below Screen will appear and click on Refresh Button

http://appsdba.info

Now Request is completed, click the View Output button to check the output of the request

We checked that Internal Managers are up and working well.

PATCHING - Blog for DBA, RAC, EBS DBA — Blog for …Patching is one of Jobs Apps DBA do...

Documents