Troubleshooting and FAQs › Troubleshooting the Manager › Repairing Job Records Containing Stale Cluster Aliases

Repairing Job Records Containing Stale Cluster Aliases

If a job has a remote dependency specified using an alias of a remote cluster and that remote cluster alias is changed, the job can get stuck in DepWait state. This might also occur if groups of nodes use different cluster aliases within the same cluster.

Other symptoms are:

• Job dependencies cannot be shown in SCHEDULE SHOW JOB/FULL output and in the Motif GUI.
• RETRY.LOG is filled with multiple attempts to retry remote connections.
• Removing a dependency or deleting a job leaves stale dependency records in DEPENDENCY.DAT

This happens because dependency records stored in the database are not updated when a remote cluster alias changes. Therefore, any connection to the stale cluster alias fails and job dependencies cannot be satisfied.

Use the logical name NSCHED$ALIAS_GROUPS to tell Job Management Manager about cluster aliases which have been added or changed for remote clusters or nodes, when using inter-cluster dependencies. The logical name allows Job Management Manager to resolve mismatches in the database, update job records if necessary, and proceed with job dependencies.