If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > strang warning on export

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 01-19-06, 17:38
DBA-Jr DBA-Jr is offline
Registered User
 
Join Date: Mar 2005
Posts: 108
strang warning on export

Hi All,
Here are the facts. If I telnet to my DB server, connect to database1 and export any table, I receive warning msg for each varchar column. For example,
SQL3132W The character data in column "SUBJECT" will be truncated to size
"128".

The column is defined as varchar(128).

Also, DESCRIBE TABLE does display values under "Type name". Instead, values from "Length", "Scale" and "Nulls" (they are right to "Type nmae") are shifted to the position under "Type name".

If I connect to datanase2 in the same instance, everything is normal.

If I connect to database1 remotely, everything is normal.

I can not figure out what the problem is.
Any advice is highly appreciated. Thanks.
Reply With Quote
  #2 (permalink)  
Old 01-20-06, 01:53
przytula przytula is offline
Registered User
 
Join Date: Nov 2004
Posts: 374
export

never seen this before : db2level ? platform ?
try to bind again : db2ubind.lst and db2cli.lst and db2schema.bnd
if v8 try also db2updv8 -d xxxx
Hope this will help
__________________
Best Regards, Guy Przytula
DB2/ORA/SQL Services
DB2 DBA & Advanced DBA Certified
DB2 Dprop Certified
http://users.skynet.be/przytula/dbss.html
Reply With Quote
  #3 (permalink)  
Old 01-22-06, 15:32
DBA-Jr DBA-Jr is offline
Registered User
 
Join Date: Mar 2005
Posts: 108
Thank you for advice. It still does the same.

DB2 level:
"DB2 v8.1.0.58", "s040914", "MI00093", and FixPak "6"

OS level:
Red Hat Enterprise Linux AS release 3 (Taroon Update 6)
Kernel 2.4.21-32.ELsmp on an i686

The only difference between database1 and database2 is the code set. database1 (with error) is using ISO8859-1, while database2 (without error) is using UTF-8. I tried to set profile variable DB2CODEPAGE=819 (corresponding to ISO8859-1), it still didn't work.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On