Log file corrupted

[RodBarnes]

When I attempt to view the log for a job, I get this message:

Code: Select all

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

I ran DS.CHECKER and it did not report any issues.

Then I tried UVFIXFILE RT_LOG12 FIX and got:

Code: Select all

Beginning TRACE of RT_LOG12.
RT_LOG12/OVER.30: No error
TRACE of RT_LOG12 completed.

Scanning free buffer chain.
Scan complete.

Scanning overflow buffers.
Warning: No link to overflow group 1.
Warning: No link to overflow group 2.
Warning: No link to overflow group 3.
...
Warning: No link to overflow group 417.
Warning: No link to overflow group 418.
Warning: No link to overflow group 419.
Scan complete.

901 group(s) processed.
1175 group buffer(s) processed.
7127 record(s) processed.
Number of data bytes = 1490736.

Where it listed groups 1 through 419. It has been way too long since I had to try and fix a Pick Hash file.

Since it is a log file, can I simply recreate this file? I'm not worried about losing the information that was in the log. Or is there a better way?

Thanks.

[chulett]

Code: Select all

CLEAR.FILE RT_LOG12

Re-establish any auto-purge setting afterwards.

I assume you either ran out of disk space or this hashed file went up against the 2GB Barrier and lost, yes?

[RodBarnes]

I assume you either ran out of disk space or this hashed file went up against the 2GB Barrier and lost, yes?

Exactly. Weird thing is, I'm pretty sure I had it set to my standard 3-day max -- and this is a very small job.

Anyway, that command resolved the issue. Thanks!

[ray.wurlod]

These days fixtool is the preferred repair utility, rather than uvfixfile. It takes a -H or -help command line argument to give you a syntax summary.