Page 1 of 1

blink error not in log

Posted: Mon Oct 06, 2008 12:42 pm
by boligoma
Hi all,

I'm trying to write a hashed file with 123 millions from DB2. At some point, I have the error:

Program "DSD.StageRun": Line 631, Internal data error.
File '/opt/IBM/software/DataStage/InformationServer/DS_HASH/HASH/DATA.30':
Computed blink of 0x870 does not match expected blink of 0x0!
Detected within group starting at address 0x80000000!

I've searched the forum, but the suggestions are only to clear the log file, and run it again, I've tried several times by cleaning up the hash and create the file again.

The data system has about 112 free GB, I don't know what else could be the mystake.

Thanks!

Ismael

Posted: Mon Oct 06, 2008 1:05 pm
by chulett
A job's "log file" is a hashed file and a blink error in a hashed file is a blink error, even if it's not a log. You've corrupted the hashed file by trying to write more than 2.2GB of data to it, you'll need to switch it to 64BIT.

Posted: Mon Oct 06, 2008 3:13 pm
by boligoma
Thanks chulett, unfortunately I can't see what suggestions you have because of the Premium Content. How I can turnaround this issue?, I'm thinking using several hashed files on different jobs. Is this logical?

Posted: Mon Oct 06, 2008 3:18 pm
by boligoma
Thanks chulett, unfortunately I can't see what suggestions you have because of the Premium Content. How I can turnaround this issue?, I'm thinking using several hashed files on different jobs. Is this logical?

Posted: Mon Oct 06, 2008 3:33 pm
by chulett
Search the forums for "64BIT", that should turn up quite a number of conversations on the subject of large hashed files.

Posted: Mon Oct 06, 2008 3:42 pm
by ray.wurlod
Get a premium membership.

Premium membership is one of the mechanisms through which the hosting and bandwidth charges incurred by DSXchange are defrayed. It's not expensive, at less than 30c per day.