Dbvisit Replicate communicates with both source and target database to replicate data. This communication includes reading and writing data through Data Source Name (DSN) configured using ODBC data source and drivers. A DSN for SQL server on source system is required by Dbvisit Replicate to successfully execute configurational scripts that prepares the target MSSQL environment for replication. On target system, a DSN with same name as source system is required by the APPLY service which interacts with target database to replicate changes of source database.
When source Oracle database is on Linux environment and target MSSQL database is on Windows environment, DSN is required only on target Windows machine because the initial setup wizard is executed on target Windows machine unlike the other scenario where setup wizard is executed on source machine when both source and target databases are running on Windows OS.
DSN on WIndows
When source oracle database and target MSSQL database are both running on Windows machine, Dbvisit Replicate required identical DSN on both system. A DSN is required on source machine for initial configuration step that interacts with target MSSQL database. On target system a DSN with the same name as source machine is required to replicate changes of source database.
...
| Note |
|---|
Windows to Windows Oracle to MSSQL replication is a beta feature and it will be fully supported in next release. |
DSN on Linux
If the source oracle database is running on Linux machine then ODBC drivers for Linux is required to set up DSN. ODBC driver manager is required in order to install ODBC driver for Linux. Microsoft provides ODBC driver for Linux that provides native connectivity from Linux to Microsoft SQL Server. You can download ODBC driver for Linux from following page.
...
| Note |
|---|
Installation instructions are available on same page. This download includes a script (build_dm.sh) to build ODBC driver manager. Please read instructions carefully and configure your system according to your environment requirement. |
Installation of ODBC driver will insert following record in /etc/odbcinst.ini file.
| Section | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Crosscheck whether this specification are inserted or not.
Once the installation is done, DSN can be created. To create DSN, login as root and create a DSN entry in /etc/odbc.ini file.Following is an example of DSN named "mstest"
| Section | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Once DSN is created. "isql" command can be used to test DSN. If DSN is working properly then isql command will return SQL prompt from where you can execute SQL statements on target database running on Windows machine. Following is the example of testing DSN testdb1.
| Section | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Note |
|---|
ODBC drivers for Linux have been released by Microsoft but Dbvisit Replicate currently does not support them. A future release of Dbvisit Replicate will support these ODBC drivers for Linux, which will allow execution of the setup wizard on Linux for MSSQL replication. |