Dbvisit Replicate communicates with both source and target database to replicate data. This communication includes reading and writing data through the system Data Source Name (DSN) configured using ODBC data source and drivers. A system DSN for SQL server on source system is required by Dbvisit Replicate to successfully execute configurational scripts that prepares the target SQL Server environment for replication. On target system, a system 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 SQL Server database is on Windows environment, system 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.
| Info |
|---|
Configuration script can use user DSN as well as system DSN to communicate with SQL Server database but the APPLY service on Windows OS requires only system DSN. Therefore creating system DSN is recommend because it is useful in both cases. |
...
| 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.
| No Format | ||
|---|---|---|
| ||
[SQL Server Native Client 11.0] Description=Microsoft SQL Server ODBC Driver V1.0 for Linux Driver=/opt/microsoft/sqlncli/lib64/libsqlncli-11.0.so.1790.0 Threading=1 UsageCount=1 |
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"
| No Format | ||
|---|---|---|
| ||
[mstest] Driver=SQL Server Native Client 11.0 Description=My Sample ODBC Database Connection Trace=Yes Server=<IP Address of Target Windows Machine> |
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.
| No Format | ||
|---|---|---|
| ||
oracle@dbvldemo101[/home/oracle]: isql -v dbtest sa ******* +---------------------------------------+ | Connected! | | | | sql-statement | | help [tablename] | | quit | | | +---------------------------------------+ SQL> select * from avi.sample |
| 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 SQL Server replication. |