...
Starting the dbvrep setup wizard
1.Create a directory, where all files relevant to Replicate configuration will be saved:
| No Format |
|---|
cd $HOME
mkdir replicate
cd replicate |
The following is a step-by-step guide of configuring a replication using the setup wizard. To accept the default answer for a question, just press the Return key.
12. On the source server, as oracle, in the $HOME directory, execute the dbvrep executable to start Dbvisit Replicate.
| No Format |
|---|
/usr/dbvisit/replicate/dbvrep |
The output will be.:
| No Format |
|---|
[oracle@source replicate]$ /usr/dbvisit/replicate/dbvrep Initializing......done Dbvisit Replicate version 2.8.700 Copyright (C) Dbvisit Software Limited. All rights reserved. No DDC file loaded. Run "setup wizard" to start the configuration wizard or try "help" to see all commands available. dbvrep> |
3. Start the setup wizard and accept the end-user license agreement.
| No Format |
|---|
dbvrep> setup wizard This wizard configures Dbvisit Replicate. The setup wizard creates configuration scripts, which need to be run after the wizard ends. No changes to the databases are made before that. The progress is saved every time a list of databases, replications, etc. is shown. It will be re-read if wizard is restarted and the same DDC name and script path is selected. Run the wizard now? [yesYes] yes Accept end-user license agreement? (viewView/yesYes/noNo) [viewView] yes |
3. Follow the steps and give the name of the replication. Name it dbvrep_XE. replicate.
| No Format |
|---|
Before starting the actual configuration, some basic information is needed. The DDC name and script path determines where all files created by the wizard go (and where to reread them if wizard is rerun) and the license key determines which options are available for this configuration. (DDC_NAME) - Please enter a name for this replication (suggestion: use the name of the source database): [] dbvrep_XE replicate |
4. Use the trial license key included with Dbvisit Replicate and select the MAX edition of the product.
...
Enter the location of the directory where the Setup Wizard will place the configuration files. Accept the default value.
| No Format |
|---|
(SETUP_SCRIPT_PATH) - Please enter a directory for location of configuration scripts on this machine: [/u01/app/oracle/dbvrep_XEreplicate] |
Enter the location where Dbvisit Replicate will find the Oracle network configuration files. Accept the default value.
| No Format |
|---|
Network configuration files were detected on this system in these locations: [/u01/app/oracle/product/11.2.0/xe/network/admin] (TNS_ADMIN) - Please enter TNS configuration directory for this machine: [/u01/app/oracle/product/11.2.0/xe/network/admin] |
...
Describe the first database. This will be the source database and will be the Oracle database on the machine called source.
| Note |
|---|
The SYSDBA and DBA passwords (normally SYS and SYSTEM) are only used during the configuration and are not used or stored as part of a running replication. |
| No Format |
|---|
Step 1 - Describe databases ======================================== The first step is to describe databases used in the replication. There are usually two of them (source and target). Store SYSDBA and DBA passwords? Passwords only required during setup and initialization? (yesYes/noNo) [yesYes] |
Specify the default database which is Oracle.
| No Format |
|---|
Let's configure the database, describing it'sits type, connectivity, user names etc. What type of database is this? (Oracle/MySQL/SQL Google Cloud SQL/SQL Server/Oracle AWS RDS/CSV/Hadoop): [Oracle] |
6. The TNS alias for the source database is ttorcl_src SOURCE
| No Format |
|---|
Please enter database TNS alias: [] ttorcl_srcSOURCE |
Enter the username and password of a user with SYSDBA. Accept the default of SYS and change_on_install.
...
7. Specify the defaults to create the Dbvisit Replicate schema Schema in the source database. Accept the default username of dbvrep and the default password of dbvpasswd.
| No Format |
|---|
Connecting to database ttorcl_srcSOURCE as SYSTEM to query list of tablespaces and to detect ASM (by looking whether any redo logs or archived logs are stored in ASM). Enter the Dbvisit Replicate owner (this user will be created by this script): [dbvrep] Please enter password for this user: [dbvpasswd] |
Specify the USERS tablespace as the default tablespace for the dbvrep user.
| No Format |
|---|
Permanent tablespaces detected on the database: REPOE_DATA, USERS. Please enter default permanent tablespace for this user: [REPOE_DATA] USERS |
Specify the TEMP tablespace as the temporary tablespace for the dbvrep user.
| No Format |
|---|
Temporary tablespaces detected on the database: TEMP. Please enter default temporary tablespace for this user: [TEMP] |
The first database is now configured. Add the next database. This will be the target database and will be the Oracle database on the machine called target.
| No Format |
|---|
Following databases are now configured: 1: Oracle ttorcl_src, SYS/***, SYSTEM/***, dbvrep/***, USERS/TEMP, dbvrep/, ASM:NO, TZ: +00:00 |
8. Add the next database. This will be the target database. It is also an Oracle database.
| No Format |
|---|
Enter the number of the database to modify it, or "add", or "done": [add] Enter the Dbvisit Replicate owner (this user will be created by this script): [dbvrep] Please enter password for this user: [dbvpasswd] |
Specify the USERS tablespace as the default tablespace for the Dbvisit Replicate Schema (dbvrep) user.
| No Format |
|---|
Permanent tablespaces detected on the database: REPOE_DATA, USERS. Please enter default permanent tablespace for this user: [REPOE_DATA] USERS |
Specify the default database which is Oracle.
| No Format |
|---|
Let's configure the database, describing it's type, connectivity, user names etc. What type of database is this? (Oracle/MySQL/SQL Server/Oracle AWS RDS/CSV/Hadoop): [Oracle] |
9. The TNS alias is ttorcl_trg.
| No Format |
|---|
Please enter database TNS alias: [] ttorcl_trg |
Specify the TEMP tablespace as the temporary tablespace for the Dbvisit Replicate Schema (dbvrep) user.
| No Format |
|---|
Temporary tablespaces detected on the database: TEMP. Please enter default temporary tablespace for this user: [TEMP] |
The first database is now configured. Add the next database. This will be the target database and will be the Oracle database on the machine called target.
| No Format |
|---|
Following databases are now configured: 1: Oracle SOURCE, SYS/***, SYSTEM/***, dbvrep/***, USERS/TEMP, dbvrep/, ASM:No, TZ: +00:00 |
8. Add the next database. This will be the target database. It is also an Oracle database.
| No Format |
|---|
Enter the number of the database to modify it, or "add", or "done": [add] |
Enter the username and password of a user with SYSDBA. Accept the default of SYS and change_on_install.
| No Format |
|---|
Please enter SYSDBA user name: [SYS] Please enter password for this user: [change_on_install] |
Enter the username and password of a user with the DBA role. Accept the default of SYSTEM and manager.
| No Format |
|---|
Please enter user with DBA role: [SYSTEM] Please enter password for this user: [manager] |
Specify the default database which is Oracle.
| No Format |
|---|
Let's configure the database, describing it's type, connectivity, user names etc. What type of database is this? (Oracle/MySQL/SQL Server/Oracle AWS RDS/CSV/Hadoop): [Oracle] |
9. The TNS alias is TARGET.
| No Format |
|---|
Please enter database TNS alias: [] TARGET |
Specify the defaults to create the Dbvisit Replicate schema in the target database. Accept the default username of dbvrep and the default password of dbvpasswd.
| No Format |
|---|
Connecting to database ttorcl_trg as SYSTEM to query list of tablespaces and to detect ASM (by looking whether any redo logs or archived logs are stored in ASM). Enter the Dbvisit Replicate owner (this user will be created by this script): [dbvrep |
Enter the username and password of a user with SYSDBA. Accept the default of SYS and change_on_install.
| No Format |
|---|
Please enter SYSDBA user name: [SYS] Please enter password for this user: [dbvpasswdchange_on_install] |
Specify the USERS tablespace as the default tablespace for the dbvrep userEnter the username and password of a user with the DBA role. Accept the default of SYSTEM and manager.
| No Format |
|---|
PermanentPlease tablespacesenter detecteduser onwith theDBA databaserole: REPOE_DATA, USERS. [SYSTEM] Please enter default permanent tablespacepassword for this user: [REPOE_DATAmanager] USERS |
Specify the TEMP tablespace as the temporary tablespace for the dbvrep user.
| No Format |
|---|
Temporary tablespaces detected on the database: TEMP. Please enter default temporary tablespace for this user: [TEMP] |
11. Both source and target database have now been defined.
| No Format |
|---|
Following databases are now configured:
1: Oracle ttorcl_src, SYS/***, SYSTEM/***, dbvrep/***, USERS/TEMP, dbvrep/, ASM:NO, TZ: +00:00
2: Oracle ttorcl_trg, SYS/***, SYSTEM/***, dbvrep/***, USERS/TEMP, dbvrep/, ASM:NO, TZ: +00:00
Enter the number of the database to modify it, or "add", or "done": [done] |
Step 2 - Replication Pairs
12. Set source and targets for each replication pair. Select 1 as the source database (default) and 2 as the target database.
| No Format |
|---|
Step 2 - Replication pairs ======================================== The second step is to set source and targets for each replication pair. Let's configure the replication pair, selecting source and target. Following databases are described: 1: ttorcl_src (Oracle) 2: ttorcl_trg (Oracle) Select source database: [1] Select target database: [2] |
Specify the defaults to create the Dbvisit Replicate Schema in the target database. Accept the default username of dbvrep and the default password of dbvpasswd.
| No Format |
|---|
Connecting to database TARGET as SYSTEM to query list of tablespaces and to detect ASM (by looking whether any redo logs or archived logs are stored in ASM).
WARN-1877: This database is not in Archivelog mode; set it before starting Replicate scripts if this is a source database.
Enter the Dbvisit Replicate owner (this user will be created by this script): [dbvrep]
Please enter password for this user: [dbvpasswd] |
Specify the USERS tablespace as the default tablespace for the Dbvisit Replicate Schema (dbvrep) user.
| No Format |
|---|
Permanent tablespaces detected on the database: REPOE_DATA, USERS. Please enter default permanent tablespace for this user: [REPOE_DATA] USERS |
13. Select the default values for the following configuration entries.
| No Format |
|---|
Will be DDL replication enabled? [yes]
Use fetcher to offload the mining to a different server? (yes/no) [no]
Would you like to encrypt the data across the network (yes or no) [no]
Would you like to compress the data across the network (yes or no) [no]
How long do you want to set the network timeouts. Recommended range between 60-300 seconds [60] |
...
Specify the TEMP tablespace as the temporary tablespace for the Dbvisit Replicate Schema (dbvrep) user.
| No Format |
|---|
Temporary tablespaces detected on the database: TEMP.
Please enter default temporary tablespace for this user: [TEMP] |
11. Both source and target database have now been defined.
| No Format |
|---|
Following databases are now configured:
1: Oracle SOURCE, SYS/***, SYSTEM/***, dbvrep/***, USERS/TEMP, dbvrep/, ASM:No, TZ: +00:00
2: Oracle TARGET, SYS/***, SYSTEM/***, dbvrep/***, USERS/TEMP, dbvrep/, ASM:No, TZ: +00:00
Enter the number of the database to modify it, or "add", or "done": [done] |
Step 2 - Replication Pairs
12. Set source and targets for each replication pair. Select 1 as the source database (default) and 2 as the target database.
| No Format |
|---|
Step 2 - Replication pairs
========================================
The second step is to set source and targets for each replication pair.
Let's configure the replication pair, selecting source and target.
Following databases are described:
1: SOURCE (Oracle)
2: TARGET (Oracle)
Select source database: [1]
Select target database: [2] |
13. Select the default values for the following configuration entries.
| No Format |
|---|
Will DDL replication be enabled? (Yes/No) [Yes]
Use fetcher to offload the mining to a different server? (Yes/No) [No]
Should where clauses (and change auditing) include all columns, not just changed and PK? (Yes/No) [No]
Would you like to encrypt the data across the network? (Yes/No) [No]
Would you like to compress the data across the network? (Yes/No) [No]
How long do you want to set the network timeouts. Recommended range between 60-300 seconds [60] |
14. Define the method to use to lock and copy the data initially to ensure the data is in sync before the replication starts. Use the single-scn method (default).
| No Format |
|---|
Lock and copy the data initially one-by-one or at a single SCN? one-by-one : Lock tables one by one and capture SCN single-scn : One SCN for all tables ddl-only : Only DDL script for target objects resetlogs : Use SCN from last resetlogs operation (standby activation, rman incomplete recovery) no-lock : Do not lock tables. Captures previous SCN of oldest active transaction. Requires pre-requisite running of pre-all.sh script (one-(one-by-one/single-scn/ddl-only/resetlogs/no-lock) [single-scn] |
15. Define what data instantiation script to create? This method copies the initial data set to ensure the data is in sync before the replication starts. Use dp_networklink which is the DataPump method over a database network link (DB_LINK) (default).
| No Format |
|---|
What data instantiation script to create? dp_networklink : Data Pump with network link. No export datafile is created (APPLY.sh) dp_exp : Data Pump with export datafile. Creates an export datafile (APPLY.sh) exp : Pre-datapump exp/imp with export datafile (APPLY.sh) ddl_file : DDL file created (APPLY.sql) ddl_run : DDL is automatically executed on target load : All replicated data is created and loaded automatically none none (dp_networklink/dp_exp/exp/ddl_file/ddl_run/load/none) [dp_networklink] |
16. The replication pair is now configured.
| No Format |
|---|
Following replication pairs are now configured: 1: ttorcl_srcSOURCE (Oracle) ==> ttorcl_trgTARGET (Oracle), DDL: yesYes, fetcher: noNo, process suffix: (no suffix), compression: noNo, encryption: noNo, network timeout: 60, prepare type: single-scn, data load: dp_networklink Enter number of replication pair to modify it, or "add", or "done": [done] |
Step 3 - Replicated Tables
...
| No Format |
|---|
Step 3 - Replicated tables ======================================== The third step is to choose the schemas and tables to be replicated. If the databases are reachable, the tables are checked for existence, datatype support, etc., schemas are queried for tables. Note that all messages are merely hints/warnings and may be ignored if issues are rectified before the scripts are actually executed. Following tables are defined for replication pairs: 1: ttorcl_srcSOURCE (Oracle) ==> ttorcl_trgTARGET (Oracle), DDL: yesYes, suffix: (no suffix), prepare: single-scn No tables defined. Enter number of replication pair to modify it, or "done": [1] |
18. Specify the REPOE schema is to be replicated.
| No Format |
|---|
Please enter list of all individual tables to be replicated. Enter schema name(s) only to replicate all tables in that schema. Use comma or space to delimit the entries. Enter the tables and schemas: [] repoeREPOE Selected schemas: REPOE |
We do not need to add more tables, so select NO (default).
| No Format |
|---|
Add more tables or schemas? Selected schemas: REPOE |
We do not need to add more tables, so select NO (default).
| No Format |
|---|
Add more tables or schemas? (YES/NO) [NO] |
19. We are not replicating PL/SQL. Press Return to skip this option.
| No Format |
|---|
To replicate changes of PL/SQL objects in schema(s), please enter the schemas to be replicated. Note that specifying any entry will cause additional privileges to be
granted to dbvrep. Enter through a comma or space-delimited list.
Enter the list of schemas (PL/SQL): [] |
20. We are not going to use any advanced options, so specify no (default).
| No Format |
|---|
You can also specify some advanced options:
1. Rename schemas or tables.
2. Specify filtering conditions.
3. (Tables only) Configure Change Data Capture; this does not maintain a copy of the source table, but logs all operations as separate entries. This is useful for ETL or
as an audit trail. This usually requires adding of new columns (timestamps, old/new values etc.) to the target table.
Specify rename name or filter condition for any of the specified schemas (YES/NO): [no] |
21. There are no tables to exclude from the schema. Press enter.
| No Format |
|---|
(PREPARE_SCHEMA_EXCEPTIONS) - Specify tables to exclude from PREPARE SCHEMA, if any: [] |
22. The tables are now defined for the replication. Press Return.
| No Format |
|---|
Following tables are defined for replication pairs: 1: ttorcl_src (Oracle) ==> ttorcl_trg (Oracle), DDL: yes, suffix: (no suffix), prepare: single-scn REPOE(tables) Enter number of replication pair to modify it, or "done": [done] (YES/NO) [NO] |
19. We are not replicating PL/SQL. Press Return to skip this option.
| No Format |
|---|
To replicate changes of PL/SQL objects in schema(s), please enter the schemas to be replicated. Note that specifying any entry will cause additional privileges to be granted to
dbvrep. Enter through a comma or space-delimited list.
Enter the list of schemas (PL/SQL): [] |
20. We are not going to use any advanced options, so specify no (default).
| No Format |
|---|
You can also specify some advanced options:
1. Exclude some tables from schema-level replication
2. Rename schemas or tables.
3. Specify filtering conditions.
4. (Tables only) Configure Change Data Capture; this does not maintain a copy of the source table, but logs all operations as separate entries. This is useful for ETL or as an
audit trail. This usually requires adding of new columns (timestamps, old/new values etc.) to the target table.
Specify rename name, filter condition or audit for any of the specified schemas? (Yes/No) [No] |
21. There are no tables to exclude from the schema. Press enter.
| No Format |
|---|
(PREPARE_SCHEMA_EXCEPTIONS) - Specify tables to exclude from PREPARE SCHEMA, if any: [] |
22. The tables are now defined for the replication. Press Return.
| No Format |
|---|
Following tables are defined for replication pairs:
1: SOURCE (Oracle) ==> TARGET (Oracle), DDL: Yes, suffix: (no suffix), prepare: single-scn
REPOE(tables)
Enter number of replication pair to modify it, or "done": [done] |
Step 4 - Process Configuration
23. Specify information about the processes and where they are going to run. Press Return to accept the default values.
| No Format |
|---|
Step 4 - Process configuration
========================================
The fourth step is to configure the replication processes for each replication.
Following processes are defined:
1: MINE on SOURCE Not configured.
2: APPLY on TARGET Not configured.
Enter number of process to modify it, or "done": [1] |
24. Add information where the MINE process is going to run. Accept all the defaults.
| No Format |
|---|
Fully qualified name of the server for the process (usually co-located with the database, unless mine is offloaded using fetcher): [source]
Server type (Windows/Linux/Unix): [Linux]
Enable email notifications about problems? (Yes/No) [No]
Enable SNMP traps/notifications about problems? (Yes/No) [No]
Directory with DDC file and default where to create log files etc. (recommended: same as global setting, if possible)? [/u01/app/oracle/replicate] |
Step 4 - Process Configuration
23. Specify information about the processes and where they are going to run. Press Return to accept the default values.
| No Format |
|---|
Step 4 - Process configuration ======================================== The fourth step is to configure the replication processes for each replication. Following processes are defined: 1: MINE on ttorcl_src Not configured. 2: APPLY on ttorcl_trg Not configured. Enter number of process to modify it, or "done": [1] |
24. Add information where the MINE process is going to run. Accept all the defaults.
| No Format |
|---|
Enter number of process to modify it, or "done": [1] Fully qualified name of the server for the process (usually co-located with the database, unless mine is offloaded using fetcher): [source] Server type (Windows/Linux/Unix): [Linux] Enable email notifications about problems (yes/no)? [no] Enable SNMP traps/notifications about problems (yes/no)? [no] Directory with DDC file and default where to create log files etc. (recommended: same as global setting, if possible)? [/u01/app/oracle/dbvrep_XE] |
All the settings will be displayed. Press Return to accept the default values.
| No Format |
|---|
Following settings were pre-filled with defaults or your reloaded settings:
----------------------------------------
[MINE_REMOTE_INTERFACE]: Network remote interface: source:7901
[MINE_DATABASE]: Database TNS: SOURCE
[TNS_ADMIN]: tnsnames.ora path: /u01/app/oracle/product/11.2.0/xe/network/admin
[MINE_PLOG]: Filemask for generated plogs: /u01/app/oracle/replicate/mine/%S.%E (%S is sequence, %T thread, %F original filename (stripped extension), %P process type, %N process name, %E default extension)
[LOG_FILE]: General log file: /u01/app/oracle/replicate/log/dbvrep_%N_%D.%E
[LOG_FILE_TRACE]: Error traces: /u01/app/oracle/replicate/log/trace/dbvrep_%N_%D_%I_%U.%E Checking that these settings are valid... |
All the settings will be displayed. Press Return to accept the default values.
| No Format |
|---|
Following settings were pre-filled with defaults or your reloaded settings: ---------------------------------------- [MINE_REMOTE_INTERFACE]: Network remote interface: source:7901 [MINE_DATABASE]: Database TNS: source [TNS_ADMIN]: tnsnames.ora path: /u01/app/oracle/product/11.2.0/xe/network/admin [MINE_PLOG]: Filemask for generated plogs: /u01/app/oracle/dbvrep_XE/mine/%S.%E (%S is sequence, %T thread, %F original filename (stripped extension), %P process type, %N process name, %E default extension) [LOG_FILE]: General log file: /u01/app/oracle/dbvrep_XE/log/dbvrep_%N_%D.%E [LOG_FILE_TRACE]: Error traces: /u01/app/oracle/dbvrep_XE/log/trace/dbvrep_%N_%D_%I_%U.%E Checking that these settings are valid... Do you want change any of the settings? [no] |
...
Do you want to change any of the settings? [No] |
25. Add information where the APPLY process is going to run. Accept all the defaults.
| No Format |
|---|
Following processes are defined: 1: MINE on ttorlc_srcSOURCE Host: source, SMTP: noNo, SNMP: noNo 2: APPLY on ttorcl_trgTARGET Not configured. Enter number of process to modify it, or "done": [2] |
Add Add information where the APPLY process is going to run. Accept all the defaults.
| No Format |
|---|
EnterFully qualified numbername of processthe toserver modify it, or "done": [1] Fully qualified name of the server for thefor the process (usually co-located with the database, unless mine is offloaded using fetcher): [target] Server type (Windows/Linux/Unix): [Linux] Enable email notifications about problems? (yesYes/noNo)? [noNo] Enable SNMP traps/notifications about problems? (yesYes/noNo)? [noNo] Directory with DDC file and default where to create log files etc. (recommended: same as global setting, if possible)? [/u01/app/oracle/dbvrep_XE] |
All the settings will be displayed. Press return.
| No Format |
|---|
Following settings were pre-filled with defaults or your reloaded settings:
----------------------------------------
[APPLY_REMOTE_INTERFACE]: Network remote interface: target:7902
[APPLY_DATABASE]: Database TNS: target
[TNS_ADMIN]: tnsnames.ora path: /u01/app/oracle/product/11.2.0/xe/network/admin
[APPLY_STAGING_DIR]: Directory for received plogs: /u01/app/oracle/dbvrep_XE/apply
[LOG_FILE]: General log file: /u01/app/oracle/dbvrep_XE/log/dbvrep_%N_%D.%E
[LOG_FILE_TRACE]: Error traces: /u01/app/oracle/dbvrep_XE/log/trace/dbvrep_%N_%D_%I_%U.%E
Checking that these settings are valid...
Do you want change any of the settings? [no] |
26. The processes are now defined.
| No Format |
|---|
Following processes are defined:
1: MINE on ttorcl_src
Host: source, SMTP: no, SNMP: no
2: APPLY on ttorcl_trg
Host: target, SMTP: no, SNMP: no
Enter number of process to modify it, or "done": [done] |
27. Dbvisit Replicate wizard has completed and all the scripts have been created. No database changes have been made yet.
| No Format |
|---|
|
28. Do not run the script, but exit out of the wizard.
| No Format |
|---|
Run this script now? (yes/no) [NO] dbvrep> exit Directory with DDC file and default where to create log files etc. (recommended: same as global setting, if possible)? [/u01/app/oracle/replicate] |
All the settings will be displayed. Press return.
| No Format |
|---|
Following settings were pre-filled with defaults or your reloaded |
...
settings:
----------------------------------------
[APPLY_REMOTE_INTERFACE]: Network remote interface: target:7902
[APPLY_DATABASE]: Database TNS: TARGET
[TNS_ADMIN]: tnsnames.ora path: /u01/app/oracle/product/11.2.0/xe/network/admin
[APPLY_STAGING_DIR]: Directory for received plogs: /u01/app/oracle/replicate/apply
[LOG_FILE]: General log file: /u01/app/oracle/replicate/log/dbvrep_%N_%D.%E
[LOG_FILE_TRACE]: Error traces: /u01/app/oracle/replicate/log/trace/dbvrep_%N_%D_%I_%U.%E
Checking that these settings are valid...
Do you want to change any of the settings? [No] |
26. The processes are now defined.
| No Format |
|---|
Following processes are defined:
1: MINE on SOURCE
Host: source, SMTP: No, SNMP: No
2: APPLY on TARGET
Host: target, SMTP: No, SNMP: No
Enter number of process to modify it, or "done": [done] |
27. Dbvisit Replicate wizard has completed and all the scripts have been created. No database changes have been made yet.
| No Format |
|---|
Created file /u01/app/oracle/replicate/replicate-APPLY.ddc.
Created file /u01/app/oracle/replicate/replicate-MINE.ddc.
Created file /u01/app/oracle/replicate/config/replicate-setup.dbvrep.
Created file /u01/app/oracle/replicate/config/replicate-dbsetup_SOURCE_dbvrep.sql.
Created file /u01/app/oracle/replicate/config/replicate-dbsetup_TARGET_dbvrep.sql.
Created file /u01/app/oracle/replicate/config/replicate-grants_SOURCE_dbvrep.sql.
Created file /u01/app/oracle/replicate/config/replicate-grants_TARGET_dbvrep.sql.
Created file /u01/app/oracle/replicate/config/replicate-onetime.ddc.
Created file /u01/app/oracle/replicate/start-console.sh.
Created file /u01/app/oracle/replicate/replicate-run-source.sh.
Created file /u01/app/oracle/replicate/scripts/replicate-source-start-MINE.sh.
Created file /u01/app/oracle/replicate/scripts/replicate-source-stop-MINE.sh.
Created file /u01/app/oracle/replicate/scripts/replicate-source-dbvrep-MINE.sh.
Created file /u01/app/oracle/replicate/scripts/systemd-dbvrep-MINE_replicate.service.
Created file /u01/app/oracle/replicate/scripts/upstart-dbvrep-MINE_replicate.conf.
Created file /u01/app/oracle/replicate/replicate-run-target.sh.
Created file /u01/app/oracle/replicate/scripts/replicate-target-start-APPLY.sh.
Created file /u01/app/oracle/replicate/scripts/replicate-target-stop-APPLY.sh.
Created file /u01/app/oracle/replicate/scripts/replicate-target-dbvrep-APPLY.sh.
Created file /u01/app/oracle/replicate/scripts/systemd-dbvrep-APPLY_replicate.service.
Created file /u01/app/oracle/replicate/scripts/upstart-dbvrep-APPLY_replicate.conf.
Created file /u01/app/oracle/replicate/Nextsteps.txt.
Created file /u01/app/oracle/replicate/replicate-all.sh.
===============================================================================================================================================================================
Dbvisit Replicate wizard completed
Script /u01/app/oracle/replicate/replicate-all.sh created. This runs all the above created scripts. Please exit out of dbvrep, review and run script as current user to setup
and start Dbvisit Replicate.
=============================================================================================================================================================================== |
28. Do not run the script, but exit out of the wizard.
| No Format |
|---|
Optionally, the script can be invoked now by this wizard.
Run this script now? (Yes/No) [No] |
You have now completed the Setup Wizard to configure a simple one-way replication. The Wizard has created the configuration files above but has not changed anything in the source or target databases.
The next step will be to execute the scripts created by the Setup Wizard to initialize the replication.