Error with source column type changing

• Dug Fazzani

  SSC Enthusiast

  Points: 106

  More actions

  September 13, 2010 at 8:40 am

  #146958

  Hi,

  We have several SSIS packages looking at an oracle database.

  They work fine for about a month and then suddenly all fail at the same time.

  The message we get is

  Code: 0xC020837F

  Description: The data type of "output column "MARKET_AREA" (198)" does not match the data type "System.String" of the source column "MARKET_AREA"

  This happens for several columns for several tables.

  The only thing I notice between them is that they are all fields we have coded in for example simply coding 'M62' for this field in the select statement.

  The database hasn't changed at all - and anyway as I said they are all text fields we have hard coded into the SQL.

  We can fix the packages by simply double clicking on the bits that fail and accepting the auto fix SSIS generates for us but this solution only lasts a few weeks and then it breaks again.

  Any ideas?

  Doug

• Dug Fazzani

  SSC Enthusiast

  Points: 106

  More actions

  September 15, 2010 at 7:07 am

  #1221299

  Any advice?

  We're really getting it in the neck to stop this happening and I have no idea how.

  Thanks

• exe2911jan

  Newbie

  Points: 9

  More actions

  October 26, 2010 at 2:04 am

  #1242069

  Hi Dug,

  I am currently looking in to this also and was wondering if you have found a result ?

  Would be VERY interested in ANY suggestions.

  Found this reply somewhere:

  The error is correct I think both VFP Char and SQL Server Varchar maps to .NET bytes a value type and not string which is a reference type.

  Change SQL Server column to Nvarchar instead of varchar that may fix it

  It could give you a hint - did not solve my problem though. Think problem/ solution is with first line.

  Have now spend a week now 24/7 with this issue - what a joke ......

  Would appreciate any feedback.

  cheers

  Djan

• Dug Fazzani

  SSC Enthusiast

  Points: 106

  More actions

  October 26, 2010 at 2:12 am

  #1242071

  Hiya,

  We've actually upgraded to SQL Server 2008 and *so far* we have not had this problem.

  But then again it was intermittent so it might not have solved it for definite.

  But it does look promising so far.