Documente Academic
Documente Profesional
Documente Cultură
info
PATCHIN G
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 R11,R12 are examples of a Maintenance pack.
PATCHIN G STEPS
Step 1 : Set Environment Variables Login as Oracle user. In R12 we will do as follows $ cd /d01/oracle/PROD/apps/apps_st/appl $. ./APPSPROD_erp.env
Step 2 : Stop Apps Services In R12 we will do as follows $ cd /$ADMIN_SCRIPT_HOME Execute the following script $./adstpall.sh apps/appspassword
Please Note : Database and Database Listener Should be up.
Step 3 - Enable Maintenance Mode We need to run adadmin to change maintenance mode as shown below. In R12 we will do as follows: $cd /d01/oracle/PROD/apps/apps_st/appl/ad/12.0.0/bin $./adadmin After running adadmin, below screen will appear
10
11
12
13
14
Select option 3 and press Enter key to return to main menu as shown below
15
16
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 u8746079.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).
17
18
19
20
21
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.
22
23
24
25
26
Now status showing all application services are up, we can now access oracle apps.
27
28
29
Above screen showing Internal Manager is up. Now we need to run a request to verify that Internal Managers are working. Double Click on Concurrent -> Request as shown below:
30
31
32
Below Screen wil be displayed, Select the request button to select the request Active Users:
33
Search for Active Users Request and click on Find button as shown below:
34
Select Active Users Request ,as shown below and click on OK button:
35
36
Select Specific Requests Option and Put the Request Id created in above screen and click on Find Button:
37
Now Active Users Request is completed successfully, click the View Output button to check the output of the request:
38