The Scene: SQL Server 2008 R2 Cum 7 (10.50.1600.1) on a 64 bit Win 2008 R2 standard server Oracle 11.2.0 64-bit client w/OLE DB; TNSNames.ora verified through SLQPlus interactions The Script: Using 64 Bit Import and Export Wizard, construct a table/view copy from an Oracle View (access and connectiviity validated) using "Oralce Provider for OLE DB" into an idenical table on server using "SQL Server Native client 10.0" in an accessable Database in the 64 Bit world using Double-byte string (oh - so Visual Basic am I) types. The Problem: When perfoming the "Edit Mappings", All the "Types" report '130' for character data When "Next" -> "Convert Types without Conversion Checking" and [Source Information] Source Location : EPIW_PROD Source Provider : OraOLEDB.Oracle.1 Cannot locate the mapping file to map the provider types to SSIS types [Destination Information] Destination Location : USAROC9050VM005\HRMDM Destination Provider : SQLNCLI10 Mapping file (to SSIS type): S:\Program Files\Microsoft SQL Server\100\DTS\MappingFiles\MSSQLToSSIS10.XML [Conversion Table] SSIS conversion file: S:\Program Files\Microsoft SQL Server\100\DTS\binn\DtwTypeConversion.xml Supporting elements: Reviewed XML mapping files and have six for Oracle: OracleToMSSQL.XML OracleToMSSQL10.XML OracleToSSIS10.XML OracleClientToMSSQL.XML OracleClientToMSSQL10.XML OracleCLientToSSIS10.XML Result: Stored DTSX fails with event 12291 in the application event log (Just "FAiled", nothing else) Questions: Why is the type mapping file not being "found"? Where are the mappings stored/Modified? Is one of the map files the correct one for Oracle OLE DB? What is its name? How can these settings become corrupted? Workarrounds: Yes - manual mapping. Pain in the ... (you know!?) My feeling is that this Wizard SHOLD atomatically MAp data types by resolving the Mapping file - but I am not sure that the actual file needed to support OLD DB is available, or that there is one. Thanks for any/all the assistance Tony in Rochester, NYRichard A. "Tony" Eckel Rochester, NY

Tony, the workaround is Microsoft Connector for Oracle by Attunity for SSIS you could find this in our forum by doing a search first. As an aside, I do not blame anyone here, it is because Oracle 11 g appeared after SSIS was released.Arthur My Blog

Well - I tried thatlink, and then with this 1.1 version here, but there is nothing added to the 64 bit Import Export Wizard. While it may show up in the Developement Studio, there is a business reluctance to mount that on this server, so the Wizard is the best means to coble together simple flows... What am I missing? Are there additional steps to link Attunity into the 64 or 32 bit Wizards? TonyRichard A. "Tony" Eckel Rochester, NY