Help appreciated...
We are having problems connecting to a Sybase 12.5 database.
OS = Solaris 8 box
Datastage version = 6.0.
Sybase and Datastage reside on same box.
------------------------------------------------------------
Error is:
---------
MSG = [DataDirect][ODBC 20101 driver][SQL Server]EMP not found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output)
------------------------------------------------------------
---------------------------------------------------------
This is what we have tested
-----------------------------------------------------------
Defined datasource Sybase1 in .odbc.ini
Included Sybase1 in uvodbc.config
Tested connectivity to Sybase1 via dssh "CONNECT" and it worked.
Ascential then asked us to run demoodbc and it didn't work - results are below.
$ pwd
/apps/datastage/datastage/Ascential/DataStage/DSEngine
$ . ./dsenv
$ cd -
/apps/datastage/datastage/Ascential/DataStage/branded_odbc/demo
$ ./demoodbc Sybase1 -UID edw -PWD passwordx
./demoodbc DataDirect Technologies, Inc. ODBC Sample Application.
./demoodbc: will connect to data source 'Sybase1' as user 'edw/passwordx'.
6066:
[DataDirect][ODBC 20101 driver]6090
......SQLExecute has Failed. RC=-1
SQLSTATE = 53
NATIVE ERROR = 208
MSG = [DataDirect][ODBC 20101 driver][SQL Server]EMP not found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output)
Edited by - zinna on 12/02/2002 23:48:23
Sybase 12.5 Connection
Moderators: chulett, rschirm, roy
-
ray.wurlod
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
What you got is cool.
[DataDirect][ODBC 20101 driver][SQL Server] allow you to determine that the connection was made to SQL Server satisfactorily, as does the fact that you received a non-zero DBMS error code (this means that SQL Server generated the error code 208, which means "table does not exist").
So, there's no EMP table in SQL Server. That's OK, the test of the fact that the ODBC driver can connect to SQL Server has been satisfactory. And that was the point of the exercise.
(If you're not happy with this, create an EMP table in SQL Server matching the dBase table supplied in the test suite, test again, and it will return a result set.)
[DataDirect][ODBC 20101 driver][SQL Server] allow you to determine that the connection was made to SQL Server satisfactorily, as does the fact that you received a non-zero DBMS error code (this means that SQL Server generated the error code 208, which means "table does not exist").
So, there's no EMP table in SQL Server. That's OK, the test of the fact that the ODBC driver can connect to SQL Server has been satisfactory. And that was the point of the exercise.
(If you're not happy with this, create an EMP table in SQL Server matching the dBase table supplied in the test suite, test again, and it will return a result set.)