Depending on what you're scripting your prescheduled command in, you can
include a loop that checks the databases every 10 seconds. Something
like....
dbstop
while (are databases that aren't completely stopped?) {
sleep 10
}
Then when the while loop exists, your backups will start.
Alex Paschal
Storage Administrator
Freightliner, LLC
(503) 745-6850 phone/vmail
-----Original Message-----
From: Stormy Maddux [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 13, 2002 2:20 PM
To: [EMAIL PROTECTED]
Subject: preschedulecmd and a wait period
One of our servers has several large Oracle database and although they run a
preschedulecmd from the dsm.opt to shut down, by the time the dbstop command
is run and the backup starts, some of the databases are still not shut down,
the datafiles are shown in use and tried multiple times.
Are there inherent ofsets in the pre and post schedule command executions?
Is there anyway to build in a "wait" along with the scheduled command??
Thanks,
Stormy Maddux
