Oracle Applications 11i System

Administration Diagnostic &

Troubleshooting
Topics

• Basic Applications Diagnostics and Troubleshooting Tools

• Application Security
• Concurrent Processing
• Useful Scripts

2
 Basic Applications Diagnostics
and Troubleshooting Tools

Basic Applications Tools

(Help) About Oracle Applications - Prime Use: Shows Applications version, Form short name, Form version
(Help) Record History - Prime Use: Shows primary table/view form is using
(Help) Diagnostics  Examine - Prime Use: Shows values of fields not visible on form
(Help) Diagnostics  Examine … choose $DESCRIPTIVE_FLEXFIELD$ block -
Prime Use: Shows user-friendly names of Descriptive Flexfields

(Help) Diagnostics  Examine … choose $ENVIRONMENT$ block –

Prime Use: Shows values of primary environment variables

(Help) Diagnostics  Examine … choose $PROFILES$ block –

Prime Use: Shows value in effect for any given profile option for that user.

(Help) Diagnostics  Examine … choose SYSTEM block and LAST_QUERY field. –

Prime Use: Shows the SELECT statement that was last executed by your form.
Note: Should also mention the FORM_STATUS and ERROR_ITEM fields in this block.

3
Basic Applications Tools

•(Help) Diagnostics  Display Database Error - Prime Use: Shows any database error message
•(Help) Diagnostics  Properties  Item - Prime Use: Shows forms canvas to which a field belongs
•(Help) Diagnostics  Trace (checkbox) - Prime Use: Turning on/off forms tracing. Trace file (*.trc) is put
into user_dump_dest.

•(Navigate) Concurrent  Program  Define

•Utilities: SQL Trace profile option
•Application Developer responsibility - Log on as Applications Developer responsibility,
A. (Navigate) Concurrent -> Programs - to see all concurrent programs
B. (Navigate) Application -> Form - to see all forms
C. (Navigate) Application -> Messages - to see Apps. Error messages
D. (Navigate) Application -> Database -> Tables - to see all tables
E. (Navigate) Application -> Database -> Sequence - to see all sequences
F. (Navigate) Application -> Database -> View - to see all views

4
Application Security

Responsibility
Responsibility Determines :
How much of an application’s functionality a user can use

What reports and concurrent program a user can access

Which application data these reports and concurrent programs can access.

Components of a Responsibility
•Data Group
•Request Group
•Menu
•Function and menu exclusion

5
Data Group
A data group defines the mapping between Oracle Application product
and Oracle ID

An Oracle username and password allow access to an

application’s table in an Oracle database.

Each Oracle username in a datagroup determines the

database table and privileges accessible by the corresponding application

6
Request Group
A request group defines the concurrent program that may

be run by an application user under a particular responsibility

Request group can include

•Individual Report and concurrent program

•Request Set

7
Forms
form is a user interface to insert ,update and delete data into and from

Database. A form must be registered with Oracle Application Object Library

Function

•Form Function - A function that invokes an Oracle Forms form

•Sub function - A non form function is a securable subset of forms
functionality , which means a function executed from within a form

One can navigate to a form function ( form) using the navigate window

A sub function can only be run from a form

8
Menu

•A menu is a hierarchical arrangement of application functions,

that are displayed in the navigator window

•menus can also point to non form function that do not display in
the navigator

•Each responsibility is associated with a menu

•A menu consists of menu entries , which could be a submenu or
a function

9
•Create a test User
•Create a test Responsibility
•Create a test Application
•Create a test Data Group
•Create a test Oracle ID
•Create a test Request Group
•Create a test Form
•Create a test Form Function
•Create a test Menu
•Set Signon Audit profile option

10
Running Security and User Reports
•Function Security Menu Report
•Function Security Navigator Report
•Function Security Function Report
•Active Users Report
•Active Responsibilities Report
•Report Group Responsibilities Report
•Reports and Sets by Responsibility Report
•Users of a Responsibility Report
•Sign-On Audit Forms Report
•Sign-On Audit Users Report
•Sign-On Audit Responsibilities Report
•Sign-On Audit Unsuccessful Logins Report
•Sign-On Audit Concurrent Requests Report 11
Concurrent Processing

Concurrent Program
A concurrent program is an executable file that runs simultaneously with

other concurrent programs and with online operations.

•Any long running data intensive program

•Operating system script
•Oracle Reports
•When submitted through a Standard Submission form a concurrent
program generates a concurrent request

•A concurrent manager intercept a concurrent request and starts the

process
12
Request Group
•A request group is a collection of reports and concurrent programs
•A system administrator defines request group in order to control user
access to reports and concurrent programs

•Only a system administrator can define a request group

Request Set
•Request set is a set of reports and concurrent programs with common
run and print options.

•End user and system administrator can define request set

13
Concurrent Processing Components

•Internal Concurrent Manager - The Internal Concurrent

Manager (ICM) is the "manager" of all concurrent processing
that occurs within Oracle Applications. ICM is an instance of
the program, FNDLIBR.
•The ICM controls all of the other concurrent managers
•Conflict Resolution Manager - The Conflict Resolution
Manager (CRM) is a running instance of the program,
FNDCRM. Its job is to remove a substantial burden from the
ICM, that is of resolving conflicts, such as request incompatibilities.

14
•Parallel Concurrent Processing - Parallel Concurrent Processing
(PCP) is the ability to distribute concurrent processing over multiple
machines. This architecture has following advantages.
1. High performance
2. Fault Tolerance
3. Single Point of Control

•The biggest advantage for PCP is fault tolerance.You will see slightly
higher performance. You will see the most improvement on concurrent
processing jobs that are compute-intensive. Data-intensive jobs will not
have as significant an improvement, except where PCP is combined
with Oracle Parallel Server (OPS).
•The APPLDCP environment variable is used to indicate whether PCP is
on or off.

15
•Internal Monitor - When you are using PCP, you must allow for the
possibility that the Internal Concurrent Manager on the master system
can fail. In this case, Oracle Applications uses a special process, called
the Internal Monitor (IM), that watches for just such an event. If it
happens, IM will attempt to start an ICM on its machine. That ICM would
then become the master.

•When IM is running, it is running an instance of the program, FNDIMON.

•The Standard Manager accepts any and all requests. It has no

predefined specialization rules and is active all the time. It is not
recommended to add specialization rules to the standard manager as it
can cause problems.

16
•Concurrent Managers - Concurrent Managers are the primary
workhorse of the concurrent processing system. Most concurrent
managers run the standard concurrent library called FNDLIBR. There
are additional concurrent libraries (e.g., INVLIBR, ARLIBR, PALIBR,
etc.).

•NOTE: Yes, concurrent managers and the ICM run the same program,
FNDLIBR.

17
•Transaction Managers - Transaction Managers (TMs) are the process
by which Applications handles synchronous tasks that can not afford to
wait in the queue. An example of a Transaction Manager occurs in
Order Management. When some enters an order, that order is checked
against inventory, work in process, orders, and several other systems to
see if we can deliver this to the customer when we promise.

•TMs are immediate concurrent programs that work only when signaled
by a client. Unlike CMs that continuously poll the system looking for
work, TMs wait until signaled. Also, the TMs do not establish on-going
connections with the client. Once the request has been sent to the TM,
the connection remains only long enough for the TM to obtain the
answer and return the result set.

18
Generic Service Management (GSM)
•An E-Business Suite system depends on a variety of services such as
Forms Listeners, HTTP Servers, Concurrent Managers, Workflow
Mailers, etc.  Such services are composed of one or more processes
that must be kept running for the proper functioning of the E-Business
Suite.  Until recently many of these processes had to be individually
started and monitored by system administrators.  Management of these
processes was complicated by the fact that these services could be
distributed across multiple host machines.  The new Service
Management feature for Release 11i helps to greatly simplify the
management of these processes by providing a fault tolerant service
framework and a central management console built into Oracle
Applications Manager 11i.

•Service Management is an extension of Concurrent Processing, which

provides a powerful framework for managing processes on multiple
host machines. 
19
Generic Service Management (GSM)
•With Service Management, the Internal Concurrent Manager (ICM)
manages the various service processes across multiple hosts. On
each host, a Service Manager acts on behalf of the ICM, allowing the
ICM to monitor and control service processes on that host
•Set System Profile – Concurrent GSM Enabled to Y
•Need to configure FNDSM listener & corresponding tnsnames.ora,
FND_TOP/bin/gsmstart.sh
•Important:  If GSM is not correctly configured, problems may occur
with the managers failing to start. In this case, the GSM functionality
may be turned off by resetting this Profile to 'N' and bouncing the
managers (i.e. shutting down the icm and restarting it).  This will
allow concurrent managers to run while the configuration error is
resolved.

•For more detailed information about GSM and its functionality refer
to OracleMetalink Note 165041.1. 20
Concurrent Processing Tasks

•Submit an individual concurrent request

•Submit a concurrent request set
•Scheduling a concurrent request
•Monitoring a concurrent request
•Viewing a concurrent request's log file
•Viewing a concurrent request's output

21
Concurrent Processing Tasks

