 | Level: Introductory Wayne Ha (ha@ca.ibm.com), IBM SAP Integration and Support Center, IBM
Patrick Zeng (pzeng@ca.ibm.com), World Wide DB2 SAP Technical Sales Enablement and Support, IBM
30 Aug 2007 Learn how to enable database high availability (HA) using IBM® Linux®,UNIX® and Windows® (DB2 V8 or DB2 9) High Availability and Disaster Recovery (HADR) capability in an SAP ABAP and Java™ dual stack environment, as well as how to enable automatic failover using IBM Tivoli® System Automation for Multiplatforms (SA MP) in such an HA system. This article takes you through the planning and preparation stages, and then gives instructions on installing this solution. Finally, there is detailed information that you'll need to implement this solution with SAP.
In this article
- Introduction to DB2 HADR and Tivoli SA MP, and explanation of the approaches for SAP applications to reconnect to the new active database after a failover
- Planning information, including configuration of the test system, hardware and software requirements
- Preparation information, including network setup, file systems setup, and setting up user groups
- Installation steps for all the various pieces of this solution
- Detailed instructions for running SAP with DB2 HADR and Tivoli SA MP
Introduction
DB2 HADR is a database replication feature that provides a high availability solution for both partial and complete site failures. HADR protects against data loss by replicating data changes from a source database, called the primary, to a target database, called the standby. In case of a failure the takeover by the standby database only takes some seconds since the standby database server is already up and running. The only work to be done is to reconnect all clients to the standby server.
IBM Tivoli SA MP is a high-availability cluster solution which provides several monitoring mechanisms to detect system failures and a set of rules to initiate the correct action without any user intervention. The set of rules is called a policy, which describes the relationships between applications or resources. This provides SA MP with extensive up-to-date information about the system landscape so that it can restart the resource on the current node or move the whole application to another cluster node.
This article uses the scripts provided by SAP to set up the cluster on a DB2 HADR system. It also discusses two different approaches for SAP applications (ABAP+Java) to reconnect to the new active database after a failover. One approach is to use DB2 Automatic Client Reroute (ACR) feature, and the other approach is to use virtual host and IP address to the database server.
Details of procedures and examples of output are provided so that you can follow each step carefully and to compare with your own experiences.
Download | Description | Name | Size | Download method |
|---|
| PDF file | dm-0708ha.pdf | 118KB | HTTP |
|---|
Resources Learn
Get products and technologies
-
Download IBM product evaluation versions and get your hands on application development tools and middleware products from DB2, Lotus®, Rational®, Tivoli®, and WebSphere®.
Discuss
About the authors | | | Wayne Ha is a member of the IBM SAP Integration and Support Center at the IBM Toronto Lab. His current activities are integration testing of SAP products with IBM DB2 for Linux, Unix and Windows (LUW) and helping customers with problem analysis and troubleshooting. He is also a customer advocate providing support for large customer accounts running SAP and DB2 for LUW. He can be reached at ha@ca.ibm.com. |
| | | Patrick Zeng is a member of World Wide DB2 SAP Technical Sales Enablement and Support team. He has many years experience of supporting SAP and DB2 customers. He is a Certified DB2 Solutions Expert and a Certified SAP Technology Consultant. He can be reached at pzeng@ca.ibm.com. |
Rate this content
| | | |
