Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Look up keyword
Like this
1Activity
0 of .
Results for:
No results containing your search query
P. 1
Oracle Apps DBA Patching Information 11i,R12

Oracle Apps DBA Patching Information 11i,R12

Ratings: (0)|Views: 15|Likes:
Published by Katam Srinivas
VfreshersJobs.com provides Oracle Apps DbA,Oracle DBA Information to Experienced candidates as well as Freshers Candidates to Learn News things and improve their Knowledge and skills
VfreshersJobs.com provides Oracle Apps DbA,Oracle DBA Information to Experienced candidates as well as Freshers Candidates to Learn News things and improve their Knowledge and skills

More info:

Published by: Katam Srinivas on Jul 12, 2012
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as DOCX, PDF, TXT or read online from Scribd
See more
See less

09/28/2014

pdf

text

original

 
Standalone/Oneoff patches :
This is used to define patch created to fix single/particularproblem.
Mini Pack :
This is group of oneoff patches for a particular product like INV, GL, AP andnamed like 11i.GL.E ( means this group of patches contain fix for 11i GL product (GeneralLedger till time E is released ) This is cummutative which means it will include 11i.GL.A,
11i.GL.B ….11iGL.D till 11i.GL.E earlier in 10.7 it used to called as patchset.
 
Family Pack :
Group of mini packs in one family buldeled together is called as family pack.they are usually named as
11i_PF.
Few example of falilies are SCM ( 11i.SCM_PF.G )
,
ATG (11i.ATG_PF.H )
_PF
indicate Product Family Pack 
Maintenance Pack :
Group of family pack together is called as maintenance pack. So if you sayyour Verison is 11.5.10 then its maintenance pack 10 ( 3rd digit is maintenance pack ) soTo wind up things you can say
few one off patch make mini pack , few mini pack related to same family bundeled togetheras family pack & all family pack fixed till that time are bundeled in Maintenance pack .
 Oh wait I forgot to tell about
NLS Patch
( When you have more than one language , like english& arabic or french .. ) then apart from normal patch you have to apply patch for specificlanguage Installed in your system called as NLS patch ( What is NLS or MLS coming soon ..)As Oracle Apps DBA patching is quite basic thing you do regularly so lets continue with basics .If you have not gone through my previous posts please do so now as its quite important tothrough basics .Apps patches are buldled somthing like p123456_11i_Unix.zip where
p menas patch
next fewdigit are patch number
Unix
is platform or OS on which this patch can be applied.When you unzip a patch you will see some files types which I am explaining here
readme.txt
- This file contain steps to spply patches, List of Prerequisite patch should be thereon apps Instance (If not apply that patch )
cXXXXXXX.drv
c stand for copy driver file , this copies patch content to respective patchlocation , driver is like bus driver which provides instruction on work adpatch need to perform.
dXXXXXXX.drv
d stand for Database driver & contain content related to database like creating
 packages, tables, adding column….
 
gXXXXXXX.drv
This contain files related to forms , reports, graphis or messages
uXXXXXXX.drv
Sometime these three types of files are bundled together into single driver filecalled Unified driver fileSo now you know which type of driver file to apply where ? its common sense if this is d driveryou just need to apply once on concurrent manager tier and c & g on all tiers as database is single& if you run it once its enough . If you applied it again by mistake its no harm & will not causeany issues . Similary c & g you need to apply from all tiers , because c will copy your content &g will generate message files.If you are not sure where to apply what just apply it on all tiers & depending on your context filein APPL_TOP/admin/SID_hostname.xml it will apply where to install what by checking xml tag
 
TIER_ADFORMS , TIER_ADWEB , TIER_ADADMIN open your xml file & see theseparameters are there or not ( For xml file your system should be Autoconfig enabled ) all systemafter 11.5.8 by default are autoconfig enabled . For more info on Autoconfig check 
Cloning
is the act of creating an identical copy of an already existing Oracle Applicationssystem.Simply copying all of the components from source to target system does not provide us aworking Oracle Applications system, there are various configuration files that must be changed& for this purpose we do
Cloning.
Do keep in mind that the new system & the existing system must have same component
versions & operating system type (You can’t clone from windows to linux or Solaris).
 
Performing Cloning prerequisites steps:
 We need to perform certain prerequisites steps before cloning the source system:
STEP 1
Login as Applications file user & run the environment file.
STEP 2
We need to check certain software component versions:
(i)
Check the version of perl, it should be atleast 5.005 or above.To check perl version, Type the following command-$ perl -vMake sure that perl is included in the PATH (environment variable of user; echo $PATH).
(ii)
Check the version of JRE & JDK which should be atleast 1.1.8 & 1.3.1 or above respectively.for this type:$ java -version
(iii)
Check the version of zip which should be atleast 2.3 or above.for this type :$ zip
If you don’t have following versions, upgrade these software components as per the operating
system.
STEP 3:
It is
recommended
to apply the latest AD Minipack & the latest AutoConfig Templatepatch as mentioned in the metalink note
230672.1
but
not necessary
.
 
STEP 4:
Then we check whether latest Rapid Clone patch is there or not, for this we query thedatabase whether latest Rapid Clone patch and other prerequisite patches as mentioned in themetalink document
230672.1
as follows:
$ select * from AD_BUGS where bug_number=’&patch number’;
 
If it shows ” no rows selected ” that means you need to apply the patch. Do
ensure that you applyall the patches as per the requirement.
STEP 5:
If your system is autoconfig enable configure the application tier by running theadautocfg.sh script as follows:$ cd $COMMON_TOP/admin/scripts/<$CONTEXT_NAME>$adautocfg.shIf your system is not autoconfig enable then set up the autoconfig on application tier with thehelp of metalink document
165195.1
( Migrating to AutoConfig on the Applications Tier).
NOTE
:
 
To check whether your system is AutoConfig enable or not , open any configuration file,if you see the text
“This file is automatically generated by AutoConfig….”
at the top,thismean your system is autoconfig enabled.
 
Also all the applications after 11.5.7 are autoconfig enabled.
STEP 6:
Now we set up AutoConfig on the database tier. For this we need to copy AutoConfig tothe RDBMS ORACLE_HOME as follows:
• login as Applmgr . Set up the environment file & create appsutil.zip file in AD_TOP by typing
the following command:$
perl $AD_TOP/bin/admkappsutil.pl
 This creates appsutil.zip in the $APPL_TOP/admin/out directory.
• Now login as Oracle on the database tier & copy the appsutil.zip file to the <RDBMS
ORACLE_HOME> and unzip it:$ cd <RDBMS ORACLE_HOME>$ cp $APPL_TOP/admin/out/appsutil.zip$ unzip -o appsutil.zip (Option -o will overwrite any existing appsutil directory in databaseORACLE_HOME)Now run 
on the database tier:$ cd <RDBMS ORACLE_HOME>/appsutil/scripts/<context_name>/adautocfg.sh
Based on lot of request I am discussing on Shared APPL_TOP & Shared Application Tier. For next fewdays I will start with basics of Shared APPL_TOP likewhat's is Shared APPL_TOP ?

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->