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.
prvtemx_perf.action_cancel_sql_xml(
p_sid IN NUMBER,
p_serial_num IN NUMBER,
p_inst_id IN NUMBER,
p_sql_id IN VARCHAR2,
p_show_sql IN NUMBER)
RETURN XMLTYPE;
Produces in XML format the report information and DCL to kill a connected session
prvtemx_perf.action_kill_session_xml(
report_reference IN VARCHAR2,
p_isnt_id IN NUMBER,
p_sid IN NUMBER,
p_serial_num IN NUMBER,
p_show_sql IN NUMBER)
RETURN XMLTYPE;
conn / as sysdba
SELECT sid
FROM v$mystat
WHERE rownum = 1;
SID
----------
17
SELECT serial#
FROM v$session
WHERE sid = 17;
SERIAL#
----------
16744
set head off
set pagesize 0
set linesize 201
SELECT prvtemx_perf.action_kill_session_xml('TEST', 1, 17, 16744, 1)
FROM dual;
-- manually formated the output for display: PRVTEMX_PERF.ACTION_KILL_SESSION_XML('TEST',1,17,16744,1)
-----------------------------------------------------------------------------------
<report db_version="21.0.0.0.0" elapsed_time="0.00" cpu_time="0.00" cpu_cores="2" hyperthread="Y" con_id="1" con_name="CDB$ROOT" timezone_offset="-18000" packs="2">
<report_id><![CDATA[/orarep/session/kill_session]]></report_id>
<sql>ALTER SYSTEM KILL SESSION '17,16744,@1' immediate</sql>
</report>
prvtemx_perf.report_session_details_xml(
report_reference IN VARCHAR2,
p_sid IN NUMBER,
p_isnt_id IN NUMBER,
p_serial_num IN NUMBER,
p_activity_dimension IN VARCHAR2,
p_is_realtime IN NUMBER,
p_starttime IN DATE,
p_endtime IN DATE,
p_monitor_list_detail IN NUMBER,
p_show_sql IN NUMBER)
RETURN XMLTYPE;