Oracle R12/12i log file (Patch, Clone, Startup/Shutdown):
=======================================
Log files are useful in troubleshooting
issues in Oracle Applications. Here is the list of Log file location in Oracle
Applications for Startup/Shutdown, Cloning, Patching, DB & Apps Listener
and various components in Apps R12/12i:
A.
Startup/Shutdown Log files for Application Tier in R12
Instance Top is new TOP added in R12
Startup/Shutdown error message text files
like adapcctl.txt, adcmctl.txt…
$INST_TOP/apps/$CONTEXT_NAME/logs/appl/admin/log
–Startup/Shutdown error message related to
tech stack (10.1.2, 10.1.3 forms/reports/web)
$INST_TOP/apps/$CONTEXT_NAME/logs/ora/ (10.1.2 & 10.1.3)
$INST_TOP/apps/$CONTEXT_NAME/logs/ora/10.1.3/Apache/error_log[timestamp]
$INST_TOP/apps/$CONTEXT_NAME/logs/ora/10.1.3/opmn/
(OC4J~…, oa*, opmn.log)$INST_TOP/apps/$CONTEXT_NAME/logs/ora/10.1.2/network/
(listener log)
$INST_TOP/apps/$CONTEXT_NAME/logs/appl/conc/log (CM log files)
B.
Log files related to cloning in R12
=================================
Preclone log files in source instance
i) Database Tier – /$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/(StageDBTier_MMDDHHMM.log)
ii) Application Tier –
$INST_TOP/apps/$CONTEXT_NAME/admin/log/ (StageAppsTier_MMDDHHMM.log)
Clone log files in target instance
Database Tier -
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/ApplyDBTier_<time>.log
Apps Tier
– $INST_TOP/apps/$CONTEXT_NAME/admin/log/ApplyAppsTier_<time>.log
—–
If your clone on DB Tier fails while
running txkConfigDBOcm.pl (Check
metalink note – 415020.1)
During clone step on DB Tier it prompts for
“Target System base directory for source homes” and during this you have to
give like /base_install_dirlike ../../r12 and not oracle home like
../../r12/db/tech_st_10.2.0
C.
Patching related log files in R12:
==================================
i) Application Tier adpatch log -
$APPL_TOP/admin/$SID/log/
ii) Developer (Developer/Forms &
Reports 10.1.2) Patch - $ORACLE_HOME/.patch_storage
iii) Web Server (Apache) patch -
$IAS_ORACLE_HOME/.patch_storage
iv) Database Tier opatch log –
$ORACLE_HOME/.patch_storage
D.
Autoconfig related log files in R12:
================================
i) Database Tier Autoconfiglog :
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/MMDDHHMM/adconfig.log
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/MMDDHHMM/NetServiceHandler.log
ii) Application Tier Autoconfig log -
$INST_TOP/apps/$CONTEXT_NAME/admin/log/$MMDDHHMM/adconfig.log
Autoconfig context file location in R12 -
$INST_TOP/apps/$CONTEXT_NAME/appl/admin/$CONTEXT_NAME.xml
E.
R12 Installation Logs:
====================
Database Tier Installation
RDBMS $ORACLE_HOME/appsutil/log/$CONTEXT_NAME/<MMDDHHMM>.logRDBMS
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/ApplyDBTechStack_<MMDDHHMM>.logRDBMS
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/ohclone.logRDBMS
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/make_<MMDDHHMM>.logRDBMS
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/installdbf.logRDBMS
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/adcrdb_<SID>.log RDBMS
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/ApplyDatabase_<MMDDHHMM>.logRDBMS
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/<MMDDHHMM>/adconfig.log RDBMS
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/<MMDDHHMM>/NetServiceHandler.log
Application
Tier Installation
$INST_TOP/logs/<MMDDHHMM>.log
$APPL_TOP/admin/$CONTEXT_NAME/log/ApplyAppsTechStack.log
$INST_TOP/logs/ora/10.1.2/install/make_<MMDDHHMM>.log
$INST_TOP/logs/ora/10.1.3/install/make_<MMDDHHMM>.log
$INST_TOP/admin/log/ApplyAppsTechStack.log
$INST_TOP/admin/log/ohclone.log
$APPL_TOP/admin/$CONTEXT_NAME/log/installAppl.log
$APPL_TOP/admin/$CONTEXT_NAME/log/ApplyAppltop_<MMDDHHMM>.log
$APPL_TOP/admin/$CONTEXT_NAME/log/<MMDDHHMM>/adconfig.log
$APPL_TOP/admin/$CONTEXT_NAME/log/<MMDDHHMM>/NetServiceHandler.log
Inventory
Registration:
$Global
Inventory/logs/cloneActions<timestamp>.log
$Global
Inventory/logs/oraInstall<timestamp>.log
$Global Inventory/logs/silentInstall<timestamp>.log
F.
Other log files in R12
1) Database Tier
1.1) Relink Log files :
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME
/MMDDHHMM/ make_$MMDDHHMM.log
1.2) Alert Log Files :
$ORACLE_HOME/admin/$CONTEXT_NAME/bdump/alert_$SID.log
1.3)
Network Logs :
$ORACLE_HOME/network/admin/$SID.log
1.4)
OUI Logs :
OUI Inventory Logs :
$ORACLE_HOME/admin/oui/$CONTEXT_NAME/oraInventory/logs
2) Application Tier
$ORACLE_HOME/j2ee/DevSuite/log
$ORACLE_HOME/opmn/logs
$ORACLE_HOME/network/logs
Tech Stack Patch 10.1.3 (Web/HTTP Server)
$IAS_ORACLE_HOME/j2ee/forms/logs
$IAS_ORACLE_HOME/j2ee/oafm/logs
$IAS_ORACLE_HOME/j2ee/oacore/logs
$IAS_ORACLE_HOME/opmn/logs
$IAS_ORACLE_HOME/network/log
$INST_TOP/logs/ora/10.1.2
$INST_TOP/logs/ora/10.1.3
$INST_TOP/logs/appl/conc/log
$INST_TOP/logs/appl/admin/log
Oracle E-Business Suite uses
three OC4J (oacore, oafm & forms)
for Java Applications including Forms and HTTP Server for
static HTML content.
All these four components
are managed (including startup/shutdown) by OPMN (OracleProcess Manager
& Notification) .
A. Script to start/stop OPMN in R12 - $ADMIN_SCRIPTS_HOME/ adopmnctl.sh
B. Script to start/stop HTTP Server in R12 - $ADMIN_SCRIPTS_HOME/ adapcctl.sh
C. Script to start/stop oacore OC4J in R12 - $ADMIN_SCRIPTS_HOME/adoacorectl.sh
D. Script to start/stop oafm OC4J in R12 - $ADMIN_SCRIPTS_HOME/ adoafmctl.sh
E. Script to start/stop forms OC4J in R12 - $ADMIN_SCRIPTS_HOME/ adformsctl.sh
.
Processes in Instance:
VISR12_focusthread.focusthread.com
———————————+——————–+———+———
ias-component | process-type | pid | status
———————————+——————–+———+———
OC4JGroup:default_group | OC4J:oafm | 1032 | Alive
OC4JGroup:default_group | OC4J:forms | 933 | Alive
OC4JGroup:default_group | OC4J:oacore | 808 | Alive
HTTP_Server | HTTP_Server | 748 | Alive
———————————+——————–+———+———
ias-component | process-type | pid | status
———————————+——————–+———+———
OC4JGroup:default_group | OC4J:oafm | 1032 | Alive
OC4JGroup:default_group | OC4J:forms | 933 | Alive
OC4JGroup:default_group | OC4J:oacore | 808 | Alive
HTTP_Server | HTTP_Server | 748 | Alive
.
How to
troubleshoot status code 204 Issue for OC4J ?
1. First check startup
log at $LOG_HOME/appl/admin/log/ adoacorectl.txt,adoafmctl.txt, adoaformsctl.txt
2. Next check log at $LOG_HOME/ ora/ 10.1.3/ opmn/ opmn.log
If you see error like
—-
09/07/22 18:28:10 [libopmnoc4j] Port information in the ONS notification is incorrect for proc: 1154637034. Some of the reasons for the failure are:
1. ajp, rmi and jms ports could not be bound by the process.
2. If a port value for a certain port ID is handed by OPMN to the OC4J process and this value is not returned back in the ONS notifications. For example, this can happen for certain bad JGroups related configurations.
09/07/22 18:28:10 [libopmnoc4j] Process Start Error: default_group~oafm~default_group~1 (1154637034:26689)09/07/22
18:28:11 [pm-process] Stopping Process: default_group~oafm~default_group~1 (1154637034:26689)09/07/22 18:28:11
[libopmnoc4j] Process Stop Error: default_group~oafm~default_group~1 (1154637034:26689)09/07/22 18:28:11 [libopmnoc4j]
Failed to construct stop command for proc: 115463703409/07/22 18:28:11 [libopmnoc4j] Forcefully Terminating Process:
default_group~oafm~default_group~1 (1154637034:26689)09/07/22 18:28:13 [pm-requests] Request d Completed. Command: /start?process-type=oafm
.
2. Next check log at $LOG_HOME/ ora/ 10.1.3/ opmn/ opmn.log
If you see error like
—-
09/07/22 18:28:10 [libopmnoc4j] Port information in the ONS notification is incorrect for proc: 1154637034. Some of the reasons for the failure are:
1. ajp, rmi and jms ports could not be bound by the process.
2. If a port value for a certain port ID is handed by OPMN to the OC4J process and this value is not returned back in the ONS notifications. For example, this can happen for certain bad JGroups related configurations.
09/07/22 18:28:10 [libopmnoc4j] Process Start Error: default_group~oafm~default_group~1 (1154637034:26689)09/07/22
18:28:11 [pm-process] Stopping Process: default_group~oafm~default_group~1 (1154637034:26689)09/07/22 18:28:11
[libopmnoc4j] Process Stop Error: default_group~oafm~default_group~1 (1154637034:26689)09/07/22 18:28:11 [libopmnoc4j]
Failed to construct stop command for proc: 115463703409/07/22 18:28:11 [libopmnoc4j] Forcefully Terminating Process:
default_group~oafm~default_group~1 (1154637034:26689)09/07/22 18:28:13 [pm-requests] Request d Completed. Command: /start?process-type=oafm
.
Fix
Clear directory under persistence from below directory and restart all three OC4J
$ORA_CONFIG_HOME/ 10.1.3/ j2ee/ oacore/ persistence
$ORA_CONFIG_HOME/ 10.1.3/ j2ee/ oafm/ persistence
$ORA_CONFIG_HOME/ 10.1.3/ j2ee/ forms/ persistence
Clear directory under persistence from below directory and restart all three OC4J
$ORA_CONFIG_HOME/ 10.1.3/ j2ee/ oacore/ persistence
$ORA_CONFIG_HOME/ 10.1.3/ j2ee/ oafm/ persistence
$ORA_CONFIG_HOME/ 10.1.3/ j2ee/ forms/ persistence
This could be because of .lock files
and explained in Metalink Note 372412.1 OC4J Fails to
startup with “ERROR Failed to set the internal configuration of the OC4J JMS
Server”
.
.
3. If all
services are up and running and you still get “Page not found” in Apps
R12, then
Check logs in
$LOG_HOME/ora/10.1.3/opmn/oacore_default_group_1/oacorestd.err
——-
——-
09/07/22 18:44:20 Exception in static
block of jtf.cache.CacheManager. Stack trace is:
oracle. apps. jtf. base. resources. FrameworkException: IAS Cache initialization failed. The Distributed Caching System failed to initialize on port: 12357. The list of hosts in the distributed caching system is: 127.0.0.1 . The port 12357 should be free on each host running the JVMs.
at oracle. apps. jtf. cache. IASCacheProvider.init(IASCacheProvider.java:335)
at oracle. apps. jtf. cache. CacheManager.activateCache(CacheManager.java:1451)
oracle. apps. jtf. base. resources. FrameworkException: IAS Cache initialization failed. The Distributed Caching System failed to initialize on port: 12357. The list of hosts in the distributed caching system is: 127.0.0.1 . The port 12357 should be free on each host running the JVMs.
at oracle. apps. jtf. cache. IASCacheProvider.init(IASCacheProvider.java:335)
at oracle. apps. jtf. cache. CacheManager.activateCache(CacheManager.java:1451)
–
As error indicates issue is
with Java Object Cache (JOC) to knwo more about JOCclick here
To confirm that issue is because
of Java Object Cache (JOC), check log file
$LOG_HOME/appl/rgf/javacache.log
—
[2009-07-22T18:44:20.856+01:00] [ias] [NOTIFICATION] [] [cache.Lifecycle] [host: focusthread.com] [nwaddr: X.X.X.X] [tid: 11] [userId: avisr12] [ecid: X.X.X.X:39334:1248284660856:1,1] JOC is shutdown. vid=0
—
[2009-07-22T18:44:20.856+01:00] [ias] [NOTIFICATION] [] [cache.Lifecycle] [host: focusthread.com] [nwaddr: X.X.X.X] [tid: 11] [userId: avisr12] [ecid: X.X.X.X:39334:1248284660856:1,1] JOC is shutdown. vid=0
—
Fix : There are
two potential solution (or more depneding on root cause of JOC issue)
1. Check if not other service is using JOC port (JOC port is defind by parameters_java_object_cache_port in context file), run Autoconfig and test again
1. Check if not other service is using JOC port (JOC port is defind by parameters_java_object_cache_port in context file), run Autoconfig and test again
2. Disable JOC
by changing s_long_running_jvm in context file from true to falseand
run Autoconfig
.
Log File Location for OACore& JOC in R12
.
Log File Location for OACore& JOC in R12
- $LOG_HOME/ appl/ admin/ log/ adoacorectl.txt,
adoafmctl.txt, adoaformsctl.txt
- $LOG_HOME/ ora/ 10.1.3/ opmn/ opmn.log
- $LOG_HOME/ ora/ 10.1.3/ opmn/ oacore_default_group_1/
oacorestd.err
- $LOG_HOME/ appl/ rgf/ javacache.log
- $LOG_HOME/ ora/ 10.1.3/ j2ee/ oacore/
oacore_default_group_1/ application.log
No comments:
Post a Comment