Log Corrupted

myukassign · Post by **myukassign** » Wed Oct 29, 2008 1:33 pm

I have ran a job which produced so many logs.

and currently when i view the log from directory i am getting an error.

Error selecting from log file RT_LOG34
Command was: SSELECT RT_LOG34 WITH @ID LIKE '1N0N' COUNT.SUP
Error was: Read operation failure. Internal file corruption detected. File must be repaired.#

Nothing is working now. Job is not able to comple as welll. What can be done

ray.wurlod · Post by **ray.wurlod** » Wed Oct 29, 2008 1:55 pm

Clear or repair the log hashed file. Search here for clues.

myukassign · Post by **myukassign** » Wed Oct 29, 2008 3:10 pm

I have gone through some posts and many places i found, I should clear the job log.

but bit confused by your reply 'Clear/repair hashed log files'.

can you clarify this point to me or you can give me link to any post where it is addressed.

sorry for bothering u as i have to do it in production enviorment, i dont want to take a chance.

any specific command can help me to clear this hashed log files / or i need to manully delete.... m in doubt

chulett · Post by **chulett** » Wed Oct 29, 2008 3:15 pm

While corrupted hashed files can be 'repaired' it's not really worth the effort for a job log unless there's vital information in there.

So, to clear it you need to run CLEAR.FILE RT_LOG34 from the Administrator or TCL prompt. Remember to reestablish your auto purge settings for the job afterwards as they will be gone along with everything else.

ray.wurlod · Post by **ray.wurlod** » Wed Oct 29, 2008 3:49 pm

CLEAR.FILE is probably safer than either of the repair utilities (uvfixfile or fixtool), for various reasons. Reinstate your log purge settings after clearing the log using the Director client.

myukassign · Post by **myukassign** » Wed Oct 29, 2008 3:53 pm

but where should i specify the job name in that command.

if i run it will it clear all the logs of all the jobs ?

chulett · Post by **chulett** » Wed Oct 29, 2008 4:05 pm

No, not all. RT_LOG34 is the log for job number 34, the one you are having problems with per your error message. It doesn't go by name but rather by the internal number assigned in the repository.

myukassign · Post by **myukassign** » Wed Oct 29, 2008 4:12 pm

great

let me try this tomorrow and i promise my result will be posted here

myukassign · Post by **myukassign** » Tue Nov 18, 2008 3:44 am

It worked!!

chulett · Post by **chulett** » Tue Nov 18, 2008 8:23 am

But of course!

jonathanhale · Post by **jonathanhale** » Tue Feb 24, 2009 8:05 am

CLEAR.FILE RT_LOG21

executed in administrator commands

returns

"Unable to Clear File RT_LOG21"

"filename = "

Can I delete the log folder from the unix file system? Will this force DataStage to recreate the log? Or will it increase the corruption?

ray.wurlod · Post by **ray.wurlod** » Tue Feb 24, 2009 5:13 pm

Do you actually have a job number 21 that has been compiled?

CLEAR.FILE is also blocked (it attempts to take an exclusive lock) if the log is open - typically in Director.

IBM Analytics Champion 2009 - 2020 · Post by **asorrell** » Tue Feb 24, 2009 7:13 pm

Jonathan - In the future please don't "Hijack" a thread that is marked "Resolved", even if you think your problem is related. I'd recommend starting a new topic and including a link to the previous thread to let people know you tried that solution and it didn't work for you.

Thanks!

(FYI - I'm a content editor for the DSXchange)

jonathanhale · Post by **jonathanhale** » Wed Feb 25, 2009 2:57 am

sorry for the false posting - I know better now.

But, Just to close, yes there was a Job 21. And, the log was not open anywhere.

It's only a small project in Dev, so I resolved it by deleting and recreating the project.

chulett · Post by **chulett** » Wed Feb 25, 2009 8:21 am

Ripley: I say we take off and nuke the entire site from orbit. It's the only way to be sure.

Log Corrupted

Log Corrupted

What to do if Unable to Clear file?