How to back out logs when rollforward of logical logs fail

I came upon a post saying to "Start in queiscent and back out the logs" when rollforward of logical logs fail. The online.log mentions : 16:13:23 Rollforward of log record failed. iserrno = 126 16:13:23 Log Record: log = 172944, pos = 97f070, type = OLDRSAM:RUPDATE(74), trans = 27 16:13:24 Assert Failed: Chunk 10 is being taken OFFLINE. 16:13:24 Informix Dynamic Server Version 7.31.UC6 Can someone tell me how to back out the logs ? Is this by using 'oninit -phy' ? Is there some other way to avoid rollforwarding a problematic log ? Krgds Alain

alain deschamps wrote: > I came upon a post saying to "Start in queiscent and back out the > logs" when rollforward of logical logs fail. > The online.log mentions : > 16:13:23 Rollforward of log record failed. iserrno = 126 > 16:13:23 Log Record: log = 172944, pos = 97f070, type = > OLDRSAM:RUPDATE(74), trans = 27 > 16:13:24 Assert Failed: Chunk 10 is being taken OFFLINE. > 16:13:24 Informix Dynamic Server Version 7.31.UC6> > Can someone tell me how to back out the logs ? Is this by using > 'oninit -phy' ? > Is there some other way to avoid rollforwarding a problematic log ? > > Krgds > Alain > > The error means you have to restore the DB. There is not other proper way to handle this. (IFMX Advanced support could interfere with fast recovery and bring it online, however, that usually means more or less corruption is left over in the database as a consequence). When you restore 7.31.UC6 , you might want to use a different set of disks , and not overwrite whats currently on disk. Just as a precaution in case the restore fails, too . Rgds Tilman