> I just made some nbackup tests (FB 2.5.2 SS, Windows XP) and noticed that

whenever I use it to restore a database, it's Oldest transaction (OIT) gets
stuck. It remains at the same value until next database sweep. Is it a bug
or a feature ?



I think the problem is here:




What nbackup do is




* start transaction

* execute ALTER DATABASE START BACKUP

* commit transaction

* do physical copy of db file


* start transaction

* execute ALTER DATABASE END BACKUP

* commit transaction





the START BACKUP will redirect all subsequent db changes into delta file,

which means the following COMMIT will write its changes into delta,

not the original file, which means the copied database contains

this transaction in ACTIVE state.

On first connect to copied database the state of this "active" transaction
is

changed to "rollback", thus it becomes your stuck OIT.




Ivan

[Non-text portions of this message have been removed]