Blog Archives

How to check from backend if frontend Logging is Enabled

You may at times face an issue where you have a rapidly growing udump directory. One of the possible reason for that can be if debug logging is enabled from the front end at user/site level.

Apart from manually checking from Forms interface following SQL queries will help in listing the same:

1. This will display values of profile options “FND: Debug Log Enabled” (AFLOG_ENABLED) and”Initialization SQL Statement – Custom'” (FND_INIT_SQL) at each level. If the values are respectively ‘Y’ and/or contains sql statement for these profile options then log and/or trace are enable for that level (which could be at site, user, … level):

set pagesize 200 linesize 200
col NAME for a25
col LEV for a6
col CONTEXT for a25
col VALUE for a50
col USER_PROFILE_OPTION_NAME for a37
select po.profile_option_name “NAME”,
po.USER_PROFILE_OPTION_NAME,
decode(to_char(pov.level_id),
‘10001’, ‘SITE’,
‘10002’, ‘APP’,
‘10003’, ‘RESP’,
‘10005’, ‘SERVER’,
‘10006’, ‘ORG’,
‘10004’, ‘USER’, ‘???’) “LEV”,
decode(to_char(pov.level_id),
‘10001’, ”,
‘10002’, app.application_short_name,
‘10003’, rsp.responsibility_key,
‘10005’, svr.node_name,
‘10006’, org.name,
‘10004’, usr.user_name,
‘???’) “CONTEXT”,
pov.profile_option_value “VALUE”
from FND_PROFILE_OPTIONS_VL po,
FND_PROFILE_OPTION_VALUES pov,
fnd_user usr,
fnd_application app,
fnd_responsibility rsp,
fnd_nodes svr,
hr_operating_units org
where (po.profile_option_name like ‘%AFLOG_ENABLED%’ or po.profile_option_name like
‘%FND_INIT_SQL%’)
and pov.application_id = po.application_id
and pov.profile_option_id = po.profile_option_id
and usr.user_id (+) = pov.level_value
and rsp.application_id (+) = pov.level_value_application_id
and rsp.responsibility_id (+) = pov.level_value
and app.application_id (+) = pov.level_value
and svr.node_id (+) = pov.level_value
and org.organization_id (+) = pov.level_value
order by “NAME”, pov.level_id, “VALUE”;

2. This will display all profile options with values and levels where the word TRACE, LOG, or DEBUG is found in the PROFILE_OPTION_NAME:
set pagesize 200
col NAME for a25
col LEV for a6
col CONTEXT for a25
col VALUE for a50
col USER_PROFILE_OPTION_NAME for a37
select po.profile_option_name “NAME”,
po.USER_PROFILE_OPTION_NAME,
decode(to_char(pov.level_id),
‘10001’, ‘SITE’,
‘10002’, ‘APP’,
‘10003’, ‘RESP’,
‘10005’, ‘SERVER’,
‘10006’, ‘ORG’,
‘10004’, ‘USER’, ‘???’) “LEV”,
decode(to_char(pov.level_id),
‘10001’, ”,
‘10002’, app.application_short_name,
‘10003’, rsp.responsibility_key,
‘10005’, svr.node_name,
‘10006’, org.name,
‘10004’, usr.user_name,
‘???’) “CONTEXT”,
pov.profile_option_value “VALUE”
from FND_PROFILE_OPTIONS_VL po,
FND_PROFILE_OPTION_VALUES pov,
fnd_user usr,
fnd_application app,
fnd_responsibility rsp,
fnd_nodes svr,
hr_operating_units org
where (po.PROFILE_OPTION_NAME like ‘%TRACE%’ or po.PROFILE_OPTION_NAME like ‘%DEBUG%’ or po.PROFILE_OPTION_NAME like ‘%LOG%’)
and pov.application_id = po.application_id
and pov.profile_option_id = po.profile_option_id
and usr.user_id (+) = pov.level_value
and rsp.application_id (+) = pov.level_value_application_id
and rsp.responsibility_id (+) = pov.level_value
and app.application_id (+) = pov.level_value
and svr.node_id (+) = pov.level_value
and org.organization_id (+) = pov.level_value
order by “NAME”, pov.level_id, “VALUE”;

Advertisements

Oracle Apps Purge Log/Out Commands

Following command will help you in regular purging of log and out files in Oracle EBS R12

1. Report cache logs: Retention period 5days
/usr/bin/find $LOG_HOME/ora/10.1.2/reports/cache/ -mtime +5 -exec rm  {} \;

2. Apache logs: Retention period 7days
/usr/bin/find $LOG_HOME/ora/10.1.3/Apache/ -mtime +7 -exec rm  {} \;

3. Concurrent manager log files : Retention period 30days
/usr/bin/find $LOG_HOME/appl/conc/log/ -mtime +30 -exec rm  {} \;

4. Concurrent manager out files : Retention period 30days
/usr/bin/find $LOG_HOME/appl/conc/out/ -mtime +30 -exec rm  {} \;

5. Appltmp logs: Retention period 30days
/usr/bin/find $APPLTMP/ -mtime +30 -exec rm  {} \;

6. Opmn logs: Retention period 7days
/usr/bin/find $LOG_HOME/ora/10.1.3/opmn/ -mtime +7 -exec rm  {} \;

 

You can also run the below concurrent request from Sysadmin responsibility:

Purge Concurrent Request and/or Manager Data Program