What were you trying to do that didn't work?

with RFE RHEL-115495 and TSAnet TS019631899 , team has modified the re-intigration logic to use reint_attr for node re-intigration, IBM has given explanation of the flag:

~~~

he reint_attr flag is a flag set internally within the Db2 engine, intended for use with the integrated solution... I suspect it was provided as a reference along with our script for how Db2 w/ Pacemaker handles reintegration after a takeover. 

At a high level, after a successful takeover (standby becomes primary) the db2sysc process of the new primary will set the reintegration flag. Once the old primary host rejoins the cluster, the db2hadr script running start/monitor actions will observe the flag and restart the old primary as standby. If restarting the old primary as standby was successful, only then should the reintegration flag be unset.

Whether or not the reintegration flag gets set after a takeover depends on if the instance is configured as part of a Pacemaker cluster. However, I don't think Redhat should use our flags in the non-integration solution.
1. There is a bunch of other functionality tied together in the integrated solution, we don't have a way to expose the reintegration flag by itself today.
2. The 'other functionality`, and the reintegration flag itself is depends on the resource model Db2 configures using the db2cm utility. I suspect it would likely be difficult to make this work without Db2 development make some changes.

Redhat may partially be able to replicate this solution in a non-integrated cluster by simply setting this flag as part of a successful promote operation, and using it to indicate to the 'old' primary database that it should start as standby. Of course this depends on the customer configuring their resource as a promotable clone, which I don't think is always the case.

~~~

What is the impact of this issue to you?

re-integration logic always fails in first attempt  

Please provide the package NVR for which the bug is seen:

How reproducible is this bug?:

Steps to reproduce

1.  execute db2 resource migration incident (fence current primary)
2.  
3.  

Expected results

promote action in db2 RA should enable re-intigration flag 

Actual results