It seems that the backup failed and you never unquiesced the db after
it failed. It was still in quiesce mode. The only way to take it out
of quiesce mode is to unquiesce it or stop and start the instance.
On Jul 31, 10:19 am, bic1s...@gmail.com wrote:
I have a script to do this:
CONNECT TO mydb;
QUIESCE DATABASE IMMEDIATE FORCE CONNECTIONS;
CONNECT RESET;
backup database mydb to e:\sqlbackups\mydb compress;
CONNECT TO mydb;
UNQUIESCE DATABASE;
During the backup, the server ran out of disk space. We freed up
space.
The next day, we couldn't connect to the db, so it was rebooted.
When backup ran that night here's the output:
QUIESCE DATABASE IMMEDIATE FORCE CONNECTIONS
SQL1371N Instance or database "mydb" is already quiesced. Quiesce
type:
"Database".
CONNECT RESET
DB20000I The SQL command completed successfully.
backup database mydb to e:\sqlbackups\mydb compress
SQL1035N The database is currently in use. SQLSTATE=57019
CONNECT TO mydb
Database Connection Information
Database server = DB2/NT 8.2.5
SQL authorization ID =
Local database alias = mydb
UNQUIESCE DATABASE
DB20000I The UNQUIESCE DATABASE command completed successfully.
And yet, I can quiesce and unquiesce the db without any problems. Any
ideas?
