|
-
 Originally Posted by vnktummala
... I don't have 10046 trace file.
This is a job for oradebug -one of the many Oracle unsong super heroes.
Please try this...
0- Initiate offending process.
1- Figure out the SPID of the offending process.
2- Log into the system as sysdba
3- Start oradebug...
oradebug setospid SPID-from_step_1;
4- Enable 10046...
oradebug event 10046 trace name context forever, level 12
5- Wait... wait... keep waiting... then wait a little more 
6- Disable 10046 tracing...
oradebug event 10046 trace name context off
7- tkprof trace file and bingo! you got your 10046 trace on remote session.
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|
Reply With Quote