alter system checkpoint in hot backup script. Why

From: Guy Dallaire <gd-newsgroups_at_spamex.com>
Date: Mon, 10 Nov 2003 17:31:46 -0500
Message-ID: <ulUrb.1104$IK2.109764@news20.bellglobal.com>

Hello,

While visiting http://www.geocities.com/lydian_third/ (Which by the way is a REALLY GOOD resource) I noticed in an hot backup article, that the author is doing:

alter tablespace ... begin backup;
host copy ...
alter tablespace ... end backup;
alter system checkpoint; <- This puzzles me

Why are we issuing a checkpoint ? In the article, is says that it is to force its header SCN back into synchronisation with the rest of the database. I don't see the point (no pun intended) of the checkpoint here. The author really knows what he's doing, I'm sure, but I'd like to know why this is necessary/beneficial.

Isn't oracle supposed to know that the datafile is out of backup mode and automatically start updating the header when needed ?

Thanks Received on Mon Nov 10 2003 - 16:31:46 CST