home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC84391 Status: Closed

IMPORT DOES NOT GIVE CORRECT ORIGINAL ERROR MESSAGE IF IT FAILS WITH
AUTHORIZATION ISSUE WHILE DOING IMPLICIT BIND

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
If IMPORT fails with authorization issue while doing implicit 
BIND, you might see the following error messages: 
 
SQL3022N  An SQL error "-552" occurred while processing the 
SELECT string in the Action String parameter. 
SQL3022N  An SQL error "-552" occurred while processing the 
SELECT string in the Action String parameter. 
SQL3021N  The user does not have the authority to run the 
specified IMPORT command on table "USER1.TABLE1". 
 
i.e. IMPORT does not give the original SQL0552N error message 
right after the SQL3022N error message, but duplicate SQL3022N 
error message. 
 
The APAR serves to give the correct original error message 
instead of duplicate utility error message as below: 
 
SQL3022N  An SQL error "-552" occurred while processing the 
SELECT string in the Action String parameter. 
SQL0552N  "USER1" does not have the privilege to perform 
operation "BIND". SQLSTATE=42502 
SQL3021N  The user does not have the authority to run the 
specified IMPORT command on table "USER1.TABLE1".
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 1.                      * 
****************************************************************
Local Fix:
Check db2diag.log or obtain a DB2 trace to know the orginal 
error information.
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 10.1 Fix Pack 1.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.06.2012
01.11.2012
01.11.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList