Friday, January 19, 2007

Log files location

Log files and their location

Installation Log file
Cloning Log file
Autoconfig log files
Rolling back autoconfig configuration files
Apache/Jserv configuration files
Apache/Jserv Logs
Forms Server
Adodfcmp
fdfcmp/fndfvgn/gndmdgen
User Exits
Concurrent Manager
Internal Manager
Concurrent Program logs
Sql*net, net8 listener
ssp5(iProcurement)

Installation Log file
Database log files $ORACLE_HOME/appsutil/log/CONTEXT_NAME/
Applications log files $APPL_TOP/admin/CONTEXT_NAME/log/

Cloning Log file
perl adcfgclone.pl dbTier $ORACLE_HOME(9i)/appsutil/log/CONTEXT_NAME/ApplyDBTier_TIMESTAMP.log
perl adcfgclone.pl appsTier $APPL_TOP/admin/CONTEXT_NAME/log/ApplyAppsTier_TIMESTAMP.log

Autoconfig log files
Application Tier $APPL_TOP>/admin/CONTEXT_NAME/log/MMDDhhmm
Database Tier $/appsutil/log/CONTEXT_NAME/mmddhhmm

Rolling back autoconfig configuration files
Application Tier $APPL_TOP/admin//out/
Database Tier $ORACLE_HOME/appsutil/out//

Apache/Jserv configuration files
jserv.properties $APACHE_TOP/Jserv/etc/
jserv.conf $APACHE_TOP/Jserv/etc/
zone.properties $APACHE_TOP/Jserv/etc/
httpd.conf $APACHE_TOP/Apache/conf/
httpds.conf $APACHE_TOP/Apache/conf/
oracle_apache.conf $APACHE_TOP/Apache/conf/
apps.conf $APACHE_TOP/Apache/conf/

Apache/Jserv Logs
error_log $APACHE_TOP/Apache/logs/
access_log $APACHE_TOP/Apache/logs/
mod_jserv.log $APACHE_TOP/Jserv/logs/
jserv.log $APACHE_TOP/Jserv/logs/

Forms Server
When starting forms server we can specify a log file name.
Examples:
WIN/NT
f60srv32 log=c:\temp\f60srv.log
Unix
f60ctl start log=/temp/f60srv.log
f45ctl start port=9000 log=/temp/forms.log

Adodfcmp
adodfcmp.log $/admin/odf/
or
$PROD_TOP/patch//odf/

fdfcmp/fndfvgn/gndmdgen
L.req $APPL_TOP/admin or $APPL_TOP/install/log,

User Exits
userexit.log User exits from forms generate log file under directory from where the forms server is
started if variable FDUDEBUG is set to ON

Concurrent Manager
Concurrent Manager w.mgr Two methods to see concurrent manager logs
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

Retrieve Manager log files under:
$FND_TOP/$APPLLOG
or if you have defined common directory :
$APPLCSF/$APPLLOG

Internal Manager
Internal Manager .mgr
(mgrname which figures
in startmgr file is 'std' by
default) Two methods to see internal manager log:
Directly from Oracle Applications:
System Administrator responsability
Navigator:
Concurrent =>
Manager =>
Administer, button Processes (Concurrent Processes window) =>
button Internal Manager Log

Retrieve Internal Manager log file under:
$FND_TOP/$APPLLOG
or if you have defined common directory :
$APPLCSF/$APPLLOG

Concurrent Program logs
Concurrent Program logs l.req Two methods to see concurrent program logs:

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...

Retrieve Concurrent Program log files under:
$PROD_TOP/$APPLLOG
or if you have defined common directory :
$APPLCSF/$APPLLOG


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.

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=Directory(preferably under $APACHE_TOP/logs)
DebugLevel=5
DebugSwitch=ON

No comments: