If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > Informix > Informix 2000 to SQL 2008R2SSIS error!

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 02-02-12, 11:44
mdgraves mdgraves is offline
Registered User
 
Join Date: Feb 2012
Location: Atlanta, GA, USA
Posts: 1
Red face Informix 2000 to SQL 2008R2 SSIS error! error message: Ambiguous column

I am involved in a project to create a reporting database from an Avaya telephony system (running on an Informix 2000 db) into a SQL 2008R2 database.

Specs. For the Informix 2000 Avaya, I have the OLOD4032.DLL (4.20.04.05) OpenLink Generic 32 bit v4.0. I am using SQL 2008R2, build 10.50.1777EntEdit on 64-bit platform (Win2008R2 EntEdit SvPk1). Using the ODBC Admin 32-bit tool, I was able to configure a DSN with connection success.

When I use the "import data" wizard (SSIS background) in SQL SSMS, I can get it to recognize the 32-bit older driver. I see my dbase, tables, etc., from source, and have created my target tables.

When I try to PREVIEW data, or run the SSIS / Wizard package, I get this error:

Error 0xc0202009: Data Flow Task 1: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "OpenLink ODBC Provider" Hresult: 0x80004005 Description: "[OpenLink][ODBC][Informix Server]Ambiguous column (item_type). (-324)". (SQL Server Import and Export Wizard)

Below is the query:

SELECT S.acd_no,
S.item_type,
S.item_name,
S.value,
S.descr
FROM root.synonyms s

Any HELP would be appreciated.

Last edited by mdgraves; 02-02-12 at 12:35.
Reply With Quote
  #2 (permalink)  
Old 03-20-12, 10:29
Mikefox1207 Mikefox1207 is offline
Registered User
 
Join Date: Mar 2012
Location: Somewhere In Europe
Posts: 9
Hello
I'm afraid, it could be a bit problematic, there are several differences between both systems, for example, there's no serial data type in MSSQL. I built a similar project, I do dbexport to unl files first, then SSiS imports from flat files. If you do not have to exchange data online, try in this way.

Regards
Mike
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On