|
Possible Causes |
Possible Solutions |
|---|---|
|
Incorrect interval |
Fix interval |
|
Output file disk full |
Check for insufficient disk space |
|
Output file disk not accessible |
Check for or disk not mounted or in mount verify timeout |
|
Node restriction |
Relax or modify node restriction |
|
Special Day Restrictions |
Relax or modify Special Day Restrictions |
|
Dependencies not satisfied ([ ]) |
1.Check parent jobs for successful completion 2.Check for new or changed remote cluster aliases in job records. See Repairing Job Records Containing Stale Cluster Aliases in this guide. |
|
Dependencies failed |
Check parent jobs for reasons for failure |
|
Remote dependency or network down |
Check why network connection is not available |
|
Dependency did not run |
Check why parent job did not run |
|
Dependencies entered, but interval not entered |
Check interval, or set interval to 0 |
|
One or more dependencies satisfied unexpectedly |
Check for manual or out-of-order runs of parent jobs |
|
On HOLD |
Release job |
|
No job slots available |
Wait, increase /MAX_JOBS |
|
Incorrect next run time |
Modify job’s next run time |
|
No privilege to run |
Check ownership, privileges, names, identifiers |
|
Job was not scheduled for expected time |
No action required |
|
Load Balance Group assigned to the job is empty |
Add one or more nodes to the Load Balance Group or remove the Load Balance Group from the job |
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |