If concurrent ma nagers are running then see the process using ps- ef | grep FND : Normally can take upto 5 minutes to kill all processes so be patient.

To abort all procsses = kill -9 `ps -ef | grep FND | awk `{print $2}’`

Status of each concurrent requests are hosted at FND_Concurrent_requests & Fnd_concurrent_queues. Running is R and complegted is set as C in this tables. Read more…

While installing apps 12 under OEL 5, I came across a problem and one of the suggestion made was to relink/compile an apps setup to see if that resolves the problem…

1. Locate your environment file.

For me, apps 12 with VISION database the env file “APPSVIS_ebs.env” is located at “/oracle/u01/apps/apps_st/appl” where “/oracle/u01” is Oracle_base

2. Setup your environment by running the env file

[applmgr@ebs appl]$ . APPSVIS_ebs.env

[applmgr@ebs appl]$ set | grep ORACLE
IAS_ORACLE_HOME=/oracle/u01/apps/tech_st/10.1.3
INCLUDE_FLAGS=’-I. -I$(FND_TOP)/include -I$(ORACLE_HOME)/precomp/public -I$(ORACLE_HOME)/rdbms/demo’
ORACLE_CONFIG_HOME=/oracle/u01/inst/apps/VIS_ebs/ora/10.1.2
ORACLE_HOME=/oracle/u01/apps/tech_st/10.1.2
ORACLE_TERM=vt220
PCC=’$(ORACLE_HOME)/bin/proc’
PCCINC=’. include=$(FND_TOP)/include include=$(ORACLE_HOME)/precomp/public’

3. Run adadmin now

Accept all default parameters and enter system password MANAGER & apps user password apps for default install.

To relink apps select option 2 and then 1.

Generally, in Oracle Applications

– All *.fmb located at $AU_TOP/forms/US

– All *.fmx will be located at their respective Product top’s/forms/US.

If you want to create any new form, copy .fmb in to $AU_TOP/forms/US.
11i – Using f60gen syntax, you can generate .fmx in respective product top/forms/US

12 – use frmcmp

http://applicationsdba.wordpress.com/?s=frmcmp

Some people will place both .fmb & .fmx at their Product top’s/forms/US itself.  At runtime it will use .fmx file.

Utility	Execution command	Action Performed
AD Administration	Adadmin	Driver program that performs maintenance tasks on the apps layer and within the database.
Auto Patch	Adpatch	Applies patches in several modes. Can also be used to add new languages and products.
Auto Upgrade	Adaimgr	Upgrades to the latest version of Oracle E-Business Suite.
Rapid Install AD Controller	Adctrl	Allows for the monitoring of status of workers spawned by Auto Upgrade, AD Admin, or Auto Patch and allows for the restarting of failed tasks.
FNDLOAD AD File Identification	Adident	Identifies version and translation level of one or more Apps files. Similar to Grep.
AD Splicer	Adsplice	Registers off cycle products.
File Character Set Converter	Adncnv	Converts text files from one character set to another.
AD Configuration	Adutconf.sql	Access standard information about the installed configuration of the Apps layer.
Auto Configuration	Adautocfg	AutoConfig. Provides central help to manage various configuration files.
AD Relink	Adrelink	Relinks executable programs with server libraries.
AD Merge Patch	Admrgpch	Merges several patches into single integrated patch without guaranteeing to take into account dependencies.
License Manager	Adlicmgr.sh	Licenses products, country specific functionalities, or languages.
AD Java Clone Utility	Adclone adjkey	Clones instances for more accurate testing. Generates the key for SSL.

1. Database monitoring
2. Apache monitoring
3. Forms monitoring
4. Concurrent Manager monitoring
5. Server monitoring
6. Network monitoring
7. Additional monitoring and troubleshooting

1. Database monitoring :

• Check Database alert log files & Database listener log file
• Check Database is up and running using “ps –ef | grep “ commands
• Look for Database sessions (idle sessions, high active sessions, high CPU consumers, total sessions, long running sessions, and blocking sessions). You will find number of sql/shell scripts on google for it.
• Database storage (datafile sizing, objects that are unable to extend, and maximum extent issues)

2.Apache monitoring : Check status of apache using  “ adapcctl.sh status ”

• The $APACHE_TOP/Apache/logs directory contains files such as error_log and error_log_pls.
• The JServ log files are located in the $APACHE_TOP/Apache/Jserv/logs and $APACHE_TOP/Apache/Jserv/logs/jvm directories.

If you want to enable additional logging, you can modify level of debug messaging in the jserv.log file.
The location of the jserv.log file is defined by the log.file parameter in the jserv.properties file.

Steps for enabling additional logging:

1. Set LogLevel to DEBUG in $APACHE_TOP/Apache/conf/httpd.conf.
2. Set ApJservLogLevel to DEBUG in $APACHE_TOP/Jserv/etc/jserv.conf.
3. Make the following changes to $APACHE_TOP/Jserv/etc/jserv.properties:

• Add wrapper.bin.parameters=-Djbo.debugoutput=console
• Set log=true
• Set log.channel=true
• Set log.channel.info=true
• Set log.channel.debug=true

Once these changes are made, review the log files for information to assist with troubleshooting the underlying issue.

Troubleshooting iAS Configuration :

The most comprehensive tool is the AOL/J Test.

• To access AOL/J Test tool directly, use  :/OA_HTML/jsp/fnd/aoljtest.jsp”>http://<hostname>:<port>/OA_HTML/jsp/fnd/aoljtest.jsp
• Enter the requested information, and click the Test button to continue.
• The program will establish a connection to database and return a screen with the Java version and classpath environment settings.  From this screen, the user can select a link to Enter AOL/J Setup Test
• The AOL/J Setup Tests page can be used to verify DBC file settings, display and test the Web Agent settings, display and test the Servlet Agent settings, and test X Server access.

Testing Java Servlet Configuration :

To validate Java servlet configuration access following URL:
http://[host IP:port]/oa_servlets/oracle.pps.fnd.text.HelloWorldServlet

Monitoring the JVM Pool : http://[hostname]:[port]/servlets/OAAppModPoolMonitor

With the 5.10 Framework, above link is invalid, and global Diagnostics button or OAM is the source for this information instead.

3. Forms monitoring  : One can monitor Forms server using GUI tool OAM  (oracle applications manager)

Monitoring Forms Dump Files : Forms Server dump files are created on Forms Node. These files are created in the directory where Forms process was started. The dump files are named f60webmx_dump_xxxx, where xxxx is a process number.

4. Concurrent Manager monitoring

Monitoring Concurrent Manager log Files :

Concurrent Manager log and output files are located in the $APPLCSF/$APPLLOG and $APPLCSF/$APPLOUT directories.

Reviewing active concurrent requests :

This could be done using OAM or running script SQL>@$FND_TOP/sql/afcmrrq

Monitoring pending concurrent requests:

At OAM select “Site Map > Administration > Concurrent Request > Pending Requests menu”

Canceling active concurrent requests :

This could be done using OAM or use TOAD/SQLplus to look for resource intensive SQL session. Killing such session should release pressure on system.

5. Server monitoring:

Make sure Server is accessible, use OS commands to look at CPU/DISK/IO/Memory Utilisation

6. Network monitoring  :

Use “ping” and “tracert“ commands

7. Additional monitoring and troubleshooting

Monitoring configuration issues:
Monitoring database and system backups: Often nightly backups overlap working hours causing database performance issues
Troubleshooting JInitiator :  If users encounter problems running applications on their workstations,try
• Clearing the JAR cache
• Using the Java console