adding odbc to linked server

I have a odbc driver to a customized text file system (on aix), I am using
winsql to query from that sysem, does sql server allow to register it as a
linked server. I am guessing i should be able to register as i have odbc
driver to the system. Please suggest me if it is possible
When i try to do it, i am getting message like i mentioned here
Error 7399: OLE DB provider 'MSDASQL' reported an error.
Client unable to establish connection error:1408F0C6:SSL3_GET_RECORD: packet
length too long]
OLE DB error trace [OLE/DB Provider 'MSDASQL' IDBInitialize::Initialize
returned 0x80004005: ],
Thanks,
Subbu.
Hi
ODBC datasource use the MSDASQL provider and require a System DSN. This
error can occur if it is a User DSN. See sp_addlinkedserver in books online
for an example. If you still have problems you may want to turn ODBC tracing
on to debug it.
John
"Subbaiahd" <subbaiahd@.hotmail.com> wrote in message
news:%23XK7zvYzEHA.576@.TK2MSFTNGP14.phx.gbl...
>I have a odbc driver to a customized text file system (on aix), I am using
> winsql to query from that sysem, does sql server allow to register it as a
> linked server. I am guessing i should be able to register as i have odbc
> driver to the system. Please suggest me if it is possible
> When i try to do it, i am getting message like i mentioned here
> Error 7399: OLE DB provider 'MSDASQL' reported an error.
> Client unable to establish connection error:1408F0C6:SSL3_GET_RECORD:
> packet
> length too long]
> OLE DB error trace [OLE/DB Provider 'MSDASQL' IDBInitialize::Initialize
> returned 0x80004005: ],
>
> Thanks,
> Subbu.
>
|||There is a problem with odbc driver after i corrected it i am able to
register as linked server without any errors, and i can see the list of
tables in enterprise manager, but I am not able to run a query , see below
for error message i am getting for a query
query:
select CLI_ID, CLIENT_NAME
from IMPACT...CLI WHERE CLI_ID = '00001083'
error message:
Server: Msg 306, Level 16, State 1, Line 1
The text, ntext, and image data types cannot be compared or sorted,
except when using IS NULL or LIKE operator.
Can you please give me more details how to to turn ODBC tracing on to debug.
Thanks,
Subbu.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:enu1IB0zEHA.1452@.TK2MSFTNGP11.phx.gbl...
> Hi
> ODBC datasource use the MSDASQL provider and require a System DSN. This
> error can occur if it is a User DSN. See sp_addlinkedserver in books
online
> for an example. If you still have problems you may want to turn ODBC
tracing[vbcol=seagreen]
> on to debug it.
> John
> "Subbaiahd" <subbaiahd@.hotmail.com> wrote in message
> news:%23XK7zvYzEHA.576@.TK2MSFTNGP14.phx.gbl...
using[vbcol=seagreen]
a
>
|||Hi
In the ODBC Data Source Manager applet (either in control panel or on
the Administrators menu), you will see a trace tab, with a button to
start tracing. At a guess CLI_ID is being interpreted as text, ntext
or image and that you need to specify CLI_ID LIKE '00001083'.
John
"Subbaiahd" <subbaiahd@.hotmail.com> wrote in message news:<u8FDdVX0EHA.2624@.TK2MSFTNGP11.phx.gbl>...[vbcol=seagreen]
> There is a problem with odbc driver after i corrected it i am able to
> register as linked server without any errors, and i can see the list of
> tables in enterprise manager, but I am not able to run a query , see below
> for error message i am getting for a query
> query:
> select CLI_ID, CLIENT_NAME
> from IMPACT...CLI WHERE CLI_ID = '00001083'
> error message:
> Server: Msg 306, Level 16, State 1, Line 1
> The text, ntext, and image data types cannot be compared or sorted,
> except when using IS NULL or LIKE operator.
>
> Can you please give me more details how to to turn ODBC tracing on to debug.
> Thanks,
> Subbu.
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:enu1IB0zEHA.1452@.TK2MSFTNGP11.phx.gbl...
> online
> tracing
> using
> a
|||I started odbc tracing , but could not understand the log. If you want to
see i can paste its contents but the log file size is 2MB. I dont have a
clue to proceed further, can you please help me.
Query:
select CLI_ID, CLIENT_NAME
from IMPACT...CLI WHERE CLI_ID like '00001083'
Error message:
Server: Msg 7356, Level 16, State 1, Line 1
OLE DB provider 'MSDASQL' supplied inconsistent metadata for a column.
Metadata information was changed at execution time.
OLE DB error trace [Non-interface error: Column 'CLI_ID' (compile-time
ordinal 1) of object 'CLI' was reported to have a DBCOLUMNFLAGS_ISLONG of
128 at compile time and 0 at run time].
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:3b81e6a.0411231254.6732697d@.posting.google.co m...
> Hi
>
> In the ODBC Data Source Manager applet (either in control panel or on
> the Administrators menu), you will see a trace tab, with a button to
> start tracing. At a guess CLI_ID is being interpreted as text, ntext
> or image and that you need to specify CLI_ID LIKE '00001083'.
> John
>
> "Subbaiahd" <subbaiahd@.hotmail.com> wrote in message
news:<u8FDdVX0EHA.2624@.TK2MSFTNGP11.phx.gbl>...[vbcol=seagreen]
below[vbcol=seagreen]
debug.[vbcol=seagreen]
This[vbcol=seagreen]
it as[vbcol=seagreen]
odbc[vbcol=seagreen]
error:1408F0C6:SSL3_GET_RECORD:[vbcol=seagreen]
IDBInitialize::Initialize[vbcol=seagreen]
|||Hi
Searching google for "OLE DB provider 'MSDASQL' supplied inconsistent
metadata for a column" turns up quite a few posts, so you can gain
solace in that you are not alone! If you ran the query without the
where clause does it still cause a problem? Suggestions from other
posts include using OPENQUERY or using the Oracle OLEDB driver
instead. This post points you to a KB article on the error and how you
may gain more information:
http://tinyurl.com/55x93
HTH
John
"Subbaiahd" <subbaiahd@.hotmail.com> wrote in message news:<#wvDYOk0EHA.3500@.TK2MSFTNGP09.phx.gbl>...[vbcol=seagreen]
> I started odbc tracing , but could not understand the log. If you want to
> see i can paste its contents but the log file size is 2MB. I dont have a
> clue to proceed further, can you please help me.
> Query:
> select CLI_ID, CLIENT_NAME
> from IMPACT...CLI WHERE CLI_ID like '00001083'
> Error message:
> Server: Msg 7356, Level 16, State 1, Line 1
> OLE DB provider 'MSDASQL' supplied inconsistent metadata for a column.
> Metadata information was changed at execution time.
> OLE DB error trace [Non-interface error: Column 'CLI_ID' (compile-time
> ordinal 1) of object 'CLI' was reported to have a DBCOLUMNFLAGS_ISLONG of
> 128 at compile time and 0 at run time].
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:3b81e6a.0411231254.6732697d@.posting.google.co m...
> news:<u8FDdVX0EHA.2624@.TK2MSFTNGP11.phx.gbl>...
> below
> debug.
> This
> online
> tracing
> using
> it as
> a
> odbc
> error:1408F0C6:SSL3_GET_RECORD:
> IDBInitialize::Initialize