Page 1 of 1

Re: Datastage Director Refersh and Compile error

Posted: Thu Nov 15, 2012 6:29 pm
by SURA
I am using 8.7. I created a new job and compiled. In the designer client it said, compiled successfully whereas in director shown not compiled.

I thought of config issue.

Posted: Fri Nov 16, 2012 3:02 am
by ArndW
Oddly enough, I've been seeing this problem since yesterday on one of the 8.7 machines here. Whe I manually do a "refresh" in the Director the correct state is displayed. But if I don't, the job status is "not compiled" but the director merrily refreshes the state of other running jobs. I will have to look into that problem further today.

Re: Datastage Director Refersh and Compile error

Posted: Fri Nov 16, 2012 8:13 am
by chulett
SURA wrote:I thought of config issue.
I thought of bug. :wink:

Posted: Fri Nov 16, 2012 10:40 am
by mandyli
I am thinking about that client issue or else we need to apply 8.7 FP1 Server and client too.

Posted: Fri Nov 16, 2012 10:43 am
by ArndW
I have seen the problem demonstrated again today, with the same client and the same settings (refresh rate in the director) everything works as expected on one 8.7 machine but on the other, which I believe was installed with the same response file as the first machine, the director doesn't reflect the "compiled" status of a job.

Offhand the only difference I can think of is that I'm admin on the development machine and only a lowly viewer on the production machine, where the error manifests itself.

Posted: Mon Jan 21, 2013 8:30 pm
by ami
Has anyone had a solution for this issue yet?
We have just upgraded from 8.5 to 8.7FP1 on a Windows platform and we are seeing the same problem.
We have raised a PMR with IBM but I'm not holding my breath.

Gavin Magill
ETL Developer
IAG Insurance
Christchurch NZ.

Posted: Tue Jan 22, 2013 1:15 am
by ray.wurlod
Welcome aboard, Gavin

Does a manual refresh (Ctrl+R) in Director correct the status for you?

Resolution To this Issue.

Posted: Tue Feb 19, 2013 3:28 pm
by GavMagill
Hi All

IBM have responded to this issue with a patch for our Windows 8.7 Fixpack 1 environment. The patch number is JR45546.

I don't know if they have also provided a fix for Unix installs as well but this patch has fixed the issue for our install.

Note that it is a server side patch only.

Cheers

Gavin Magill
Contract ETL Developer
IAG Insurance
Christchurch NZ