Page 1 of 1

Checksum error

Posted: Fri Feb 14, 2014 8:51 am
by Hung1261
I just ran into the same problem as noted here and not sure what stage in my job caused this error. Could you show me how to disable operation combination? Thanks.

Posted: Fri Feb 14, 2014 9:04 am
by chulett
Add $APT_DISABLE_COMBINATION to the job and set it to TRUE.

Posted: Fri Feb 14, 2014 9:38 am
by Hung1261
Thank you - Still showing the same messages, not any more that I can pin point to where the error is...

Posted: Fri Feb 14, 2014 10:16 am
by chulett
Shouldn't be the same... similar but not the same. Post the messages here.

Posted: Fri Feb 14, 2014 10:21 am
by Hung1261
APT_CombinedOperatorController(0),0: Failure during execution of operator logic. (shown few times)
APT_CombinedOperatorController(0),0: Internal Error: (!exportLog_->hasError()): checksum/checksum.C: 391
Traceback: Could not obtain stack trace; check that 'dbx' and 'sed' are installed and on your PATH
JnPocLocHierSK.LnChecksum_Sort,1: Failure during execution of operator logic.

Posted: Fri Feb 14, 2014 10:49 am
by chulett
Then it wasn't added or set correctly, it would seem. Can you double-check that it was added to the job and the value you set it to? Also, one of the first log messages should show all of the environment variables in play when the job runs, is it listed there?

Posted: Fri Feb 13, 2015 9:18 am
by Hung1261
This is very strange that the job ran for a few months and now error out with Chksum again...

$NTZ_DATA_SOURCE = NZSQL [$PROJDEF]
$APT_CONFIG_FILE = /opt/IBM/InformationServer/Server/Configurations/default.apt [$PROJDEF]
$APT_DISABLE_COMBINATION = True

Error:

Checksum,1: Internal Error: (!exportLog_->hasError()): checksum/checksum.C: 391
Traceback: Could not obtain stack trace; check that 'dbx' and 'sed' are installed and on your PATH

Posted: Fri Feb 13, 2015 9:42 am
by chulett
Time to get you into your own post... and here we are.

Next question is always going to be - what changed?

Posted: Fri Feb 13, 2015 2:23 pm
by qt_ky
I wonder if a NULL value appearing in the column being checksum'ed could cause such an error.

Posted: Tue Jul 25, 2017 3:58 am
by battaliou
We had a similar issue involving a lookup. Solution was to use a transformer with function NullToZero() on the lookup column.