If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

much easier to create a script and force applications with quiesce command
schedule this script with crontab or any other at tool

Best Regards, Guy Przytula
Database Software Consultant
Good DBAs are not formed in a week or a month. They are created little by little, day by day. Protracted and patient effort is needed to develop good DBAs.
Spoon feeding : To treat (another) in a way that discourages independent thought or action, as by overindulgence.
DB2 UDB LUW Certified V7-V8-V9-V9.7-V10.1-V10.5-V11 Fundamentals- DB Admin - Advanced DBA -Dprop..
Information Server Datastage Certifiedhttp://www.infocura.be

If I understand it correctly and if we encounter the same symptoms as IBM describes in the article, it should mean that Automatic Offline Backup (steps DB2 takes to accomplish Offline Backup via Automatic Maintenance) is implemented incorrectly and doesn't work at all.

@zulfiqarali.memon - Thank you for pointing me to the article. I already knew it, in addition it contains only very generic information, it doesn't contain a useful piece of info that could help me in our situation.

If I understand it correctly and if we encounter the same symptoms as IBM describes in the article, it should mean that Automatic Offline Backup (steps DB2 takes to accomplish Offline Backup via Automatic Maintenance) is implemented incorrectly and doesn't work at all.

No, the key phrase of that note is:
'When you have users trying to connect in a loop, the timing issue is exposed. If there was no connection attempt, the backup would be successful.'

Yes, my first note had a mistake: this job doesn't just do a backup attempt but issues a QUIESCE DATABASE command before this.
But QUIESCE DATABASE doesn't prevent the database manager from the database activation to check if the user trying to connect has DBADM or QUIESCE_CONNECT authorities on this database.

The only way to prevent these undesirable activations is to QUIESCE INSTANCE with RESTRICT ACCESS MODE.
But it seems that this Automatic Maintenance job doesn't quiesce the instance, but quiesces only the database.

I've seen that once at a client. They 'solved' that by temporarely change the SVCENAME so no remote clients could find the instance anymore...I tend to get goosepickels when I see that kind of constructions.

Somewhere between "too small" and "too large" lies the size that is just right.
- Scott Hayes

I've seen that once at a client. They 'solved' that by temporarely change the SVCENAME so no remote clients could find the instance anymore...I tend to get goosepickels when I see that kind of constructions.

Yes, I've seen the same.
We have to do such things (alternatively we can use a firewall) since AFAIK there is no ability to prevent let's say remote jobs with SYS* authorities from db activation attempts.