Page #89 (List of Tables)

---

Chapter 5: Operational Setup

Example 5-1: DB2 UDB installation verification

Example 5-2: Using versionInfo.sh to verify the fix pack installation

Example 5-3: Successful Verification by using ivt.sh

Example 5-4: ServerCluster block of the plug-in configuration file

Example 5-5: Cataloging the DB2 UDB z/OS and S/390 subsystem

Example 5-6: Port Conflict during the installation verification test

Example 5-7: The conflicting port 9090 on AIX

Example 5-8: Remote Database Cataloging

Example 5-9: Starting the Application Server

Example 5-10: Using serverStatus.sh to verify the Application Server is running

Example 5-11: Add URI Entry into plug-in file for AccessEmployee application

Example 5-12: Data Preparation Scripts for DB2 EJB Sample Application

Chapter 6: WebSphere Application Server V5 Performance Tuning

Example 6-1: List PMI service configuration objects

Example 6-2: Enabling HTTP Server server-status in httpd.conf on Windows

Example 6-3: Using netstat to determine the time_wait values

Example 6-4: Sample output from the Runtime Advisor

Example 6-5: Use of singleton to cache EJB initial context references

Example 6-6: Use of gaurd statements for logging

Chapter 7: Monitoring and Tuning of DB2 UDB V8

Example 7-1: Command syntax for UPDATE MONITOR SWITCHES

Example 7-2: Command to activate snapshot monitoring

Example 7-3: Command syntax for get snapshot

Example 7-4: Output of a DBM snapshot

Example 7-5: Output of a database snapshot

Example 7-6: Syntax of CREATE EVENT MONITOR statement

Example 7-7: Default table spaces

Example 7-8: Sample output for a snapshot of a buffer pool

Example 7-9: Agent information from the snapshot monitor

Example 7-10: Snapshot for locks (database part)

Example 7-11: Snapshot for locks (application part)

Example 7-12: Snapshot for locks (list of locks)

Chapter 8: DB2 UDB V8 and WAS V5 Integrated Performance

Example 8-1: DataStoreHelper

Example 8-2: Monitor WebSphere application from DB2 UDB

Example 8-3: DB2 UDB Sanpshot command

Example 8-4: Use IBMSession to hold the session information

Example 8-5: Servlet initially creates a session object

Example 8-6: Subsequently modifying the session object

Example 8-7: Using connection pooling and PreparedStatement

Chapter 9: Integrated Troubleshooting

Example 9-1: DB2 diagnostic log file db2diag.log

Example 9-2: Using db2support to collect diagnostic information

Example 9-3: Using JDBC Trace for the Legacy JDBC Driver

Example 9-4: New user creating and authority changing

Example 9-5: Error messages from query employee running

Example 9-6: SystemOut.log Investigation

Example 9-7: SystemOut.log investigation after changing currentSchema property

Example 9-8: JDBC Trace investigation

Example 9-9: Reproducing problem using similar SQL statements

Example 9-10: Information from the DB2 diagnostic log DB2DIAG.LOG

Example 9-11: Snapshot of TRADE3DB for concurrency scenario

Example 9-12: Database configuration setting of TRADE3DB

Example 9-13: Update the configuration

Example 9-14: Snapshot results after resolving concurrency problem

Example 9-15: db2diag.log file to evaluate high CPU consumption scenario

Example 9-16: Snapshot to evaluate high CPU consumption scenario

Example 9-17: Buffer pool values

Example 9-18: Bufferpool settings

Example 9-19: Database configuration change for high CPU consumption scenario

Example 9-20: db2diag.log file to evaluate high CPU consumption scenario

Example 9-21: Snapshot to evaluate high CPU consumption scenario

Example 9-22: Num_PoolAgents configuration

Appendix A: Trade3 Application

Example A-1: Trade.acf configuration file

---