Running a query for the first time on DB2 takes a fixed amount of time.
But when query is executed for the second time, the amount of time is
usually less since the query is (most probably) cached already.
I would like to clear out the DB2-UDB 8.2 query cache (I want the

Might some kind soul take on this Oracle statement and
translate it into DB2? Yes ... I know the equivalent of SYSDATE
is CURRENT TIMESTAMP, and that DUAL is SYSIBM.SYSDUMMY1.
But I'm puzzled by the 'Q' (Quarter), and NEXT_DAY

We currently are running a CRM application that uses DB/2 7.2 for the data
repository. We will be upgrading to 8.2 later this year....maybe....time and
resources permitting.
The database is currently being hosted with a managed service provider (MSP)

I'm looking for DB2 V7 release . So far , I've been only able to
retrieve V8 personal edition on IBM ftp .
So does anyone know where I can find a v7 release ...
Thanks in advance .

Sometimes we get DSNU255I running DSNUTILB in a LOAD LOG NO RESUME YES of a
partitionned Tablespace.
For example, le last one was during the SORT-BUILD phase of loading in
paralell 78 records in a TS having 10 part (only one index).

I just downloaded the file
414465677 Jun  5 16:15 LNX26_V822_PE_x86-64.tar
from the IBM Web DB2 web site, and it looks like the file is corrupt.
N. Shamsundar

While doing some TPC benchmark testing on DB2-UDB 8.2, I face the
following problem when running this query:
select *
from lineitem

Need product information on IBM's Integration Integrator (I.I) for
conversion of SyBase calls to UDB calls.  Production allows for
conversion of modules one-by-one and then when all modules are
converted the database (SyBase) can be converted and I.I removed.

My client wants to disallow a birth date in the future. First I tried
the obvious:
ALTER TABLE IS3.ANIMALS
    ADD CONSTRAINT b_d_f

I've just noticed the following errors in my db2diag.log file:
2003-07-18-01.29.18.203000-240 E3301H585          LEVEL: Severe (OS)
PID     : 1532                 TID  : 2944        PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000         DB   : DBNAME

Transferrate & Overhead's defaults have been reduced in version 8.2,
respectively 0.9 to 0.18 and 24.1 to 12.67.
1) Why reducing so much the transferrate so that it seems ridiculous
compared to values preconised by IBM for ESS storage :

I'm toying with a test setup at which I try to let 2 instances work
together as partitions. When I fire up both instances, and I try to
connect to a test database called parttest (a simple 1 table database).
I get the following exception:

I'm doing a simple SELECT with an ORDER BY clause, and I'd like to get the
rows back with a row number included.  Something like this:
SELECT <????> POSITION, NAME, TOTAL FROM MYTABLE ORDER BY TOTAL DESC
So I want the rows in the result to be numbered 1, 2, 3, 4 etc. so it looks

This is the Query which i am using
describe table db2prod.c9t_assignment
but i get an error
describe table db2prod.c9t_assignment

I installed the trial version of DB2 UDB 8.2, I was wondering, how can
I determine the exact execution time (in miliseconds not timerons) for
a specific query ?
Thank you very much.