Farren,

You should be happy. Things are working
exactly as they should. That is one of the large
benefits that you get by using transaction logging.
Since every change to a logged database is captured in
the transaction log, you are backing up only the necessary
changes when you back up the transaction logs.
The DBIIDs shouldn't normally change during the week, unless
you run maintenance activity (like compaction)... which most
customers perform on the weekends just before their
full (selective) backups.

Thanks,

Del

----------------------------------------------------

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 11/03/2005
08:56:34 AM:

> Hi
>
> I'm sorry, I'm still slightly confused. The problem is that under
> incremental backup I am not often seeing the databases backed up. I now
> know that if the db is compacted that will change the dbiid and thus it
> will be backed up, but is this enough.
>
> My position is this. We do a full backup each weekend, so I'm happy with
> this. Each day we do an incremental which apparently doesn't back any
> databases up, but we do then back up the transaction logs. So I'm happy
> that we can restore from the weekly and then roll forward without too
much
> trouble.
>
> So can I be happy that things are working as necessary, or should the
> database dbiids be changing under other circumstances as well and thus
> being backed up during the week also?
>
> I apologise if I'm just being dumb here :-(
>
> Many thanks again
>
> Farren Minns
> Solaris System Admin / Oracle DBA
> IT - Hosting Services
>
> John Wiley & Sons, Ltd.