Skip to Content
-1

SSMA Migration tool is not able to connect to Sybase ASE

Oct 06, 2017 at 08:38 AM

356

avatar image

Hi All,

We are trying to migrate Sybase DB (version 16) to MS SQL2012 DB

SSMA is unable to connect to the Sybase ASE.

I tried the following methods.

a. Standard mode, filled using the settings present in ODBC Console

Server name : BI4
Server Port : 2638
User : dba
Password : <password>

Error message box:-
ERROR [08001][Sybase][ODBC Driver]Client unable to establish a connection

b.Advanced method, using connection settings available in Microsoft docs, https://docs.microsoft.com/en-us/sql/ssma/sybase/connect-to-sybase-sybasetosql

driver=Adaptive Server Enterprise;Server=BI4;uid=dba;pwd=<Password>;Port=2638;

Error message box:-

ERROR [08001][Sybase][ODBC Driver]Client unable to establish a connection

c.Advanced mode, using simple ODBC DSN string

DSN=BI4_CMS_DSN

The output dock says:

Connection to Sybase established successfully.

Connection string: DSN=BI4_CMS_DSN

A few minutes later it throws an error message box saying:

Error collecting data. See inner exception for details.



On searching on the last error “Error collecting data. See the inner exception for details.” I found this link https://support.microsoft.com/en-ie/help/2020727/-error-collecting-data--see-the-inner-exception-for-details--message-w

<snippet from the above link>

Cause

0" style="box-sizing: border-box; outline: none; margin-right: auto; margin-left: auto; max-width: 1600px; width: 896px; color: rgb(0, 0, 0); font-family: "Segoe UI", "Segoe UI Web", "Segoe UI Symbol", "Helvetica Neue", "BBAlpha Sans", "S60 Sans", Arial, sans-serif; background-color: rgb(255, 255, 255);">

SQL Server Migration Assistant (SSMA) uses Sybase’s OLEDB provider to connect to Sybase. The error generally occurs when the Sybase's OLEDB provider is not installed on the system where SSMA is running.

<\snippet from the above link>

Questions:

a.If I am using ODBC Driver, I am not supposed to be asked about OLEDB?

b.If OLEDB is required where do I download this driver from? I did not find this from Sybase website.

c.Why is the connections strings mention in the instructions not working and simple DSN string seems to help? Is the ODBC driver version not compatible with SSMA? This is the version installed.

d.How to make this finally work?


10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

3 Answers

Bret Halford
Oct 09, 2017 at 06:31 PM
1

I will note that it would be unusual for the login name "dba" to be used, ASE's default administrator login is named "sa". "dba" could be used and assigned sa_role and sso_role, but it would be an unusual customization of an ASE system.

Share
10 |10000 characters needed characters left characters exceeded
Luis Darui
Oct 09, 2017 at 05:52 PM
-1

I Rishi,

Looks like you need assistance with SQL Server Migration Assistance, which is not used by SAP at all. You should contact Microsoft or get help in MSDN about this. The SAP Community will most likely assist you with the usage of SAP software and the features used by SAP.

Here are the hyperlinks to the official documentation about SSMA and SSMA for SAP ASE:

https://docs.microsoft.com/en-us/sql/ssma/sql-server-migration-assistant

https://docs.microsoft.com/en-us/sql/ssma/sybase/sql-server-migration-assistant-for-sybase-sybasetosql

Share
10 |10000 characters needed characters left characters exceeded
Dawn Kim
Oct 12, 2017 at 08:39 PM
0

Hi,
When using Microsoft tools they can connect with oledb and odbc. Usually with oledb it uses it's own converts to odbc using it's own internal driver.

What I am seeing from the documents is that SSMA uses oledb.

You need to get the SDK for SAP ASE. Follow this other SCN on how to get the developers edition.

https://answers.sap.com/questions/132428/how-do-i-download-the-ase-sdk-without-having-a-sup.html

Please note you will need to get the SDK 15.7 version. We dropped the oledb driver from the SDK 16.0 series.

Thanks,
Dawn Kim

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Installing the driver seems to pan out, but now it's throwing

[53018]
[Message Class: 16]
[Message State: 0]
[Transaction State: 1]
[Native Code: 257]
[ASEOLEDB]SQL Anywhere Error -157: Cannot convert '08/10/09' to a timestamp

Any idea on this?

0