Troubleshooting 11i issues Adam Janbolat

380 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
380
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Troubleshooting 11i issues Adam Janbolat

  1. 1. Troubleshooting 11i issues Adam Janbolat www.dba4aday.com [email_address]
  2. 2. DBA JOKE <ul><ul><li>No one really knows what the Database Administrator does, and no one is smart enough to know if the DBA is doing it or not. But every shop must have one DBA, because no place can afford two of them. </li></ul></ul>
  3. 3. Different issues with each user <ul><li>A user needs a trace file to upload to support </li></ul><ul><li>A user is waiting on a payroll process that should not take more than 10 min but it has been running for three hours </li></ul><ul><li>A user heard someone talk about locking issues and now they have locking issues! </li></ul><ul><li>A user is getting error ORA-1652: unable to extend temp segment when running his/her code from sqlplus </li></ul><ul><li>Your manager says the application is running slow; can you improve performance </li></ul><ul><li>A developer wants you to tune her code because it is a dba thing to do </li></ul>
  4. 4. Overview <ul><li>Tracing application forms </li></ul><ul><li>Tracing database processes </li></ul><ul><li>Tracing concurrent requests </li></ul><ul><li>Locking issues </li></ul><ul><li>Temp space issues </li></ul>
  5. 5. Diagnostic Tools <ul><li>Enterprise Manager </li></ul><ul><li>unix/sql scripts </li></ul>
  6. 6. Tracing Forms <ul><li>Verify diagnostics is turned on in the Help menu. </li></ul><ul><li>You can turn it on for any user by setting this profile option to No: </li></ul><ul><li>Hide Diagnostics menu entry </li></ul>MIS: DEMO
  7. 7. Turn diagnostics on for user BROWN
  8. 8. Set the profile option to No
  9. 9. Tracing forms
  10. 10. Tracing forms
  11. 11. Tracing forms <ul><li>The form will produce a trace file in the udump directory. </li></ul><ul><li>The trace file will be ora_173xxx.trc </li></ul><ul><li>Use tkprof on the trace file: </li></ul><ul><li>tkprof ora_173.trc ora_173.out explain=apps/password sort=prsela </li></ul><ul><li>Which users have trace enabled: </li></ul>MIS: DEMO
  12. 12. Who has diagnostics privs <ul><li>Run this query to find who has diagnostics privs: </li></ul><ul><ul><ul><li>select a.user_name </li></ul></ul></ul><ul><ul><ul><li>from fnd_user a, </li></ul></ul></ul><ul><ul><ul><li>fnd_profile_option_values b </li></ul></ul></ul><ul><ul><ul><li>where a.user_id=b.level_value and </li></ul></ul></ul><ul><ul><ul><li>b.profile_option_id=3214 and </li></ul></ul></ul><ul><ul><ul><li>b.profile_option_value='N' and </li></ul></ul></ul><ul><ul><ul><li>b.level_id= 10004 </li></ul></ul></ul>
  13. 13. Tracing database processes <ul><li>Identify the process </li></ul><ul><li>Trace the process </li></ul><ul><li>Trace file will end up in the udump directory </li></ul><ul><li>Use tkprof on the trace file </li></ul>
  14. 14. Tracing concurrent request <ul><li>Find out the request_id </li></ul><ul><li>Find out if the process has child processes </li></ul><ul><li>Use this query to find which process it is: </li></ul><ul><li>select oracle_process_id from fnd_concurrent_requests where request_id=941206 </li></ul><ul><li>Oracle_process_id corresponds to the spid in OEM. </li></ul>

×