A fix is available
APAR status
Closed as program error.
Error description
Using istool to re-import a job with -replace option the following error is received: $ /opt/IBM/InformationServer/Clients/istools/cli/istool import -dom mydomain:9080 -u <user> -p <pwd> -ar /tmp/myarchive.ar -replace -ds 'server/PROJECT' Beginning import [1/1] server/PROJECT/Jobs/Category/myJob.pjb ignored Unexpected error importing design. See the log in the Web Console for more details. Elapsed time: 00:00:09 Imported 0 assets The job is not imported and is left in an uncompiled state. When I look in the Web Console log I find the following error: IS-ISTOOLS-DS-AI 2009-06-19 11:37:51,180 Error com.ascential.xmeta.exception.data.DuplicateIdentityException: 2 matches found for object of type "http:///1.1/DataStageX.ecoreDSFunctionCall" with identity "::runABC:SERVER:PROJECT:JOB:SERVER:PROJECT". It was found that the issue was because the job had the same routine specified for the Before and After subroutine.
Local fix
Workaround: Create two new versions of the single before/after routine; one to handle just the before case and one to handle just the after case. (Note that it is better to create two new names for these routines rather than to reuse the existing common routine's name). Any existing job that currently uses the same routine for both the before and after job routine should then be changed to use the new before routine for the before case and the different after routine for the after case. The job should be exported again, and then the resulting xxx.ar file should be importable as both new and overwriting.
Problem summary
**************************************************************** USERS AFFECTED: Affects all platforms, when using istools for import. **************************************************************** PROBLEM DESCRIPTION: This problem can occur when re-importing a job via istools (Information Server Manager and command line) when that job usesbefore and after job routines, and the same routine is used as both the before and after job routine. An initial import works successfully. A subsequent re-import, with overwriting, will fail. The error messages in the web console log will include references to DuplicateIdentityExceptions. **************************************************************** RECOMMENDATION: Install the patch patch_JR33458_domain_all_8100 This fix is included in 8.1 FP1. ****************************************************************
Problem conclusion
This was caused by the model identity definitions of the before and after routines. They were not specific enough for the usage of a single routine as both the before and after routine. The solution involves specifying new model identity definitions to make this usage unique.
Temporary fix
Comments
APAR Information
APAR number
JR33458
Reported component name
INFO SRVR PLATF
Reported component ID
5724Q3612
Reported release
810
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-06-24
Closed date
2009-06-29
Last modified date
2010-01-11
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
SERVER
Fix information
Fixed component name
INFO SRVR PLATF
Fixed component ID
5724Q3612
Applicable component levels
R810 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSZJPZ","label":"InfoSphere Information Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
12 October 2021