3 Replies Latest reply: Jun 18, 2010 8:09 AM by riedelme RSS

    How to stop use of plsql_debug?

    768212
      When I execute a package body DDL statement SQL Developer 2.1.x warns,

      Warning: PLW-06015: parameter PLSQL_DEBUG is deprecated; use PLSQL_OPTIMIZE_LEVEL=1
      How can SQL Developer be configured to not use PLSQL_DEBUG?

      PLSQL_DEBUG is set to false in an sql*plus session using the same connection details,

      show parameters plsql

      NAME TYPE VALUE

      plsql_ccflags string
      plsql_code_type string INTERPRETED
      plsql_debug boolean FALSE
      plsql_native_library_dir string
      plsql_native_library_subdir_count integer 0
      plsql_optimize_level integer 2
      plsql_v2_compatibility boolean FALSE
      plsql_warnings string ENABLE:ALL

      Oracle SQL Developer v 2.1.1.64

      Oracle 11g SE: 11.1.0.6.0

      Executing 'ALTER SESSION set plsql_debug=false' has stopped the warning but sql developer should not be setting this to true to begin with since it is deprecated.

      See also: http://stackoverflow.com/questions/3045401/how-to-prevent-parameter-plsql-debug-is-deprecated-compiler-warning-in-oracle-s/3051149

      Edited by: user4384958 on 16-Jun-2010 06:57
        • 1. Re: How to stop use of plsql_debug?
          riedelme
          I hope somebody provides a better answer than this, but until someone does ...

          You can create an on-login trigger to execute the command via EXECUTE IMMEDIATE when you log in to avoid having to do it manually
          • 2. Re: How to stop use of plsql_debug?
            -K-
            Don't have an answer either, but would like to suggest a better workaround.
            A logon trigger will be executed by everyone, you only need it in sqldev. So better just create a startup script with the ALTER and specify it inside Preferences - Database.

            Have fun,
            K.
            • 3. Re: How to stop use of plsql_debug?
              riedelme
              -K- wrote:
              A logon trigger will be executed by everyone, you only need it in sqldev. So better just create a startup script with the ALTER and specify it inside Preferences - Database.
              True, but that's the best I could think of. Going farther afield he could see if the user agent could be detected from the current session and if so only execute it for that tool

              Too many hoops to jump through :(

              Edited by: riedelme on Jun 18, 2010 6:08 AM