eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

SYS.DBMS_STREAMS_ADM dependencies on DBMS_STREAMS_TABLESPACE_ADM

Line 618: -- dbms_streams_tablespace_adm.clone_tablespaces and place the tablespace

614: -- At the source database:
615: -- - Mark all the tablespaces in the supplied list of tablespaces as read
616: -- only.
617: -- - Clone the tablespaces using
618: -- dbms_streams_tablespace_adm.clone_tablespaces and place the tablespace
619: -- set in the source directory.
620: -- - Add supplemental log groups for the tables in the tablespaces if
621: -- necessary.
622: -- - Setup a Streams queue at the source.

Line 636: -- dbms_streams_tablespace_adm.attach_tablespaces.

632: -- - Move the tablespace set to the destination directory using
633: -- dbms_file_transfer.
634: -- At the destination database:
635: -- - Attach the tablespaces using
636: -- dbms_streams_tablespace_adm.attach_tablespaces.
637: -- - Set key columns for all the tables in the tablespaces if necessary.
638: -- - Setup Streams queue.
639: -- - Create an apply process and add all supported tables to the apply
640: -- rules.

Line 675: tablespace_names IN dbms_streams_tablespace_adm.tablespace_set,

671: -- sharing. Else, only uni-directional
672: -- sharing is setup.
673:
674: PROCEDURE maintain_tablespaces(
675: tablespace_names IN dbms_streams_tablespace_adm.tablespace_set,
676: source_directory_object IN VARCHAR2,
677: destination_directory_object IN VARCHAR2,
678: destination_database IN VARCHAR2,
679: setup_streams IN BOOLEAN DEFAULT TRUE,

Line 723: tablespace_names IN dbms_streams_tablespace_adm.tablespace_set,

719: -- if NULL, name will be generated
720: -- For a bi-directional setup, two queues will be created on each database.
721:
722: PROCEDURE maintain_tts(
723: tablespace_names IN dbms_streams_tablespace_adm.tablespace_set,
724: source_directory_object IN VARCHAR2,
725: destination_directory_object IN VARCHAR2,
726: source_database IN VARCHAR2,
727: destination_database IN VARCHAR2,

Line 922: tablespace_names IN dbms_streams_tablespace_adm.tablespace_set,

918: instantiation IN BINARY_INTEGER DEFAULT
919: dbms_streams_adm.instantiation_full);
920: PROCEDURE pre_instantiation_setup(
921: maintain_mode IN VARCHAR2,
922: tablespace_names IN dbms_streams_tablespace_adm.tablespace_set,
923: source_database IN VARCHAR2,
924: destination_database IN VARCHAR2,
925: perform_actions IN BOOLEAN DEFAULT TRUE,
926: script_name IN VARCHAR2 DEFAULT NULL,

Line 945: tablespace_names IN dbms_streams_tablespace_adm.tablespace_set,

941: exclude_flags IN BINARY_INTEGER DEFAULT NULL);
942:
943: PROCEDURE post_instantiation_setup(
944: maintain_mode IN VARCHAR2,
945: tablespace_names IN dbms_streams_tablespace_adm.tablespace_set,
946: source_database IN VARCHAR2,
947: destination_database IN VARCHAR2,
948: perform_actions IN BOOLEAN DEFAULT TRUE,
949: script_name IN VARCHAR2 DEFAULT NULL,

Line 969: tablespace_names IN dbms_streams_tablespace_adm.tablespace_set,

965: exclude_flags IN BINARY_INTEGER DEFAULT NULL);
966:
967: PROCEDURE cleanup_instantiation_setup(
968: maintain_mode IN VARCHAR2,
969: tablespace_names IN dbms_streams_tablespace_adm.tablespace_set,
970: source_database IN VARCHAR2,
971: destination_database IN VARCHAR2,
972: perform_actions IN BOOLEAN DEFAULT TRUE,
973: script_name IN VARCHAR2 DEFAULT NULL,