Re: Oracle 9.2.0.5 "10046" Tracing Causes Server Crash on Windows 2000?
- From: Tanel Põder <tanel.poder.003@xxxxxxx>
- To: <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 3 Aug 2004 17:46:28 +0300
It seems that, you are using parallel query and cursor_sharing=force|similar
here, it might be that the problem occurs when all of these features
"collide". Do you need your query to run in parallel? (parallel option
triggers lots of bugs, including data/query result corruption ones, in my
experience).
Tanel.
----- Original Message -----
From: "Freeman, Donald" <dofreeman@xxxxxxxxxxx>
To: "Oracle-L (E-mail)" <oracle-l@xxxxxxxxxxxxx>
Sent: Tuesday, August 03, 2004 5:26 PM
Subject: Oracle 9.2.0.5 "10046" Tracing Causes Server Crash on Windows 2000?
> I am finally getting to practice some of the tracing functionality that =
> is discussed here and ran into something I haven't seen dicussed here. =
> We had a complaint about a query that performs inconsistently and I =
> enabled my session trigger on user logon to capture it. The server =
> failed at a point shown below. The first entry is the alert log entry. =
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
Other related posts:
