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
Multi-Dimensional SQL ODBO package for MDX support. PL/SQL definitions to support OLE DB for MDX.
AUTHID
CURRENT_USER
Constants
Name
Data Type
Value
General
MDX_DATE
VARCHAR2(8)
'MDX_DATE'
MDX_NUMBER
VARCHAR2(10)
'MDX_NUMBER'
MDSCHEMA_ACTIONS
BINARY_INTEGER
1
MDSCHEMA_CUBES
BINARY_INTEGER
2
MDSCHEMA_DIMENSIONS
BINARY_INTEGER
3
MDSCHEMA_FUNCTIONS
BINARY_INTEGER
4
MDSCHEMA_HIERARCHIES
BINARY_INTEGER
5
MDSCHEMA_LEVELS
BINARY_INTEGER
6
MDSCHEMA_MEASURES
BINARY_INTEGER
7
MDSCHEMA_PROPERTIES
BINARY_INTEGER
8
MDSCHEMA_MEMBERS
BINARY_INTEGER
9
MDSCHEMA_SETS
BINARY_INTEGER
10
MDSCHEMA_ROWSET_MAX
BINARY_INTEGER
11
Data Types
TYPE odbo_boolean_sequence IS VARRAY(32767) OF NUMBER;
TYPE odbo_short_sequence IS VARRAY(32767) OF NUMBER;
TYPE odbo_number_sequence IS VARRAY(32767) OF NUMBER;
TYPE odbo_string_sequence IS VARRAY(32767) OF VARCHAR2(10922);
Dependencies
ALL_ANALYTIC_VIEW_BASE_MEAS
DBA_ATTRIBUTE_DIM_ATTRS
MDX_ODBO_DIMENSIONS
ALL_ANALYTIC_VIEW_CALC_MEAS
DBA_ATTRIBUTE_DIM_KEYS
MDX_ODBO_FUNCTIONS
ALL_ANALYTIC_VIEW_DIMENSIONS
DBA_ATTRIBUTE_DIM_TABLES
MDX_ODBO_HIERARCHIES
ALL_ANALYTIC_VIEW_HIERS
DBA_HIER_COLUMNS
MDX_ODBO_LEVELS
ALL_ANALYTIC_VIEW_LEVELS
DBMS_HCS_LIB
MDX_ODBO_MEASURES
ALL_ATTRIBUTE_DIM_TABLES
DBMS_MDX_ODBO_FUNCTION_T
MDX_ODBO_PROPERTIES
ALL_TABLES
DBMS_MDX_ODBO_KEYWORD_T
PLITBLM
ALL_TAB_COLUMNS
DBMS_MDX_ODBO_PROPVAL_T
Documented
No
Exceptions
Error Code
Reason
ORA-18250
The input parameter to the MDX PL/SQL function is invalid
exec dbms_mdx_odbo.close(1);
BEGIN dbms_mdx_odbo.close(1); END;
*
ERROR at line 1:
ORA-18252: There are no active MDX queries.
ORA-06512: at "SYS.DBMS_MDX_ODBO", line 81
ORA-06512: at "SYS.DBMS_MDX_ODBO", line 1498
ORA-06512: at line 1
dbms_mdx_odbo.execute(
mdx_str IN VARCHAR2,
query_properties IN odbo_string_sequence,
column_axis OUT SYS_REFCURSOR,
row_axis OUT SYS_REFCURSOR,
page_axis OUT SYS_REFCURSOR,
chapter_axis OUT SYS_REFCURSOR,
section_axis OUT SYS_REFCURSOR,
slicer OUT SYS_REFCURSOR,
mdx_info OUT CLOB,
query_id OUT NUMBER);
dbms_mdx_odbo.get_schema_rowset(
rowset_type IN NUMBER,
restrictions IN odbo_string_sequence,
empty IN odbo_boolean_sequence,
rowset OUT sys_refcursor,
query_properties IN odbo_string_sequence);
Returns the integer identifier for a dimension type
If this wasn't an unsupported package I would open an SR
dbms_mdx_odbo.mdx_dimension_type(dimtype IN VARCHAR2)
RETURN INTEGER DETERMINISTIC;
BEGIN
dbms_output.put_line(dbms_mdx_odbo.mdx_dimension_type('STANDARD'));
END;
/
BEGIN
*
ERROR at line 1:
ORA-06592: CASE not found while executing CASE statement
ORA-06512: at "SYS.DBMS_MDX_ODBO", line 503
ORA-06512: at line 2
SELECT dbms_mdx_odbo.mdx_dimension_type('TIME')
FROM dual;
SELECT dbms_mdx_odbo.mdx_dimension_type('TIME')
*
ERROR at line 1:
ORA-06592: CASE not found while executing CASE statement
ORA-06512: at "SYS.DBMS_MDX_ODBO", line 503
dbms_mdx_odbo.mdx_get_hierarchy_cardinality(
cubeowner IN VARCHAR2,
cubename IN VARCHAR2,
dimalias IN VARCHAR2,
hierarchyalias IN VARCHAR2)
RETURN INTEGER DETERMINISTIC;
dbms_mdx_odbo.mdx_get_level_cardinality(
cubeowner IN VARCHAR2,
cubename IN VARCHAR2,
dimalias IN VARCHAR2,
hierarchyalias IN VARCHAR2,
levelname IN VARCHAR2)
RETURN INTEGER DETERMINISTIC;