Skip to Main Content
Cloud Management and AIOps

This is an IBM Automation portal for Cloud Management and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Created by Guest
Created on Jul 13, 2020

Cloud Tie breaker for GCP

Hi Team,

In our environment all the DB2 db's are running in GCP cloud environment which are enabled with HADR along with TSA. We use network tie breaker in our environment, recently we faced HADR split brain issue due to network issue and raised case with IBM (TS003746592) for the same.

Below are the response from IBM for our issue:
This is a known issue/limitation of the network tiebreaker, RSCT uses UDP for heartbeats, the network tiebreaker uses ICMP, when there is a network problem and the network recovers the ICMP protocol is brought up before UDP is , so the tiebreaker can be reserved while the UDP (RSCT heartbeat) is still failing.
This ends up with a domain_merge
The solution is that:
1) don't use network tiebreaker, use arbitrator node, NFS, Cloud or disk tiebreaker instead
2) don't have network failures
3) increase the period/sensitivity so that longer network outages are not reported by RSCT

many DB2 db's are critical in our environment so we need to have robust solution for this issue. We prefer to change our TSA tie breaker from network to cloud. But for cloud IBM provided solution is for AWS. We need same solution for GCP, We checked the same with google and they told us to inform IBM regarding same. This is the reason i raised this case. We need to your help regarding this solution. Please let us know if any other details required.

Idea priority Urgent
RFE ID 143889
RFE Product Tivoli System Automation for Multiplatforms (SA MP)