On 18-Nov-02 Charles F. Fisher wrote:
The site I'm at is getting ready to upgrade to 4.2.3. One reason is to be
able to run CLEANUP BACKUPGROUPS on the database; are there any special
actions or precautions that should be taken before doing so (once the
upgrade is in place)?
We didn't and
The site I'm at is getting ready to upgrade to 4.2.3. One reason is to be
able to run CLEANUP BACKUPGROUPS on the database; are there any special
actions or precautions that should be taken before doing so (once the
upgrade is in place)?
Chuck Fisher
[EMAIL PROTECTED]
On 18-Nov-02 Charles F. Fisher wrote:
The site I'm at is getting ready to upgrade to 4.2.3. One reason is to be
able to run CLEANUP BACKUPGROUPS on the database; are there any special
actions or precautions that should be taken before doing so (once the
upgrade is in place)?
We didn't and
Is there any special syntax for the cleanup backupgroups question. I
upgraded to 4.2.2.12 and tried to run the
cleanup command and received the following error:
Anrd tb.c(1167) threadid(31) invalid encoded data length
Anr0104e imutil.c(8363) Error deleting
PROTECTED]
Subject: Cleanup Backupgroups question
Is there any special syntax for the cleanup backupgroups question. I
upgraded to 4.2.2.12 and tried to run the
cleanup command and received the following error:
Anrd tb.c(1167) threadid(31) invalid encoded data length