Hi

We have an environment that relies on 5 databases to which a number
of applications connect. The service they provide is 24x7 and so we
need to keep downtime to a minimum.

Our strategy has been to build a database pooling and management
object that provides maximum throughput whilst ensuring only the
required amount of connections are maintained based on load from the
applications. This object also manages the database becoming
unavailable, placing the applications in a wait state and notifying
system admins of this event.

The plan was to be able to perform the following maintenance of the
databases. Not necessarily every night, probably a SWEEP and BACKUP
every night (EARLY morning), and then the following twice a week.
1- SWEEP the database
2- "gfix -shut" the database
3- MEND the database
4- VALIDATE the database
5- RENAME the database
6- GBAK -B the database
7- GBAK -B -R the database to its original name

The Problem:
We have created a user called TESTUSER and provided access rights to
all database objects. We have run a GFIX -SHUT on the database, which
should make the database unavailable to all but SYSDBA (right?!?).
The issue is our applications are managing to reconnect after a short
while, using TESTUSER and we have not brought the database online.

Please could someone advise on what we are doing wrong or what we be
the best way to make the database(s) unavailable to the TESTUSER
whilst these maintenance tasks are being executed.

thanx