Stopping Log entries
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 306
- Joined: Wed Jun 21, 2006 11:41 am
Stopping Log entries
Hi,
A developer has just run a job in dev with the "no Limit" for the warnings. We managed to terminate the job(by recompiling) and clear the log, but it keeps writing to it. Is there any way to stop this.......3 hours later??
Thanks for any info....
John
A developer has just run a job in dev with the "no Limit" for the warnings. We managed to terminate the job(by recompiling) and clear the log, but it keeps writing to it. Is there any way to stop this.......3 hours later??
Thanks for any info....
John
-
- Premium Member
- Posts: 306
- Joined: Wed Jun 21, 2006 11:41 am
-
- Premium Member
- Posts: 306
- Joined: Wed Jun 21, 2006 11:41 am
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You can't stop it without terminating the process (usually a database process) that is generating the errors. And note too that these are buffered, so a few thousand will still arrive after that.
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.
-
- Participant
- Posts: 106
- Joined: Thu Jun 08, 2006 8:51 am
-
- Premium Member
- Posts: 306
- Joined: Wed Jun 21, 2006 11:41 am
OK..I figured I would be patient. I just went back in Director to take a peek and recieve teh following pop-up......
Any ideas what to do with this??
Error selecting from log file RT_LOG207
Command was: SSELECT RT_LOG207 WITH @ID LIKE '1N0N' COUNT.SUP
Error was: Internal data error. File 'D:\DataStage\CostFoundation/RT_LOG207/DATA.30': Computed blink of 0x800 does not match expected blink of 0x0! Detected within group starting at address 0x1800!
Thanks - - John
Any ideas what to do with this??
Error selecting from log file RT_LOG207
Command was: SSELECT RT_LOG207 WITH @ID LIKE '1N0N' COUNT.SUP
Error was: Internal data error. File 'D:\DataStage\CostFoundation/RT_LOG207/DATA.30': Computed blink of 0x800 does not match expected blink of 0x0! Detected within group starting at address 0x1800!
Thanks - - John
Sure, a 'blink' is a 'backwards link' and you can search the forums for that term to find some previous conversations on this topic.
Basically, the log has become corrupt, undoubtedly due to the high volume of writes causing it to run smack into the 32bit addressing barrier of 2.2GB. At this point you'll need to find the job number in question and issue a CLEAR.FILE RT_LOGnnn where 'nnn' is the job number. Do this from the Administrator or a TCL prompt connected to the project in question. After that, you'll need to reestablish any Auto Purge settings for that log as they will be removed as well.
Have the log writes stopped yet?
ps. Patience isn't always a virtue.
Basically, the log has become corrupt, undoubtedly due to the high volume of writes causing it to run smack into the 32bit addressing barrier of 2.2GB. At this point you'll need to find the job number in question and issue a CLEAR.FILE RT_LOGnnn where 'nnn' is the job number. Do this from the Administrator or a TCL prompt connected to the project in question. After that, you'll need to reestablish any Auto Purge settings for that log as they will be removed as well.
Have the log writes stopped yet?
ps. Patience isn't always a virtue.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Premium Member
- Posts: 306
- Joined: Wed Jun 21, 2006 11:41 am