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.
ltric.apply_ric_commit_table(
state_name IN VARCHAR2,
ct_owner IN VARCHAR2,
ct_name IN VARCHAR2);
TBD
Overload 2
ltric.apply_ric_commit_table(
state_name IN VARCHAR2,
recurctabowners IN OUT wmsys.ltutil.wm$ident_tab,
recurctabnames IN OUT wmsys.ltutil.wm$ident_tab);
ltric.apply_ric_constraints(
table_owner IN VARCHAR2,
table_name IN VARCHAR2,
cons_view_where_clause IN VARCHAR2,
dirty_rows_where_clause IN VARCHAR2,
dirty_version IN NUMBER);
ltric.apply_ric_restrict(
table_owner_var IN VARCHAR2,
table_name_var IN VARCHAR2,
ver IN NUMBER,
otherws IN VARCHAR2,
otherwsver IN NUMBER,
mp_root_ws IN VARCHAR2,
opvar IN VARCHAR2);
ltric.apply_ric_restrict_post(
child_workspace IN VARCHAR2,
parent_workspace_var IN VARCHAR2,
post_ver IN NUMBER,
parver IN NUMBER,
mp_root_workspace IN VARCHAR2);
exec wmsys.ltric.backupRicLocksList;
BEGIN wmsys.ltric.backupRicLocksList; END;
*
ERROR at line 1:
ORA-06550: line 1, column 7:
PLS-00904: insufficient privilege to access object LTRIC
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
ltric.createRicWhereClause(
ct_col_qualifier IN VARCHAR2,
ct_cols IN VARCHAR2,
pt_col_qualifier IN VARCHAR2,
pt_cols IN VARCHAR2,
newstr IN VARCHAR2)
RETURN VARCHAR2;
ltric.do_cr_ric_check(
parent_ws IN VARCHAR2,
parent_ws_curver IN NUMBER,
child_ws IN VARCHAR2,
parver IN NUMBER,
table_owner_var IN VARCHAR2,
table_name_var IN VARCHAR2,
opvar IN VARCHAR2,
resolveop IN VARCHAR2,
mp_root_workspace IN VARCHAR2);
ltric.genVtptNotExistsWc(
ct_cols_var IN VARCHAR2,
pt_cols_var IN VARCHAR2,
pt_owner_var IN VARCHAR2,
pt_name_var IN VARCHAR2,
ctqual IN VARCHAR2)
RETURN VARCHAR2;
ltric.getPtBeforeTrigStrs(
ct_owner_name IN VARCHAR2,
table_name IN VARCHAR2,
par_tab_owner IN VARCHAR2,
par_tab_name IN VARCHAR2,
upd_trig_name IN VARCHAR2,
ric_update_sql OUT CLOB,
del_trig_name IN VARCHAR2,
ric_delete_sql OUT CLOB);
ltric.getricInsteadOfTrigStrs(
owner_name_var IN VARCHAR2,
table_name IN VARCHAR2,
ric_insert_sql IN OUT CLOB,
ric_update_sql IN OUT CLOB,
ric_delete_sql IN OUT CLOB,
recreatecttrigs IN NUMBER);
ltric.lockRicRows(
table_owner IN VARCHAR2,
table_name IN VARCHAR2,
state_var IN VARCHAR2,
opcode IN VARCHAR2,
where_clause IN VARCHAR2,
check_conf IN BOOLEAN);
exec wmsys.ltric.recreatePtUpdDelTriggers;
BEGIN wmsys.ltric.recreateptupddeltriggers; END;
*
ERROR at line 1:
ORA-06550: line 1, column 7:
PLS-00904: insufficient privilege to access object LTRIC
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
exec wmsys.ltric.restoreRicLocksList;
BEGIN wmsys.ltric.restoreRiclockslist; END;
*
ERROR at line 1:
ORA-06550: line 1, column 7:
PLS-00904: insufficient privilege to access object LTRIC
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
ltric.ric_enable_versioning_internal(
table_owner_v IN VARCHAR2,
table_name_v IN VARCHAR2,
ric_insert_sql IN OUT CLOB,
ric_update_sql IN OUT CLOB,
ric_delete_sql IN OUT CLOB);