I am running an application on V5R4 which utilises CPYTOIMPF
command. The application is crashing at
CPYTOIMPF when tried to run more than three times. If I sign off and
sign on again, then the application is working for another three aor

How can I implement using REORGCHK to tell REORG what DB2 UDB v8
tables, etc to perform REORG on?
Any example script will be highly appreciated.
Okonita

DB2 9.1.3 on Windows.
If I take a backup from a system where all DB2 data is on drive D: and
try to restore or "create from backup", onto drive E: of another system,
I find:

I want to track the DML changes that are occurring on important
tables.
I can create a trigger to track these but how can i get the Ip address
and SQl statement executed.

If i do a "Select nextval for <seq_name> from sysibm.sysdummy1",
it increases the values of nextval by1.
How can i find out the nextval of a sequence without actually
increasing the value.

Hi, All
I have trouble with db2 instance creation (DB2 9.1.2 on AIX 5.3)
When i run command for instance creation :
./db2icrt -a SERVER -p 50000 -s ese -u db2fenc1 db2inst1

1) Am I right here for DB2Viper2beta?
2) Just ran into coupla problems installing Db2Viper2beta on Windows Server
2k8beta3.
Interested or should I simply try with a released OS?

How can i find out the space that is currently not utilized/utilized
in the tablespace?
I tried from syscat.tablespaces, but it doesn't seem to give me that
information.

I wanted to create a table with a unique index in a partitioned
database and found out that both the Primary key and all Unique
constraints must contain the partitioning key. If not explictliy
specified the partitioning key (distribution key)  is choosen from the

   I apologize if I'm asking a question that was asked and
answered...?
   We have a DB2 v9.1.0.2 (fixpak2) partition environment..
   We have the issue of users creating  test tables in userspace1 and

Receive this message in db2diag.log:
MESSAGE : DB2 is waiting for log files to be archived.
Database hangs.  Using DB2 8.2.2 on Solaris with Veritas backup
software.

The SYSIBM.SQLPRIMARYKEYS stored procedure is corrupt in one of my
database. How do I go about re-creating this? I have tried rebinding
"call sysproc.rebind_routine_package('P', 'SYSIBM.SQLPRIMARYKEYS',
'ANY')" but get a nasty -443 error. Also, the SQLPRIMARYKEYS entry

db2 ESE v9.1.3, windows xp, local database sample.
I run db2ce, connect to this sample database and issue these commands:
---
create table newtab_test (a int not null generated always as identity,

I have a mixed workload DB2 UDB 8.2 FP 14 Windows x64 database. The
database performs as per the expectations. I have just one small
question. The sort related parameters are configured as follows:
Sort heap threshold (4KB)                  (SHEAPTHRES) = 50000

Let's say I have a table TABLE 1:
CREATE TABLE TABLE1
(
       TAB1_ID BIGINT,