Symptoms

Snapshot creation process stops responding.This occurs when snapshots are initiated on two different SRDF/Metro configurations. Example from Dell Lab: GLOBAL DEBUG(EXTRA) - AUTO_UNLINK(YES) - CACHE_FULL_SYM(Y) - CHECKONLINE(YES) - CONSISTENT(YES) - FREE(YES) - REL_LINK(YES) - SECURE(NO) - WAIT_FOR_D(YES) CREATE ( - NAME(S_DESAI_METRO1_%TIME6%) - SOURCE(SYMDV#(560-56F)) - REMOTE(RAGROUP(02) UNIT(822C)) - ) CREATE ( - NAME(S_DESAI_METRO2_%TIME6%) - SOURCE(SYMDV#(4E2-4F1)) - REMOTE(RAGROUP(03) UNIT(822C)) - ) ACTIVATE (CONSISTENT(Y) EXPIRATION(1) SECURE(NO))

Cause

Code defect related to subtask activation logicThe issue is triggered when the ACTIVATE SUBTASK mechanism is involved during snapshot creation.

Resolution

Workaround:Disable subtask activation using the global parameter: ACTIVATE_SUBTASK#(0)This prevents the faulty subtask activation logic from running, allowing snapshot creation to run successfully.Example: GLOBAL DEBUG(EXTRA) - ACTIVATE_SUBTASK#(0) - AUTO_UNLINK(YES) - CACHE_FULL_SYM(Y) - CHECKONLINE(YES) - CONSISTENT(YES) - FREE(YES) - REL_LINK(YES) - SECURE(NO) - WAIT_FOR_D(YES) CREATE ( - NAME(S_DESAI_METRO1_%TIME6%) - SOURCE(SYMDV#(560-56F)) - REMOTE(RAGROUP(02) UNIT(822C)) - ) CREATE ( - NAME(S_DESAI_METRO2_%TIME6%) - SOURCE(SYMDV#(4E2-4F1)) - REMOTE(RAGROUP(03) UNIT(822C)) - ) ACTIVATE (CONSISTENT(Y) EXPIRATION(1) SECURE(NO))

Support Cases