2 options
Striving for optimal journal performance on DB2 universal database for iSeries / IBM, International Technical Support Organization.
- Format:
- Book
- Author/Creator:
- IBM International Technical Support Organization Staff, Corporate Author.
- Series:
- IBM redbooks.
- IBM redbooks
- Language:
- English
- Subjects (All):
- Database management.
- IBM Database 2.
- OS/400.
- Physical Description:
- xvi, 162 p. : ill.
- Edition:
- 1st ed.
- Place of Publication:
- Rochester, Minn. : IBM Corp., International Technical Support Organization, 2002.
- Language Note:
- English
- Contents:
- Front cover
- Contents
- Figures
- Tables
- Notices
- Trademarks
- Preface
- The team that wrote this redbook
- Special notice
- Comments welcome
- Part 1 Background
- Chapter 1. An introduction to journaling performance
- 1.1 A customer call to a journaling expert: Interview
- 1.2 The journal environment: Background
- 1.3 What's new in V5R1
- 1.3.1 A little history
- 1.3.2 Minimize the Entry-Specific Data parameter
- 1.3.3 Journaling for non-database objects
- 1.3.4 Journal PRPQs (5799-BJC, 5799-AJC)
- 1.3.5 Summary of V5R1 enhancements
- Chapter 2. The testing environment
- 2.1 The hardware
- 2.1.1 Teraplex Center
- 2.1.2 The "Cluster Lab"
- 2.1.3 The ITSO laboratory
- 2.2 Application environments
- 2.2.1 Banesco's end-of-day batch process
- 2.2.2 Retail store application
- Part 2 Performance considerations
- Chapter 3. Hardware choices
- 3.1 Factors to be investigated
- 3.2 The testing scenarios
- 3.3 Test results and findings
- 3.4 Conclusions
- Chapter 4. Journaling tuning
- 4.1 System Managed Access Path Protection (SMAPP)
- 4.2 Journal parameters
- 4.2.1 CRTJRN and CHGJRN parameters
- 4.2.2 Journal recovery ratio (JORECRA)
- 4.2.3 Changing and managing journal receivers
- 4.3 Recovering at a hot site - APYJRNCHG
- 4.4 The testing environment
- 4.5 The testing scenarios
- 4.6 Test results and findings
- 4.6.1 Recovering from a hot site
- 4.6.2 Throughput impact (MINENTDTA with BLOBs)
- 4.7 Focus Program tests
- 4.7.1 Focus Program results
- Chapter 5. Application and software environment tuning
- 5.1 Application tuning
- 5.2 Analyzing application performance
- 5.3 Increasing performance
- 5.3.1 Batch job parallelism
- 5.3.2 Database indexes
- 5.3.3 Minimize and optimize database table extensions
- 5.3.4 Managing your open data path buffer
- 5.3.5 Symmetric Multiprocessing (SMP).
- 5.3.6 Enable Concurrent Writes (ECW)
- 5.3.7 Be journal friendly
- 5.3.8 Commitment control
- 5.4 Performance test scenario
- 5.5 Results and conclusions
- Chapter 6. Remote journaling performance
- 6.1 Introduction
- 6.2 Remote journal basics
- 6.2.1 Asynchronously maintained remote journals
- 6.2.2 Synchronously maintained remote journals
- 6.2.3 The potential communications bottleneck
- 6.2.4 High Availability Business Partners (HA BP) solutions
- 6.3 Test environment
- 6.4 Performance benchmark scenario
- 6.5 Conclusions and findings
- 6.5.1 Communication infrastructure comparison
- 6.5.2 Comparison between synchronous and asynchronous remote journal
- 6.5.3 Comparison regarding the (5799-BJC) PRPQ
- 6.5.4 Comparison synchronous RJ: send volume versus acknowledge volume
- 6.5.5 Comparison among various journal receiver size option parameters
- 6.5.6 Comparison between remote journal asynchronous and HA solution
- 6.5.7 Unsent journal entries comparing old and new HA BP approach
- 6.5.8 Conclusions for HA BP solution
- 6.5.9 Catch-up mode tests
- Part 3 Conclusions and recommendations
- Chapter 7. Conclusion
- 7.1 General performance considerations
- Appendix A. How to calculate the fast write percentage
- Instructions
- Related publications
- IBM Redbooks
- Other resources
- Referenced Web sites
- How to get IBM Redbooks
- IBM Redbooks collections
- Index
- Back cover.
- Notes:
- "SG24-6286-00."
- Includes bibliographical references (p. 157) and index.
- OCLC:
- 560375672
The Penn Libraries is committed to describing library materials using current, accurate, and responsible language. If you discover outdated or inaccurate language, please fill out this feedback form to report it and suggest alternative language.