APAR status
Closed as fixed if next.
Error description
Load with "lock force" option, run on a table with constraints, does not force off locks and errors out with SQL0911 RC 68 (if locktimeout is set to a specific value). If locktimeout is set to -1, then the load waits for the locks indefenitely. Test case: (i) Create a table with a constraint definded on it. (ii) Run a db2 +c select with RR on the same table from one window (iii) Run a load with lock force option into this table from a second window. This is supposed to force off any existing locks on the table, but instead just times out after whatever value the locktimeout is set to.
Local fix
The load works fine when... (i) Constraint checking is turned OFF (ii) The db2 +c select is done with CS instead of RR (iii) The load command is issued with the "with read access" and "with lock force" options. (Note :- with read access is not compatible with a load replace)
Problem summary
Problem Description: load with force not forcing all locks Problem Summary: see above Users affected: Those using the load with LOCK FORCE option
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
IZ23947
Reported component name
DB2 UDB ESE AIX
Reported component ID
5765F4100
Reported release
820
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-06-07
Closed date
2009-02-06
Last modified date
2009-02-06
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
R820 PSN
UP
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"820","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
06 February 2009