Multiple containter instances with standardize
Posted: Mon Feb 25, 2008 6:47 pm
We just tracked down some fatal errors to the QualityStage Standardize Stage when using multiple instances of a shared container. We have a container that validates an address, rejects invalid rows, replaces nulls with default values, etc... In a parallel job, we have 2 entities coming in on a row, so we split them using copy and sent each entity to the validating container and then to separate outputs. We saw the following error instantly:
( also saw with USADDR.UCL and USAREA.PAT as we removed stages to narrow down the problem )
and on the next run:
I've read that shared containers are design time objects and are replaced when compiled, but they seem to cause a problem when the container is used multiple times in one job and contains the Standardize Stage. In testing we found there is not a problem using the Standardize stage twice in the same job or using a container multiple times in the same job without a Standardize stage.
Has anyone run into this before? Is this a bug/limitation or are we doing something wrong? Any ideas would be appreciated as we are planning to remove Standardize from our shared containers tomorrow.
Code: Select all
Unable to link rule file, VPHONE.UTO, file may need provisioning
and on the next run:
Code: Select all
From previous run
DataStage Job 133 Phantom 12577
Job Aborted after Fatal Error logged.
Program "DSD.WriteLog": Line 305, Abort.
Attempting to Cleanup after ABORT raised in job STD_TEST_JOB.
DataStage Phantom Aborting with @ABORT.CODE = 1
Has anyone run into this before? Is this a bug/limitation or are we doing something wrong? Any ideas would be appreciated as we are planning to remove Standardize from our shared containers tomorrow.