Hi,
I have 96% used disk in my Linux. After a little research it turns out: - extent0.dbf --- 5.5 GB - tranlog3.dbf --- 1.0GB - tranlog4.dbf --- 1.0GB - tranlog5.dbf --- 1.0GB - tranlog6.dbf --- 1.0GB - tranlog7.dbf --- 1.0GB - tranlog8.dbf --- 57.8 MB Most of them accessed last time long time ago. I also found this: https://github.com/noha/stone-creator/blob/master/bin/delete-old-tranlogs.sh Is this a script to remove these files ? I'm reading Chapter 8 - Managing Transaction Logs but not found yet if it possible to remove the old ones. Regards, Bruno |
Hi,
Also: System currentObjectSecurityPolicy repository oldestLogFileIdForRecovery. "answer 8" So it seems that is sure to remove "tranlog3" to "tranlog7" ... Regards, Bruno |
The tranlogs that are completly safe to delete are those needed for the oldest backup you want to keep. I shared some time ago this daily maintainance script I run for my app (backupAndClean.sh). See it attached. The interesting part for you is almost at the end where I delete unneeded tranlogs. And yes, I also use the Norbert Halt script , but I think I modified it. I also attach it here (delete-old-tranlogs.sh) Hope this helps! On Wed, Dec 16, 2015 at 3:07 PM, BrunoBB via Glass <[hidden email]> wrote: Hi, _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Hi,
I think as a rule you can remove (or move to other disk) everything below number: System currentObjectSecurityPolicy repository oldestLogFileIdForRecovery. In my case the "answer 8" so i can delete: - tranlog3.dbf --- 1.0GB - tranlog4.dbf --- 1.0GB - tranlog5.dbf --- 1.0GB - tranlog6.dbf --- 1.0GB - tranlog7.dbf --- 1.0GB I have deleted all these file and everything is working ok. Regards, bruno |
The stone needs the tranlogs older than (inclusive) listed by
oldestLogFileIdForRecovery ... for backups you can move the tranlogs and backups to a separate spindle//machine ... as they are only needed when restoring from backup and ... when you do restore, you will want to put the tranlogs back in the tranlog directory ... Dale On 12/17/2015 09:45 AM, BrunoBB via Glass wrote: > Hi, > > I think as a rule you can remove (or move to other disk) everything below > number: > System currentObjectSecurityPolicy repository oldestLogFileIdForRecovery. > > In my case the "answer 8" so i can delete: > - tranlog3.dbf --- 1.0GB > - tranlog4.dbf --- 1.0GB > - tranlog5.dbf --- 1.0GB > - tranlog6.dbf --- 1.0GB > - tranlog7.dbf --- 1.0GB > > I have deleted all these file and everything is working ok. > > Regards, > bruno > > > > -- > View this message in context: http://forum.world.st/Tranlogs-space-on-Linux-tp4867404p4867620.html > Sent from the GLASS mailing list archive at Nabble.com. > _______________________________________________ > Glass mailing list > [hidden email] > http://lists.gemtalksystems.com/mailman/listinfo/glass _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
s/older/newer/ ...
On 12/17/2015 11:00 AM, Dale Henrichs wrote: > The stone needs the tranlogs older than (inclusive) listed by > oldestLogFileIdForRecovery ... for backups you can move the tranlogs > and backups to a separate spindle//machine ... as they are only needed > when restoring from backup and ... when you do restore, you will want > to put the tranlogs back in the tranlog directory ... > > Dale > > On 12/17/2015 09:45 AM, BrunoBB via Glass wrote: >> Hi, >> >> I think as a rule you can remove (or move to other disk) everything >> below >> number: >> System currentObjectSecurityPolicy repository >> oldestLogFileIdForRecovery. >> >> In my case the "answer 8" so i can delete: >> - tranlog3.dbf --- 1.0GB >> - tranlog4.dbf --- 1.0GB >> - tranlog5.dbf --- 1.0GB >> - tranlog6.dbf --- 1.0GB >> - tranlog7.dbf --- 1.0GB >> >> I have deleted all these file and everything is working ok. >> >> Regards, >> bruno >> >> >> >> -- >> View this message in context: >> http://forum.world.st/Tranlogs-space-on-Linux-tp4867404p4867620.html >> Sent from the GLASS mailing list archive at Nabble.com. >> _______________________________________________ >> Glass mailing list >> [hidden email] >> http://lists.gemtalksystems.com/mailman/listinfo/glass > _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Dale,
Why i need so many tranlogX.dbf to restore a backup ? I'm reading chapter 8 "To Initiate a Checkpoint" If i do: System startCheckpointSync. The tranlog will start from 0 again ? or it is just a like a commit without realising locks ? Page 54: "At any point, the method Repository>>oldestLogFileIdForRecovery identifies the oldest log file needed for recovery from the most recent checkpoint,...." Is System startCheckpointSync this checkpoint ? Regards, Bruno |
Bruno,
On 12/17/2015 11:44 AM, BrunoBB via Glass wrote: > Dale, > > Why i need so many tranlogX.dbf to restore a backup ? When you make a backup, you need to keep all of the tranlogs that were created after the backup was made ... otherwise you won't be able to restore from your backup and the replay tranlogs to restore your system to the state prior to crash ... If you make a new backup you can throw all of the tranlogs associated with the old backup and start keep tranlogs for the new backup ... > > I'm reading chapter 8 "To Initiate a Checkpoint" > If i do: > System startCheckpointSync. > > The tranlog will start from 0 again ? or it is just a like a commit without > realising locks ? no the tranlog file names increase with each new tranlog ... the stone keeps track of the tranlog numbers it has written and the ones that it needs to restore ... When you restore from a backup, the last tranlog file written is recorded, so the stone will know what tranlog is needed to restore post backup > > Page 54: > "At any point, the method Repository>>oldestLogFileIdForRecovery identifies > the oldest log file needed for recovery from the most recent > checkpoint,...." > > Is System startCheckpointSync this checkpoint ? Yes that method starts a checkpoint ... Keep in mind that the tranlogs are used for recovery in two cases: 1. the stone crashes and you restart the tranlog - which starts at the most recent checkpoint and then recovers from tranlogs to get the most recent commit. 2. the stone crashes and the extents are corrupted, so you have to restore from backup in which case after restoring from the backup, you will need to restore from tranlogs kept since the backup was made (including the tranlogs needed to restore to the checkpoint of the backup) Dale _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Free forum by Nabble | Edit this page |