I searched far and wide for more information on how to correct this
problem, but did not find any information on what to do.
We have successfully installed DB2 8.1 on Linux.
SuSE 9.0.

Here is what I get from CLP commands
db2 =>  VALUES date('20-12-2003')
SQL0181N  The string representation of a datetime value is out of
range.

I get SQL0670N when altering a table to add an extra colum.
Can an SMS tablespace be changed to have a larger page size ?
Many thanks,
Nigel Robbins

I interrupted running a sql batch file containing several insert
statements.
The db server stops responding to any commands and just hangs.
The entries in the log file are as below, Any idea what could be

After moving to new version of DB2 we faced with strange problem - code that
worked fine with DB2 v7.2.x on DB2 v 8.1 sometimes write error message like
the:
===message===

I have a db2 database with tablespaces of several pagesizes.  It is to
be placed on a new server with a RAID 5 configuration.
I am told that neither striping size, nor any other configuraton issue
of the RAID array has any effect on the database as far as pagesize is

Folks,
I did run into a small problem afterall. Running my first SP I am
seeing a number of errors in the windows 2k server event viewer.
Following is a paste:

Helpful folks,
I ran across a statement I found rather confusing in the IBM-published
Advanced DBA Certification Guide and Reference for UDB V8. On page 107
the author is explaining why the a very low amount of prefetching may

We are trying to set up version 8 for first time and during install it
asks if I want a partitioned instance. I said no. But just curious, is
this same as the EEE in version 7. I recall in version 7, the extended
enterprise edition is a separate install. Has IBM decided to combined

I have a function which calls a proc which returns a cursor. When i
try to create this in db, it says..
DB21034E  The command was processed as an SQL statement because it was
not a

Hi,
V8.1 fp4a
We have been performing some performance measurements on SQL functions
and have observed the following and need to verify if this is expected

When exporting character data with column length greater than 254, the data
is truncated. For some reason I have to export the data in DEL format. Is
there a way to avoid the truncation of data ?

I have a small function below, when i try to create this, it says the
following error..
DB21034E  The command was processed as an SQL statement because it was
not a

Hi All;
On DB2 (OS390) v7.1 is there any reason to avoid the use of varchar()
datatype for columns less than 50 bytes in length? Current DBA
standard is to only use varchar when length of character field exceeds

Am I the only one in the world that selects dates and timestamps with
OLEDB?
V8 of UDB has brought me a big problem.  
The PATCH2=24 setting no longer works the way it used to.  The