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 IC69201 Status: Closed

CREATE TABLE FAILED AND RETURN ERROR CODE -487 WHEN USER MAPPING DEFINED
WITH ACCOUNTING OPTION.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
The ACCOUNTING user mapping option should be invalid now. 
 
If you create user mapping with options ACCOUNTING, error code 
"-487" will be returned. 
 
For example, 
create user mapping for user server S options(ACCOUNTING 
'<your_id>', remote_authid '<your_id>', remote_password 
'<your_password>') 
DB20000I  The SQL command completed successfully. 
 
=> db2 set passthru S 
DB20000I  The SQL command completed successfully. 
 
=> db2 "create table t1(c1 char(5))" 
DB21034E  The command was processed as an SQL statement because 
it was not a  valid Command Line Processor command.  During SQL 
processing it 
returned:  SQL1822N  Unexpected error code "-487" received from 
data source 
"S". Associated text and tokens are " SQL0487N  Routine "" 
(specific 
name "") attempted to execute a".  SQLSTATE=560BD
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* N/A                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See error description.                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.7 FP3 or higher                             * 
****************************************************************
Local Fix:
Do not use accounting option.
available fix packs:
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem First Fixed in DB2 Version 9.7 Fix Pack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.06.2010
25.09.2010
24.01.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP3
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.3 FixList
9.7.0.3 FixList