Hi Costas,

  I'm sure someone has already come back to you about
this problem, but for what it's worth here is my two
pennyworth!

  The logfile name can only go up to 999, so at that
point it will re-cylce itself back to 001.  If you
still have a 001 file left on the system, it will
report a duplicate name.

  To overcome this problem, I use a job that runs
every week that goes around looking for logfiles over
one week old and writing them to tape, they are then
purged.  Of course, it depends how long each of your
logfiles last (I'll assume you are using AUTO, to
switch to the next log in the sequence).  If your
logfiles are switching once a minute, you'll have to
look for old ones on a much more regular basis!

 You can force the database to go back to logfile 001
using DBUTIL and BUILD'ing a new logging set, but all
users must be off the database to do this.  I have a
job set up to do this.  If you'd like a copy drop me a
line.

Best regards

Bob Browett



--- Costas Anastassiades <[log in to unmask]> wrote:
> When (or how) are database logids reset (to zero or
> one etc) ?
>
> Reading our db log files (which span many days) we
> keep coming up
> against a message that indicates that duplicate
> logids have been found.
> My guess is, that because we keep the same log file
> cycle for many days
> (we only use them for traceability), the logid is
> being reset at some
> point and then starts over at zero or one thus
> duplicating itself.
>
> Thank you as always.
>
> Costas Anastassiades,
> Intracom SA
> Athens - Greece
>

===
Best Regards

Bob
[log in to unmask]
(tel: 0468 224038)

"Make it so"
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com