Output has been truncated

Batter · #1 (**permalink**) 09-28-10, 05:17

Hi,
when i running in command prompt (WinXP):
db2 -x select message_data from message where message_id = 3409948 > c:\output.xml

In output.xml i get trauncated data which ends with 'Output has been truncated' message.
MESSAGE_DATA is LONG VARCHAR 32600
And in output i get only 8192 characters || 'Output has been truncated'

How can i get full output 32000 characters long, without truncation.

Using DB connect tool ver 9.5

tonkuma · #2 (**permalink**) 09-28-10, 07:01

How about this?

(tested on Command Editor of DB2 9.7 on Windows/XP.)

Code:

------------------------------ Commands Entered ------------------------------
EXPORT TO c:\output.xml OF DEL MODIFIED BY nochardel 
SELECT message_data 
 FROM  message
 WHERE message_id = 3409948
;
------------------------------------------------------------------------------
SQL3104N  The Export utility is beginning to export data to file 
"c:\output.xml".

SQL3105N  The Export utility has finished exporting "1" rows.


Number of rows exported: 1

Batter · #3 (**permalink**) 09-28-10, 07:22

I get message:
SQL1325N The remote database environment doesn't support the command or one of command options

changed to:
EXPORT TO c:\output.xml OF IXF
SELECT message_data
FROM message
WHERE message_id = 3409948

SQL2019N An error occurred while binding the utilities to the database

tonkuma · #4 (**permalink**) 09-28-10, 07:47

Is your table on DB2 for Windows/XP?

If not, the filetype of EXPORT command must be IXF.
And you can't use this way.

DB2 Version 9.5 for Linux, UNIX, and Windows Message Reference, Volume 2

Quote:

SQL1325N The remote database environment does not support the command or one of the command options.

Explanation:
An attempt has been made to issue a DB2 workstation database specific command or command option against a host database through DB2 Connect or federated server. The following commands generate this error when issued against a DB2 for MVS*, DB2 for OS/400* or SQL/DS* database:
...

As well, the following commands generate this error with incorrect options:
v IMPORT (Import table) The filetype must be IXF, commitcount must be 0 for offline import or must not be automatic for online import, and the first word in the Action String (for example, ″REPLACE into ...″) must be INSERT.
v EXPORT (Export table) The filetype must be IXF.

The command cannot be processed.

Batter · #5 (**permalink**) 09-28-10, 07:49

As i wrote before, i tried IXF:
changed to:
EXPORT TO c:\output.xml OF IXF
SELECT message_data
FROM message
WHERE message_id = 3409948

SQL2019N An error occurred while binding the utilities to the database

Internet Services

Web Development

Digital Marketing

Consumer Tech