SuspendedPropagated for HADR group

-

Problem(Abstract)

The 'lssam' command is showing Control=SuspendedPropagated for HADR resource group when the database resource is shown as Failed offline on one node and Online on the other. What does this mean ?

Environment

Here's an example of the lssam output that shows this situation :

Online IBM.ResourceGroup:db2_db2inst1_db2inst1_AM-rg Request=Lock Nominal=Online
'- Online IBM.Application:db2_db2inst1_db2inst1_AM-rs Control=SuspendedPropagated
|- Failed offline IBM.Application:db2_db2inst1_db2inst1_AM-rs:alx00005 Node=Offline
'- Online IBM.Application:db2_db2inst1_db2inst1_AM-rs:alx00006


Resolving the problem

It is expected behaviour to see the Control flag set to SuspendedPropogated when the resource group is locked.

It is also expected behaviour to see the HADR resource group locked when it is not in a peer connected state. The DB2 engine is suppose to unlock
the group once peer connected state is re-established ... at this point the SuspendedPropagated flag should get removed.



​Source: https://www-304.ibm.com/support/docview.wss?uid=swg21469579​


Popular posts from this blog

Shrink you container size up to 95%.

-
BLAFS is a bloat-aware filesystem for container debloating. The design principles of BLAFS are effective, efficient, and easy to use. It detects the files used by the container, and then debloats the container by removing the unused files. The debloated containers are still functional and can run the same workload as the original containers, but with a much smaller size and faster deployment. https://github.com/negativa-ai/BLAFS?tab=readme-ov-file
Read more

alma linux: dnf Module yaml error: Unexpected key in data

-
While applying recent updates to a server running Rocky Linux 8, an error presented itself. Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual. dnf update libmodulemd For a detailed explanation as to the cause of this problem.
Read more