4 Replies Latest reply on Mar 7, 2018 10:31 AM by athlon007

FDMEE - Import step is triggered twice

athlon007 Dec 15, 2017 10:08 AM

Dear fellow FDMEE Administrators.

We are facing an issue during the import stage of FDMEE. What happens is that the Import runs roughly 10 minutes, does a Transform and also Validate (all have the green check icon), but then it triggers another Import, even though the 1st one went through ok.

This only happens for our biggest location we import. The other do not trigger a 2nd import, which are using the same scripts mapping etc.

This seems to happen since were upgraded to Windows 10. Are there new timeout settings in place?

I would be grateful to have any feedback if others are facing a similar issue.

Thanks alot,

Roma

1. Re: FDMEE - Import step is triggered twice

SureshM-Oracle Dec 18, 2017 10:24 AM (in response to athlon007)

Are you triggering import via Batch or through manual process?
Does the process logs shows two ODI process that gets execute one after another?
What version of FDMEE are you in?
Like Show 0 Likes(0)

Actions
2. Re: FDMEE - Import step is triggered twice

athlon007 Jan 4, 2018 2:22 PM (in response to SureshM-Oracle)

Hello,

The import is triggered manually

The process logs shows different ODI process numbers.

FDMEE version 11.1.2.4.210

Thanks alot for helping
Roman
Like Show 0 Likes(0)

Actions
3. Re: FDMEE - Import step is triggered twice

SureshM-Oracle Jan 4, 2018 3:13 PM (in response to athlon007)

Is it a distributed environment? If yes, do you have multiple FDMEE servers?
I would advise to raise an SR with Oracle Support at this point in time to review your environment and provide you the solution.
Like Show 0 Likes(0)

Actions
4. Re: FDMEE - Import step is triggered twice

athlon007 Mar 7, 2018 10:31 AM (in response to athlon007)

Hello,

In case somebody else runs into this issue it was the following:

Since Upgrading to Windows 10 our FDMEE import from a Staging table never stopped, it just kept reimporting after the validation step.

Solution was to amend the timeout setting in our Load Balance from 5min to 10min.

Hope this may help somebody else once.

Cheers
Like Show 0 Likes(0)

Actions

Go to original post

Join the world’s largest interactive community dedicated to Oracle technologies.