SQL3107W There is at least one warning message in the message file.

When I try to call db2move $todbname load from a shell script it will
give me this error in the log. When I call it from the command line
using the exact same dataset it works perfectly. Does anyone know
what might be causing that to occur? Below is the .msg file.
>
Thanks for any help. I really need to put this script to bed. This
is the last hangup.
>
Regards
Eric
>
++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++
++
Script snippet:
#
# Import Data
#
cd $db2moveimpdir/$expdate - This is the directory that I extracted
the .ixf files into.
mv db2move.lst db2move.lst.orig - Copy the original db2move.lst so I
can SED it using the next line.
sed -e "/$fromdbuser/ s//$todbuser/g" db2move.lst.orig db2move.lst
>
`db2move "$todbname" load` - Still in the directory I run the command
wait
>
++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++
+++
LOAD.out error:
>
*** Table "DB8INST1"."ALCO_LOGIN_SESSION": ERROR 3107. Check message
file tab359.msg!
>
*** SQL Warning! SQLCODE is 3107
>
*** SQL3107W There is at least one warning message in the message
file.
>
++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++
+++
>
root@hopdb1 # more tab359.msg
>
SQL3104N The Export utility is beginning to export data to file
"tab359.ixf".
>
SQL3105N The Export utility has finished exporting "7" rows.
>
SQL3501W The table space(s) in which the table resides will not be
placed in
>
backup pending state since forward recovery is disabled for the
database.
>
SQL3039W The memory available to LOAD for DATA BUFFER prohibits full
LOAD
>
parallelism. Load parallelism of "1" will be used
>
SQL3109N The utility is beginning to load data from file
>
"/backups/eldtest/dba/db2import/db2move/20071015/tab359.ixf".
>
SQL3500W The utility is beginning the "LOAD" phase at time
"10-29-2007
>
07:40:53.079771".
>
SQL3150N The H record in the PC/IXF file has product "DB2 02.00",
date
>
"20071015", and time "084357".
>
SQL3153N The T record in the PC/IXF file has name "tab359.ixf",
qualifier "",
>
and source " ".
>
SQL3168W The PC/IXF column specified to be loaded into database
column "5" is
>
not compatible with the database column. Nulls will be inserted.
>
SQL3519W Begin Load Consistency Point. Input record count = "0".
>
SQL3520W Load Consistency Point was successful.
>
SQL3110N The utility has completed processing. "7" rows were read
from the
>
input file.
>
SQL3519W Begin Load Consistency Point. Input record count = "7".
>
SQL3520W Load Consistency Point was successful.
>
SQL3515W The utility has finished the "LOAD" phase at time
"10-29-2007
>
07:40:53.253147".
>
SQL3500W The utility is beginning the "BUILD" phase at time
"10-29-2007
>
07:40:53.300471".
>
SQL3213I The indexing mode is "REBUILD".
>
SQL3515W The utility has finished the "BUILD" phase at time
"10-29-2007
>
07:40:53.529893".
>
SQL3107W There is at least one warning message in the message file.

On Oct 31, 4:59 pm, EricDeWerth <Eric.DeWe...@gmail.comwrote:
>
>
>
>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
AFAIK db2 thinks there a difference between the table you are
exporting from and the table you are loading to (column 5). Can you
post a describe of both tables?
>
/Lennart- Hide quoted text -
>
- Show quoted text -