| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> Re: 10046 - Unable to trace JDBC thin client?
None taken, sometimes it is the obvious. In this case I have cleared out
the entire directory prior to my tests. In addition, I have successfully
executed the same process with a SQL*Plus session.
I will be researching the oradebug and set_ev methods to see if I receive
similar results. Thanks for all the input.
"Daniel Fink" <Daniel.Fink_at_Sun.COM>
Sent by: oracle-l-bounce_at_freelists.org
08/17/2004 01:28 PM
Please respond to oracle-l
To: oracle-l_at_freelists.org
cc:
Subject: Re: 10046 - Unable to trace JDBC thin client?
Tracy,
I don't mean to insult you (or anyone else on the list), but are you
*positive* you are looking in the right directory with the
right file name? I've seen databases where the *_dump_dest locations are
not where I would expect them to be
($ORACLE_BASE/admin/$ORACLE_SID). This is especially confusing when the
expected directory structure is there, has some old files,
but the instance is pointing to a new location.
Daniel Fink
American Express made the following
annotations on 08/17/2004 12:13:50 PM
"This message and any attachments are solely for the intended recipient and may contain confidential or privileged information. If you are not the intended recipient, any disclosure, copying, use, or distribution of the information included in this message and any attachments is prohibited. If you have received this communication in error, please notify us by reply e-mail and immediately and permanently delete this message and any attachments. Thank you."
 |
 |