By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
454,236 Members | 1,309 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 454,236 IT Pros & Developers. It's quick & easy.

DB2 backup and connection timeout

P: n/a
I am looking for some insight into a backup problem for an online
database backup performed each night on my Linux Instance (SuSe 9
kernel 2.6) of DB2 DPF 8.2. The backup is initiated using a script
that does a db2_all, first to the catalog partition and then to the
remaining partitions of the cluster. The entire backup takes about a
half hour.

My system is periodically monitored by an application that does a
remote connection using the db2 client on a Unix box. If the
connection is not completed within a specified period of time, a text
message is sent to alert of the slowdown. For some reason, several
minutes after the backup of the catalog partition is done, ie a few
minutes into the backup of the remaining partitions, the connection
process times out. I have tried moving the backup to different time of
night and the behavior is the same.

This appears to happen only since the upgrade to 8.1 FP 11. Is there
something in the behavior of DB2 backup that has changed that might
cause this?

What can be done to eliminate this timeout?

Sep 11 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Ian
mike_dba wrote:
I am looking for some insight into a backup problem for an online
database backup performed each night on my Linux Instance (SuSe 9
kernel 2.6) of DB2 DPF 8.2. The backup is initiated using a script
that does a db2_all, first to the catalog partition and then to the
remaining partitions of the cluster. The entire backup takes about a
half hour.

My system is periodically monitored by an application that does a
remote connection using the db2 client on a Unix box. If the
connection is not completed within a specified period of time, a text
message is sent to alert of the slowdown. For some reason, several
minutes after the backup of the catalog partition is done, ie a few
minutes into the backup of the remaining partitions, the connection
process times out. I have tried moving the backup to different time of
night and the behavior is the same.

This appears to happen only since the upgrade to 8.1 FP 11. Is there
something in the behavior of DB2 backup that has changed that might
cause this?

What can be done to eliminate this timeout?
It would be helpful if you provided a little more information.

For example, the DB2 error that you get, and perhaps some/all of the
script that does the checking.

Sep 11 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.