Last Friday I installed some automatic updates to my Win2003 detected
by the automatic update.

Today (next monday) I noticed a lot of _RBLDAxxxx in my working
directory.

When I run rebuild batch utility like

C:\PVSW\bin\rbldcli -c -sK -pP -f8 -k0 D:\Auto6\D6\CheqCli.ga6

it starts normally, the file CheqCli.ga6 is renamed to CheqCli.^^^ and
at the end when it starts making the indexes, it creates the _RBLDAxxxx
file but the files are not deleted when the indexing terminates.

Prior to the system update the rebuilds ran perfectly.

Anybody knows how to make the rbldcli utility to delete the working
_RBLDAxxxx files at the end?

Using Pervasive 9.5, thanks in advance,

Jose L Viejo

This is a wild guess: Check to make sure you still have Delete rights
to the directory where you're rebuilding the files.

Wayne Freeman
Analytica Business Systems
www.analyticabiz.com
A Pervasive Premier VAR

glicuado ha scritto:

Thx Wayne, the admin user is the one running the rebuild, full
rights... It used to work normally...

Jose Luis


Wayne ha escrito:

The rebuild utility does not rename the original file until the
rebuild is complete.
A Btrieve data file with the "*.^^^" is in backup, "Continuous
Operations" mode. The original data file should be present also.
I suspect that if a file is in continuous operations there is not
enough time between the file close and file delete (original file) and
rename (temp file) that rebuild does after it rebuilds the file. The
database engine may still be trying to process something with the
original file continuous operations keeping it open just a little too
long.

As to the _RBLDAxxxx files that is the rebuilt data file (hopefully
complete) that normally is renamed to the original file name.

1) Make sure the files are not in continuous operations before trying
to rebuild them.
2) Check the logs. If the only thing that failed was the rename you
might be able to get away with just doing the rename process yourself.
Just do like the rebuild utility would do and delete the original
files (a backup here would make more sense) and rename the new one to
the original name. If however as you say many failed this way it
would be difficult to figure out which temp file should be renamed to
which regular file.

Leonard

On 25 Sep 2006 17:33:47 -0700, "glicuado" <jlviejo (AT) gmail (DOT) com> wrote: