|
Problem IC88607
|
Status: Geschlossen |
GET SNAPSHOT MAY REPORT A VERY HIGH INCORRECT VALUE FOR "APPLICATION CONNECTS" |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problembeschreibung: |
"db2 get snapshot for database on DBNAME" may report a very high
"Application Connects" value, 4294967295 in following example.
Here is an example of the snapshot:
----------------------------------
Database Snapshot
Database name = SAMPLE
Database path = /home/....
Input database alias = SAMPLE
Database status = Active
Catalog database partition number = 0
Catalog network node name =
Operating system running at database server= AIX 64BIT
Location of the database = Local
First database connect timestamp = 02/05/2012 ...
Last reset timestamp = 02/05/2012 ...
Last backup timestamp = 02/03/2012 ...
Snapshot timestamp = 02/05/2012 ...
Number of automatic storage paths = 1
Automatic storage path = /home/db2inst1
File system ID = 92233722172434...
Storage path free space (bytes) = 3074293760
File system used space (bytes) = 79822848
File system total space (bytes) = 3221225472
High water mark for connections = 5
Application connects = 4294967295 <<----
Secondary connects total = 4
Applications connected currently = 0
Appls. executing in db manager currently = 0
Agents associated with applications = 4
Maximum agents associated with applications= 5
Maximum coordinating agents = 5
----------------------------------
- This problem exists on any DB2 version, v9.1, v9.5 and v9.7.
- The incorrect value reported in snapshot is due to an error in
'reset monitor' internal processing.
- The fix of APAR will modify the reset monitor behavior so that
subsequent snapshots report Application connects value
correctly.
- There is no side effect by this APAR.
- There is no work around but if users execute it again later,
it may report correct value since the problem is a timing
issue. |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Recommended to upgrade to DB2 for LUW v10.1 FP2 *
**************************************************************** |
| Local-Fix: |
|
| verfügbare FixPacks: |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Lösung |
Fix available from v101fp2 onwards. |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 27.11.2012
01.01.2013
01.01.2013 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.1.0.2
|
 |
| 10.5.0.2
|
|
