Computed blink of 0x830 does not match expected blink

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
arnie_nits
Participant
Posts: 101
Joined: Mon Aug 13, 2007 2:32 am

Computed blink of 0x830 does not match expected blink

Post 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 *]
DS_SUPPORT
Premium Member
Premium Member
Posts: 232
Joined: Fri Aug 04, 2006 1:20 am
Location: Bangalore

Post 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.
arnie_nits
Participant
Posts: 101
Joined: Mon Aug 13, 2007 2:32 am

Post by arnie_nits »

Thanks...

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

Regards,
Arnie.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

But the original log remains corrupted, a trap for others, until that situation is remedied.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

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

"You can never have too many knives" -- Logan Nine Fingers
magmaj
Participant
Posts: 1
Joined: Wed May 14, 2008 7:44 am
Location: Poland

Post by magmaj »

I had the same issue.
Log clearing didn't help.

I saved the job under the new name and then it worked.
asorrell
Posts: 1707
Joined: Fri Apr 04, 2003 2:00 pm
Location: Colleyville, Texas

Post 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.
Andy Sorrell
Certified DataStage Consultant
IBM Analytics Champion 2009 - 2020
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

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

"You can never have too many knives" -- Logan Nine Fingers
Post Reply