Closed as program error.
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
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.
Code has been corrected to log all the error messages related so that user can understand and take corrective actions.
Check the nzlog log file.
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels
Rate this page:
Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.