Logical logs backup

Hi, We are using IDS 11.5 and OS is RHEL 5.3 We have 10 logical logs having the id from 4-13. I did a database import to the existing database and hence the logical logs becomes full. The status of the logical logs is Logical log 4 to 7 -> U_B__ Logical log 8 -> U_C_L Logical log 9-13 -> U_B__ All the logical logs are 100% full Hence i did a logical log backup and level 0 backup After that the status is Logical log 4 to 8 -> U_B__ Logical log 9 -> U_C_L Logical log 10-13 -> U_B__ But yet the status of %used didnt go off to 0 When i did a another logical log backup and level 0 backup. the status becomes Logical log 4 to 9 -> U_B__ Logical log 10 -> U_C_L Logical log 11-13 -> U_B__ And now the %used gets decreases from 100 to a number Is there anyway i can take backup and clear all the existing logical logs? Should i use the automaticl backup using alarm program? Thanks in advance! Thanks, Lakki

Hi, logical logs that have the 'B'-flag (in output of "onstat -l") are backed up (already). So even before you did the manual logical log backup, all your logs were already backed up, except log 8 because it was the (then) current log file. Your (manual) logical log backup also advanced the current log file by one. Hence afterwards all logs were backed up except log 9 as this now is the current log file. So I would guess that somehow your log files do get backed up "automatically". [ Or they get backed up to "/dev/null". This means that they do not really get backed up, but the server treats them as backed up as soon as they become full. Hence you don't need to bother with log backup. This is a special mode requiring the configuration of onconfig parameter LTAPEDEV being set to /dev/null. Although I do not think you have this configuration, because it should cause some kind of message for the manual log backup along the lines that this is not possible/allowed to /dev/null ... ] You can manually advance the current logical log file by one log using the command "onmode -l". This will not by itself backup the completed logical log. (The previous current log will be "completed" even when not full. And as a completed log it is a candidate for log backup.) Wait for a moment or two and then check again using "onstat -l". I guess you will see that this log will soon get the 'B'-flag ... Also you can check the IDS message log file (or use "onstat -m") to see a message about log backup. Then you can find out how the log was "automatically" backed up. The most common mechanism is the "alarm program", but there can be others, or the /dev/null setting as mentioned above. Regards, Martin -- Martin Fuerderer IBM Informix Development Munich, Germany Information Management IBM Deutschland Research & Development GmbH Chairman of the Supervisory Board: Martin Jetter Board of Management: Erich Baier Corporate Seat: Boeblingen, Germany Reg.-Gericht: Amtsgericht Stuttgart, HRB 243294 ids-bounces@iiug.org wrote on 08/20/2009 08:03:25 AM: > [image removed] > > Logical logs backup [16729] > > LAKSHMI DEVI PALANISSAMY > > to: > > ids > > 08/20/2009 08:04 AM > > Sent by: > > ids-bounces@iiug.org > > Please respond to ids > > Hi, > > We are using IDS 11.5 and OS is RHEL 5.3 > > We have 10 logical logs having the id from 4-13. > I did a database import to the existing database and hence the logical logs > becomes full. > The status of the logical logs is > Logical log 4 to 7 -> U_B__ > Logical log 8 -> U_C_L > Logical log 9-13 -> U_B__ > All the logical logs are 100% full > > Hence i did a logical log backup and level 0 backup > After that the status is > Logical log 4 to 8 -> U_B__ > Logical log 9 -> U_C_L > Logical log 10-13 -> U_B__ > > But yet the status of %used didnt go off to 0 > > When i did a another logical log backup and level 0 backup. the > status becomes > Logical log 4 to 9 -> U_B__ > Logical log 10 -> U_C_L > Logical log 11-13 -> U_B__ > > And now the %used gets decreases from 100 to a number > > Is there anyway i can take backup and clear all the existing logical logs? > Should i use the automaticl backup using alarm program? > > Thanks in advance! > > Thanks, > Lakki > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. >

Hi, Even then the logs are backed up, the %used status still shows 100. And on performing the backup twice, the %used is getting reduced from 100% Regards, Lakshmi

Hi, the (%) used column in "onstat -l" output tells you, how much of the logical log has been used, i.e. how much full it is. Normally the logs are filled completely (100%) and only then a switch to the next logical log file happens. Only if a logical log switch is happening before the log is 100% full, you will see a % less than 100. This is e.g. when doing a manual log switch using "onmode -l" (as I mentioned in last e-mail). Even when the log has been backed up (and therefore it is ready to be re-used), the "used'percentage" will not be reset to zero immediately *after the backup). Instead it will be done just before the log file is actually being re-used, when it becomes again the current log after a complete cycle through all the log files. So with that it is normal that you see for the backed up logical log files that they are backed up, but still they have a used-% of more that 0, and this usually is 100. There's nothing to be concerned about with that. :) Regards, Martin -- Martin Fuerderer IBM Informix Development Munich, Germany Information Management IBM Deutschland Research & Development GmbH Chairman of the Supervisory Board: Martin Jetter Board of Management: Erich Baier Corporate Seat: Boeblingen, Germany Reg.-Gericht: Amtsgericht Stuttgart, HRB 243294 ids-bounces@iiug.org wrote on 08/20/2009 10:53:22 AM: > [image removed] > > Re: Logical logs backup [16731] > > LAKSHMI DEVI PALANISSAMY > > to: > > ids > > 08/20/2009 10:54 AM > > Sent by: > > ids-bounces@iiug.org > > Please respond to ids > > Hi, > > Even then the logs are backed up, the %used status still shows 100. And on > performing the backup twice, the %used is getting reduced from 100% > > Regards, > Lakshmi > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. >

