>>>Chief among them is the ability to stop a database and/or tablespace and
>>>start it in read-only or utility mode like is possible on the mainframe
>>Can you give us more information on why this would help? Keep in mind
>>that in v8, LOAD, REORG and BACKUP are all online operations.
> What you mean is that a Backup has the "option" to be Online.
> The DB2 online backup for Linux, UNIX and Windows has many flaws. There are
> many horror stories about people who try to restore from a backup, but don't
> have the logs, and the restore fails. Without the logs, the online backup is
> Online backups are very dangerous for that reason and I would never use one
> unless it was absolutely required. If I did use an online backup, I would
> supplement it with offline backups whenever it was feasible (when no users
> could connect to the database).
> Most people don't really need an online backup, except that there is often a
> problem doing an offline backup while there is a connection to the DB still
> active (even if not being used) which causes the offline backup to fail. I
> have even had trouble with the Control Center connections to cause
> contention problems with offline backups (when no other user has connected
> to the DB).
> Rather than worrying about killing all the connections, it would be
> preferable (IMO) to allow the database (or tablespace) to be stopped and
> restarted in read-only mode or utility mode that would always allow an
> offline backup to occur. Or at the very least allow an online backup to be
> created that does not require any logs to be valid (assuming that no updates
> have occurred).
> On DB2 for OS/390, it has always been possible to take a self-contained
> backup (image copy) while the database is available to applications for read
> only that does not need any logs to use in a recovery. Such a backup can be
> taken when the database is in utility-only mode, or read-only mode, or
> really can be taken any time the utility can get an exclusive lock on the
> resource (without having to worry about any active benign connections from
> other applications).
> DBA's should be able to take offline backups (or an online backup that does
> not require logs) when the database is in read-only mode.
> I really think that the Toronto team needs to look at the DB2 OS/390 backup
> and recovery capabilities and try to get some of the same functionality. A
> DB2 for OS/390 DBA could never live without the ability to start a database
> in read-only or utility-only mode.
> In general production DBA's on Linux, UNIX, and Windows spend a large
> percentage of their time dealing with contention caused by database
> connections that are not even being used. A DB2 for OS/390 DBA rarely
> worries about disconnecting threads from a database to perform DBA work
> (usually only in the case of application problem).