Re: Helping me find the quilty SQL, which wreck my package all the time

Joe Bayer wrote:

> The problem is, sql like 'ALTER TABLE bla truncate partition', 'ALTER table
> split partition ', etc ,etc
> will not be catched into v$open_cursor, if we take a snapshot of v$sql,
> there will be too many potential quilty ones, and it will be difficult for
> me to tell which one is the real ONE. (the package dependency shows 1200
> items).
>
> Thanks for your help.

Capture the suspect SQL ... all of it ... from v$open_cursor then move it all back to a test environment where you can use a small stored procedure to incrementally loop through each one and 'exit' the loop when it breaks.

But one should probably ask why anyone is performing any DDL in a production environment. Once a year with an upgrade I can understand. But this sounds like there is a very bad design not too far below the surface.

-- 
Daniel Morgan
http://www.outreach.washington.edu/ext/certificates/oad/oad_crs.asp
http://www.outreach.washington.edu/ext/certificates/aoa/aoa_crs.asp
damorgan_at_x.washington.edu
(replace 'x' with a 'u' to reply)