Skip to main content

Search

Welcome to Tibero GTS!

MSSQL DBLINK Error Cases

Document Type | Technical Information

Category | Interface/Integration

Applicable Product Version | 7FS02PS04

Document Number | TADTI191

 

Overview

This document is a technical guide summarizing major error cases, causes, and solutions that may occur during MSSQL ↔ Tibero DBLINK integration.

Various errors can occur depending on MSSQL settings, ODBC settings, Gateway settings, Tibero parameter settings, etc., when configuring DBLINK. The causes and solutions for each error type are summarized below.

 
 

Methods

1. [CASE1] XACT_ABORT Setting

A. Symptom

Cannot start a nested transaction.
XACT_ABORT option is set to OFF, so nested transactions are required.
Msg 7395

B. Cause

  • Distributed transaction usage is not enabled in MSSQL.

  • XACT_ABORT option is set to OFF.

C. Action

  • Check XACT_ABORT in SQL Server Management Studio → DB Properties → Connections.

  • Restart SSMS.

→ When XACT_ABORT is set, it operates to roll back the entire transaction if a runtime error occurs.

 

2. [CASE2] Missing Provider String Setting

A. Symptom

Current cursor is not updatable.
Cannot perform INSERT INTO.
Msg 7343

B. Cause

  • Provider String setting omitted when creating DBLINK.

C. Action

  • Add the following option to the Provider String when creating DBLINK.

Updatable Cursor=True

 

3. [CASE3] RPC Setting Not Configured

A. Symptom

Server 't_link2' is not configured for RPC.
Msg 7411

B. Cause

  • RPC option not set in MSSQL Linked Server.

C. Action

  • Enable RPC and RPC Out options in Linked Server settings.

  • Required when calling remote stored procedures.

 

4. [CASE4] ODBC Version/Patch Issues

A. Symptom

Invalid attribute/option identifier.
Failed to start distributed transaction.
Failed to execute psm.

B. Cause

  • ODBC driver version mismatch.

  • Patch not applied.

  • Server/client version compatibility issues.

C. Action

  • Apply IMS-196024 ODBC when using Tibero6.

  • Use the latest ODBC driver if possible.

D. Compatibility Criteria

  • Whether the client driver fully supports specific server features.

  • Example: Tibero5sp1 FS02 DB can use Tibero6/7 ODBC.

 

5. [CASE5] DBLINK_CONN_TIMEOUT Setting

A. Symptom

TBR-2131 : Generic I/O error

B. Cause

  • Exceeded DBLINK_CONN_TIMEOUT value.

  • Default values vary by version.

C. Action

Execute as Tibero SYS account:

alter system set DBLINK_CONN_TIMEOUT=seconds;

Apply in TIP file:

$TB_HOME/config/$TB_SID.tip
DBLINK_CONN_TIMEOUT=seconds

A restart is required.

 

6. [CASE6] Gateway Service Start Failure

A. Symptom

Invalid JVM DLL handle.
Failed to load JVM DLL.
Failed creating Java.

B. Cause

  • msvcr71.dll corrupted or missing.

  • JVM DLL path error.

  • Windows library issues.

C. Action

  1. Restore msvcr71.dll (system32).

  2. Change Java version (5 or 1.4).

  3. Run prunmgr.exe and reset JVM path.

%JAVA_HOME%\bin\server\jvm.dll
or
%JAVA_HOME%\bin\client\jvm.dll

 

F. How to Collect ODBC Logs

Set environment variables:

TBCLI_LOG_DIR=<log_path>
TBCLI_LOG_LVL=TRACE

Log format:

tbcli_YYYYMMDDHHMMSS_PID.log

※ After adding system variables, Gateway service restart is required.

Note

  • MSSQL Linked Server operates in the structure of OLE DB → ODBC → Tibero Gateway → Tibero.

  • XACT_ABORT and RPC settings are essential in distributed transaction environments.

  • ODBC driver version compatibility with server version must be confirmed.

 

Caution

If any of MSSQL, ODBC, Gateway, or Tibero settings are missing, DBLINK errors may occur.

Gateway may fail to run if 32bit/64bit environments are mixed.

A restart is mandatory after modifying the TIP file.

In Windows environments, JVM path and Visual C++ Runtime libraries need to be verified.

 

 

 

Related to