•Create a request set

•Create a request group
•Create a concurrent executable
•Create a concurrent program
•Create a concurrent manager
•Stop and restart a concurrent manager
•Stop and restart the ICM
•Canceling a concurrent request
•Holding a concurrent request
•Terminating a concurrent request

22
Purging the request table

When tables FND_CONCURRENT_REQUESTS and

FND_CONCURRENT_PROCESSES reaches to above 20K rows, the
performance diminishes. You may want to run Purge Concurrent
Request on a regular basis.
The Purge Concurrent Requests job can be used to purge:
Requests, Mgr logs, and All requests depending on what is
chosen. Use the following options: Enter = All, Mode = AGE,
Mode Value = 15
The std.mgr log continuously grows where it may good to
archive it regularly.
23
Useful Scripts

Concurrent Processing Scripts

•Analyze a concurrent request

•Analyze all pending concurrent requests
•Clean the concurrent manager tables
•Retrieve all log files for a concurrent request
•Get a concurrent program’s incompatibilities
•List responsibilities that can run a given concurrent program
•Available at http://ap9019pc.us.oracle.com/

•ccm.sql - Available at metalink NOTE:171855.1

24
$FND_TOP/sql has many useful script to debug CM.

afimlock.sql - To list the Locks that the ICM is waiting for

afimchk.sql - To check the status of ICM
afrqrun.sql - Lists all Running, Terminating, Paused Requests
afrqwait.sql - Selects all the Pending Requests
afcmrrq.sql - Lists managers that are currently running a request
(username, request id, program name, start date, etc).

25
Diagnostic Database Scripts

•Describe Database Space

•Describe Data Files
•Describe a Database Object
•Count Database Objects by Type
•Table Definitions
•Describe Tablespace
•Describe Database Users

26
Diagnostic Applications Scripts
Some important scripts are as below:
Located in $AD_TOP/sql
•Check and List Compilation Errors - aderrch2.sql
•List Job Timing Information - adtimdet.sql
•Count Objects by Type - adutcobj.sql
•Applications Configuration Script - adutconf.sql
•List Product Dependencies - adutfpd.sql
•List Pinned Objects - ADXCKPIN.sql
•Report Database Configuration - ADXRCSDC.sql
•Report Table Sizes - ADXRSFTS.sql
•Show Extent Failure - ADXRSSIE.sql
•Show User Space - ADXRSSUS.sql
27
Controlling Servers scripts

•Stopping servers
•Starting servers
•Located in $COMMON_TOP/admin/scripts

Some important scripts are as below:

•Forms Server Listener - adfroctl.sh

•Forms Server - adfmsctl.sh
•Report Review Agent - adalnctl.sh
•Reports Server - adrepctl.sh
•Concurrent Managers - adcmctl.sh
•Net8 Listener - addlnctl.sh
•Apache Listener - adapcctl.sh
•Oracle 8i database server - addbctl.sh

28
Checking Certification

•MetaLink (External):
http://metalink.oracle.com/
•Certify - Oracle's Certification Matrix (Internal):
http://certify.us.oracle.com/
•Certify User's Guide (Internal):
http://certify.us.oracle.com/certifyuserguide.pdf
•Certify FAQ (Internal):
http://certify.us.oracle.com/certfaq.html
•RDBMS Patch Set Tracking System:
http://ess30.us.oracle.com:8002/
•Interoperability Patches:
http://sac.us.oracle.com/download/index.html

29
 Apache and Jserv

• Httpd.conf
• Oracle_apache.conf – calls plsql.conf,6iserver.conf. Has
directives for oracle
• Jserv.conf
Main jserv config file.
• Jserv.properties
Userd by the JVM. Has the port in which Jserv listens
• Root.properties
This groups the class files for micro JVMs
Stores the property class.autoreload

30
Apache and Jserv

• Files are cached in webcache $OA_HTML/_pages

• DAD config is in
$APACHE_TOP/Apache/modplsql/cfg/wdbsvr.app
This stores the DAD config with Apps password
For DB connectivity – uses DBC file in $FND_TOP/secure
This has the guest and gateway user id
It can be created using adgendbc.sh script

31
 Forms server

• Jinitiator stored in $COMMON_TOP/util/jinitiator

• For digitally signing,
$AD_TOP/bin/adjkey –initialize
adjbuild.sh <Dir of jinit> <Dir of jinit/jinitiator>
• Forms server config is stored in $OA_HTML/bin/appsweb.cfg
• All forms in $AU_TOP/forms/US
• To check form version use adident command.

32
 Question ?
Comments/ Suggestion

33