Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
 Posted - 2004-11-15 : 21:44:49
|
| I'm trying to access cms informix data via sql qa. The link shows tables but if i try to query using : select * from lserver...tbl1, the error shows up.Server: Msg 7399, Level 16, State 1, Line 1OLE DB provider 'MSDASQL' reported an error. [OLE/DB provider returned message: Unspecified error][OLE/DB provider returned message: [OpenLink][ODBC][Driver]General error][OLE/DB provider returned message: [OpenLink][ODBC][Driver]General error]OLE DB error trace [OLE/DB Provider 'MSDASQL' IDBSchemaRowset::GetRowset returned 0x80004005: I've tried google and the links were specific, couldn't find one that uses informix.My real problem is this: we've recently restored data to the informix system, but the weird problem is, third party tool can generate a report on the restored data but sql server could not see this data. I was informed that the data is pseudo data.Please help, any idea appreciated.--------------------keeping it simple... |
|
|
Kristen
Test
22859 Posts |
Posted - 2004-11-16 : 00:42:36
|
| Did you litterally mean "lserver...tbl1" or do you need to provide the server/owner?"we've recently restored data"Original permissions still there / the same passwords etc.?Drop and recreate the linked server? (Can't imagine why that would help - just thinking out loud!)Kristen |
 |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2004-11-16 : 01:06:38
|
i provided all of the name part, still same error.actually the informix server (according to the vendor, is one giant database), if you restore something, it'll add an additional field that tells you which row was restored and which one is realtime). So you get one unique table in the entire server.i created another linked server, but same errors (i appreciate the thought).I was about to check the validity of the claim (vendor)by querying through QA. Another error i'm encountering is (removing the where clause):Server: Msg 7313, Level 16, State 1, Line 1Invalid schema or catalog specified for provider 'MSDASQL'.OLE DB error trace [Non-interface error: Invalid schema or catalog specified for the provider.].quote:
Originally posted by Kristen
Did you litterally mean "lserver...tbl1" or do you need to provide the server/owner?"we've recently restored data"Original permissions still there / the same passwords etc.?Drop and recreate the linked server? (Can't imagine why that would help - just thinking out loud!)Kristen
--------------------keeping it simple... |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2004-11-16 : 01:34:10
|
Those error messages are just Fantastic aren't they? Or do I mean Fantasy?  Hopefully someone with some actual knowledge of informix will be along in a bit ...Kristen |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2004-11-16 : 01:42:25
|
ha ha ha, they're mighty incredible (unspecified error!), just makes you want to pick up the phone and call helpdesk and spend $ just to know what the error message actually means, then a couple more of $, to have them "fix" the problem.thanks Kristen for the responses  (and i'm thankful you're still awake).--------------------keeping it simple... |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2004-11-16 : 20:47:47
|
| any idea will be greatly appreciated...--------------------keeping it simple... |
|
|
|
MacTed
Starting Member
1 Post |
Posted - 2004-11-30 : 11:23:00
|
| Hi, Jen --The error you need to deal with is coming from the OpenLink ODBC driver, `[OpenLink][ODBC][Driver]General error`, and may be due to a number of scenarios.The most common cause is simple incompatibility with the Microsoft SQL Server Linked Server feature, particularly if your OpenLink driver is Release 4.1 or earlier (shipped prior to 2002). Full compatibility with OLE DB and this SQL Server feature was not delivered by OpenLink until Release 5.x, but it is definitely part of the currently shipping Releases 5.1 and 5.2 (depending on platforms and databases involved). Compatibility was improved dramatically in Release 4.2, over all previous versions.Fastest resolution will come if you open a Support Case through OpenLink's online Support Center, [url]http://support.openlinksw.com/[/url]. There is no charge for this service. Best regards,TedTed Thibodeau, Jr. // voice +1-781-273-0900 x32Evangelism & Support // [url]mailto:tthibodeau@openlinksw.com[/url]OpenLink Software, Inc. // [url]http://www.openlinksw.com/[/url]Universal Data Access and Virtual Database Technology ProvidersOpenLink Blogs[url]http://www.openlinksw.com/weblogs/uda/[/url][url]http://www.openlinksw.com/weblogs/virtuoso/[/url][url]http://www.openlinksw.com/blog/~kidehen/[/url] |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2004-12-01 : 00:57:33
|
Thank you Ted, i'll check the site, we have 3.2, so i'm hoping that's the problem. --------------------keeping it simple... |
|
|
|
|
|
|
|
|
linked server problem