How To Get Log Files From Various Programs For

Oracle Apps
1. CONCURRENT PROGRAMS
——————————————
two methods to see concurrent program logs :

a. directly from Oracle Applications :

System Administrator responsability (for own and other users requests) :
Navigator: Concurrent => Requests, button View Log…

Other responsabilities (for own requests), menus could be different:

Navigator: Requests , button View Log…
Navigator: Other => Requests , button View Log…
Navigator: Other => Requests => View , button View Log…
Navigator: Control => Requests => View , button View Log…

b. retrieve Concurrent Program log files under :

$/$APPLLOG
or if you have defined common directory :
$APPLCSF/$APPLLOG

File format is :
l.req

2. CONCURRENT MANAGERS
——————————————
two methods to see concurrent manager logs :

a. directly from Oracle Applications :

System Administrator responsability

Navigator: Concurrent => Requests, choose a request …
menu: Special => Manager Log
or
Navigator: Concurrent => Manager => Administer, button Processes (Concurrent Processes
window)
=> button Manager Log

b. retrieve Manager log files under :

$FND_TOP/$APPLLOG
or if you have defined common directory :
$APPLCSF/$APPLLOG
File format is :

w.mgr3. INTERNAL MANAGER

————————————-
two methods to see internal manager log :

a. directly from Oracle Applications :

System Administrator responsability

Navigator: Concurrent => Manager => Administer, button Processes (Concurrent Processes
window)
=> button Internal Manager Log

b. retrieve Internal Manager log file under :

$FND_TOP/$APPLLOG
or if you have defined common directory :
$APPLCSF/$APPLLOG

File format is :
.mgr

(mgrname which figures in startmgr file is ‘std’ by default)

4. AD, FND AND OTHER UTILITIES

—————————————————-
Some AD utilities like adpatch, adadmin, etc. generate log file under
$APPL_TOP/admin or $APPL_TOP/install/log, file names are :

adunload.log
adrelink.log
adlibout.log
adlibin.log
adfrmgen.log
admrgpch.log
adrepgen.log
adctrl.log
admvcode.log
adaimgr.log
adwork01.log, adwork02.log, adwork03.log, …

Utility adodfcmp generates log file under $/admin/odf/

or $/patch//odf/, file name is:

adodfcmp.log
FND utilities like fdfcmp, FNDFFVGN, FNDMDGEN generate log file under
$APPL_TOP/admin or $APPL_TOP/install/log, file name is :

L.req

5. USER EXITS
———————-
User exits from forms generate log file under directory from where the forms
server is started if variable FDUDEBUG is set to ON. File name is:

userexit.log

6. FORMS SERVER
—————————
When starting forms server you can specify a log file name.

Exemples:

WIN/NT
f60srv32 log=c:\temp\f60srv.log

Unix
f60ctl start log=/temp/f60srv.log
f45ctl start port=9000 log=/temp/forms.log>

7. SQL*NET, NET8 LISTENER

——————————————-
You can specify LOG_DIRECTORY_ and LOG_FILE_ specific values for theses parameters in
listener.ora. You can set LOG_FILE and TRACE_FILE variables from a lsnrctl session. There
are also LOG_DIRECTORY_SERVER and LOG_FILE_SERVER parameters in sqlnet.ora.

8. APACHE, JSERV

————————–

Logs from Apache server are under $APACHE_TOP/logs, file names are :

error_log, access_log, httpds_access_log, httpds_error_log, sqlnet.log

Logs from Jserv are under $ORACLE_HOME/Apache/Jserv/logs , file names are :

jserv.log, debug.log

Note: it is recommended to clean up these log files, shutdown and restart apache server before
trying to reproduce the issue and analyze.
9. SSP5 (iPROCUREMENT)

—————————————

Apache and Jserv logs are useful to check for iProcurement (SSP5), you can also add these lines
in ssp_init.txt (should be under $ORACLE_HOME/Apache/Jserv/etc) to generate specific SSP5
log file :

DebugOutput= (preferably under $APACHE_TOP/logs)

DebugLevel=5
DebugSwitch=ON

Note: don’t forget to restart Apache server after editing ssp_init.txt.

10. DATABASE
———————-

In case of ORA- and other database errors it could be useful to check the
file alert.log.

You should find it under bdump directory (background_dump_dest parameter)

or $ORACLE_HOME/rdbms/log.