PL/SQL Developer debugger won't step into code across db link












0















I'm using Allround Automations PL/SQL Developer 12.0.2.1818 64 bit to try to debug a process using multiple packages split across 3 Oracle 11g databases.



I've added debug information to all relevant packages across all 3 databases, but when I run the debugger, starting at the top-level package (i.e. the one at the beginning of the process) as soon as it reaches a package on another database, even though I click 'Step into' it just runs the code in the background and then steps over it.



Is there any way to make it step into the package so that I can continue to go through the debug line by line? This behaviour is making it impossible to debug the code.










share|improve this question



























    0















    I'm using Allround Automations PL/SQL Developer 12.0.2.1818 64 bit to try to debug a process using multiple packages split across 3 Oracle 11g databases.



    I've added debug information to all relevant packages across all 3 databases, but when I run the debugger, starting at the top-level package (i.e. the one at the beginning of the process) as soon as it reaches a package on another database, even though I click 'Step into' it just runs the code in the background and then steps over it.



    Is there any way to make it step into the package so that I can continue to go through the debug line by line? This behaviour is making it impossible to debug the code.










    share|improve this question

























      0












      0








      0








      I'm using Allround Automations PL/SQL Developer 12.0.2.1818 64 bit to try to debug a process using multiple packages split across 3 Oracle 11g databases.



      I've added debug information to all relevant packages across all 3 databases, but when I run the debugger, starting at the top-level package (i.e. the one at the beginning of the process) as soon as it reaches a package on another database, even though I click 'Step into' it just runs the code in the background and then steps over it.



      Is there any way to make it step into the package so that I can continue to go through the debug line by line? This behaviour is making it impossible to debug the code.










      share|improve this question














      I'm using Allround Automations PL/SQL Developer 12.0.2.1818 64 bit to try to debug a process using multiple packages split across 3 Oracle 11g databases.



      I've added debug information to all relevant packages across all 3 databases, but when I run the debugger, starting at the top-level package (i.e. the one at the beginning of the process) as soon as it reaches a package on another database, even though I click 'Step into' it just runs the code in the background and then steps over it.



      Is there any way to make it step into the package so that I can continue to go through the debug line by line? This behaviour is making it impossible to debug the code.







      debug oracle-11g






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 17 at 13:09









      Bad PandaBad Panda

      11




      11






















          0






          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "3"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1395372%2fpl-sql-developer-debugger-wont-step-into-code-across-db-link%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Super User!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1395372%2fpl-sql-developer-debugger-wont-step-into-code-across-db-link%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          How to make a Squid Proxy server?

          Is this a new Fibonacci Identity?

          19世紀