Oracle to SQL

[Former Member]

Hi...,

I had an old R/3 system on top of SQL/NT (A) and another SQL/NT server (B) is used to VB application.

Now, R/3 system (A) is migrated to Oracle/UNIX (C).

I have a lot of interface programs from R/3 on SQL/NT (A) to another SQL/NT server (B). Coding is using "EXEC SQL" syntax to read/update table on (B) directly.

Now, after migration, I tried to connect between R/3 on Oracle/UNIX (C) and SQL/NT server (B) but it didn't work.

Any idea what the problem is during migration?

Would you please to assist me how to correct it?

Thanks in advance.

kha

[reiner_hille-doering · Accepted solution]

It seems that you are using the ABAP "multiconnect" feature. This is supposed to work even if the databases come from a different vendors. You need of cause the necessrary client libraries be installed on the SAP Application Server(s). This would mean in your case that you need a SAP DBSL (Database Support Library) for MS SQL Server. I cannot really imagine that this exists for UNIX, because it would require Microsoft's SQL Server client libraries for UNIX.

In the other direction it would work, because there are NT-based DBSLs for both MSSQL and Oracle.

[Former Member · Accepted solution]

Thanks for your reply.

According to your message, I have to install SAP DBSL for MS SQL Server on my R/3 system over Oracle/Unix, isn't it?

Would you please guide me more detail?

Thanks..

[reiner_hille-doering · Accepted solution]

> According to your message, I have to install SAP DBSL

> for MS SQL Server on my R/3 system over Oracle/Unix,

> isn't it?

Yes. But the problem is that I assume that the SAP DBSL for MS SQL Server does NOT exit for UNIX. The DBSL is just a shared library (DLL on Windows) that sits on top of the DB vendor's client libraries.

The SQL Server DBSL for Windows is called "dbmssslib.dll", but this depends on the MS SQL Server client (some Microsoft DLLs that implement the protocoll to talk to MSSQL Server). I don't think that these DLLs exist for UNIX.