Re: Getting Oracle to tell me why it's unhappy

In <3AF7416D.B9DE83A8_at_more.net> Ricky Sanchez <rsanchez_at_more.net> writes:

>One minor additional point: this technique will only produce a trace file on
>the error event itself. It will not produce a voluminous spew of text for
>either other sql statements or other sessions. An obvious approach would be to
>use the sql trace trace facility, but then you have mountains of trace files
>and significant overhead until the actual offending event is encountered. This
>error trap technique is much simpler and can be done in a production
>environment.

	Tes, that's important on this one. While it's not the "produvtion"
	instance, it's a full blown simualtion with _lot's_ of data going inot
	it.

	Is there anyway to turn on this trap _without_ shuting the DB down?

	Thanks, again.