Dbvisit Replicate is configured using a setup wizard. The setup wizard does not make any database changes, instead it creates a set of configuration scripts that can be inspected before executing to give full visibility of database changes.
If any mistakes are made, then the wizard can be cancelled by typing ctrl-c, and then restarted. The setup wizard will remember previous information entered.
This configuration will take about 15 minutes.
Please ensure the follow pre-requisites checks have been tested. Otherwise the replication will not function
Starting the dbvrep setup wizard
The following is a step-by-step guide of configuring a replication using the setup wizard.
1. Connect to the source (dbv01) server as oracle
su - oracle
2. In the home directory of oracle start Dbvisit Replicate
[oracle@source ~]$ dbvrep Initializing......done Dbvisit Replicate version 2.6.00.3735 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
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? [yes] yes
Accept end-user license agreement? (view/yes/no) [view] yes
3. Follow the steps and give the name of the replication. Name it dbvrep_orcl
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_orcl
4. For the next questions, leave the defaults as they are
(LICENSE_KEY) - Please enter your license key: [(trial)]
Which Replicate edition do you want to trial (LTD/XTD/MAX): [MAX]
(SETUP_SCRIPT_PATH) - Please enter a directory for location of configuration scripts on this machine: [/home/oracle/dbvrep_orcl] Network configuration files were detected on this system in these locations: /home/oracle/app/oracle/product/11.2.0/dbhome_2/network/admin /home/oracle/app/oracle/product/11.2.0/dbhome_2/network/admin
(TNS_ADMIN) - Please enter TNS configuration directory for this machine: [/home/oracle/app/oracle/product/11.2.0/dbhome_2/network/admin]
5. Describe the first database. This will be the source database and will be Oracle.
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? (yes/no) [yes]
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]
6. The TNS alias is TTORCL_SRC
Please enter database TNS alias: [] ttorcl_src
Please enter SYSDBA user name: [SYS]
SYS password is oracle:
Please enter password for this user: [change_on_install] ******
Please enter user with DBA role: [SYSTEM]
SYSTEM password is oracle:
Please enter password for this user: [manager] ******
7. Specify the defaults to create the Dbvisit Replicate schema in the source database. Choose the USERS tablespace as the default tablespace
Connecting to database ttorcl_src 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] Permanent tablespaces detected on the database: APEX_1930613455248703, APEX_2041602962184952, APEX_2610402357158758, APEX_2611417663389985, APEX_2614203650434107, EXAMPLE, USERS.
Please enter default permanent tablespace for this user: [APEX_1930613455248703] USERS Temporary tablespaces detected on the database: TEMP.
Please enter default temporary tablespace for this user: [TEMP] Following databases are now configured: 1: Oracle ttorcl_src, SYS/***, SYSTEM/***, dbvrep/***, USERS/TEMP, dbvrep/, ASM:NO, TZ: +00:00
8. The first database is now configured. Add the next database. This will be the target database. It is also an Oracle database
Enter the number of the database to modify it, or "add", or "done": [add]
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
Please enter database TNS alias: [] ttorcl_trg
Please enter SYSDBA user name: [SYS]
SYS password is oracle
Please enter password for this user: [change_on_install] ******
Please enter user with DBA role: [SYSTEM]
SYSTEM password is oracle
Please enter password for this user: [manager] ******
10. Specify the defaults to create the Dbvisit Replicate schema in the source database. Choose the USERS tablespace as the default tablespace
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]
Please enter password for this user: [dbvpasswd] Permanent tablespaces detected on the database: APEX_1930613455248703, APEX_2041602962184952, APEX_2610402357158758, APEX_2611417663389985, APEX_2614203650434107, EXAMPLE, USERS.
Please enter default permanent tablespace for this user: [APEX_1930613455248703] USERS 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
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]
12. Set source and targets for each replication pair
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]
13. Specify defaults for the replication pair
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]
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
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) (one-by-one/single-scn/ddl-only/resetlogs) [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)
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 (dp_networklink/dp_exp/exp/ddl_file/ddl_run/load/none) [dp_networklink]
16. The replication pair is now configured
Following replication pairs are now configured: 1: ttorcl_src (Oracle) ==> ttorcl_trg (Oracle), DDL: yes, fetcher: no, process suffix: (no suffix), compression: no, encryption: no, network timeout: 60, prepare type: single-scn, data load: dp_networklink Enter number of replication pair to modify it, or "add", or "done": [done]
17 Add the schemas or tables to be replicated
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_src (Oracle) ==> ttorcl_trg (Oracle), DDL: yes, suffix: (no suffix), prepare: single-scn No tables defined. Enter number of replication pair to modify it, or "done": [1]
18. Add the OE schema to be replicated
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: [] oe Selected schemas: OE
Add more tables or schemas? (YES/NO) [NO]
19. We are not going to replicated PL/SQL
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
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. The tables are now defined for the replication
Following tables are defined for replication pairs: 1: ttorcl_src (Oracle) ==> ttorcl_trg (Oracle), DDL: yes, suffix: (no suffix), prepare: single-scn OE(tables) Enter number of replication pair to modify it, or "done": [done]
22. Specify information about the processes and where they are going to run
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]
23. Add information where the MINE process is going to run. Accept all the defaults
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)? [/home/oracle/dbvrep_orcl] Following settings were pre-filled with defaults or your reloaded settings: ---------------------------------------- [MINE_REMOTE_INTERFACE]: Network remote interface: source:7901 [MINE_DATABASE]: Database TNS: ttorcl_src [TNS_ADMIN]: tnsnames.ora path: /home/oracle/app/oracle/product/11.2.0/dbhome_2/network/admin [MINE_PLOG]: Filemask for generated plogs: /home/oracle/dbvrep_orcl/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: /home/oracle/dbvrep_orcl/log/dbvrep_%N_%D.%E [LOG_FILE_TRACE]: Error traces: /home/oracle/dbvrep_orcl/log/trace/dbvrep_%N_%D_%I_%U.%E Checking that these settings are valid...
Do you want change any of the settings? [no]
24. Add information where the APPLY process is going to run. Accept all the defaults
Following processes are defined: 1: MINE on ttorcl_src Host: source, SMTP: no, SNMP: no 2: APPLY on ttorcl_trg Not configured. Enter number of process to modify it, or "done": [2]
Fully qualified name of the server for 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 (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)? [/home/oracle/dbvrep_orcl] Following settings were pre-filled with defaults or your reloaded settings: ---------------------------------------- [APPLY_REMOTE_INTERFACE]: Network remote interface: target:7902 [APPLY_DATABASE]: Database TNS: ttorcl_trg [TNS_ADMIN]: tnsnames.ora path: /home/oracle/app/oracle/product/11.2.0/dbhome_2/network/admin [APPLY_STAGING_DIR]: Directory for received plogs: /home/oracle/dbvrep_orcl/apply [LOG_FILE]: General log file: /home/oracle/dbvrep_orcl/log/dbvrep_%N_%D.%E [LOG_FILE_TRACE]: Error traces: /home/oracle/dbvrep_orcl/log/trace/dbvrep_%N_%D_%I_%U.%E Checking that these settings are valid...
Do you want change any of the settings? [no]
25. The processes are now defined
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]
26. Dbvisit Replicate wizard has completed and all the scripts have been created. No database changes have been made yet
Created file /home/oracle/dbvrep_orcl/dbvrep_orcl-APPLY.ddc. Created file /home/oracle/dbvrep_orcl/dbvrep_orcl-MINE.ddc. Created file /home/oracle/dbvrep_orcl/config/dbvrep_orcl-setup.dbvrep. Created file /home/oracle/dbvrep_orcl/config/dbvrep_orcl-dbsetup_ttorcl_src.sql. Created file /home/oracle/dbvrep_orcl/config/dbvrep_orcl-dbsetup_ttorcl_trg.sql. Created file /home/oracle/dbvrep_orcl/config/dbvrep_orcl-grants_ttorcl_src.sql. Created file /home/oracle/dbvrep_orcl/config/dbvrep_orcl-grants_ttorcl_trg.sql. Created file /home/oracle/dbvrep_orcl/config/dbvrep_orcl-onetime.ddc. Created file /home/oracle/dbvrep_orcl/start-console.sh. Created file /home/oracle/dbvrep_orcl/dbvrep_orcl-run-source.sh. Created file /home/oracle/dbvrep_orcl/dbvrep_orcl-run-target.sh. Created file /home/oracle/dbvrep_orcl/Nextsteps.txt. Created file /home/oracle/dbvrep_orcl/dbvrep_orcl-all.sh. ======================================================================================================================================================================== Dbvisit Replicate wizard completed Script /home/oracle/dbvrep_orcl/dbvrep_orcl-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. ======================================================================================================================================================================== Optionally, the script can be invoked now by this wizard. Run this script now? (yes/no) [NO]
27. Do not run the script, but exit out of the wizard
Run this script now? (yes/no) [NO]
dbvrep> exit [oracle@source ~]$
Add Comment