Re: Can't free logical logs
Posted in 1998
In response to Diane Houston, Sanjit wrote on 20 May 1998 :- > Hi Diane, > Try the following steps - > 1. Login as 'informix' and Set proper TBCONFIG. > > 2. tbstat -u > take all 'PID' for all users other than root and informix users. Agreed. But note the following extract from OnLine Administrator's Guide v5.0 :- Check that the process is not in a critical section. Look at the third-position flag of the tbstat -u output. If the process flag is X, DO NOT KILL THE PROCESS. If you do, OnLine aborts with an immediate shutdown. Check that the process is not holding a latch. Obtain the address of the process from the tbstat -u output. Execute tbstat -s to look at a summary of latch information. Verify that the address of this process is not listed as the owner of any latch. If the process address is associated with a latch, DO NOT KILL THE PROCESS. If you do, OnLine aborts with an immediate shutdown. > 3. tbmode -z PID > use this individually for all the PIDs. >> 4. Login as 'root' and kill and PIDs with -15 option. >> kill -15 PIDs It may just be me being twitchy, having suffered from OnLine aborts and the subsequent late nights restoring, but I don't like "kill"-ing any Informix processes. I appreciate -15 is less severe than -9 (a definite no-no!!). >> 5. Login as informix , set your TBCONFIG and increase the 'Logical >> Log number' with some handful number from 'tbmonitor' for time >> being. >> 6. tbtape -a >> take logical log backup. >> 7. tbmode -ky >> stop your informix >> 8. tbinit >> restart informix >> 9. Change the logical log number to the previous status. Regards Glyn Balmer I.T. Consultant BICC Cables Limited Erith Kent UK Tel: 0181 225-2281 Fax: 0181 311-3300 email: glynb@bicceri.demon.co.uk