dbms_capture_adm_ivk.abort_schema_inst_ivk(
schema_name IN VARCHAR2,
container IN VARCHAR2);
-- appears to be runnable from pdb$root but have not tested this
-- as there is no validation in this proc.
exec dbms_capture_adm_ivk.abort_schema_inst_ivk('SCOTT', 'PDBDEV');
dbms_capture_adm_ivk.abort_table_inst_ivk(
table_name IN VARCHAR2,
container IN VARCHAR2);
-- appears to be runnable from pdb$root but have not tested this
-- as there is no validation in this proc.
exec dbms_capture_adm_ivk.abort_table_inst_ivk('SERVERS', 'PDBDEV');
dbms_capture_adm_ivk.create_capture_ivk(
queue_name IN VARCHAR2,
capture_name IN VARCHAR2,
rule_set_name IN VARCHAR2,
start_scn IN NUMBER,
source_database IN VARCHAR2,
user_database_link IN BOOLEAN,
first_scn IN NUMBER,
logfile_assignment IN VARCHAR2,
negative_rule_set_name IN VARCHAR2,
capture_user IN VARCHAR2,
checkpoint_retention_time IN NUMBER,
start_time IN TIMESTAMP,
enable_procedure IN BOOLEAN,
source_root_name IN VARCHAR2,
capture_class IN VARCHAR2,
clone_capture_name IN VARCHAR2);
dbms_capture_adm_ivk.supp_log_level_check(
supplemental_logging IN VARCHAR2,
check_for_keyalways IN BOOLEAN)
RETURN BINARY_INTEGER;
-- having no idea what the proper string for the first parameter is
-- I threw something at it which it appears does not work but does
-- prove out the validity of the syntax.
SELECT supplemental_log_data_min, supplemental_log_data_pk
FROM sys.v_$database;