Hi,
I'm using PL/SQL developer5.1.2.682 02.8838 against a 10g database and I hit a problem with saying "Unable to initialize debugger" using the untouched "SCOTT" account
I did a search on the forum and came across a previous entry relating to this problem in an earlier db incarnation.
I ran the suggested piece of code (Marco's suggestion)
declare
debug_session_id varchar2(100);
begin
debug_session_id := sys.dbms_debug.initialize;
-- sys.dbms_debug.debug_on;
end;
/
and got the following response...
ERROR at line 1:
ORA-01031: insufficient privileges
ORA-06512: at "SYS.PBSDE", line 78
ORA-06512: at "SYS.DBMS_DEBUG", line 224
ORA-06512: at line 4
I first granted execute on dbms_debug to public - still same error
I then granted execute on dbms_debug to scott - still same error
I then granted RESOURCE to SCOTT so his roles were now CONNECT,RESOURCE. - still same error
In desperation, I then granted DBA to SCOTT and ran it again - this time it worked
Obviously, it's not ideal to have to grant DBA to every developer accessing a 10g database (I'm aware that this is not a PL/SQL Developer limitation but am wondering whether there are any suggestions as to more refined grants I can give than DBA to get this working?
thanks
I'm using PL/SQL developer5.1.2.682 02.8838 against a 10g database and I hit a problem with saying "Unable to initialize debugger" using the untouched "SCOTT" account
I did a search on the forum and came across a previous entry relating to this problem in an earlier db incarnation.
I ran the suggested piece of code (Marco's suggestion)
declare
debug_session_id varchar2(100);
begin
debug_session_id := sys.dbms_debug.initialize;
-- sys.dbms_debug.debug_on;
end;
/
and got the following response...
ERROR at line 1:
ORA-01031: insufficient privileges
ORA-06512: at "SYS.PBSDE", line 78
ORA-06512: at "SYS.DBMS_DEBUG", line 224
ORA-06512: at line 4
I first granted execute on dbms_debug to public - still same error
I then granted execute on dbms_debug to scott - still same error
I then granted RESOURCE to SCOTT so his roles were now CONNECT,RESOURCE. - still same error
In desperation, I then granted DBA to SCOTT and ran it again - this time it worked
Obviously, it's not ideal to have to grant DBA to every developer accessing a 10g database (I'm aware that this is not a PL/SQL Developer limitation but am wondering whether there are any suggestions as to more refined grants I can give than DBA to get this working?
thanks