
www.Usenet.com
| <-- __Chronological__ --> | <-- __Thread__ --> |
"Artur Fajok" <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>...
> > rollforwarddb -j = rolls forward the database i.e. restores the database
> > to the last checkpoint without applying journals. This will also switch
> > off journalling for a database i.e. any journalled tables will not be
> > journalled and instead will only be journalled after the next checkpoint
> > i.e. ckpdb +j
> >
>
> I always thought that 'rollforward -j' restores database to checkpoint
> without applying journals. It does not switch journaling off - it leaving
> journaling state as it was in checkpoint - if database wasn't journaled
> in time checkpoint was taken, it may LOOK like rollforwarddb switched
> it off.
>
> Am I right?
Here is very specific testing I've done between II 2.0 and II 2.6:
Sequence of events(note journaling is turned off in cbf when a new
table is created):
Table State Table State
II 2.0 II 2.6
createdb
create table disabled disabled
set journaling on table at next ckp at next ckp
ckpdb -j at next ckp at next ckp
rollforwarddb -j at next ckp at next ckp
ckpdb +j enabled enabled
rollforwarddb -j at next ckp at next ckp * point 1
rollforwarddb +j at next ckp enabled * point 2
point 1:
why is the state not recovered to state it was in the previous
ckp(enabled)? The database says it is in a journaled state here, but
table is not.
point 2:
difference in table journaling state between 2.0 and 2.6
| <-- __Chronological__ --> | <-- __Thread__ --> |