Log Corrupted
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 238
- Joined: Fri Jul 25, 2008 8:55 am
Log Corrupted
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
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
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Clear or repair the log hashed file. Search here for clues.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Premium Member
- Posts: 238
- Joined: Fri Jul 25, 2008 8:55 am
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
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
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.
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.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
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.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Premium Member
- Posts: 238
- Joined: Fri Jul 25, 2008 8:55 am
-
- Premium Member
- Posts: 238
- Joined: Fri Jul 25, 2008 8:55 am
-
- Premium Member
- Posts: 33
- Joined: Tue Nov 06, 2007 1:09 pm
What to do if Unable to Clear file?
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?
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?
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
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.
CLEAR.FILE is also blocked (it attempts to take an exclusive lock) if the log is open - typically in Director.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
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)
Thanks!
(FYI - I'm a content editor for the DSXchange)
-
- Premium Member
- Posts: 33
- Joined: Tue Nov 06, 2007 1:09 pm