Page 1 of 1

Computed blink of 0x830 does not match expected blink

Posted: Mon Nov 16, 2009 11:36 pm
by arnie_nits
Hi,

I was running a job and it aborted halfway.

I tried to run the job again but it didnot run atall. This job was running sucessfully before. I just added 1 extra column this time.

When I tried to run the job status in director I got error:

Error selecting from log file RT_LOG10197
Command was: SSELECT RT_LOG10197 WITH @ID LIKE '1NON'COUNT
Error was Internaldata error. File
'/apps/ascential/Ascential/Datastage/Projects/LA
Computed blink of 0x830 doesnot match expected blink of 0x0! Detected
at address 0x29800!

I have no clue about this. Please help.

Regards,
Arnie.

[* Note: PLease avoid topic titles like "DataStage Error" as that encompases about 90% of the articles in the forum. Title changed to be more descriptive - Andy *]

Posted: Tue Nov 17, 2009 12:42 am
by DS_SUPPORT
I hope the log file is corrupted, you can clear the log file , by executing the command, from the administrator command prompt.

Code: Select all

CLEAR.FILE RT_LOG10197
This will clear the Auto Purge settings of that job, so please set it again.

Posted: Tue Nov 17, 2009 1:15 am
by arnie_nits
Thanks...

Well I took a copy and ran that....it ran successfuly.

Regards,
Arnie.

Posted: Tue Nov 17, 2009 2:40 am
by ray.wurlod
But the original log remains corrupted, a trap for others, until that situation is remedied.

Posted: Tue Nov 17, 2009 6:18 am
by chulett
Right... that mention of a 'Computed blink' means corruption, typically from a massive amount of entries pushing it over the 32bit addressing 2GB barrier. It needs to be addressed.

Posted: Wed Nov 17, 2010 8:21 am
by magmaj
I had the same issue.
Log clearing didn't help.

I saved the job under the new name and then it worked.

Posted: Wed Nov 17, 2010 8:25 am
by asorrell
If the corruption is bad enough the log clearing won't fix it. The easiest fix in that case is to make a copy, delete original.

Posted: Wed Nov 17, 2010 8:28 am
by chulett
This 'log clearing', are we talking about CLEAR.FILE or from the Director? What I assume we've been discussing here is the former here and I've never seen corruption that it didn't 'correct'... maybe just got lucky. :wink: