Installation Prerequisites
Before installing Dbvisit Replicate please ensure that the following prerequisites are met.
Oracle to Oracle Replication : Prerequisite Checklist
| Task | Comment | ||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Oracle software is installed on source and target servers. | The Oracle software version can be different between the source and target servers.Dbvisit Replicate supports Oracle 9.2 and later. | |||||||||||||||||||||||||||||||||||||||
| 2 | Oracle source database is up and running. | We require database to be in ARCHIVELOG mode. To determine if database is in archivelog mode run SQL command: SQL> archive log list Example output: Database log mode Archive Mode Automatic archival Enabled Archive destination /oracle/oraarch/orcl Oldest online log sequence 3959 .. | |||||||||||||||||||||||||||||||||||||||
| 3 | Dbvisit Replicate software can be run with any OS user id except root. It does not have to be the same user id as the Oracle software. However, file system read access to the redo and archive logs is required and that is why the user has to be part of the oinstall or dba group. If ASM is used on MINE, a bequeath connection must be made to the ASM instance and the user may also have to be a member of the sysasm group. | ||||||||||||||||||||||||||||||||||||||||
| 4 | Oracle target database is up and running. Create users in target db you plan to configure or replication as well as any roles that may exist in the source db. The users schemas should be empty on the target. | Having target database in ARCHIVELOG mode is optional in one-way replication. | |||||||||||||||||||||||||||||||||||||||
| 5 | Ensure there is enough disk space and available memory for Dbvisit Replicate to run | See System Requirements | |||||||||||||||||||||||||||||||||||||||
| 6 | Ensure Oracle listener is running on the source server | ||||||||||||||||||||||||||||||||||||||||
| 7 | Ensure Oracle listener is running on the target server (only if target database is Oracle). | ||||||||||||||||||||||||||||||||||||||||
| 8 | Ensure Oracle SQL*Net connection to target database from source database.(only if target database is Oracle). | Use tnsping to test if the SQL*Net connection can be made from source server to target database. | |||||||||||||||||||||||||||||||||||||||
| 9 | Ensure Oracle SQL*Net connection to source database from target database. | Use tnsping to test if the SQL*Net connection can be made from target server to source database. | |||||||||||||||||||||||||||||||||||||||
| 10 | Ensure that the firewall port is opened between the source and the target servers for the Dbvisit Replicate ports. | Dbvisit Replicate uses the following default ports for communication between the source and target servers. The ports need to be open on their respective servers:
These ports are configurable and can be changed if required. For configurations not listed in the table above similar rules apply. Run | |||||||||||||||||||||||||||||||||||||||
| 11 | Ensure source server name can be resolved to correct IP address (not 127.0.0.1). | On source server run: ping source_hostname | |||||||||||||||||||||||||||||||||||||||
| 12 | Ensure target server name can be resolved to correct IP address (not 127.0.0.1). | On target server run: ping target_hostname | |||||||||||||||||||||||||||||||||||||||
| 13 | Ensure all data types that need to be replicated are supported by Dbvisit Replicate. | Run the SQL query in Supported Datatypes to determine if there are any unsupported datatypes | |||||||||||||||||||||||||||||||||||||||
| 14 | For RAC, ensure all redo and archive threads are on shared storage and accessible by all nodes. | ||||||||||||||||||||||||||||||||||||||||
| 15 | For AIX, please ensure the following packages are installed | These are available from the install CD or the IBM website: bos.adt.libm bos.adt.debug These packages need to be installed as root using smit. | |||||||||||||||||||||||||||||||||||||||
Oracle to SQL Server Replication : Prerequisite Checklist
| Task | Comment | Comment | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Oracle software is installed on source server. | Dbvisit Replicate supports Oracle 9.2 and later. | ||||||||||||||
| 2 | SQL Server is installed on target servers. | Dbvisit Replicate supports SQL Server 2005 and later | ||||||||||||||
| 3 | Oracle source database is up and running. | We require database to be in ARCHIVELOG mode. To determine if database is in archivelog mode run SQL command: SQL> archive log list Example output: Database log mode Archive Mode Automatic archival Enabled Archive destination /oracle/oraarch/orcl Oldest online log sequence 3959 .. | ||||||||||||||
| 4 | Dbvisit Replicate software can be run with any OS user id except root. It does not have to be the same user id as the Oracle software. However, file system read access to the redo and archive logs is required and that is why the user has to be part of the oinstall or dba group. If ASM is used on MINE, a bequeath connection must be made to the ASM instance and the user may also have to be a member of the sysasm group. | |||||||||||||||
| 5 | Ensure there is enough disk space and available memory for Dbvisit Replicate to run. | See System Requirements | ||||||||||||||
| 6 | Ensure Oracle listener is running on the source server. | |||||||||||||||
| 7 | Ensure Oracle SQL*Net connection to source database from target database. | Use tnsping to test if the SQL*Net connection can be made from target server to source database. Click here for more information | ||||||||||||||
| 8 | Ensure that the firewall port is opened between the source and the target servers for the Dbvisit Replicate ports. | Dbvisit Replicate uses the following default ports for communication between the source and target server. The ports need to be open on their respective servers:
These ports are configurable and can be changed if required. For configurations not listed in the table above similar rules apply. Run | ||||||||||||||
| 9 | Ensure source server name can be resolved to correct IP address (not 127.0.0.1). | On source server run: ping source_hostname | ||||||||||||||
| 10 | Ensure target server name can be resolved to correct IP address (not 127.0.0.1). | On target server run: ping target_hostname | ||||||||||||||
| 11 | Ensure all data types that need to be replicated are supported by Dbvisit Replicate. | Run the SQL query in Supported Datatypes to determine if there are any unsupported datatypes in source database. Few datatypes can not be replicated from Oracle to SQL Server. Click here for more information. | ||||||||||||||
| 12 | For RAC, ensure all redo threads are on shared storage and accessible by all nodes. | |||||||||||||||
| 13 | Ensure that the firewall port is opened on the target server for SQL Server. | SQL Server uses 1433 port by default. | ||||||||||||||
| 14 | Remote connection is enabled in SQL Server. | |||||||||||||||
| 15 | User must have required privileges. | Dbvisit Replicate creates dbvrep database in SQL Server as metadata repository followed by executing SQL statements through APPLY service. You can either use single username or two different usernames for each task. | ||||||||||||||
| 16 | System DSN connection to SQL Server exists. | System DSN is required for executing *-all.bat script that configures source and target database for replication and to run APPLY service. Click here for more information. | ||||||||||||||
| 17 | Target database in SQL Server has been created and is operational. | It is in Step 1 - Describe databases Question is "Enter the database with the user data:" | ||||||||||||||
Oracle to MySQL Replication : Prerequisite Checklist
| Task | Comment | Comment | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Oracle software is installed on source server. | Dbvisit Replicate supports Oracle 9.2 and later. | ||||||||||||||
| 2 | MySQL is installed on target servers. | Dbvisit Replicate supports MySQL 5 and later. | ||||||||||||||
| 3 | MySQL client software is installed on the source server(s). | Dbvisit Replicate running on the source server(s) requires the MySQL client software in order to be able to connect and communicate with the MySQL database running on the target. The client software version can be easily determined and installed via yum, as per the following: root@source> yum list mysql-community*... root@source> yum install mysql-community-client.x86_64 | ||||||||||||||
| 4 | Oracle source database is up and running. | We require database to be in ARCHIVELOG mode. To determine if database is in archivelog mode run SQL command: SQL> archive log list Example output: Database log mode Archive Mode Automatic archival Enabled Archive destination /oracle/oraarch/orcl Oldest online log sequence 3959 .. | ||||||||||||||
| 5 | Dbvisit Replicate software can be run with any OS user id except root. It does not have to be the same user id as the Oracle software. However, file system read access to the redo and archive logs is required and that is why the user has to be part of the oinstall or dba group. If ASM is used on MINE, a bequeath connection must be made to the ASM instance and the user may also have to be a member of the sysasm group. | |||||||||||||||
| 6 | Ensure there is enough disk space and available memory for Dbvisit Replicate to run. | See System Requirements | ||||||||||||||
| 7 | Ensure Oracle listener is running on the source server. | |||||||||||||||
| 8 | Ensure Oracle SQL*Net connection to source database from target server. | Use tnsping to test if the SQL*Net connection can be made from target server to source database. Click here for more information. By default Dbvisit Replicate will look for a TNSNAMES file in the same location on the target server as it is located on the Oracle source server. So you can create this location on the target and simply copy the TNSNAMES file across, and check that the details are correction for the connection back to the Oracle source database. If you wish to change the location of this file on the target server then edit the APPLY DDC file, and adjust the TNS_ADMIN parameter accordingly. | ||||||||||||||
| 9 | Ensure that the firewall port is opened between the source and the target servers for the Dbvisit Replicate ports. | Dbvisit Replicate uses the following default ports for communication between the source and target servers. The ports need to be open on their respective servers:
These ports are configurable and can be changed if required. For configurations not listed in the table above similar rules apply. Run | ||||||||||||||
| 10 | Ensure source server name can be resolved to correct IP address (not 127.0.0.1). | On source server run: ping source_hostname | ||||||||||||||
| 11 | Ensure target server name can be resolved to correct IP address (not 127.0.0.1). | On target server run: ping target_hostname | ||||||||||||||
| 12 | Ensure all data types that need to be replicated are supported by Dbvisit Replicate. | Run the SQL query in Supported Datatypes to determine if there are any unsupported datatypes in source database. Few datatypes can not be replicated from Oracle to MySQL. Click here for more information. | ||||||||||||||
| 13 | For RAC, ensure all redo threads are on shared storage and accessible by all nodes. | |||||||||||||||
| 14 | Ensure that the firewall port is opened on the target server for SQL Server. | MySQL uses 3306 port by default. | ||||||||||||||
| 15 | Ensure that you can connect to the MySQL database on the target from the source server(s) - using the MySQL client which Dbvisit Replicate will connect through | For example: [oracle@source ~]$ mysql -u oracle -p --host target Once connected you can issue the following to ensure you are on the correct server: mysql> select @@hostname; | ||||||||||||||
| 16 | User must have required privileges. | Dbvisit Replicate creates dbvrep database in MySQL as metadata repository followed by executing SQL statements through APPLY service. You can either use single username or two different usernames for each task. Use "grant all privileges on *database.* to 'username'@'%' identified by 'userpassword' " command. | ||||||||||||||
Where to Get Additional Oracle client Installation Information
Oracle client for Linux
For Oracle 11.2, you can refer to http://docs.oracle.com/cd/E11882_01/install.112/e24325/toc.htm#i1011296 .
For other versions, start at http://tahiti.oracle.com/ , select your version and then go for "Quick Client Installation Guide for Linux x86-64".
Watch this explanatory video for an alternative overview of our Installation Prerequisites: