Bug 47636

GemStone/S 64 Bit

3.4.1, 3.4, 3.3.9, 3.3.8, 3.3.7, 3.3.6, 3.3.5, 3.3.4, 3.3.3, 3.3.2, 3.3.1, 3.3

All Platforms

3.4.2

Backups taken under tranlog0.dbf after using /dev/null cannot be restored

Normally GemStone starts with tranlog1.dbf as the first tranlog in a series.  But after using /dev/null for tranlogs and then switching back to normal tranlogs, the first log will be tranlog0.dbf.

If a backup is taken while tranlog0.dbf is in effect, you will be unable to restore this backup.  When subsequently attempting to restore tranlogs or commit the restore, the system will respond as though the restoreFromBackups: had never occurred:

   topaz 1> run
   SystemRepository restoreFromBackup: 'backupOnT0.dat'
   %
   finshed restore commitRestore
   --- MM/DD/2018 HR:MN:SC.XXX Logging out
   The restore from backup completed, with XXXXXXX objects restored.
    Ready for restore from transaction log(s). (error 4046)
   topaz> login
   ....
   topaz 1> run
   SystemRepository restoreStatus
   %
   Restore is not active.
   topaz 1> run
   SystemRepository restoreFromArchiveLogs: '/my/archive/tlogs'
   %
    ----------------------------------------------------
   GemStone: Error Nonfatal
   a ImproperOperation occurred (error 2717), , You cannot restoreLogs without first executing restoreFromBackup
   topaz 1>

Workaround

Increment the tranlog ID by executing "SystemRepository startNewLog" before taking the backup.


Last updated: 6/29/18