Page Comparison

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
..

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.

Use tnsping to test if the SQL*Net connection can be made from source server to target database.

Dbvisit Replicate uses the following default ports for communication between the source and target servers:
- 7901
- 7902
For 2-way replication the default ports are:
- 7901
- 7902
- 7903
- 7904
These ports are configurable and can be changed if required.

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.

We require database to be in ARCHIVELOG mode. To determine if database is in archivelog mode run SQL command:

SQL> archive log list

On source server run:

ping source_hostname

On target server run:

ping target_hostname

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.

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.

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.

It is in Step 1 - Describe databases

Question is "Enter the database with the user data:"

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

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
..

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.

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.

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;

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.