Re: Help with full logical logs

I'm not certain that this is accurate. My understanding was that LBU_PRESERVE only needs to be set to 1 if you're using OnArchive or OnBAR. I didn't think that Ontape logs its log backups. LBU_PRESERVE was new to 6.x, after On-Archive was introduced. Back in the Online 5.x days we used to have logical logs fill up all the time, and an ontape -a always fixed the problem, even though all of the logs were filled. Art S. Kagel wrote in message <36432D24.779F@bloomberg.net>... >Joachim Scherer wrote: >> >> Hi: >> my logical logs are full. ontape -a doesn't work anymore. How can free >> the logs without loosing my data. And hopefully without doing a restore. > >Right, ontape -a will not work if the last log is full because it >cannot log the fact of the log backup. I guess you have LBU_PRESERVE >set to 0 or not present in your ONCONFIG. The only option is to change >LTAPEDEV to /dev/null in onmonitor (changing it in the file is not >enough it has to be changed in memory unlike TAPEDEV so you need to use >onmonitor). > >This will cause all logs to be wiped clean without saving them. For >safety IMMEDIATELY after the logs clear up run ontape -s -L 0 to get >a FULL backup since you have just thrown your log files away (you can >probably get away with a -L 1 or -L 2 if the level 0 is very recent but >I like to be safe and use -L0 after a near disaster). After that >change LBU_PRESERVE to 1 in your ONCONFIG file so that the last log >file cannot fill up then you will be able to us ontape -a to recover >next time. Don't forget to change LTAPEDEV back and to bounce the >server when the archive is complete to get the new LBU_PRESERVE value >activated. > >Art S. Kagel > >PS- Be thankful you are not using Sybase where this problem means doing >a full restore to recover.