DB2 FOR LUW / DB2FORLUW / A10 - DB2

The check on database configuration parameter BLOCKNONLOGGED is 
done before an implicit or explicit "COPY NO" is converted to a 
"COPY YES TO..." via the DB2_LOAD_COPY_NO_OVERRIDE registry, 
thus defeating the purpose of the registry variable. 
 
Consider the following: 
 
db2 connect to SAMPLE 
db2 update db cfg using BLOCKNONLOGGED NO 
db2set DB2_LOAD_COPY_NO_OVERRIDE='COPY YES to /db2inst1/backups' 
 
 
Then perform a LOAD command without specifying a COPY flag: 
 
$ db2 "load from /dev/null of del replace into mytab" 
SQL3039W  The memory available to LOAD for DATA BUFFER prohibits 
full LOAD 
parallelism.  Load parallelism of "3" will be used 
 
SQL27966W  The DB2_LOAD_COPY_NO_OVERRIDE registry variable value 
"COPY YES to 
/db2inst1/backups' overrides the COPY NO parameter specified in 
the 
Load. 
 
SQL3109N  The utility is beginning to load data from file 
"/dev/null". 
... 
 
Since a COPY flag was not specified, it defaults to "COPY NO" 
and as such, the registry setting forces conversion this 
implicit "COPY NO" to "COPY YES to /db2inst1/backups" 
 
 
In the case when database configuration parameter BLOCKNONLOGGED 
is set to YES however, this becomes problematic: 
 
db2 connect to SAMPLE 
db2 update db cfg using BLOCKNONLOGGED YES 
db2set DB2_LOAD_COPY_NO_OVERRIDE='COPY YES to /db2inst1/backups' 
 
 
Then perform a LOAD command without specifying a COPY flag: 
 
$ db2 "load from /dev/null of del replace into mytab copy no " 
SQL2032N  The "COPY FLAG" parameter is not valid. 
SQLSTATE=22531 
 
 
This APAR fix will ensure that the BLOCKNONLOGGED YES 
enforcement is checked after the load copy override is 
performed.

**************************************************************** 
* USERS AFFECTED:                                              * 
* using LOAD command                                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to version 10.1 Fix Pack 5                           * 
****************************************************************

First fixed in version 10.1 Fix Pack 5

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

20.01.2015
13.07.2015
13.07.2015