After deleting old SQL Package, JOBS still attempt to run package
Article ID: 87444
Updated On:
Products
CA Automic Workload Automation - Automation Engine
Issue/Introduction
Error Message :
N/A
After deleting or renaming an SQL package, JOBS within the workflow will randomly try to run the the old deleted or renamed package.
Essentially, the job fails because it tries to grab a non-existent package.
The way to detect this is to look at the agent log and search for the old name of the SQL package in the log.
N/A
After deleting or renaming an SQL package, JOBS within the workflow will randomly try to run the the old deleted or renamed package.
Essentially, the job fails because it tries to grab a non-existent package.
The way to detect this is to look at the agent log and search for the old name of the SQL package in the log.
Environment
OS Version: N/A
Cause
Cause type:
Other
Root Cause: N/A
Other
Root Cause: N/A
Resolution
Recreate the parent workflow and job from scratch.
Fix Status: No Fix
Fix Version(s):
N/A
Fix Status: No Fix
Fix Version(s):
N/A
Additional Information
Workaround :
Manually start the workflow each time it should executed.
However, this is not the best option if the job runs several times throughout the day/night.
Manually start the workflow each time it should executed.
However, this is not the best option if the job runs several times throughout the day/night.
Feedback
Yes
No
Powered by
