DSXchange

I have a job that is doing change capture on some data.
New records get inserted and changes get updated and old records get expired. A typical type 2 dimension.

There are 2 surrogate key stages in the job referencing the same file.

When processing I get the following error in the job log:

skey_cust_mast_id_chg,1: Input 0 reached EOF but the operator logic did not
designate another input to process via setActiveInput()
or advanceToNextInput(), as is required in eSpecificInput mode.

Any ideas?

Thanks.

Hi There,

Did you ever get a workaround to this as I am encountering the same exact problem?

Thanks,

Daren

Daren, please start your own post for this and let us know all of the gory details of the problem that you are having there.

Hi Craig,

I have actually managed to locate the cause in my instance. I am using an ODBC connector stage to read a table and then that is used, via a Transformer stage, as a lookup to a lookup stage.

If I load the data using ODBC connector stage into a dataset and use that as input, the error disappears. If I replace ODBC connector stage with Oracle enterprise stage, the error disappears.

I have escalated this via our support to IBM.

Thanks for the reply

Daren

Interesting. Let us know what they say, please.

I was supplied a patch to install on my C: drive and this did the trick - the ODBC connector stage now works. It seems to have updated my local settings for the client.

The patch is called: patch_JR31443v2_client_windows_801fp1.ispkg

No idea if this is an official name or not. It was executed using the following command:

C:\IBM\InformationServer\ASBNode\apps\jre\bin>java.exe -jar updater.jar

Thanks,

Daren