Posted: Thu Apr 27, 2006 3:02 am
Singhal, a quick use of the search facility would have shown you that this type of file corruption has been encountered before and many people have posted responses.
The file needs to be repaired. If you go into TCL or the ADMIN command mode you can do a "CLEAR.FILE RT_LOG161" and this will most likely clear the file and fix the problems at the same time. If not, then you should use the fixtool program located in the project /bin directory from UNIX on this log file to repair it.
The question you should ask yourself is whether or not there are other corrupted files out there. Do you know what might have caused the log file corruption in the first place?
The file needs to be repaired. If you go into TCL or the ADMIN command mode you can do a "CLEAR.FILE RT_LOG161" and this will most likely clear the file and fix the problems at the same time. If not, then you should use the fixtool program located in the project /bin directory from UNIX on this log file to repair it.
The question you should ask yourself is whether or not there are other corrupted files out there. Do you know what might have caused the log file corruption in the first place?