10053 trace

[vnktummala]

Hi,

I have a 250 lines query with lot of joins developed by our BO team for one of the BO reports. I tried to generate explain plan for that query but it just simply hanging there.

So, I stopped that and started generating explain plan with 10053 trace. It is running since last one and half hour and the trace file is now 50MB.

As I am using 10053 first time, I have no idea how much time it will take (but I am sure it should not be more than one and half hour). Any comments will be much appreciated.

Thanks,

[PAVB]

10053 trace It will take as much time as the query takes to run.

[vnktummala]

Thanks Paul. I killed the session after two hours. Trace file is so huge 75MB so it is impossible for me to understand it.

My first trial with 10053 was not successful ...

Thanks,

[vnktummala]

I am in a strange situation where in I am not able to generate explain plan for one query.

This is the same query that I tried to do 10053. 10053 is generating gigs of trace file and never ending. 10046 trace file size is increasing but when I do tkprof on the trace file i can't see any thing there apart from system queries.

The same query is fine in UAT. Indexes / constraints are same in both the environments. Only difference is production had few million rows more than UAT.

If any one want to know more information to help me out please let me know. I am happy to provide.

Thanks,

[vnktummala]

adding to my above post ...

when I try to generate explain plan or try to execute the query that particular session is using 100% CPU.

Thanks,

[PAVB]

...i can't see any thing there apart from system queries.

Use tkprof sys=no option

[vnktummala]

Thanks Paul.

Yes, I have used that.

Finally, developers changed the query logic and it is good now...

Thanks,