468,556 Members | 2,117 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 468,556 developers. It's quick & easy.

MSSQL linked server to Oracle RDB

Hi,

I am using MSSQL 2k, and I have a linked server set up to an Oracle RDB
version 7. It goes thru an OLE DB provider for ODBC drivers on a system
DSN, which is using an Oracle RDB ODBC driver version 3.0.2.

The problem occurs when I send a query that returns zero rows - query
analyzer just does not complete nor return. This problem is not seen
when there are rows being returned.

I ran a trace and this is the error message I get-:
Non-interface error: OLE DB provider MSDASQL returned an incorrect
value for DBPROP_CONCATNULLBEHAVIOR which should be either
DBPROPVAL_CB_NULL or DBPROPVAL_CB_NON_NULL

Anybody who experienced this before has a solution?

Thanks,
Lawrence

Jul 23 '05 #1
2 5872
lawk wrote:
Hi,

I am using MSSQL 2k, and I have a linked server set up to an Oracle RDB
version 7. It goes thru an OLE DB provider for ODBC drivers on a system
DSN, which is using an Oracle RDB ODBC driver version 3.0.2.

The problem occurs when I send a query that returns zero rows - query
analyzer just does not complete nor return. This problem is not seen
when there are rows being returned.

I ran a trace and this is the error message I get-:
Non-interface error: OLE DB provider MSDASQL returned an incorrect
value for DBPROP_CONCATNULLBEHAVIOR which should be either
DBPROPVAL_CB_NULL or DBPROPVAL_CB_NON_NULL

Anybody who experienced this before has a solution?

Thanks,
Lawrence


Oracle version 7 is Jurassic era and unsupported by Oracle.
Unless Microsoft can help you you are on your own.

And if you are in the US you are not Sarbanes-Oxley compliant
if that is a concern.
--
Daniel A. Morgan
http://www.psoug.org
da******@x.washington.edu
(replace x with u to respond)
Jul 23 '05 #2
http://support.microsoft.com/default...b;en-us;280106

Also, you could try experimenting with SET CONCAT_NULL_YIELDS_NULL,
since that seems to be mentioned in the error.

Apart from that, common advice is to try the latest (or at least a
different) version of MDAC, or try using Oracle's OLE DB provider
instead of Microsoft's (or vice versa).

Although if Oracle 7 is unsupported (as Daniel mentioned), then you may
not get much help from either MS or Oracle on this.

Simon

Jul 23 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

3 posts views Thread by francisl | last post: by
3 posts views Thread by David Gray | last post: by
2 posts views Thread by tim.pascoe | last post: by
4 posts views Thread by arichie | last post: by
8 posts views Thread by Yusuf INCEKARA | last post: by
4 posts views Thread by kenneth.osenbroch | last post: by
1 post views Thread by UniDue | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.