Question on "Execute Script" (F5)
Karen Short <[email protected]>
| Newsgroups | gmane.comp.db.oracle.toad.free |
|---|---|
| Message-ID | <4627147.23561318006765890.JavaMail.SYSTEM@alvqcfw02> |
Message from: Short I am running Toad for Orace 9.1.0.62. A colleague wrote a procedure (proc_init_ba) that was returning different results for different individuals who ran the procedure. After spending quite some time thinking the issue was related to DB security and user accounts, we determined that: If the command "execute proc_init_ba" was highlighted in an editor window and then run via the F5 key (execute script), it did not work. According to the DBA, a second session was being spawned and any queries were directed at the wrong session. If the command "execute proc_init_ba" was highlighted in an editor window and then run via the F9 key (execute statement), it worked. If the procedure proc_init_ba was highlighted in the procedure tab in the schema browswer window and run via the lightening bolt (execute procedure), it worked. If the command "execute proc_init_ba" was highlighted in an editor window and the "execute statement" icon in the upper left corner of the gui was clicked, it worked. If the procedure was run via F9 (run statement) or F5 (run script) in SQL Developer, it worked. Any thoughts on why the procedure behaves differently in Toad when run as a script?? Thanks in advance for any help. _______________________________________ Historical Messages Author: Karen Short Date: Fri Oct 07 09:58:55 PDT 2011 I am running Toad for Orace 9.1.0.62. A colleague wrote a procedure (proc_init_ba) that was returning different results for different individuals who ran the procedure. After spending quite some time thinking the issue was related to DB security and user accounts, we determined that: If the command "execute proc_init_ba" was highlighted in an editor window and then run via the F5 key (execute script), it did not work. According to the DBA, a second session was being spawned and any queries were directed at the wrong session. If the command "execute proc_init_ba" was highlighted in an editor window and then run via the F9 key (execute statement), it worked. If the procedure proc_init_ba was highlighted in the procedure tab in the schema browswer window and run via the lightening bolt (execute procedure), it worked. If the command "execute proc_init_ba" was highlighted in an editor window and the "execute statement" icon in the upper left corner of the gui was clicked, it worked. If the procedure was run via F9 (run statement) or F5 (run script) in SQL Developer, it worked. Any thoughts on why the procedure behaves differently in Toad when run as a script?? Thanks in advance for any help. __ _______________________________________