Error viewing log, Computed blink does not match expected

yaminids · Post by **yaminids** » Wed Dec 14, 2005 5:56 pm

Hello freinds,

I am getting the following error when I tried to view the log of an aborted job. Can someone please help me in resolving the issue?

Thanks a lot in advance
Yamini

Error:
Error selecting from log file RT_LOG1056
Command was: SSELECT RT_LOG1056 WITH @ID LIKE '1N0N' AND TIMESTAMP >= "2004-01-01 00:30:00" COUNT.SUP
Error was: Internal data error. File '/data/Ascential/DataStage/Projects/DATWHR/RT_LOG1056/DATA.30': Computed blink of 0x8EC does not match expected blink of 0x0! Detected within group starting at address 0x80000000!

kcbland · Post by **kcbland** » Wed Dec 14, 2005 5:59 pm

Your log is corrupted, maybe because of it exceeded 2.2 GB. You can try to recover the contents, but the easiest thing to do is clear it out completely. From DS Admin, connect to that project and issue "CLEAR.FILE RT_LOG1056". You'll lose the purge settings for the job, but at least the log (and job) will be usable and runnable.

chulett · Post by **chulett** » Wed Dec 14, 2005 6:01 pm

You corrupted the log file, probably by extending it past the 2GB limit. At this point about all you can do is clear it by going to the Administrator and issuing a CLEAR.FILE against RT_LOG1056.

Rerun the job with a row limit or set it to abort after a small number of warnings so you can see (and address) the problem.

ray.wurlod · Post by **ray.wurlod** » Wed Dec 14, 2005 7:11 pm

You should purge your log more frequently. Set auto purge. Don't let it grow past 2GB. If it's going to anyway, resize it to use 64-bit pointers.

chulett · Post by **chulett** » Wed Dec 14, 2005 9:27 pm

I'm guessing it's one of those single runs with unlimited warnings kind of thing...

ray.wurlod · Post by **ray.wurlod** » Wed Dec 14, 2005 10:25 pm

2GB is a shitload (that's a technical term) of warning messages!!!

yaminids · Post by **yaminids** » Wed Dec 14, 2005 10:34 pm

Hello there,

You are right guys about the log crossing the limit. Actually the job was extracting millions of rows from a table and the data was corrupted. For every bad row extracted it was writing an entry into the log. I manually stopped the job and cleared the log

Thanks a lot for your input
Yamini

chulett · Post by **chulett** » Thu Dec 15, 2005 8:11 am

One of the biggest reasons to not run jobs with the Abort after X Warnings option set to Unlimited.

koolnitz · Post by **koolnitz** » Thu Jul 27, 2006 4:32 pm

Guys,

Same issue here. The log file for a job exceeded 2GB and on finding this, the developer manually removed the files (using rm command) under RT_LOGnnn folder. He should have used CLEAR.FILE command!! Now the job has been locked. I want to delete this job. Will appreciate if any of you could guide me.

Thanks!

chulett · Post by **chulett** » Thu Jul 27, 2006 4:36 pm

You could take an empty log and copy the files from there over to the directory where the files were removed. That should give you normal access to things again.

Locked is a whole 'nuther issue. Search the forum for UNLOCK for various discussions on handling locked jobs.

koolnitz · Post by **koolnitz** » Thu Jul 27, 2006 4:45 pm

Bingo.. It worked :D

Thanks Craig!

dpegasus · Post by **dpegasus** » Mon Jan 15, 2007 1:18 am

chulett wrote:You corrupted the log file, probably by extending it past the 2GB limit. At this point about all you can do is clear it by going to the Administrator and issuing a CLEAR.FILE against RT_LOG1056.

Re ...

Do you know how to recover the contents in the log file? As I need to investige the reason of the large amount of warnings in the log.

kumar_s · Post by **kumar_s** » Mon Jan 15, 2007 2:23 am

If you haven't cleared the file, LIST filename in TCL or adminstrator client, should get the content in the console, and you can use that if you can make it up.

DSguru2B · Post by **DSguru2B** » Mon Jan 15, 2007 11:36 am

If you cleared it then its gone. Re-run the same job with warning limit set to maybe 2 or 3. This way you can view the log in the director and see why those warning messages were created. It will also keep the log file size in check.

ray.wurlod · Post by **ray.wurlod** » Mon Jan 15, 2007 3:48 pm

If you really are going to get millions of unavoidable warnings - though I can not see any good reason for such a situation - you can resize the log (once it has been cleared) to handle more than 2GB.

Code: Select all

RESIZE RT_LOG1056 * * * 64BIT

DSXchange

Error viewing log, Computed blink does not match expected

Error viewing log, Computed blink does not match expected

Strange error while trying to view log entries