Hi Martin, Thanks for your response! Correct me if my clarification is wrong! At one point of time, the status of the logical logs is Logical log 4 to 7 -> U_B__ Logical log 8 -> U_C_L Logical log 9-13 -> U_B__ All the logical logs are 100% full When i did a level 0 backup, the current logical log got switched from 8 to 9. And automatically the used status of logical log 9 has been reset to 0 from 100. So eventhough the %used of a logical log shows 100%, it is fine to ignore the warning as it automatically switches to next logival log and free up the current one? Thanks, Lakshmi

Hi, yes. :) Regards, Martin -- Martin Fuerderer IBM Informix Development Munich, Germany Information Management IBM Deutschland Research & Development GmbH Chairman of the Supervisory Board: Martin Jetter Board of Management: Erich Baier Corporate Seat: Boeblingen, Germany Reg.-Gericht: Amtsgericht Stuttgart, HRB 243294 ids-bounces@iiug.org wrote on 08/20/2009 12:31:52 PM: > [image removed] > > Re: Logical logs backup [16733] > > LAKSHMI DEVI PALANISSAMY > > to: > > ids > > 08/20/2009 12:32 PM > > Sent by: > > ids-bounces@iiug.org > > Please respond to ids > > Hi Martin, > > Thanks for your response! > > Correct me if my clarification is wrong! > At one point of time, the status of the logical logs is > Logical log 4 to 7 -> U_B__ > Logical log 8 -> U_C_L > Logical log 9-13 -> U_B__ > All the logical logs are 100% full > > When i did a level 0 backup, the current logical log got switched > from 8 to 9. > And automatically the used status of logical log 9 has been reset to 0 from > 100. > > So eventhough the %used of a logical log shows 100%, it is fine to > ignore the > warning as it automatically switches to next logival log and free up the > current one? > > Thanks, > Lakshmi > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. >

When the engine switches to the next logical log is it not yet available to be reused (unless you have LTAPEDEV set to /dev/null in which case your logs are never backed up and are immediately marked with a 'B' meaning backed up when they are completed - this effectively discards the logs for server restores and only preserves them for fast recovery after a crash). Only backing up the logs with ontape -c or ontape -a (or allowing an ontape -s to do that at the end of the run) will free the log for reuse. Art Art S. Kagel Oninit (www.oninit.com) IIUG Board of Directors (art@iiug.org) Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Oninit, the IIUG, nor any other organization with which I am associated either explicitly or implicitly. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Thu, Aug 20, 2009 at 6:31 AM, LAKSHMI DEVI PALANISSAMY < lakshmidevip@hcl.in> wrote: > Hi Martin, > > Thanks for your response! > > Correct me if my clarification is wrong! > At one point of time, the status of the logical logs is > Logical log 4 to 7 -> U_B__ > Logical log 8 -> U_C_L > Logical log 9-13 -> U_B__ > All the logical logs are 100% full > > When i did a level 0 backup, the current logical log got switched from 8 to > 9. > And automatically the used status of logical log 9 has been reset to 0 from > 100. > > So eventhough the %used of a logical log shows 100%, it is fine to ignore > the > warning as it automatically switches to next logival log and free up the > current one? > > Thanks, > Lakshmi > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --0015174c41749f253a047193b5c5