|
Problem IC62140
|
Status: Closed |
Automatic binding of bind files after fixpack installation fails after binding db2ubind.lst. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
After fix pack installation, the binding of the db2ubind.lst,
db2cli.lst, and db2schema.bnd files occurs automatically.
However, if one binding operation ends with warning then the
other bind files will not be bound to the database.
This problem can be recreated by the following steps:
1. Prepare IBM DB2 V9.5 FP2 environment.
2. Install fix pack V9.5 FP3a.
3. Activate or connect to the database.
The db2ubind_lst.log file may contain the following message and
the db2cli_lst.log and db2schema_bnd.log files are not
generated.
(These log files are located in the DB2DIAG path.)
=== db2ubind_lst.log ===
LINE MESSAGES FOR db2ubind.lst
------
----------------------------------------------------------------
----
SQL0061W The binder is in progress.
LINE MESSAGES FOR db2clpnc.bnd
------
----------------------------------------------------------------
----
SQL0595W Isolation level "NC" has been escalated to
"UR".
SQLSTATE=01526
LINE MESSAGES FOR db2ubind.lst
------
----------------------------------------------------------------
----
SQL0091N Binding was ended with "0" errors and "1"
warnings.
==================== |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 UDB Version 9.7 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error description field for more information. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Version 9.7 FixPack 1. *
**************************************************************** |
| Local Fix: |
User can bind the db2cli.lst and the db2schema.bnd files
manually if this problem has occured.
See:
http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp?t
opic=/com.ibm.db2.luw.qb.server.doc/doc/t0024970.html |
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in DB2 UDB Version 9.7 FixPack 1. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 21.07.2009
22.12.2009
22.12.2009 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
