RE: Schema Change of a Progress DB causes Linked Server to Fail
- From: v-xuwen@xxxxxxxxxxxxxxxxxxxx (Vincent Xu [MSFT])
- Date: Tue, 06 Jun 2006 06:58:22 GMT
Hi Brian ,
First, I still suggest you contact Progress for more information about this
issue.
However, at SQL side, My suggestion is:
Check to see if the System DSN that was used to create the linked server is
correct. If you used a provider string to configure the linked server, you
must make sure that the driver name in the provider string is correct.
Also, you can check following article:
PRB: Distributed Queries Return Error 7356 with MSDAORA
http://support.microsoft.com/default.aspx?scid=kb;[LN];251238
Hope this helps.
Best regards,
Vincent Xu
Microsoft Online Partner Support
======================================================
Get Secure! - www.microsoft.com/security
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties,and confers no rights.
======================================================
--------------------
(P35634)Date: Mon, 05 Jun 2006 22:50:20 -0400
Subject: Schema Change of a Progress DB causes Linked Server to Fail
From: "Brian Drab" <kaplan@xxxxxxxxxxxxxx>
Organization: Kaplan Trucking Company
Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-ID: <op.tapd560b14a6ot@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
User-Agent: Opera M2/8.54 (Win32, build 7730)
Newsgroups: microsoft.public.sqlserver.connect
NNTP-Posting-Host: 69-165-32-14.clvdoh.adelphia.net 69.165.32.14
Lines: 1
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.connect:47704
X-Tomcat-NG: microsoft.public.sqlserver.connect
We use SQL Server 2000 and have a Linked Server to a Progress 9.1E
Database. Everything works fine until a schema change is made in the
Progress database. We then get an error message similar to the following:
OLE DB provider 'MSDASQL' supplied inconsistent metadata.
An extra column was supplied during execution that was not found at
compile time.[Non-interface error: OLE DB provider returned an extra
column at execution time: ProviderName='MSDASQL', ColumnName=<column
name>',
Rowset="pub"."tablename"]."
After researching this at the progress site I did find an article
that basically explains the following cause and fix.
Cause:
Microsoft Linked Server instance caches metadata for faster query
resolution. This does not get properly refreshed when the Progress
Database resides on a remote server. If Progress Database resides on the
same machine as Linked Server instance, problem does not occur.
Fixes:
Drop and readd Linked Server instance in the Enterprise Manager. Contact
Microsoft for more information.
We do Drop and readd the Linked Server however the same problem persists.
What am I missing? Is there a different way to delete the cache and force
a refresh of the linked server?
Thank you.
.
- References:
- Schema Change of a Progress DB causes Linked Server to Fail
- From: Brian Drab
- Schema Change of a Progress DB causes Linked Server to Fail
- Prev by Date: Re: Is it possible to make linked server from SQL Server 2000 to MySQL
- Next by Date: Re: HELP - Connecting SQL Express Edition
- Previous by thread: Schema Change of a Progress DB causes Linked Server to Fail
- Next by thread: HELP - Connecting SQL Express Edition
- Index(es):
Relevant Pages
|
