也可以参照http://zhyuh.itpub.net/post/334/485841
两种方法都是Oracle supporter在解答TAR中提供的
[@more@] 1. Enable trace for a specific user:
- Login as System Administrator responsibility
- Move to Profile/System
- Check off the USER box - and enter your username that you are using when getting the error
- Search on the following profile option - 'Initialization SQL Statement - Custom'
2. Please set this at the user level with the following string:
BEGIN FND_CTL.FND_SESS_CTL('','', '', 'TRUE','','ALTER SESSION SET TRACEFILE_IDENTIFIER='||''''||'4764802.992' ||''''||' EVENTS ='||''''||' 10046 TRACE NAME CONTEXT FOREVER, LEVEL 12 '||''''); END;
This must be one complete line of text - so may be best to copy the string into notepad prior to putting it into the profile.
3. Once the profile is set, please change responsibilities and directly go and reproduce the problem.
To find the trace file at 'user_dump_dest':
- Please move to this directory and search for the file having 4764802.992 in the filename
- This is the trace file created - please tkprof and upload BOTH the raw and tkprof trace file to metalink.
4. Ensure that the profile option is unset before exiting the Application.
来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/207/viewspace-1023168/,如需转载,请注明出处,否则将追究法律责任。
转载于:http://blog.itpub.net/207/viewspace-1023168/