469,927 Members | 2,013 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,927 developers. It's quick & easy.

Running multiple SQL scripts in the background ... no longer possible?

Just noticed something rather annoying after upgrading my test box (a
Linux server running DB2 UDB v8 for LUW) to fixpak 11 (for reference it
was previously on fixpak 7).

In the past I've relied heavily on the ability to start multiple
long-running SQL scripts in the background and have them all run in
parallel. Unfortunately, it seems that somewhere between fixpak 7 and
fixpak 11 something has been fixed / broken which prevents more than a
single script from running at once...

For example, I might have three scripts called extract1.sql,
extract2.sql, and extract3.sql each of which connects to another DB2
database (typically the same database which sits on a mainframe), and
extracts a relatively large dataset to an IXF file.

As the scripts are long running, and as the database is on a mainframe
(which excels at running things in parallel), I'd typically set off all
these scripts simultaneously in the background:

$ db2 -tvf extract1.sql &
$ db2 -tvf extract2.sql &
$ db2 -tvf extract3.sql &

If I then periodically looked at the IXF files being exported by the
three scripts, I'd see all three growing simultaneously. Further, if I
checked for db2 processes I'd see *three* db2bp processes (one for each
script, naturally).

However, after upgrading to fixpak 11 I noticed that no matter how many
scripts I start, there's only ever *one* db2bp process, and only one
script is actually exporting anything at any given time.

I *think* I've found a work-around for the time being: start each
script in an entirely separate shell (not great, but it seems to work).

Has anyone else run across this problem and found any other solutions?


Apr 14 '06 #1
2 4510
Are you using DB2 Connect?

Apr 14 '06 #2
m0****@yahoo.com wrote:
Are you using DB2 Connect?

In as much as its part of DB2 UDB ESE, yes (specifically, DB2 UDB ESE
for LUW with fixpak 11 is installed, and the OS is Linux with a 2.6

But that did raise an interesting thought... I recently (around the
time I installed fixpak 11) changed the cataloging from node+database
to node+dcs+database for the DB2 for z/OS entries (no particular reason
other than that's the way the control center does it, and it also
enables one to catalog DB2 for z/OS databases with names longer than 8
characters). I tried changing back some of the catalog entries to just
node+database to see whether it'd make a difference, but it didn't.

(that said, I'm not sure what the difference between these two styles
of cataloging is anyway; I've used both more or less randomly over the
years and never noticed any explicit differences other than being able
to catalog DB2 for z/OS databases with names longer than 8 characters
when using a DCS entry)

Does anyone happen to know exactly which fixpak caused this change?
I've been reading through the APAR lists from fixpaks 8 thru 11, but
haven't found anything yet that sounds like this change...

Apr 15 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

4 posts views Thread by Peter Otten | last post: by
2 posts views Thread by Tim Daneliuk | last post: by
1 post views Thread by Patrick | last post: by
8 posts views Thread by TS | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.