DB2 FOR LUW / DB2FORLUW / 970 - DB2

When run db2pdcfg without any option, it should just display 
current status/settings, it should not run -flushbp.  Following 
is what been observed :- 
hotel49:/home/hotel49/juntang:)db2pdcfg 
Current PD Control Block Settings: 
 
All error catch flag settings cleared. 
 
db2cos is enabled for engine traps. 
   PD Bitmap:      0x1000 
   Sleep Time:     3 
   Timeout:        30 
 
Current bitmap value:  0x0 
 
 
State of the bufferpools: 
Oldest LSN: 00000000023281AC 
Newest LSN: 0000000002352EB7 
Initiating background flush. 
You can use "db2pdcfg -flushbp q" to monitor the progress of 
the flush operation. 
When the oldest LSN reported by the q option is greater than the 
newest LSN reported during the initial flush, then the flush has 
completed. 
 
Instance is not in a sleep state 
 
DB2 trap resilience is enabled. 
   Current threshold setting :  0 ( disabled ) 
   Number of traps sustained : 0 
 
 
FODC (First Occurrence Data Capture) options: 
   Dump directory for large objects (DUMPDIR)= 
/home/hotel49/juntang/sqllib/db2dump/ 
   Dump Core files (DUMPCORE)= AUTO

Problem Description: 
DB2PDCFG WITHOUT OPTION IS TO DISPLAY CURRRENT STATUS ONLY, IT 
SHOULD NOT RUN -FLUSHBP OPTION 
Problem Summary: 
When run db2pdcfg without any option, it should just display 
 
current status/settings, it should not run -flushbp.  Following 
is what been observed :- 
hotel49:/home/hotel49/juntang:)db2pdcfg 
Current PD Control Block Settings: 
 
All error catch flag settings cleared. 
 
db2cos is enabled for engine traps. 
   PD Bitmap:      0x1000 
   Sleep Time:     3 
   Timeout:        30 
 
Current bitmap value:  0x0 
 
 
State of the bufferpools: 
Oldest LSN: 00000000023281AC 
Newest LSN: 0000000002352EB7 
Initiating background flush. 
You can use "db2pdcfg -flushbp q" to monitor the progress of 
the flush operation. 
When the oldest LSN reported by the q option is greater than the 
newest LSN reported during the initial flush, then the flush has 
completed. 
 
Instance is not in a sleep state 
 
DB2 trap resilience is enabled. 
   Current threshold setting :  0 ( disabled ) 
   Number of traps sustained : 0 
 
 
FODC (First Occurrence Data Capture) options: 
   Dump directory for large objects (DUMPDIR)= 
/home/hotel49/juntang/sqllib/db2dump/ 
   Dump Core files (DUMPCORE)= AUTO

n/a

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
 

Problem is first fixed in Version 9.7 Fix Pack 2

n/a

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

11.11.2009
13.05.2010
13.05.2010

9.7.FP2