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
DBMS_LCR contains opaque type definitions for sys.lcr$_row_record, sys.lcr$_ddl_record, and sys.lcr$_procedure_record
AUTHID
N/A
Constants
Name
Data Type
Value
LOB Constants
not_a_lob
NUMBER
1
null_lob
NUMBER
2
inline_lob
NUMBER
3
empty_lob
NUMBER
4
lob_chunk
NUMBER
5
last_lob_chunk
NUMBER
6
LONG Data Type Constants
not_a_long
NUMBER
1
null_long
NUMBER
2
inline_long
NUMBER
3
long_chunk
NUMBER
4
last_long_chunk
NUMBER
5
XML Constants
not_xml
NUMBER
1
xml_doc
NUMBER
2
xml_diff
NUMBER
3
JSON Constants
not_oson
NUMBER
1
oson_doc
NUMBER
2
Data Types
CREATE OR REPLACE TYPE lcr$_row_unit AS OBJECT (
column_name VARCHAR2(4000),
data sys.anydata,
lob_information NUMBER,
lob_offset NUMBER,
lob_operation_size NUMBER,
long_information NUMBER,
-- as we are adding a new attribute, create a constructor for
-- older type def to preserve backwards compatibility.
CONSTRUCTOR FUNCTION lcr$_row_unit(
column_name VARCHAR2,
data sys.anydata,
lob_information NUMBER,
lob_offset NUMBER,
lob_operation_size NUMBER)
RETURN SELF AS RESULT);
/
CREATE OR REPLACE TYPE BODY lcr$_row_unit AS
CONSTRUCTOR FUNCTION lcr$_row_unit(
column_name VARCHAR2,
data sys.anydata,
lob_information NUMBER,
lob_offset NUMBER,
lob_operation_size NUMBER)
RETURN SELF AS RESULT AS
BEGIN
SELF.column_name := column_name;
SELF.data := data;
SELF.lob_information := lob_information;
SELF.lob_offset := lob_offset;
SELF.lob_operation_size := lob_operation_size;
SELF.long_information := dbms_lcr.not_a_long;
RETURN;
END;
END lcr$_row_unit;
/
CREATE OR REPLACE TYPE lcr$_row_list AS TABLE OF sys.lcr$_row_unit;
/
