Oracle E-Business Suite(R12.2) Troubleshooting

原文地址：https://s3-us-west-2.amazonaws.com/k21academy/Oracle+AppsDBA+Workshop/Training+Material+(ppt)/Day+13/M13_Troubleshooting_Scalability.pdf
Agenda
 ADOP Troubleshooting
 Logon Issues Troubleshooting
 Scalability

Lesson-1 ADOP Troubleshooting
ADOP Validate
• Part of ADOP utility,called by executing “adop -validate”
• Located in $AD_TOP/bin
• Only available above AD-TXK 7
• Does a quick check on Online Patching Cycle and alerts of errors if any
• Usually one of the first step requested by Oracle Support.

EBS_LOGON Trigger
• Critical LOGON trigger owned by SYSTEM schema
• Should be explicitly disabled during autoconfig run on patch Filesystem and
should be immediately enabled
• Otherwise status should always be ENABLED
• Suggest a cron job is placed to check its status periodically
select status from dba_trigers where owner=’SYSTEM’ and trigger_name=’EBS_LOGON’;

ADOPSCANLOG
• Key ADOP troubleshooting utility
• Located in $AD_TOP/bin
• Excellent utility to scan all your Online Patching logs with a single command
• Ability to selective reduce the amount of data that is displayed on screen
• Ability to scan even for past ADOP Sessions
adopscanlog

ADOPREPORTS.SH
• Key ADOP Reporting Utility
• Located in $AD_TOP/bin
• Provides complete report on objects in each edition
• Provides space usage in key tablespaces
• Provides status of critical AD_ZD Objects
sh adopreports.sh

AD_ZD Objects
• All Objects starting with AD_ZD should be VALID
• If any becomes invalids then Online Patching cycle will fail
• Monitor and take corrective action immediately
• Suggest cron jobs are placed to verify status
• ADOPREPORTS.SH script can also be used to check the key object status

AD_ZD_LOGS Table
• Key ADOP table which contains all the log information
• Owned by APPLSYS Schema
• First place to look for detailed Online Patching Cycle messages
• Formatted concise output available through adopmon utility
select message_text from ad_zd_logs where LOG_SEQUENCE > 622816;

ADOPMON
• Key ADOP Monitoring Utility, only available above AD-TXK 7
• Located in $AD_TOP/bin
• Formats the output of AD_ZD_LOGS table in a user friendly fashion
• Session keeps continuing to display new log information until closed.
adopmon

Lesson- 2 Logon Issues Troubleshooting
Intermittent Logon Failures
• Randomly users get “Page cannot be Displayed” or “Internal Server Error” while trying to login
• Once login page is rendered, no failures
• Possible Cause
– Few OACORE Managed Servers have failed, check Server log and restart failed OACORE Services
– If not solved, do complete Application Services Bounce

Logon Page Not Rendering
• No one is able to login to applications – Full Outage
• Possible Causes
– FMW Apache may have gone down – Check and restart Apache
– OACORE may have gone down – Restart OACORE Managed Servers
– Tablespaces might have got filled up – Check Database Alert log and take Corrective action
– Check Profile “Initilization – SQL Statement Custom” for any junk values
– ORA-00600 or ORA-07445 in alert log – Raise SR with Oracle and fix the error

General Troubleshooting
• Try the below URLs one after the other, one of it should tell you what the issue is
– http://<logon_url>/OA_HTML/ServletPing – Will error if OACORE is down
– http://<logon_url>/OA_HTML/OA.jsp?OAFunc=OAHOMEPAGE – Will error if OACORE has errors
– http://<logon_url>/OA_HTML/jsp/fnd/aoljtest.jsp – Will error if Database has connectivity issues
– http://<logon_url>/OA_MEDIA/FNDLOGOL.gif – Will error if you have issues with Media objects
– http://<logon_url>/forms/frmservlet – Will error if you have issues with Forms
– http://<logon_url>/OA_HTML/fndvald.jsp?username=sysadmin&password=<password> – Will give error stack if you
have a profile related issues.

Lesson-3 Scalability
Add Managed Servers
Add Managed Server
perl $AD_TOP/patch/115/bin/adProvisionEBS.pl \
ebs-create-managedserver -contextfile=$CONTEXT_FILE \
-managedsrvname=oacore_server11 -servicetype=oacore \
-managedsrvport=7203 -logfile=$APPLRGF/TXK/addMS_oacore_server11.log <<EOF
<apps password>
<wls password>
EOF

Change Managed Server Property
perl $AD_TOP/patch/115/bin/adProvisionEBS.pl ebs-set-managedsrvproperty -contextfile=$CONTEXT_FILE -managedsrvname=oacore_server11 –
serverstartargs=”<complete Args>” <<EOF
<wls password>
EOF

Add Managed Server configuration to Apache
oacore
perl $FND_TOP/patch/115/bin/txkSetAppsConf.pl -contextfile=$CONTEXT_FILE \
-configoption=addMS -oacore=<host>:<port1>,<host>:<port2>

forms
perl $FND_TOP/patch/115/bin/txkSetAppsConf.pl -contextfile=$CONTEXT_FILE \
-configoption=addMS -forms=<host>:<port1>,<host>:<port2>

Delete Managed Servers
Delete Managed Server
perl $AD_TOP/patch/115/bin/adProvisionEBS.pl \
ebs-delete-managedserver -contextfile=$CONTEXT_FILE \
-managedsrvname=oacore_server11 -servicetype=oacore \
-logfile=$APPLRGF/TXK/removeMS_oacore_server11.log <<EOF
<apps password>
<wls password>
EOF

Remove Managed Server configuration from Apache
oacore
perl $FND_TOP/patch/115/bin/txkSetAppsConf.pl -contextfile=$CONTEXT_FILE \
-configoption=removeMS -oacore=<host>:<port1>,<host>:<port2>

forms
perl $FND_TOP/patch/115/bin/txkSetAppsConf.pl -contextfile=$CONTEXT_FILE \
-configoption=removeMS -forms=<host>:<port1>,<host>:<port2>

Start/Stop Managed Servers
Through Admin Console
 Admin Server should be UP
 Node Manager should be UP on all target nodes
 Parallel Startup across Nodes
Through UNIX Prompt
Start Managed Server
sh $ADMIN_SCRIPTS_HOME/admanagedsrvctl.sh start oacore_server11 <<EOF
<wls password>
EOF

Stop Managed Server
sh $ADMIN_SCRIPTS_HOME/admanagedsrvctl.sh stop oacore_server11 <<EOF
<wls password>
EOF

Find Us
http://facebook.com/k21technologies
http://twitter.com/k21technologies
https://www.linkedin.com/company/k21technologies
https://www.youtube.com/user/k21technologies