Can't you just change your retention of DBBackup sets to 1 and let it expire itself, then change it back? Or am I not thinking about the same thing? I would think this would remove it from volhist as well.
On 6/6/07, Richard Sims <[EMAIL PROTECTED]> wrote:
On Jun 6, 2007, at 10:48 AM, חנה דרזי wrote: > After Unload and load database 5.3.5 on windows. > When I triy to delete dbbackup records from volume history I get: > DELETE VOLHISTORY: 0 sequential volume history entries were > I delete volumes from 4 days befor and I have volumes from 30 May > > How can I fix it ? This was pursued recently with another customer. See the thread at http://www.mail-archive.com/[email protected]/msg71919.html Database reload resets the DBBackup Series number, resulting in this situation. Using the undocumented Force parameter of DELete VOLHistory is a way out of it. This is another reason to not do database Unload-Reload without a VERY good reason. (Hope of improving DB performance does not constitute such a reason, in my experience.) Richard Sims
