Originally posted by: SystemAdmin

Hi All,

I have a map with three output cards that insert records in three separate tables. Occasionally, the third card will fail,and the error on the trace is

[i]<1452-2120>: The data could not be converted to the column override definitions.[/i]

Numbers at the front are variable.

This happens once every 20 records or so, it seems random. the problem isn't the input data though - if I rerun it with the same input the results are fine. anyone seen this before, or have any bright ideas?

Thanks.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: janhess

What version of WTX. What type of database and connection?
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

DSTX7.5, ODBC connection to an MS SQL Server 2K database. It's weird - I'm almost positive the database is at fault because the maps have been running fine for ages, but I can't find a way to interpret the error message that makes any sense.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: SystemAdmin

More details from a full (rather than error) trace:

<2372-2184>: The data could not be converted to the column override definitions.
<2372-2184>: Database load complete.
<2372-2184>: Returned status: (-1062) No suitable presentation could be found for a column
Doesn't seem to be any good reason for this that I can think of.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: SystemAdmin

Assuming the maps are running in a Windows environment, I can offer some generic ODBC suggestions you may want to try (ignore this post if maps are not running in Windows)

1. An ODBC trace will give more information. (ODBC Datasource Administrator...Tracing Tab... set file name...Start Tracing now). Note this trace can grow quite large and will significantly slow processing. Stop the trace as soon as you see the error, and examine the end of that trace.

2. I've seen ODBC problems fixed by installing the latest MDAC on the system running the maps. This can be found at http://msdn2.microsoft.com/en-us/data/aa937730.aspx which also contains a "checker" you may want to use first. I use MDAC 2.8 SP1 myself. You may want to consult with your DBA before installing MDAC (note the warning about using it on clusters on that page), especially if the system running the maps and the database are the same machine.

3. Insure the machine running the maps is fully patched (Windows Update), and the ODBC Driver version is up-to-date (version is found in ODBC Datasource Administrator "Driver" tab). I've had good results with version 2000.85.1117.00 for SQL Server. In particular, I've seen driver issues with "blobs" ("text" datatype in SQL Server), so if you are using datatypes other than the standard "ints", "chars", and "varchars" you may want to investigate the driver.

Sorry this doesn't directly address the error you are reporting, but is just some ODBC troubleshooting I've done in the past
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange