Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Refresh into an active node of DB2 caused second node to be unusable upon failing over

Answered
Loo Tong Tan User

Implementing for our customer Land Transport Authority (LTA)

part of their re-platform projects

Source: DB2 on AIX 7.2
Target: DB2 on AWS EC2 redhat 9.7 (2 nodes, HA/DR setup with EFS)

Refresh and Compare was successful,
During a test failover from active node2 to standby node1

All tablespace became RESTORE_PENDING.

Can we set the Refresh to use
LOAD ... COPY YES TO '/<efs-shared-path>' so the standby stays in sync.

Case:  #388723

Please sign in to leave a comment.

Comments

1 comment

Date Votes
  • Edwin Fivetranner

    Hi LT,

    Thank you for the feature request.

    We are already looking into how we can improve the load copy procedure for DB2. I will review how this request fits with that work. Once we have more clarity, we will let you know here.

    Best regards,

    Edwin