DB2-z/OS: planned failback doesn’t work

[] [] [] [] [] [] [] []

Symptom
Failover/failback solution provided to support planned outages of a DB2 member doesn’t work anymore.
Example:
For the sake of simplicity let assume there are two DB2 datasharing members DB2 A and DB2 B and two application servers App A and App B. All connection of App A go to member DB2 A and all connections [...]

DB2-z/OS: Running two or more DB2 members on one z/OS LPAR

[] [] [] [] [] [] [] [] []

Symptom
This SAP Note describes how you can set up a DB2 data sharing group so that two or more members are running on the identical z/OS LPAR.
Other terms
HA Failover z/OS System z DB2 data sharing LPAR
Reason and Prerequisites
Your SAP system is running with DB2 in data sharing mode and DB2 Connect as database [...]

DNS Issues with DHCP in Windows Server 2008 Failover Cluster

[] [] [] [] [] [] [] [] [] [] [] [] [] [] [] []

Symptom
If you use DHCP in Windows Server 2008 Failover Clustering, you obtain duplicate DNS entries that have the same IP-Address for two different host names.
This applies to all Windows Server 2008 versions with SP1 and SP2.
Other terms
MSCS, Windows Server 2008 Failover Clustering, Failover Cluster, DNS resolution, duplicate host name entries
Reason and Prerequisites
With Windows Server [...]

IPv4 Host name resolution on Failover Cluster Server 2008

[] [] [] [] [] [] [] [] [] [] [] []

Symptom
The commandping -4
delivers a network address in the 169.254.2.0 subnet.
Applications that report IP addresses to other applications running on computers that do not belong to the cluster, might use this address. Therefore, the address cannot be used for general communication purposes, since it is not possible to connect to the applications at [...]

DB2-z/OS: DB2 Connect 9.1 JDBC Failover for SAP Java stack

[] [] [] [] [] [] [] [] [] [] [] []

Symptom
This SAP Note describes how to enable high availability for your Java application server in case of unplanned outages of the DB2 for z/OS subsystem if you are running DB2 Connect 9.1. High availability enablement is based on the client reroute feature of the IBM Data Server Driver for JDBC (JCC driver).
If [...]

DB2-z/OS: Seamless JDBC Database Failover for SAP Java stack

[] [] [] [] [] [] [] [] [] [] [] []

Symptom
This SAP Note describes how to enable high availability for your Java application server in case of planned and unplanned outages of the DB2 for z/OS subsystem. High availability enablement is based on the seamless and cascaded failover feature of the IBM Data Server Driver for JDBC (JCC driver), which was [...]

MaxDB directories in UNIX clusters for failover

[] [] [] [] [] [] [] []

Symptom
You want to run a MaxDB/SAP DB/liveCache instance in a UNIX cluster for failover.
The database software can be configured differently for your directories depending on your requirements. This note describes tips for installing the software directories.
This note should not be considered for HotStandby implementations. During a HotStandby solution, there is no transfer of [...]