Error Import Db2 Linux - AS400

[pgu...@gmail.com]

Hello Forum

I have the following problem:

I need to import data from a DB2 AS400 Linux BD2 This particular
problem is that a file has fields LOB.

This is the command and the message that comes

export to /home/db2inst1/Documents/DB2INST1.ixf of ixf messages /home/
db2inst1/Documents/msgs.txt
select * from TFORM00015 WHERE cpersona_compania = 2 and csubsistema =
'02' and ctransaccion = '2008' and versioncontrol = 7

import from /home/db2inst1/Documents/DB2INST1.ixf of ixf messages /
home/db2inst1/Documents/msgs.txt
insert into W3PSI1.TFORM00015

Error
SQL3150N The H record in the PC/IXF file has product "DB2 02.00",
date
"20090413", and time "233509".

SQL3153N The T record in the PC/IXF file has name
"/home/db2inst1/Documents/DB2INST1.ixf", qualifier "", and source
" ".

SQL3109N The utility is beginning to load data from file
"/home/db2inst1/Documents/DB2INST1.ixf".

SQL3306N An SQL error "-7008" occurred while inserting a row into the
table.

SQL7008N REXX variable "TFORM00015" contains inconsistent data.
SQLSTATE=55019

SQL3110N The utility has completed processing. "1" rows were read
from the
input file.

May help

Greetings

Pedro Guia
3PSI

[Karl Hanson]

No expertise here with export/import, but I noticed the SQL7008 (-7008)
error. Often for DB2 on AS/400 (iSeries, System i, ...), if an attempt
to insert, update, or delete a row is made when the target table is not
journaled, SQL7008 can result. When running under transaction control,
the journal is needed to enable commit or rollback. If you can check
messages in the System i job log, the SQL7008 reason code would verify
this (see partial description below).

You can likely find more info by searching the web using search terms
like "iseries sql7008". Briefly, if this is the crux of the problem, to
fix it you can start journaling the table, or if it is an option, run
without transaction control. The latter is often called COMMIT(*NONE)
or NC (no commit).

http://tinyurl.com/djuq6n

===> wrkmsgd sql7008 qsqlmsg
Message ID . . . . . . . . . : SQL7008

Message file . . . . . . . . : QSQLMSG

Library . . . . . . . . . : QSYS

Message . . . . : &1 in &2 not valid for operation.

Cause . . . . . : The reason code is &3. Reason codes are:

1 -- &1 has no members.

2 -- &1 has been saved with storage free.

3 -- &1 not journaled, no authority to the journal, or the journal
state is *STANDBY. Files with an RI constraint action of
CASCADE, SET NULL, or SET DEFAULT must be journaled to the
same journal.
4 and 5 -- &1 is in or being created into production library but the
user has debug mode UPDPROD(*NO).

.
.

--
Karl Hanson