Hi,
Our environment is UDB v7.2 running on AIX.
We have an application that is going to be running a series of table loads
on a daily basis to refresh the data in their tables. We're currently
trying to architect the best solution for doing this. One of the main
concerns for the application is to ensure that no active users will be
getting in their way while the load process is running. Basically, what
they want to do is to force all users off the database (using the "force
applications" command), lock the tablespace with the tables being loaded
for exclusive use using the "quiesce tablespaces for table" command, run
the loads, run some stored procedures to rebuild some summary tables, run a
backup, and then release the lock with a "quiesce . . . reset" command.
There are 10 tables being loaded, and they all reside in the same
tablespace. I'm envisioning that this process will look something like
this:
1) db2 force application ( app1, app2, app3, etc . . . ) - this would
probably be done through a shell script running the "db2 list application"
command to get all the application handles
2) db2 quiesce tablespaces for table T1 exclusive
3) db2 load . . . into table T1 . . . hold quiesce . . .
4) perform loads for tables T2 through T10 with "hold quiesce"
5) run the stored procedures which will read the tables just loaded to
rebuild 2 "summary" tables (which reside in a different tablespace)
6) db2 backup database . . .
7) db2 quiesce tablespaces for table T1 reset
This seems pretty straightforward to me, but this is the first application
that we've had that has done this kind of processing with UDB, so we have
no practical experience in doing this (yet).
Any comments, warnings, corrections, advise, etc., would be welcome and
appreciated.
Thanks,
Bill Gallagher, DBA
Phoenix Life Insurance
Enfield, CT
=====
To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
For other info (and scripts), see http://people.mn.mediaone.net/scottrmcleod
