Oracle EBS Tracing

1)Tracing form based form:
->open the form:help:diagnostics:trace:trace with waits
-Trace will be generated in udump.
- perform some transaction
->Disable the trace
help:diagnostics:trace:notrace
->Use tkprof to convert the trace file to understandable format.
$cd $ORACLE_HOME/admin/PROD_node11/udump
2)Tracing html based form:
->Enable Diagnostic menu
nav:profile:system
profile: FND_Diagnostics
Site: Yes

->To trace html based application.
Click on diagnostics
Diagnostics: Set Trace Level
* Trace with waits
* Disable trace
-> Go to Udump & use tkprof
3)Tracing Concurrent Program:

nav: Concurrent:Program:Define (Query the CP. ex: Active Users)
* Enable Trace & save
- Run the CP
- Disable the trace & save
- Go to udump & use tkprof utility.

Oracle EBS Patch Management (Non-Interactive Mode)

- Applying patch in non-interactive mode:

                                File: $APPL_TOP/admin/<SID>/adalldefaults.txt

                                - Download the patch

                                - unzip the patch

                                - Go to patch dir & review README.txt doc

                                - Stop the appl services

                                - Enable Maintenance Mode

                                - Run adpatch

                                - Disable Maintenance Mode

                 Applying patch in non-interactive mode:

                                File: $APPL_TOP/admin/<SID>/adalldefaults.txt

                                - Download the patch

                                - unzip the patch

                                - Go to patch dir & review README.txt doc

                                - Stop the appl services

                                - Enable Maintenance Mode

                                - Run adpatch

                                - Disable Maintenance Mode

                                - Start the app services

                Patch History:

                                - We can check the patch history from

                (1) DB tables                                           (2) OAM

                - DB Tables:

                                (1) AD_BUGS: It contains the patches info that are applied by the installer &                                         also the patches info that are applied by user.

                                (2) AD_APPLIED_PATCHES: It contains the patches info that are applied by user.

                                (3) AD_PATCH_DRIVERS: It contains patch driver actions info(C,D,G).

                Note:

                                One-off   -> Kbs

                                Minipack -> mbs

                                Family pack -> mbs/gbs

                                Maintenance Pack -> gbs

                Saving Patch time:

                                - Apply the patch in non-interactive mode

                                Response file: $APPL_TOP/admin/<SID>/adalldefaults.txt

                                - Download & unzip the patch

                                - Review the README.txt doc

                                - Stop the app services

                                - Enable Maintenance Mode

                                - Run adpatch in non-int.. mode

                                                File: $APPL_TOP/admin/PROD/adalldefaults.txt

                                                Note:

                                                .lgi file contains informational messages

                                                (ie.. files copied, backed up)

                                - Check logfile & disable M.M

                                - Start the applcation services

                - Merging the patches (ex: NLS patches..)

                                Note: Patches are platfrom dependent & version dependent.

                                5 Languages

                                1 -base = US English

                                4 -(AR,UK,..)

                                ex: P12345

                                - Apply base lang patch (US English)

                                - Merge the NLS Patches...(4 patches)

                                utility :admrgpch

                                - Download the patches

                                - Create src & dest dir

                                - Go to src dir & unzip the patches

                                - Go to patch dir & review README.txt

                                - Merge the patches

                                - Stop the app services

                                - Enable Maintenance Mode

                                - Run adpatch in non-interactive mode

                                - Disable Maintenance Mode

                                - Start the app services

                - Skipping Patch driver actions:

                                Actions: C,D,G

                                $adpatch options=nodatabaseportion

                                $adpatch options=nocopyportion,nogenerateportion            // EBS Upgradation

                - Skipping Post patch activities:

                                Activities: Compiling invalid objects, compiling JSP, Running autoconfig ...

                                ex:

                                8457584  $adpatch options=nocompiledb,nocompilejsp,noautoconfig                (skip)

                                5474548 $adpatch options=nocompiledb,nocompilejsp,noautoconfig   (skip)

                                9589858 $adpatch options=compiledb,compilejsp,autoconfig             (Don't skip)

                - adpatch options:

                                                $adpatch preinstall=Yes  ( To upgrade ad utilites)

                                $adpatch options=hotpatch  (To apply hot patch. No downtime required)

                                                ex: Document Patches

                                $adpatch Apply=no (To run adpatch in testmode)

                - Checking Patch history using OAM:

                                - Login as SYSADMIN

                - Select "System Administrator" resp

                - nav: Oracle Applications Manager: Patching and Utilites

                ex:   codeline

                R12.0.x                    R12.A

                R12.1.x                    R12.B

                                                Product                    codelevel

                R12.0.4                    AD                           R12.AD.A.4

                R12.1.1                    AD                           R12.AD.B.1              --------->  R12.AD.B.3             

                Table: ad_trackable_entities

                -> Patch Wizard:

                                                It is a tool to create patch filters, download patches, analyze the patch impact ..

                                - nav: Oracle Applications Manager:DASHBOARD :

Oracle EBS Patch Management

                - Patch Tool Kit:

                                - adpatch

                                - adctrl

                                - admrgpch

                                - adadmin

                                - autoconfig

                - Types:

                                - One-Off               

                                - MiniPack

                                - Family Pack

                                - Maintenance Pack

- Uitlity: adpatch

                - Steps:

                                - Download the patch

                                - Unzip the patch

                                - Go to patch dir & review the README.txt doc

                                                * Patch Description

                                                * Pre-requisite info

                                                * How to apply the patch      

                                                * post install tasks

                                - Stop the application services

                                                $cd $ADMIN_SCRIPTS_HOME

                                                $./adstpall.sh apps/apps

                                - Enable Maintenance Mode

                                                adadmin 5-1

                                - Run adpatch to apply the patch

                                                Logfile: $APPL_TOP/admin/<SID>/log

                                                patch top location: /u02/9239089

                                                patch driver file: u9239089.drv

                                                no: of workers: 6

                                                - Open a terminal & login as applmgr

                                                - Run adctrl to check adworkers status

                                - After applying the patch check logfile

                                                $cd $APPL_TOP/admin/<SID>/log

                                - Disable Maintenance Mode

                                                adadmin 5-2

                                - Start the application services

                                                $cd $ADMIN_SCRIPTS_HOME

                                                $./adstrtall apps/apps

Oracle EBS AutoConfig

Autoconfig as name suggests is automated configuration of Oracle Applications 11i.

 Well if this is configuring oracle applications 11i question comes from where its getting configuration information. File from where Autoconfig runs picks parameter to configure 11i , in Oracle's terminology is called Context File. Power of configuring whole applications via this single file (One for Application Tier & other for Database Tier) makes this file quite powerful. Rest all I discuss in terms of questions answers or FAQ format about Autoconfig.
 
What is Autoconfig in 11i ?
Autoconfig is method of configuring Oracle Applications . All the information required to configure Oracle Apps 11i is stored in file called as Context file. So there are two context file, one for Database Tier & Second for Application Tier. Context file is repository for configuration stored in xml format. Its xml file and file name format is <SID>_<HOSTNAME>.xml so if your machine name is machine1 & SID is VISION then context file name will be VISION_machine1.xml
 
What are different Contexts w.r.t. Autoconfig in 11i ?
There are two context files, one for database tier called as Database Context second for Application tier called as Application Context.
 
What is location of Contexts file in 11i ?
Database Context file is under Database $ORACLE_HOME/appsutil/<SID>_<HOSTNAME>.xml
Application Context file is under $APPL_TOP/admin/<SID>_<HOSTNAME>.xml



How to run Autoconfig in 11i ?
You will use script adautocfg.sh (on both Database & Application tier) which inturn will call adconfig.sh , which further will calladconfig.pl. You should not worry about later two scripts its for information only. adautoconfig.sh is script which you use to run autoconfig.

 
Where to check log files after autoconfig is executed ?

•On database tier its under $ORACLE_HOME/appsutil/log/$CONTEXT_NAME/MM_DD_YYYY/adconfig.log

•On Application tier its under $APPL_TOP/admin/$CONTEXT_NAME/log/MMDDYYYY/adconfig.log

where CONTXT_NAME is <SID>_<HOSTNAME>
 
What if my Context file itself is corrupted, Can I create one ?
Yes you have utility called adbldxml to build xml file(Context File).
 
How to change some parameter in Context/xml file ?
If you are an expert then you can open xml file via any editor & change it but these days Oracle is recommending to use Context Editor or if you are on OAM.H or higher then use OAM (Oracle Application Manager) to change context file.

How to submit a concurrent request? Oracle apps (EBS )

- Using SRS(Standard Request Submission) form.

- Using SRS form we can

* submit a request

* View details

* view log

* view output

* Hold request

* Cancel request

...

- Steps:

- Open any form

- Go to menu bar-> view -> Requests -> Submit a new request -> Single request ....

FNCPASS UTILITY to Change password Oracle apps (EBS )

$ FNDCPASS apps/apps 0 Y system/manager SYSTEM APPLSYS WELCOME
$ FNDCPASS apps/apps 0 Y system/manager ORACLE GL GL1
$ FNDCPASS apps/apps 0 Y system/manager USER VISION WELCOME

Note: The FNDCPASS has a new mode, "ALLORACLE", in which all Oracle Application schema passwords can be changed in one call.
Apply the patch (Patch No# 4745998) to have this option, if not available currently with your Apps.
Syntax:
FNDCPASS 0 Y ALLORACLE
Example:
$ FNDCPASS apps/apps 0 Y system/manager ALLORACLE WELCOME


To change APPS/APPLSYS password, we need to give mode as SYSTEM
To change product schema passwords, i.e., GL, AP, AR, etc., we need to give mode as ORACLE
To change end user passwords, i.e., SYSADMIN, OPERATIONS etc., we need give mode as USER

Where the FNDCPASS utility is located?
Concurrent node @FND_TOP/bin