home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC84391 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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.
verfügbare FixPacks:
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

Lösung
First fixed in DB2 Version 10.1 Fix Pack 1.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
14.06.2012
01.11.2012
01.11.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.1 FixList
10.5.0.1 FixList