Hi,
My servers are running with transaction logging and fixup and compact have to be excuted with special flags to avoid the databases having a new DBIID
But I don’t understand why fixup is asigning new DBIIDs even I use the -J flag:
[25372:00009-01543] load fixup -J mail/klarsen.nsf
[22630:00002-00001] 03/16/2005 10:25:32 Database Fixup: Started
[22630:00002-00001] 03/16/2005 10:25:32 Performing consistency check on mail/klarsen.nsf…
[22630:00002-00001] 03/16/2005 10:25:41 Recovery Manager: Assigning new DBIID for /notes/data/mail/klarsen.nsf (need new backup for media recovery).
This should not be the case, or!?
//Kjeld
Subject: Fixup and TL - Why new DBIIDs?
AFAIK, It’s impossible to run fixup in a way that doesn’t change the structure of the db in such a way that TL entries made before the fixup will work on the fixed-up db. This is the whole reason that you get a new dbiid.
From the help on fixup -J:
Runs on databases that are enabled for transaction logging. Without this option, Fixup generally doesn’t run on logged databases.
If you are using a certified backup utility, it’s important that you schedule a full backup of the database as soon after Fixup finishes as possible.
So yes, you should still be getting new dbiids.
Subject: RE: Fixup and TL - Why new DBIIDs?
Hi,
Thanks for the answer, and sorry for not reading the help file properly…
//Kjeld