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

DB2LOOK FAILS IF THE DATABASE HAS LARGE NUMBER OF LBAC SECURITY LABEL
COMPONENTS

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
db2look fails if the database has large number of LBAC security 
label components. 
 
$ db2look -d DBname -e -z schema -o db2look.out 
-- No userid was specified, db2look tries to use Environment 
variable USER 
-- USER is: DB2INST1 
-- Specified SCHEMA is: schema 
-- Creating DDL for table(s) 
 
-- Schema name is ignored for the Federated Section 
-- Output is sent to file: db2look.out 
Segmentation Violation (core dumped) 
 
In some cases, Memory fault may occur.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.5 FixPack 10                            * 
****************************************************************
Local Fix:
Not Available.
Solution
Problem was first fixed in DB2 UDB Version 9.5 FixPack 10
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC81269 IC87867 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
01.02.2012
30.10.2012
30.10.2012
Problem solved at the following versions (IBM BugInfos)
9.5.FP10
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.10 FixList