Dbugging accross dynamic Sql
- Thread starter sakalk
- Start date
I'm not aware of any issues with dbms_sql. Can you send me the PL/SQL Code of this program unit and let me know where the problem occurs?
------------------
Marco Kalter
Allround Automations
------------------
Marco Kalter
Allround Automations
Thanks for the quick response. Actually I am not sure if this is related to dbms_sql, i was just guessing. I cannot send you the code as it is not that simple. The process goes through 100s of packages during a save process. My problem was that if I use a dbms_output.Put_line then it shows the process actually flows at this particular place , but if i put a breakpoint and debug , it completes the process without stopping there! Can you think of any other reasons. Thank you very much.
Maybe you are running into Oracle Server bug# 2276832. For if-then-else constructs it sometimes reports incorrect execution line numbers. The actual execution is okay though, but it is confusing.
Does the issue occur within an if-then-else consruct?
------------------
Marco Kalter
Allround Automations
Does the issue occur within an if-then-else consruct?
------------------
Marco Kalter
Allround Automations
Do you mean to say the breakpoints are taken by execution line number? And if I use If-Then-Else, the line number I clicked and line number produced by oracle during execution is different so that the breakpoint actualy get missed? Does this happen only within one if-then-else block? In my case from ste start procedure to breakpoint it goes through so many if-then-eleses!
Thanks
Sanjeewa
Thanks
Sanjeewa
The problem is not related to breakpoints, but to the execution line number that Oracle reports when execution has paused. This reported line number can be off due to the bug mentioned above.
------------------
Marco Kalter
Allround Automations
------------------
Marco Kalter
Allround Automations
