A fix is available
APAR status
Closed as program error.
Error description
A DataStage job contains Teradata stage which maps a string value to timestamp, and the job ran ok. After using the Connector Migration Tool to convert the Teradata stage to a Teradata Connector stage, the job fails with error: Framework returned error for conversion from string to calendar: Inappropriate type code for field Since the stage has setup the Timestamp field as a string in the design schema, the Teradata Connector stage behaved as it was designed by throwing a conversion error. However, since both the string and calendar data (date, time, and timestamp) are known formats they can be converted from one form to another with a code change to the Teradata Connector and Server framework to implement that functionality.
Local fix
Problem summary
Teradata Connector - read job fails with Framework returned error for conversion from string to calendar.
Problem conclusion
The Customer is treating Timestamp field as string in his design schema. So, the TDCC is behaving as expected by throwing a conversion error.
Temporary fix
Comments
APAR Information
APAR number
JR45487
Reported component name
WIS DATASTAGE
Reported component ID
5724Q36DS
Reported release
870
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-01-21
Closed date
2013-02-26
Last modified date
2013-07-09
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WIS DATASTAGE
Fixed component ID
5724Q36DS
Applicable component levels
R850 PSY
UP
R870 PSY
UP
R910 PSY
UP
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"InfoSphere DataStage"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.7"}]
Document Information
Modified date:
07 October 2021