(Win2003 Server, db2 UDB 9, RAID 5-0, 32k tablespace, managed by
database, OS caching off).  I'm mostly interested in speed of
retrieval.
Here's a metaphore to a problem that I have:

   I have 2 DB2 databases, referencing one another through nicknames.
Lets say databases are DataB1 and DataB2. The source table <tab1> is
in schema <schema1> on DataB1. DataB2 has a nickname for <tab1> in it
in a schema called DataB1.

Can someone provide some pointers to information regarding upgrading a
database from 32 bit V7 UDB to 64 bit V9 UDB on AIX hosts?

I logon the OS use  instance owner db2inst1 and enter ps -al, the
output is:
F S   UID   PID  PPID  C PRI  NI ADDR SZ WCHAN  TTY          TIME CMD
0 S   509 12434     1  0  76   0 - 13450 pipe_w pts/0    00:00:00

(DB2 9) Inoperative packages must be explicitly rebound, but invalid
packages can be rebound automatically. Do you know what is the
difference?
Example:

Greetings all.
We recently upgraded from DB2 v8.2 to 9.1 FP1 and tested the AUTO_REORG
functionality. As recommended by SAP, we scheduled the job REORGCHK_ALL
weekly. This spews out an error message for each table as follows:

DB2 on AIX 5.3.
I cannot find our v.9 license key.
/var/ifor/nodelock contains a license key for our v.8 installation. We
have v.9 installed on the same machine and I'm assuming there is a

Is it true that there are no type 4 jdbc drivers to connect to a DB2
server v7.1? The DB2 server is hosted on ACF2 (OS/390). We would be
connecting from windows and solaris boxes.
If it is true, what are my options? Will I have to install db2 connect

In a rather large database, I face this problem:
Several tables are regularly updated through rather long-running DELETE
+INSERTs. Using uncommitted read as isolation level seems unsafe, as I'd
like consistent data (that's one of the main points of using a DBMS in

DB2 V8 FP14 on RedHat Linux
Single Partition Database
Tables with LOB data
Periodically, a large delete is performed by the application.   I need

we have a little discussion about lock escalation...
What is better for performance: To have an escalation "early" (smaller
locklist) or aviod the escalation with a big lock list?
We don't care about concurrency - because the changes have to be done,

I install the UDB Ver 8.2 FixPack 9 on HP Proliant Server running RHEL
4
and Java Version is 1.4.2.
After install, i try to create new database.

We are using DB2 UDB 8.2 on AIX 5.X.
My question is regarding for setting the default schema for a
particular user group.  Let explain below.
Let say we are having the following user groups,

anybody ever used a external compresion library through the COMPRLIB
keyword in DB2 BACKUP ?
Any hints and tips ?
TIA

Generally we work with the 2 part qualified table names in db2 i.e.
<schema>. <table name>
Is there a more fully qualified table name ? I've seen that a select
from <database name>.<schema>.<tabname> also works.