HELP!!!

im looking at every logical log at 100% and naturally a blocked checkpoint. whats the best, and next best thing to do in a case like this!!!

The only thing you can do at this point is to call Tech support who will truncate your last logfile to allow room for the checkpoint and archive log records to be written (as well as the engine restart records). Then you will restart and backup the logs and count your stars that you ONLY lost a few dozen transactions. After that increase LTXHWM and LTXEHWM and set LBU_PRESERVE to 1 and shutdown and restart again. After that if you want increase the number of logical log files and plan a reliable way to keep those logs backed up! Look into my ALARMPROGRAM method for backing up the logs as they fill if you use ontape or use the logs_full.sh if you use onbar. My alarm utility is contained in the package utils3_ak in the IIUG Software Repository. Art S. Kagel Edward Rosenthal wrote: > > im looking at every logical log at 100% and naturally a blocked > checkpoint. > whats the best, and next best thing to do in a case like this!!!

i got the sysadmin to start up a backup ( legato, onbar) and after it finished ( 2 different instances) we seemed to be out of the difficulties we were in. all the 'B' flags are set ok on the logical logs, tho the numbers (100%) do not reflect it. I will add more logical logs, and increase the LTXHWM and LTXEHWM. We currently use the log_full.sh, and its supposed to be a reliable way of using the legato business suite. For some reason it was coming in too late to do any good. "Art S. Kagel" wrote: > The only thing you can do at this point is to call Tech support who will > truncate your last logfile to allow room for the checkpoint and archive > log records to be written (as well as the engine restart records). Then > you will restart and backup the logs and count your stars that you ONLY > lost a few dozen transactions. After that increase LTXHWM and LTXEHWM and > set LBU_PRESERVE to 1 and shutdown and restart again. After that if you > want increase the number of logical log files and plan a reliable way to > keep those logs backed up! > > Look into my ALARMPROGRAM method for backing up the logs as they fill if > you use ontape or use the logs_full.sh if you use onbar. My alarm utility > is contained in the package utils3_ak in the IIUG Software Repository. > > Art S. Kagel > > Edward Rosenthal wrote: > > > > im looking at every logical log at 100% and naturally a blocked > > checkpoint. > > whats the best, and next best thing to do in a case like this!!!