DB2 integrated cluster environment deployment guide
The IBM DB2 Integrated Cluster Environment for Linux is a completely integrated, high-performance, and pre-tested solution that incorporates best-of-breed software, hardware, and services. This IBM Redbooks publication provides you with the technical details of the DB2 Integrated Cluster Environment...
| Autor Corporativo: | |
|---|---|
| Otros Autores: | |
| Formato: | Libro electrónico |
| Idioma: | Inglés |
| Publicado: |
[San Jose, Calif.] :
International Technical Support Organization
c2004.
|
| Edición: | 1st ed |
| Colección: | IBM redbooks.
|
| Materias: | |
| Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009627147206719 |
Tabla de Contenidos:
- Front cover
- Contents
- Figures
- Tables
- Notices
- Trademarks
- Preface
- The team that wrote this redbook
- Acknowledgement
- Become a published author
- Comments welcome
- Chapter 1. Introduction
- 1.1 Why DB2 on Linux
- 1.1.1 DB2 + Linux = Versatility
- 1.1.2 Versatility + eServers = Value
- 1.2 What is a cluster
- 1.2.1 Cluster types
- 1.2.2 DB2 partitioned databases
- 1.3 The DB2 Integrated Cluster Environment solution
- 1.3.1 The ingredients for success
- 1.4 Benefits of DB2 Integrated Cluster Environment
- 1.4.1 Scalability pays great returns
- 1.4.2 Proven performance at a low cost
- 1.4.3 High levels of availability
- 1.4.4 Easily managed
- 1.4.5 Seamless interoperability
- 1.5 DB2 Architecture
- 1.5.1 DB2 database access
- 1.6 Summary
- Chapter 2. Selecting your cluster
- 2.1 Platform
- 2.1.1 IA32 (and x86)
- 2.1.2 AMD64 (and x86-64)
- 2.1.3 Platform selection
- 2.2 Server types and models
- 2.2.1 1U "Pizza-box" - x335
- 2.2.2 AMD64 "Pizza-box" - e325
- 2.2.3 2U 2P - x345
- 2.2.4 4P - x365
- 2.2.5 HS20 (2-way
- 14 Blades in a 7U unit)
- 2.2.6 Server selection
- 2.3 Storage
- 2.3.1 Localized vs. centralized storage topologies
- 2.3.2 Enterprise Storage Servers (ESSs)
- 2.3.3 DS4000 series
- 2.3.4 Direct Attached Fibre Storage (EXP)
- 2.3.5 Direct-attached SCSI storage (ServeRAID™)
- 2.3.6 Network Attached Storage (NAS)
- 2.3.7 Storage selection
- 2.4 Network interconnect
- 2.4.1 InfiniBand option
- 2.4.2 Network selection
- 2.5 Linux distribution
- 2.5.1 Validated enterprise-class Linux distributions
- 2.5.2 Linux distribution selection
- 2.6 Sample configurations
- 2.6.1 A 32-bit configuration
- 2.6.2 A Scaled-out 32-bit configuration
- 2.6.3 A 64-bit benchmark configuration
- 2.6.4 A 4-way building block
- 2.7 Summary
- Chapter 3. Planning and design.
- 3.1 Steps for building a large partitioned database
- 3.2 Disk considerations
- 3.2.1 Summary of the most popular RAID levels
- 3.2.2 Data placement
- 3.2.3 Log placement
- 3.2.4 Data availability and performance
- 3.2.5 General storage performance recommendations
- 3.3 Database design considerations
- 3.3.1 Understand data partitioning
- 3.3.2 Define the number of database partitions
- 3.3.3 Define database partition groups
- 3.3.4 Design the table spaces
- 3.3.5 Understand partitioning map
- 3.3.6 Choose the partitioning key
- 3.3.7 Size the tables
- 3.3.8 Size for MDC utilization
- 3.3.9 Size for MQT utilization
- 3.3.10 Configure DB2 UDB
- 3.3.11 Recommended parameters for performance
- 3.3.12 Naming conventions
- Chapter 4. Implementation
- 4.1 Lab environment
- 4.1.1 Hardware environment
- 4.1.2 Software environment
- 4.1.3 Topology of the lab environments
- 4.2 Prepare your Linux OS for DB2 Integrated Cluster Environment
- 4.2.1 Basic requirements
- 4.2.2 Installation planning and preparation
- 4.3 DB2 partitioned database setup
- 4.3.1 Considerations on DB2 installation
- 4.3.2 Preparations for DB2 UDB product installation
- 4.3.3 DB2 UDB product installation
- 4.3.4 Preparation for instance creation
- 4.3.5 Instance creation
- 4.3.6 Node configuration
- 4.3.7 Preparation for database directory (optional)
- 4.3.8 Database creation
- 4.3.9 Data loading
- 4.4 Post installation tasks - Initial tuning
- 4.4.1 Tuning your DB2 through Configuration Advisor GUI tool
- 4.4.2 Tuning your DB2 by using the autoconfigure command
- 4.4.3 Important DB2 registry and environment variables
- 4.4.4 Validating logical database design with the DB2 Design advisor
- Chapter 5. Operations and administration
- 5.1 Manageability enhancements
- 5.1.1 Health Center enhancements
- 5.1.2 Automated log file management.
- 5.1.3 Self-tuning for backup and restore
- 5.1.4 Recover database
- 5.1.5 Automatic setting of prefetch size
- 5.2 Monitoring
- 5.2.1 DB2 instruments
- 5.2.2 Linux tools
- Chapter 6. High availability
- 6.1 Introduction
- 6.1.1 What is high availability
- 6.1.2 Types of high availability
- 6.1.3 High availability in clusters
- 6.1.4 Failover in a highly available cluster
- 6.1.5 High-availability clustering configurations
- 6.1.6 High-availability software solutions
- 6.1.7 Automatic Client Reroute
- 6.2 TSA implementation
- 6.2.1 TSA fundamentals
- 6.2.2 TSA installation
- 6.2.3 TSA resource planning for an HA DB2 cluster
- 6.2.4 Basic implementation with the regdb2salin script
- 6.2.5 Advanced implementation
- 6.2.6 Scaling out your HA DB2 clusters
- 6.2.7 Notes on Logical Volume Manager
- Chapter 7. Scaling
- 7.1 Introduction to scalability
- 7.1.1 Scale-up vs. scale-out
- 7.1.2 Scalability dimensions
- 7.2 Scaling up
- 7.2.1 Adding additional processors
- 7.2.2 Taking advantage of greater parallelism
- 7.2.3 Adding additional memory
- 7.3 Scaling out
- 7.3.1 Preparing the new servers
- 7.3.2 Moving database partitions without data redistribution
- 7.3.3 Adding database partitions
- 7.3.4 Data redistribution via REDISTRIBUTE command
- 7.3.5 Alternate methods of data redistribution
- Related publications
- IBM Redbooks
- Other publications
- Online resources
- How to get IBM Redbooks
- Help from IBM
- Index
- Back cover.
