Hi,
I've successfully created a connection (linked server) in
SQL Server 2000 to an Oracle database (9i). I'm running
SQL Server on a WIN2K machine.
Now, I know that the connection is made because I can see
the list of tables and views under my Linked Server.
With that said, if I try ANY kind of query on these tables
I get a Msg 7320 error. The name of my Linked Server is
OracleSource. Here are some examples of queries that fail:
select * from openquery(OracleSource, 'select * from
ETA_USER.ABBR_DEVICE')
Select * From OracleSource..ETA_USER.ABBR_DEVICE
ETA_USER is the Schema and ABBR_DEVICE is the table name.
They are the same except one is using OpenQuery and not
the other. I know that this query works because I tried
it successfully in SQL Plus.
I have no idea what to try next and there doesn't seem to
be any help on the net (I've already consulted KB articles
270119, 251238, 248156 and 280106)
Any ideas, please!
Thanks, Skip.You might be encountering a limitation as described in :
244661 INFO: Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider
http://support.microsoft.com/?id=244661
You can also try dbcc trace (7300,3604) to see if you can get the provider
to return more information on why it is failing.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
Showing posts with label runningsql. Show all posts
Showing posts with label runningsql. Show all posts
Monday, March 19, 2012
Msg 7320
Labels:
connection,
created,
database,
insql,
linked,
microsoft,
msg,
mysql,
oracle,
runningsql,
server,
sql,
successfully,
win2k
Saturday, February 25, 2012
msdtc is causing my cluster to be unavailiable via it's virtual na
I have windows 2003 sp1 running in a 2-node cluster. The cluster is running
sql sp4. I tried failing over my cluster after a windows update and i'm not
sure if that's what threw my server's off or something else. But here's the
situation. I currently have the cluster group running on node 2, the msdtc
running on node 1 and the sql group running on node 2. When i move the msdtc
group to node 2 (ie.. the server which should be running all services)i cant
ping the sql virtual server by name or ip. I am however able to contact the
individual servers via their names sql1 and sql2. So basically i lose my
connection to the virtual sql server throughout my network when the msdtc is
running on the same server. Is there an update? upgrade? to the msdtc or
anything else i can do to fix this issue?
Ohh yes and there's no errors in the event log.
What are the Resource Group names, Resource Network Names, and Resource IP
addresses? What other resources a apart of each group?
Sounds like a DNS registration issue. Does the SQL Server group go offline
or fail over when the MSDTC group is moved to node 2?
Sincerely,
Anthony Thomas
"Sunny" <Sunny@.discussions.microsoft.com> wrote in message
news:12879549-04B5-454B-A44C-C075061EAEC1@.microsoft.com...
> I have windows 2003 sp1 running in a 2-node cluster. The cluster is
running
> sql sp4. I tried failing over my cluster after a windows update and i'm
not
> sure if that's what threw my server's off or something else. But here's
the
> situation. I currently have the cluster group running on node 2, the
msdtc
> running on node 1 and the sql group running on node 2. When i move the
msdtc
> group to node 2 (ie.. the server which should be running all services)i
cant
> ping the sql virtual server by name or ip. I am however able to contact
the
> individual servers via their names sql1 and sql2. So basically i lose my
> connection to the virtual sql server throughout my network when the msdtc
is
> running on the same server. Is there an update? upgrade? to the msdtc or
> anything else i can do to fix this issue?
> Ohh yes and there's no errors in the event log.
sql sp4. I tried failing over my cluster after a windows update and i'm not
sure if that's what threw my server's off or something else. But here's the
situation. I currently have the cluster group running on node 2, the msdtc
running on node 1 and the sql group running on node 2. When i move the msdtc
group to node 2 (ie.. the server which should be running all services)i cant
ping the sql virtual server by name or ip. I am however able to contact the
individual servers via their names sql1 and sql2. So basically i lose my
connection to the virtual sql server throughout my network when the msdtc is
running on the same server. Is there an update? upgrade? to the msdtc or
anything else i can do to fix this issue?
Ohh yes and there's no errors in the event log.
What are the Resource Group names, Resource Network Names, and Resource IP
addresses? What other resources a apart of each group?
Sounds like a DNS registration issue. Does the SQL Server group go offline
or fail over when the MSDTC group is moved to node 2?
Sincerely,
Anthony Thomas
"Sunny" <Sunny@.discussions.microsoft.com> wrote in message
news:12879549-04B5-454B-A44C-C075061EAEC1@.microsoft.com...
> I have windows 2003 sp1 running in a 2-node cluster. The cluster is
running
> sql sp4. I tried failing over my cluster after a windows update and i'm
not
> sure if that's what threw my server's off or something else. But here's
the
> situation. I currently have the cluster group running on node 2, the
msdtc
> running on node 1 and the sql group running on node 2. When i move the
msdtc
> group to node 2 (ie.. the server which should be running all services)i
cant
> ping the sql virtual server by name or ip. I am however able to contact
the
> individual servers via their names sql1 and sql2. So basically i lose my
> connection to the virtual sql server throughout my network when the msdtc
is
> running on the same server. Is there an update? upgrade? to the msdtc or
> anything else i can do to fix this issue?
> Ohh yes and there's no errors in the event log.
Subscribe to:
Posts (Atom)