Beruflich Dokumente
Kultur Dokumente
There is lot of difference between Autoconfig & Rapid Clone. Earlier dba's used to use
Autoconfig to clone Oracle Apps 11i Instance and still in background Rapid Clone
executes Autoconfig .
what's is Autoconfig ?
Autoconfig is utility to configure Oracle Applications 11i using a file based configuration
repository also called as context file or XML file.
So basic difference between Autoconfig & Rapid clone is these are two utilities one for
configuring Oracle Applications 11i & second one to clone Apps 11i Instance using first Utility .
(or)
When you run this commnad adpreclone.pl dbTier . This will run in two steps Techstack
and database.
Techstack:
It will create following directories in the ORACLE_HOME/appsutil/clone
Jlib, db, data where “Jlib” relates to libraries “db” will contain the techstack information,
“data” will contain the information related to datafiles and required for cloning.
Creates driver files at ORACLE_HOME/appsutil/driver/instconf.drv
This will create stage directory at $COMMON_TOP/clone. This also run in two steps.
Techstack:
Creates template files for
Oracle_iAS_Home/appsutil/template
Oracle_806_Home/appsutil/template
APPL_TOP preparation:
-It will create application top driver file$COMMON_TOP/clone/appl/driver/appl.drv
-Copy JDBC libraries$COMMON_TOP/clone/jlib/classes111.zip
Now Shutdown all the services of Application and database for Copy the file System to
target location
On database side:
cd $ORACLE_HOME/appsutils/clone/binperl adcfgclone.pl dbTier pwd=apps
This will use the templates and driver files those were created while running
adpreclone.pl on source system and has been copied to target system.
adchkutl.sh — This will check the system for ld, ar, cc, and make versions.
adclonectx.pl — This will clone the context file. This will ceate a new context file as per
the details of this instance.
runInstallConfigDriver — located in $Oracle_Home/appsutil/driver/instconf.drv
Relinking $Oracle_Home/appsutil/install/adlnkoh.sh — This will relink ORACLE_HOME
For data on database side, following scripts are run
Driver file $Oracle_Home/appsutil/clone/context/data/driver/data.drv
Create database adcrdb.zip
Autoconfig is run
Control file creation adcrdbclone.sql
On Application Side:
COMMON_TOP/clone/bin/perl adcfgclone.pl appsTier pwd=apps
Following scripts are run by adcfgclone.pl
Creates context file for target adclonectx.pl
Relinking of Oracle
Home$ORACLE_HOME/bin/adlnk806.sh$IAS_ORACLE_HOME/bin/adlnkiAS.sh
At the end it will run the driver file $COMMON_TOP/clone/appl/driver/appl.drv and then
runs autoconfig.
(OR)
1. How do you Apply a application patch? -> Using adpatch 2. Complete Usage of
adpatch? 1. download the patch in three ways.
a) Using OAM-Open Internet Exploreer->Select Oracle Application Manager-> Navigate
to Patch Wizard -> Select Download Patches -> Give the patch number(more than one
patch give patch numbers separated by comma-> Select option download only->Select
langauge and Platform-> Give date and time-> submit ok Note: Before doing this Your
oracle apps should be configured with metalink credentials and proxy settings
b) If your unix system is configured with metalink then goto your applmgr account and
issue following command
1.ftp updates.oracle.com
2.Give metalink username and password
3.After connecting, cd patch number
4. ls -ltr
5. get patchnumber.zip(select compatiable to OS)
c) Third way is connect to metalink.oracle.com.
1. Goto $APPL_TOP/admin/SID/log
2. tail -f patchnumber.log(Monitor this file in another session)
3. tail -f patchnumber.lgi(Monitor this file in another session)
4. TOP comand in another session for CPU Usage
3. Adcontroller during patching?
1. During patching if worker fails, restart failed worker using adctrl(You wil find the option
when u enter into adctrl)
2. If again worker fails, Goto $APPL_TOP/admin/SID/log/workernumber.log
3. Check for the error, fix it restart the worker using adctrl
4. If you the issue was not fixed, If oracle recommends if it can e ignorable, skip the
worker using adctrl with hidden option 8 and give the worker number
4. Log files during patching?
1. patchnumber.log ($APPL_TOP/admin/SID/LOG/patchnumber.log)
2. patchnumber.lgi($APPL_TOP/admin/SID/LOG/patchnumber.lgi)
3. adworker.log($APPL_TOP/admin/SID/LOG/adworker001.log)
4. l.req($APPL_TOP/admin/SID/LOG/l1248097.req)
5. adrelink.log($APPL_TOP/admin/SID/LOG/adrelink.log)
6. adrelink.lsv($APPL_TOP/admin/SID/LOG/adrelink.lsv)
7.autoconfig.log($APPL_TOP/admin/SID/LOG/autoconfig_3307.log)
5. useful tables for patching?
1. You can know whether particular patch is applied or not using ad_applied_patches or
ad_bugs
2. Using OAM->Patch wizard-> Give patch numer
3. To know mini pack patchest level, family pack patchest level and patch numbers by
executing script called patchsets.sh(It has to be downloaded from metalink
7. Reduce patch time?
Step 1 :Log on to the Oracle Application Manager (OAM) & click site map.You will be
able to log on but some services will be down.
Step 2: Click AutoConfig from the list of System Configuration features in the
Administration tab.
Step 3 : Click the Show History button for the application tier context file to access the
Context File History page.
Step 4 :Click the Show Differences from Current Configuration button to see the
recently updated parameters & Select Restore Previous Value for the Web Port and
Discoverer Port parameters.
Step 5 :Save & respond the tabs. Log out of OAM.
Step 6 :Shut down all services:
$ cd $COMMON_TOP/admin/scripts/<context_name>
$ adstpall.sh APPS/<APPS password>
Step 7 :Run the AutoConfig script, adautocfg.sh & Respond to the prompts.
Step 8 : View the log file and check for any errors.
Step 9 : Restart all services:
$ $COMMON_TOP/admin/scripts/<context_name>/adstrtal.sh APPS/<APPS password>
Step 10 :Log on to the Oracle Application Manager (OAM)
If the status of some services appears to be down, click the Refresh icon to update the
status.
If you configure through Mailer configuration wizard through OAM, Autoconfig overwrites its configuration.
Because By default Autoconfig Context file contains smtp server name as Application Tier Hostname/Concurrent
Manager Node Hostname. When you run autoconfig, it overwrites the smtp server hostname what you have
configured through OAM with the value in Autoconfig Context File. I feel the following is the simple procedure to
follow, which worked for me.(1) Take backup of existing Autoconfig Context Filelogin as APPLMGR User
$cd $APPL_TOP/admin
(2) Edit the Autoconfig Context file with SMTP server name
$vi <SID>_<hostname>.xml
Note: Above Same procedure can also be done by editing above context variables
in OAM > Site Map > System Configuration> Applications Autoconfig Context File
$cd $COMMON_TOP/admin/scripts/<SID>_<hostname>
$sh adautocfg.sh
$cd $COMMON_TOP/admin/scripts/<SID>_<hostname>
If the following Concurrent Managers are not activated or started before, activate and srart them
This is the seeded Workflow Notification Mailer Service component belongs to a container named Workflow Agent
Listener Service
This is also seeded agent listener service component required for Workflow Mailer Processing
(1) Using OAM > Site MAP > Wofkflow > Home > Service Components
or
(2) Using System Administrator Responsibility > Concurrent > Manager > Administer
That’s the procedure I did it and configured successfully workflow Notification Mailer.
Reference:
http://download.oracle.com/docs/cd/B25284_01/current/acrobat/115wfag.pdf
http://download.oracle.com/docs/cd/B25284_01/current/acrobat/115wfug.pdf
(3) Note:313954.1 Autoconfig Overwriting The SMTP Server Name For The Java M