Hi Alex,
I'll take your word for loving AIX, meantime, this does NOT seem to
change things - have a look at the output I get:
$ db2move EDIDCE07 export -l /db2/backup/db2move_20071114/lobdata_move
***** DB2MOVE *****
Action: EXPORT
Start time: Wed Nov 14 12:19:09 2007
Connecting to database EDIDCE07 ... successful! Server: DB2 Common
Server V8.2.7
EXPORT: 28 rows from table "TXDSD2 "."PARSEEDIACTIONS"
*** Table "TXDSD2 "."PARTIES": ERROR 3107. Check message file
tab2.msg!
*** SQL Warning! SQLCODE is 3107
*** SQL3107W There is at least one warning message in the message
file.
EXPORT: 66 rows from table "TXDSD2 "."PARTYBUSINESSPROTOCOLS"
EXPORT: 0 rows from table "TXDSD2 "."PARTYCATEGORIES"
*** Table "TXDSD2 "."PARTYCERTIFICATEIDS": ERROR 3107. Check message
file tab5.msg!
*** SQL Warning! SQLCODE is 3107
*** SQL3107W There is at least one warning message in the message
file.
And so on and so forth.
Boo.
Any other ideas or suggestions please?
Thanks.
Aurora
-----Original Message-----
From: Alex Levy
[mailto:db2udbdba-ezmlmshield-x94895898.[Email address protected]
Sent: 14 November 2007 13:13
To: LazyDBA Discussion
Subject: RE: Problem with db2move and VARCHAR columns
Hello Aurora
Well we feel your pain! But you're just going to love UDB.
It looks like the issue here is that you have LONG VARCHARs that are
getting truncated. All long data, not just LOBs, needs to be exported to
a LOB file.
(And remember this makes your life easier too, as there is a display
length limit on a *NIX line).
Please try db2move dbname export -l lobpath and advise how you get on.
You can specify a comma separated list of lobpaths if you prefer.
I'm sorry, I never use db2move as it's a bit old fashioned, but hope the
above will work for you.
Regards
Alex Levy
-----Original Message-----
From: Dell Anno Aurora Emanuela BUSSIGNY Contractor for NBS IS/IT
[mailto:db2udbdba-ezmlmshield-x21442060.[Email address protected]
Sent: 14 November 2007 11:17
To: LazyDBA Discussion
Subject: RE: Problem with db2move and VARCHAR columns
Hi Ed,
DB21085I Instance "db2insd8" uses "32" bits and DB2 code release
"SQL08027"
with level identifier "03080106".
Informational tokens are "DB2 v8.1.1.128", "s061108", "U810098", and
FixPak "14".
Thanks.
Aurora
-----Original Message-----
From: Edwards Ed
[mailto:db2udbdba-ezmlmshield-x66672087.[Email address protected]
Sent: 14 November 2007 12:13
To: LazyDBA Discussion
Subject: RE: Problem with db2move and VARCHAR columns
What version of DB2 are you running?
-----Original Message-----
From: Dell Anno Aurora Emanuela BUSSIGNY Contractor for NBS IS/IT
[mailto:db2udbdba-ezmlmshield-x92558521.[Email address protected]
Sent: Wednesday, November 14, 2007 6:04 AM
To: LazyDBA Discussion
Subject: RE: Problem with db2move and VARCHAR columns
Hi Amr,
That is exactly what does NOT work for me.
I used the db2move <dbname> export and the VARCHAR columns give me
problems (not LOBs).
Thanks.
Aurora
------------------------------------------------------------------------
----------------------
From: "Dell Anno Aurora Emanuela BUSSIGNY Contractor for NBS IS/IT "
To: "LazyDBA Discussion"
Date: 14-11-07 11:45
Subject: Problem with db2move and VARCHAR columns
Hi list,
please be gently explicative to me since I am rather new to this LUW
stuff (I have worked on DB2 for over 10 years, but on mainframes).
Guess what, I'm lost in AIX-land.
I am trying to execute the db2move utility with the EXPORT option of a
DB with 300 tables, and the problem is that the does not come out
"right", a lot of tables are missing - it exported 111 tables only out
of the lot, and the problem seems to be the type of the column (VARCHAR
in my case).
The export.out file contains a lot of warning messages with SQL3132W ,
such
as:
SQL3132W
The character data in column column will be truncated to size size.
Explanation:
The character data column has a defined size that is longer than the
longest default character column which can be exported; each value will
be truncated to the specified size.
I searched the APARs database, and found exactly sweet FA.
Anyone have any ideas or suggestions on how to overcome this? As
mentioend right at the top, any suggestions would need to be almost
step-by-step because this platform's intricacies are still a bit of a
mystery to me.
Thanks in advance for any pain relief.
Aurora
DB2 & UDB email list listserv db2-l LazyDBA home page