DB2 - Problem description
Problem IC78485 | Status: Closed |
DB2 IMPORT FAILS WHEN EXTRA LINE FEED CHARACTER EXISTS IN THE COMMAND | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
When using the db2 import command, it will fail if an extra line feed character (0x0A) is added in the command. The following for example will fail: db2 "IMPORT FROM /home/db2inst1/importdata/test_import.dat OF DEL > MODIFIED BY COLDEL| > METHOD P ( 1 , 2) > INSERT INTO TEST_IMPORT > (COL1,COL2)" In this case, the problem is caused by the line feed character after TEST_IMPORT. The operation will fail with the following error: SQL2018N The utility encountered an error "" while attempting to verify the user's authorization ID or database authorizations. This can also be reproduced using the SYSPROC.ADMIN_CMD() command. If the 'import' command is placed inside that routine, it will fail as long as there is a line feed character in the command. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7, Fixpak 6 * **************************************************************** | |
Local Fix: | |
Removing the line feed character, and placing the entire command in one line will workaround the problem. The placement of the line feed character may allow the command to work without have to put the entire command in one line, but to avoid hitting this APAR it is recommended to avoid using a line feed. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 Version 9.7, Fixpak 6 | |
Workaround | |
see Local Fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 02.09.2011 15.06.2012 15.06.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.7. | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.6 |