Will FixPak 10 for db2 UDB work on Redhat Enterprise Linux V3?
The IBM site says that FixPak 10 is only available for the
2.6 kernel.
http://www-306.ibm.com/software/data/db2/udb/support/downloadv8_linux2632bitinte
l.html

I am trying to set up the database for LMS on a Linux box. This box is
running SLES 9. I am trying to run the following scripts as user:
db2inst1 :
./cr_db2db_audit.sh

I'm on the west coast of Florida south of Tampa, and as I
wait for my house to look like something from the Flinstones,
and am making sure that all of my disaster recovery ducks
are in a row, I though maybe someone could use my linux-based

Greetings all,
  We have a complicated statement in DB2 which takes long hour to
complete and we have created most of the indexes. Does anybody knows
how to tune the following statement to optimize the query?

I created a view:
create view is3.base_index(bhid, index_1, index_2)
    as select bhid,
         cast(0+1.5*birth_epd+2.5*weaning_epd as decimal(8,4)),

I have a large Address table, NAME col. is varchar and has titles like:
'MR. ABC and MRS. MMM' want to update to: 'ABC and MMM'
'MR. ABC and MRS. MMM' want to update to be: 'ABC and MMM'
'DR. KKK MMM' want to update to be: 'KKK MMM'

I am trying to get connection pooling working with Tomcat 5.5 and DB2
v8.1.  This was working under Websphere Studio Application Developer
5.x but we are trying to move onto Eclipse and Tomcat.
The datasources seem to get created correctly but I get an error when I

How does DB2 on s/390 resolve the access if the table its trying to
access has an edit routine? Will it ever use indexes before invoking
the edit routine when a select statement is executed? Under what all
conditions will it not use any of the indexes available to it

Is there an easy way (without duplication of the complex expression) to
use the same complex expression in all three places?
Will something like this work?
WITH (SELECT t.*, <complex expr> AS x FROM <base_table> AS t) AS wt

I have two (actually many) dates in a table I want to validate on
insertion. The following works in the case of only one WHEN clause but
fails with two (or more), with the (improper? inappropriate?) error message:
 SQLCODE: -104, SQLSTATE: 42601, SQLERRMC: CREATE TRIGGER

Does anyone have any ideas on how to effectively manage an environment
that has multiple DB2 server environments running on different
versions? We have several different systems mostly running on UNIX, but
not all running the same level of DB2. We have version 6, 7, and 8

Can any of you explain the major differences in LOAD and IMPORT in
laymen terms?
I've read the DB2 docs: "[IMPORT] Inserts data from an external file
with a supported file format into a table, hierarchy, or view. A faster

I've tried reading just about every post I can on raid stiping / extent
size etc and I'm just getting myself more confused than ever. Here's my
situation.
On a Windows Server 2000 standard edition system with only 1gb ram

I want the result of my query to be returned in a specific order based
upon values of a column. It will be more clear with example. Let's say
my table is as below
Col1 Col2 Col3

I have a DB2 database on the IBM iSeries platform, on which I created
several Stored Procedures with the SQLCODE as a return-parameter.
These Stored Procedures are called from a Windows application (build in
Visual Basic) using an ADO/OLE DB Provider on a IBM Client Access ODBC