|
Problem IC69988
|
Status: Geschlossen |
LOG RENAME ARRAY GETS FULL IN HADR ENVIRONMENT |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 |
| Problembeschreibung: |
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. |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* HADR Env *
****************************************************************
* PROBLEM DESCRIPTION: *
* Log rename array gets full *
****************************************************************
* RECOMMENDATION: *
* Apply FP10 *
**************************************************************** |
| Local-Fix: |
Since the rename array is a memory structure the database will
need to be re-activated. |
| verfügbare FixPacks: |
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
|
| Lösung |
Problem first fixed in FP10 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 16.07.2010
16.06.2011
16.06.2011 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 9.1.0.10
|
 |
