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
Assumed to allow dynamically resetting the
database maximum string size: To be validated.
AUTHID
DEFINER
Data Types
/* Record type returned by CHECK_MAX_STRING_SIZE API */
CREATE OR REPLACE TYPE dbms_max_string_size_rec force as object
(
type VARCHAR2(128),
object_owner dbms_id,
object_name dbms_id,
column_name dbms_id,
reason VARCHAR2(4000))
NOT PERSISTABLE;
/
/* Table type returned by CHECK_MAX_STRING_SIZE API */
CREATE OR REPLACE TYPE dbms_max_string_size_tbl FORCE
AS TABLE OF (dbms_max_string_size_rec)
NOT PERSISTABLE;
/
Dependencies
DBA_REGISTRY
DBMS_MAX_STRING_SIZE_TBL
PLITBLM
DBA_TAB_COLS
DBMS_SCHEDULER
PROPS$
DBA_VIEWS
DBMS_SQL
V$PARAMETER
DBMS_ASSERT
DBMS_STANDARD
V$PDBS
DBMS_MAX_STRING_SIZE_REC
Documented
No
Exceptions
Error Code
Reason
ORA-2000
An object exists that will prevent the string size modification
dbms_max_string_size.modify_max_string_size(newValue IN VARCHAR2);
exec dbms_max_string_size.modify_max_string_size('STANDARD');
BEGIN
dbms_max_string_size.modify_max_string_size('STANDARD'); END;
*
ERROR at line 1:
ORA-01422: exact fetch returns more than requested number of rows
ORA-06512: at "SYS.DBMS_MAX_STRING_SIZE", line 9
ORA-06512: at "SYS.DBMS_MAX_STRING_SIZE", line 284
ORA-06512: at line 1