After a new pass is added to an existing match spec by copying an existing pass (eg. pass 7 added), saving the pass, saving the specification and provisioning all, the pass does not appear when running a job.
There are no error messages, however the log file indicates that only 6 passes were run.
Sometimes, by closing out the session and restarting it or rebooting the server the pass will then appear on execution of the match spec.
Sometimes nothing works except deleting the pass and manually creating it.
Anyone seen this happen?
Pinned topic Changes do not exist after provisioning in Match Specification
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2009-06-22T07:38:01Z at 2009-06-22T07:38:01Z by SystemAdmin
SystemAdmin 110000D4XK533 Posts
Re: Changes do not exist after provisioning in Match Specification2009-06-22T07:38:01ZThis is the accepted answer. This is the accepted answer.Hello,
Yes, I've seen things like that before. It seems that DataStage does not automatically realize that there was a change in the match-specification of a Quality-Stage Job.
Workaround: Generate a copy of the changed Match-Specification and save it under a new name. Exchange the Match-specification in the Match-Job with the new Match-Specification. Compile.
After this you can safely change the Match-Specification back to the old name and recompile to avoid going through the procedure of taking the new Match-Specification to your production environment.
If there is a software-solution to this I currently don't know about it.