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.
Purpose
Internal support package for PL/SQL Warnings and the DBMS_WARNING package
AUTHID
CURRENT_USER
Dependencies
ALL_WARNING_SETTINGS
DBA_WARNING_SETTINGS
WARNING_SETTINGS$
CDB_WARNING_SETTINGS
USER_WARNING_SETTINGS
Documented
No
First Available
10.1
Security Model
Owned by SYS with no privileges granted
Source
{ORACLE_HOME}/rdbms/admin/prvtplsw.plb
SHOW_WARNING_SETTING
Undocumented ... and obviously not intended for DBAs and developers
dbms_warning_internal(objno IN NUMBER)
RETURN PIPELINED warning_setting_coll;
conn uwclass/uwclass@pdbdev
ALTER SESSION SET PLSQL_WARNINGS='ENABLE:ALL';
CREATE OR REPLACE PROCEDURE dead_code AUTHID DEFINER AS
x NUMBER := 10;
BEGIN
IF x = 10 THEN
x := 20;
ELSE
x := 100;
END IF;
END dead_code;
/
SP2-0804: Procedure created with compilation warnings
SELECT plsql_warnings
FROM all_plsql_object_settings
WHERE name = 'DEAD_CODE';
conn sys@pdbdev as sysdba
SQL> SELECT COUNT(*)
2 FROM dba_warning_settings;
COUNT(*)
---------
663
SQL> set linesize 121
SQL> SELECT owner, object_id, object_type
2 FROM dba_warning_settings
3 WHERE object_name = 'DEAD_CODE';