Sunday, 26 April 2015

Monday, 6 April 2015

LOGS location oracle Ebs


Log file location for Oracle E-Business Suite R12

Below list of  log file locations could be helpful for your issue:

 Apache, OC4J and OPMN:
$LOG_HOME/ora/10.1.3/Apache
$LOG_HOME/ora/10.1.3/j2ee
$LOG_HOME/ora/10.1.3/opmn

 Startup/Shutdown Log files:
$INST_TOP/logs/appl/admin/log

 Patch log:
$APPL_TOP/admin/$SID/log/

 Autoconfig log file:

Apps:
$INST_TOP/apps/$CONTEXT_NAME/admin/log/$MMDDHHMM/adconfig.log

Db:
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/<MMDDHHMM>/adconfig.log
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/<MMDDHHMM>/NetServiceHandler.log

 Concurrent log:
$INST_TOP/apps/$CONTEXT_NAME/logs/appl/conc/log

 Clone log:
Preclone log files in source instance

Apps:
$INST_TOP/apps/$CONTEXT_NAME/admin/log/ (StageAppsTier_MMDDHHMM.log)

Db:
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/(StageDBTier_MMDDHHMM.log)
Clone log files in target instance

Apps :
$INST_TOP/apps/$CONTEXT_NAME/admin/log/ApplyAppsTier_<time>.log
Db:
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/ApplyDBTier_<time>.log

 Alert Log File:
$ORACLE_HOME/admin/$CONTEXT_NAME/bdump/alert_$SID.log

Reference:
How to find location of Install, Autoconfig, Patching , Clone and other logs in R12 [ID 804603.1]
Oracle Application Server Diagnostic Tools and Log Files in Applications Release 12 [ID 454178.1]
Oracle Applications System Administrator’s Guide

Thursday, 2 April 2015

PMON vs SMON



SMON -> performs recovery, when instance fails and,
PMON -> performs recovery, when user process fails.

PMON

• Rolls back the user’s current transaction
• Releases all the locks that are held on tables or rows
• Frees other resources used by the users
• Restarts the dead dispatcher


SMON

• Rolling forward changes that are made in the online redo log files but not in the data files. Since all the committed transactions are written to the online redo log files, these are successfully recovered as result of rolling forward changes from the online redo log files to the data files.
• Opening the database. After the database is opened, users can log on and access any data that is not locked by un-recovered transaction.
• Rolling back all the uncommitted transactions.
 

Performance tuning Concurrent Managers

Factors which will help us in improving performance

Sleep Seconds

Increase the cache size (number of requests cached) to at least twice the number of target processes.

specialized concurrent managers to dedicate certain process

For maximum throughput consider reducing the sleep time of the Conflict Resolution Manager


purge the old concurrent logs ( Purge Concurrent Request FNDCPPUR) $APPLCSF/$APPLLOG

Set profile option 'Concurrent: PCP Instance Check' to 'OFF' if instance-sensitive failover is not required

Tuning Output Post Processor (OPP) NOTE:1399454.1 Tuning Output Post Processor (OPP) to Improve Performance