APAR status
Closed as program error.
Error description
When Netezza Operator aborts the job due to maximum bad row count exceeded, it doesn't log the actual reason, "ERROR: External Table : count of bad input rows reached maxerrors limit". Steps to recreate the problem: Create a RowGenerator--->Netezza Operator job Use Integer and nvarchar(10) colums set number of rows to 10000 and execute the job Notice that it fails with Operation canceled error message. ERROR from ExecDirect: Operation canceled
Local fix
Problem summary
Netezza Operator with newer Netezza Client ODBC Drivers are logging all the ODBC Error messages, for example: when the number of rows exceeded the maximum error limit, the error message gets displayed is: Opertion Canceled instead of the maxerrors limit reached. Due to this, the user is forced to check the nzlog files to know the actual reason for the failure and can take corrective action.
Problem conclusion
Code has been corrected to log all the error messages related so that user can understand and take corrective actions.
Temporary fix
Check the nzlog log file.
Comments
APAR Information
APAR number
JR45728
Reported component name
WIS QUALITYSTAG
Reported component ID
5724Q36QS
Reported release
870
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-02-13
Closed date
2013-02-22
Last modified date
2013-02-22
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 QUALITYSTAG
Fixed component ID
5724Q36QS
Applicable component levels
R910 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSVSBF","label":"InfoSphere QualityStage"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.7"}]
Document Information
Modified date:
17 October 2021