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

DB2CFEXP DOES NOT EXPORT AUTOMATIC VALUES PROPERLY IF BACKUP CLAUSE IS
SPECIFIED

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Utility db2cfexp does not export properly configuration 
parameters with the AUTOMATIC flag if backup clause is 
specified. Because of that backup configuration file is not 
imported by db2cfimp utility properly and parameters which had 
this flag set are reset to 0.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1 Fix Pack 4.                      * 
****************************************************************
Local Fix:
Remove parentheses from the output file before importing it, 
e.g. using tr command (UNIX): 
$ tr -d '()' < old_file > new_file 
where old_file is the file stored using db2cfexp with backup 
clause.
available fix packs:
DB2 Version 10.1 Fix Pack 4 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 4.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.12.2013
02.06.2014
02.06.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList