19.06.2013 Views

DB2 UDB for z/OS Version 8 Performance Topics - IBM Redbooks

DB2 UDB for z/OS Version 8 Performance Topics - IBM Redbooks

DB2 UDB for z/OS Version 8 Performance Topics - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Impact on coupling facility: You do not need to resize the group buffer pools, lock<br />

structure or SCA in the coupling facility as a result of moving to <strong>DB2</strong> V8, even though the<br />

virtual buffer pools have now moved above the bar and have a longer memory address.<br />

Improved LPL recovery: Currently LPL recovery requires exclusive access to the table<br />

space. <strong>DB2</strong> V8 introduces a new serialization mechanism whereby LPL recovery is much<br />

less disruptive. In addition, <strong>DB2</strong> V8 automatically attempts to recover LPL pages as they<br />

go into LPL, when it determines the recovery will probably succeed. Instrumentation has<br />

also improved whereby <strong>DB2</strong> now attempts to indicate the reason pages are added to the<br />

LPL.<br />

Restart LIGHT enhancements: If indoubt units of recovery (UR) exist at the end of restart<br />

recovery, <strong>DB2</strong> will now remain running so that the indoubt URs can be resolved. After all<br />

the indoubt URs have been resolved, the <strong>DB2</strong> member that is running in LIGHT(YES)<br />

mode will shut down and can be restarted normally.<br />

Change to close processing <strong>for</strong> pseudo close: Table spaces defined as CL<strong>OS</strong>E NO are still<br />

closed during pseudo close processing at the end of the PCL<strong>OS</strong>ET interval. This caused<br />

degraded per<strong>for</strong>mance because the data sets must be physically opened again on the<br />

next access. <strong>DB2</strong> V8 now really honors the CL<strong>OS</strong>E NO attribute during pseudo close<br />

processing. See PTF UQ74866 <strong>for</strong> APAR PQ69741 <strong>for</strong> <strong>DB2</strong> V7.<br />

Buffer pool long term page fix: <strong>DB2</strong> V8 allows you to fix the buffer pool pages once in<br />

memory and keep them fixed in real storage. This avoids the processing time that <strong>DB2</strong><br />

needs to fix and free pages each time there is an I/O.<br />

Batched index page splits: Prior to V8, index page splits <strong>for</strong> indexes with inter-<strong>DB2</strong><br />

read/write interest required multiple synchronous log writes and multiple separate writes to<br />

the group buffer pool. This was required to ensure the integrity of the index <strong>for</strong> other <strong>DB2</strong><br />

members during the actual page split. <strong>DB2</strong> V8 is able to accumulate the index page split<br />

updates and process them as a single entity, thereby reducing log writes and coupling<br />

facility traffic.<br />

320 <strong>DB2</strong> <strong>UDB</strong> <strong>for</strong> z/<strong>OS</strong> <strong>Version</strong> 8 Per<strong>for</strong>mance <strong>Topics</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!