Which has the higher priority in your organization: Deploying a new database or securing the ones you already have?
Looking for a website, and resources, dedicated solely to securing Oracle databases? Check out DBSecWorx.
Connect the specified session to the debugger waiting at host:port
This demo performs added security checks to decide if the debug connection request is granted (for example, by verifying that the debugger is running on a trusted host)
Note: In 11gR1, and thereafter, an ACL or ACE must be created for this call to succeed (see link below)
dbms_debug_jdwp.connect_tcp(
host IN VARCHAR2,
port IN VARCHAR2,
session_id IN PLS_INTEGER := NULL,
session_serial IN PLS_INTEGER := NULL,
debug_role IN VARCHAR2 := NULL,
debug_role_pwd IN VARCHAR2 := NULL,
option_flags IN PLS_INTEGER := 0,
extensions_cmd_set IN PLS_INTEGER := 128);
DECLARE
vhost VARCHAR2(40) := 'bigdog.mlib.org';
vport VARCHAR2(10) := '1521';
BEGIN
IF (utl_inaddr.get_host_address(vhost) != '119.168.1.119') THEN
RAISE_APPLICATION_ERROR(-20000, 'debug connection to this host not permitted');
ELSE
dbms_debug_jdwp.connect_tcp(vhost, vport);
END IF;
dbms_debug_jdwp.disconnect;
END;
/
Allows a session to connect to a debugger through the use of either the ORA_DEBUG_JDWP operating system environment variable when running an OCI program,
or a web browser "cookie" called OWA_DEBUG_<dad> set when running an application through the PL/SQL Web Gateway
dbms_debug_jdwp.process_connect_string(
connect_string IN VARCHAR2,
connect_string_type IN PLS_INTEGER);