Hi everyone
I will really appreciate any insights into why this is happening. I am at a
loss to figure out where to look next.
We have two SQL7s: production with enterprise (unlimited users) and test
with standard (6 users).
I have a linked server defined on each, both pointing to the same oracle DB,
same definition exactly.
On production:
select count(*) from ORAPROD..OWNER.TABNAME
works fine, but
select count(*) from ORAPROD...TABNAME
Server: Msg 7314, Level 16, State 1, Line 1
OLE DB provider 'MSDAORA' does not contain table 'TABNAME'
On test:
select count(*) from ORAPROD..OWNER.TABNAME
Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'MSDAORA' reported an error. The provider did not give any
information about the error.
select count(*) from ORAPROD...TABNAME
works fine
What causes the difference? And how might I keep the test and production
SQL identical? Currently I test the current machine and alter the SQL to
conform to what works.
To make things even more interesting, running the above production SQL first
thing in the morning gives
OLE DB provider 'MSDAORA' reported an error. [SQLSTATE 42000] (Error 7399)
[SQLSTATE 01000] (Error 7312) [SQLSTATE 01000] (Error 7312). The step
failed.
But re-running it immediately works fine.
Never had a problem on test.
7312: Invalid use of schema and/or catalog for OLE DB provider '%ls'. A
four-part name was supplied, but the provider does not expose the necessary
interfaces to use a catalog and/or schema.
What is happening behind the scenes here to invalidate(?) the link?
Thanks
Trevor
Trevor Williams
DBA
RAC Group of WA
08 9421 4282
Disclaimer.
This e-mail is private and confidential. If you are not the intended
recipient, please advise us by return e-mail immediately, and delete
the e-mail and any attachments without using or disclosing the
contents in any way. The views expressed in this e-mail are those
of the author, and do not represent those of this company unless
this is clearly indicated.
You should scan this e-mail and any attachments for viruses.
This company accepts no liability for any direct or indirect
damage or loss resulting from the use of any attachments to this e-mail.
MS Sql Server LazyDBA home page