Troubleshooting and FAQs › Troubleshooting the Manager › Repairing Job Records Containing Stale Cluster Aliases › Sample scenarios
Sample scenarios
The following sample scenarios illustrate the use of the logical name NSCHED$ALIAS_GROUP to resolve cluster alias problems. The following assumptions are used for all examples:
Begin with three Job Management Manager configurations:
- A two node cluster with nodes ALPHA1 and ALPHA2 using cluster alias ALPHAS.
- A two node cluster with nodes EARTH and MARS using cluster alias PLANET.
- A two node cluster with nodes PRD1 and PRD2 not using any cluster alias.
Begin with these job dependencies:
- Job ALPHAS::ALP1 is dependent on job PLANET::E1
- Job ALPHAS::ALP2 is dependent on job PRD1::PROD1 which is set to run on PRD1 only.
- Job PLANET::PL1 is dependent on job ALPHAS::ALP3
- Job PLANET::PL2 is dependent on job PRD2::PROD2 which is set to run on PRD2 only.
- Job PRD1/PRD2::PROD3 is dependent on job ALPHAS::ALP4
- Job PRD1/PRD2::PROD4 is dependent on job PLANET::M1
The logical name NSCHED$ALIAS_GROUPS is not defined, everything works as expected.
