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

EMPTY DATABASE CATALOG ENTRY WHEN USING DB2CFIMP

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
When using "db2cfimp <file>" an additional database catalog 
entry with no name will be created which is not part of the 
config file which was imported. 
 
Database 9 entry: 
 
 Database alias                          = 
 Database name                        = 
 Local database directory            = /opt/db/data 
 Database release level               = f.00 
 Comment                                = 
 Directory entry type                 = Indirect 
 Catalog database partition number    = -1 
 Alternate server hostname            = 
 Alternate server port number         = 
 
 
How to recreate: 
- verify that there is no "empty" database cataloged in the 
source environment 
- db2cfexp dbdir.txt maintain 
- check the dbdir.txt file if there are entries which no 
database names (there are no such entries) 
- db2cfimp dbdir.txt at the target environment 
- a LIST DB DIRECTORY shows an additional catalog entry which 
has a blank database name
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 users.                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.5 FP5 or newer fix pack                    * 
****************************************************************
Local Fix:
Solution
Problem First Fixed in DB2 Version 10.5 Fix Pack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
18.07.2014
26.03.2015
26.03.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.5 FixList