|
Problem IC69809
|
Status: Closed |
LOG RENAME ARRAY GETS FULL IN HADR ENVIRONMENT |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Under certain workload conditions the rename array will get full
in a HADR environment. The db2diag log will be flooded with
messages such as:
2010-06-03-08.39.28.581384-240 I2407774E533 LEVEL:
Warning
PID : 11100 TID : 46979333744960PROC :
db2sysc 0
INSTANCE: xxxxx NODE : 000 DB : GPR
APPHDL : 0-22666 APPID: *LOCAL.db2gpr.100602004002
AUTHID : XXXXX
EDUID : 894 EDUNAME: db2agent (GPR) 0
FUNCTION: DB2 UDB, data protection services, sqlpRenameStartUse,
probe:1230
MESSAGE : Log file 1685 is not added by DB2 because renameArray
is full.File
could be renamed while in use.
This condition might lead to a excessive number of entries in
the db2diag.log with this messages. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users using HADR on all platforms *
****************************************************************
* PROBLEM DESCRIPTION: *
* Under certain workload conditions the rename array will get *
* full in a HADR environment. The db2diag log will be flooded *
* with messages such as: *
* *
* *
* *
* 2010-06-03-08.39.28.581384-240 I2407774E533 LEVEL: *
* Warning *
* *
* PID : 11100 TID : 46979333744960PROC : *
* db2sysc 0 *
* *
* INSTANCE: xxxxx NODE : 000 DB : GPR *
* *
* APPHDL : 0-22666 APPID: *
* *LOCAL.db2gpr.100602004002 AUTHID : XXXXX *
* *
* EDUID : 894 EDUNAME: db2agent (GPR) 0 *
* *
* FUNCTION: DB2 UDB, data protection services, *
* sqlpRenameStartUse, probe:1230 *
* *
* MESSAGE : Log file 1685 is not added by DB2 because *
* renameArray is full.File could be renamed while in use. *
* *
* *
* *
* This condition might lead to a excessive number of entries *
* in the db2diag.log with this messages. *
* *
* And these messages also indicate that those log files are *
* not protected from being renamed by other applications yet. *
* If these log files are incorrectly renamed while in use, *
* some operations such as online backup which still need these *
* log files could fail. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v97fp3, v95fp7 or v91fp10 *
**************************************************************** |
| Local Fix: |
Since the rename array is a memory structure the database will
need to be re-activated. |
| available fix packs: |
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
The problem is fixed in DB2 v97fp3 |
| Workaround |
restart the database |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC69987 IC69988 IC70050
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 09.07.2010
02.08.2010
27.03.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.1.FP10,
9.5.FP7,
9.7.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
