APAR status
Closed as program error.
Error description
The Teradata Plugin stage does not provide the RDBMS return codes for rejected rows, etc. This is provided for the other RDBMS plugins.
Local fix
Problem summary
No rejects are being written when encountering "Referential constraint violation" - messages showing as informational.
Problem conclusion
Teradata Plugin stage is not able to capture the Error codes when encountering "Referential constraint violation".After applying the patch, the it should capture the error messages thrown by teradata stage such as 2700 for referential integrity violation. The Teradata API should capture the error messages thrown by teradata stage such as 2700 for referential integrity violation. It could log the error message in the Director-log with the Error code 2700.
Temporary fix
Providing the Patch : JR38333
Comments
APAR Information
APAR number
JR38333
Reported component name
WIS DATASTAGE
Reported component ID
5724Q36DS
Reported release
752
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-11-24
Closed date
2011-01-11
Last modified date
2011-01-11
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
R752 PSY
UP
R753 PSY
UP
R800 PSY
UP
R801 PSY
UP
R802 PSY
UP
R810 PSY
UP
R850 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"IBM InfoSphere DataStage"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.2","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
11 January 2011