7.5.1A Upgrade issue and patch
Posted: Wed Mar 01, 2006 8:40 am
I recently reported a problem in the job 'upgrade' mechanism to Ascential that was discovered during our recent upgrade from 7.0.1 to 7.5.1A. They have been able to reproduce and correct it, too late for us but I'm hoping it may help others avoid the issue.
It's not anything horrible, or terribly hard to 'work around' just a pain in the rear and not something I wanted to deal with. Under a very certain circumstance, after the jobs are upgraded to the new release they will fail to compile. The error message they log is completely bogus and simply recompiling them again post upgrade works just fine. It's just that we had it affect hundreds of jobs in multiple projects, hence the frustration.
Specifically, this is the error from the installation log:
Which, in fact, is not missing and recompiling afterwards works just fine. The problem is caused by having a Reference Lookup inside a Shared Container that uses a Job Parameter as the Key Expression in the lookup.
Unfortunately, it was so in one of our 'standard' Shared Containers that a ton of jobs leveraged. 
If you have this issue or think you might, contact Ascential Support and reference Ecase 78132 - I have no idea how the 'fix' works, if it's pre- or post-upgrade as I'm no longer in a position to need or be able to take it for a test drive. Just hoping to save someone else some grief.
It's not anything horrible, or terribly hard to 'work around' just a pain in the rear and not something I wanted to deal with. Under a very certain circumstance, after the jobs are upgraded to the new release they will fail to compile. The error message they log is completely bogus and simply recompiling them again post upgrade works just fine. It's just that we had it affect hundreds of jobs in multiple projects, hence the frustration.
Specifically, this is the error from the installation log:
Code: Select all
Upgrading job 'X'
Job upgraded from version 36 to version 50
Recompiling job
Error re-compiling job 'X'
Reference Input has missing key expression (job.xfm.link)Which, in fact, is not missing and recompiling afterwards works just fine. The problem is caused by having a Reference Lookup inside a Shared Container that uses a Job Parameter as the Key Expression in the lookup.
Unfortunately, it was so in one of our 'standard' Shared Containers that a ton of jobs leveraged.
If you have this issue or think you might, contact Ascential Support and reference Ecase 78132 - I have no idea how the 'fix' works, if it's pre- or post-upgrade as I'm no longer in a position to need or be able to take it for a test drive. Just hoping to save someone else some grief.