Unable to view the Log file.
Moderators: chulett, rschirm, roy
This error means that the log file for this job has become corrupted. The most common cause is that the disk (at one time) filled up.
For LOG files the solution is easy, just clear the log file.
For LOG files the solution is easy, just clear the log file.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
Just doing a full log clear from the director (Job -> Clear Log -> immediate purge of all entries) should do the trick as well, if it doesn't then you can do a CLEAR.FILE (but remember that the purge settings will be gone).
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 42
- Joined: Thu Dec 28, 2006 1:39 am
-
- Premium Member
- Posts: 1735
- Joined: Thu Mar 01, 2007 5:44 am
- Location: Troy, MI
-
- Participant
- Posts: 42
- Joined: Thu Dec 28, 2006 1:39 am
-
- Premium Member
- Posts: 1735
- Joined: Thu Mar 01, 2007 5:44 am
- Location: Troy, MI
-
- Participant
- Posts: 42
- Joined: Thu Dec 28, 2006 1:39 am
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Please run the following command from the Administrator client:
Report your findings.
Code: Select all
UVFIXFILE RT_LOG43
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: 42
- Joined: Thu Dec 28, 2006 1:39 am
again I used the CLEAR.FILE RT_LOG43 and reran the job, there is no warnings but there are 119650 entries as of now. is it cause the problem?chulett wrote:Then I assume you are once again generating a bazillion warning messages and the log has 'overflowed', pushing it past the 2GB threshold. You might want to monitor it real time after it gets 'fixed' a ...
-
- Participant
- Posts: 42
- Joined: Thu Dec 28, 2006 1:39 am
For each batch id there is a insert statement, there are more than 10000 batch ids. all the insert statements presented in the log file. now the log file entries increased to 138285.chulett wrote:Too many log messages can cause the corruption issue, yes. All of those are from one run? What kind of messages are being logged? ...
Then you have reached an impasse. Either reduce the number and size of messages or, better yet, don't log them in the job log but elsewhere. This heavy I/O to the log file is most certainly slowing your job down as well.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
Why? Under what circumstances are 'all the insert statements' being logged? Perhaps you could post a small sample so we can see just what it is you are talking about...prasanna_anbu wrote:For each batch id there is a insert statement, there are more than 10000 batch ids. all the insert statements presented in the log file. now the log file entries increased to 138285.chulett wrote:Too many log messages can cause the corruption issue, yes. All of those are from one run? What kind of messages are being logged? ...
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers