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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

--------------------------- -------- ------- ------- -------<br />

IDENTIFY 0 0.00 0.00 0.00<br />

CREATE THREAD 2 261.75 1.00 1.00<br />

SIGNON 0 0.00 0.00 0.00<br />

TERMINATE 2 261.75 1.00 1.00<br />

ROLLBACK 0 0.00 0.00 0.00<br />

COMMIT PHASE 1 0 0.00 0.00 0.00<br />

COMMIT PHASE 2 0 0.00 0.00 0.00<br />

READ ONLY COMMIT 0 0.00 0.00 0.00<br />

UNITS OF RECOVERY INDOUBT 0 0.00 0.00 0.00<br />

UNITS OF REC.INDBT RESOLVED 0 0.00 0.00 0.00<br />

SYNCHS(SINGLE PHASE COMMIT) 2 261.75 1.00 1.00<br />

QUEUED AT CREATE THREAD 0 0.00 0.00 0.00<br />

SUBSYSTEM ALLIED MEMORY EOT 0 0.00 0.00 0.00<br />

SUBSYSTEM ALLIED MEMORY EOM 0 0.00 0.00 0.00<br />

SYSTEM EVENT CHECKPOINT 0 0.00 0.00 0.00<br />

HIGH WATER MARK IDBACK 1 130.87 0.50 0.50<br />

HIGH WATER MARK IDFORE 1 130.87 0.50 0.50<br />

HIGH WATER MARK CTHREAD 1 130.87 0.50 0.50<br />

In addition, the high water mark <strong>for</strong> MAXDBAT and CONDBAT are listed in the enhanced <strong>DB2</strong><br />

PE Statistics reports, under the DRDA Remote Locations section.<br />

Package in<strong>for</strong>mation added to deadlock trace records<br />

When a deadlock (IFCID 172) occurs, <strong>DB2</strong> now adds package and DBRM related in<strong>for</strong>mation<br />

about the holder and blocker that allows you to identify the culprit and victims more easily. The<br />

following in<strong>for</strong>mation is added <strong>for</strong> both the blockers and holders of the locks involved in the<br />

deadlock:<br />

► Location name<br />

► Collection name<br />

► Program or package name<br />

► Consistency token<br />

This in<strong>for</strong>mation is also available from <strong>DB2</strong> PE, as shown in Example 4-5.<br />

Example 4-5 Enhances deadlock trace record<br />

LOCATION: PMO<strong>DB2</strong>A <strong>DB2</strong> PERFORMANCE EXPERT (V2) PAGE: 1-3<br />

GROUP: N/A RECORD TRACE - LONG REQUESTED FROM: NOT SPECIFIED<br />

MEMBER: N/A TO: NOT SPECIFIED<br />

SUBSYSTEM: SDA1 ACTUAL FROM: 04/16/04 09:53:59.42<br />

<strong>DB2</strong> VERSION: V8 PAGE DATE: 04/16/04<br />

PRIMAUTH CONNECT INSTANCE END_USER WS_NAME TRANSACT<br />

ORIGAUTH CORRNAME CONNTYPE RECORD TIME DESTNO ACE IFC DESCRIPTION DATA<br />

PLANNAME CORRNMBR TCB CPU TIME ID<br />

-------- -------- ----------- ----------------- ------ --- --- -------------- ------------------------------------------------------<br />

N/P N/P 00BB46094741 N/P N/P N/P<br />

N/P N/P 'BLANK' 09:53:59.43270268 103075 3 172 DEADLOCK DATA NETWORKID: G998C442 LUNAME: HF05 LUWSEQ: 1<br />

N/P N/P N/P<br />

|-------------------------------------------------------------------------------------------------------------------------<br />

| DEADLOCK HEADER<br />

|INTERVAL COUNT: 152949 WAITERS INVOLVED: 2 TIME DETECTED: 04/16/04 09:53:59.424504<br />

|.........................................................................................................................<br />

| UNIT OF WORK<br />

| R E S O U R C E<br />

|LOCK RES TYPE: PAGESET LOCK DBID: DSNDB06 OBID: SYSDBASE<br />

|LOCK HASH VALUE: X'00000906'<br />

| B L O C K E R<br />

206 <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!