Checksum error

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
Hung1261
Participant
Posts: 4
Joined: Fri Feb 14, 2014 8:47 am

Checksum error

Post 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.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Add $APT_DISABLE_COMBINATION to the job and set it to TRUE.
-craig

"You can never have too many knives" -- Logan Nine Fingers
Hung1261
Participant
Posts: 4
Joined: Fri Feb 14, 2014 8:47 am

Post by Hung1261 »

Thank you - Still showing the same messages, not any more that I can pin point to where the error is...
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Shouldn't be the same... similar but not the same. Post the messages here.
-craig

"You can never have too many knives" -- Logan Nine Fingers
Hung1261
Participant
Posts: 4
Joined: Fri Feb 14, 2014 8:47 am

Post 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.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post 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?
-craig

"You can never have too many knives" -- Logan Nine Fingers
Hung1261
Participant
Posts: 4
Joined: Fri Feb 14, 2014 8:47 am

Post 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
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Time to get you into your own post... and here we are.

Next question is always going to be - what changed?
-craig

"You can never have too many knives" -- Logan Nine Fingers
qt_ky
Premium Member
Premium Member
Posts: 2895
Joined: Wed Aug 03, 2011 6:16 am
Location: USA

Post by qt_ky »

I wonder if a NULL value appearing in the column being checksum'ed could cause such an error.
Choose a job you love, and you will never have to work a day in your life. - Confucius
battaliou
Participant
Posts: 155
Joined: Mon Feb 24, 2003 7:28 am
Location: London
Contact:

Post by battaliou »

We had a similar issue involving a lookup. Solution was to use a transformer with function NullToZero() on the lookup column.
3NF: Every non-key attribute must provide a fact about the key, the whole key, and nothing but the key. So help me Codd.
Post Reply