Page 1 of 1
Unable to Copy, Save or Compile any jobs in a Project
Posted: Wed May 05, 2010 7:57 am
by CharlesNagy
Has anyone seen this behaviour before? Previously, everyone was working fine except that later in the day, we experienced this problem.
A contributing factor was that we were operating at or near the max number of users the system was originally specified for.
Be interested to see if anyone has had a similar issue, and if so whether a reason was found and how the problem was resolved. (Datastage Engine restart did not resolve it).
Posted: Wed May 05, 2010 8:09 am
by srinivas.g
may be the reason of project is in protected state
Posted: Wed May 05, 2010 8:48 am
by CharlesNagy
srinivas.g wrote:may be the reason of project is in protected state
Thanks, but the project was working fine before in the morning and this issue happened late afternoon. No project wide variables were altered.
Posted: Wed May 05, 2010 10:58 am
by Sreenivasulu
Can you post the error message you are getting ?
There is a bug for which IBM has provided a patch
Regards
Sreebu
Posted: Wed May 05, 2010 4:43 pm
by ray.wurlod
Charles Nagy wrote:No project wide variables were altered.
Could someone have changed the status of the project to Protected (which does not require variables)? Check using the Administrator client, project properties. If the project is protected, the command button on the General tab will be captioned "Unprotect Project" rather than "Protect Project".
If the project is not protected then check the operating system permissions of objects within the project directory on the server.
Posted: Thu May 06, 2010 7:32 am
by CharlesNagy
ray.wurlod wrote:Charles Nagy wrote:No project wide variables were altered.
Could someone have changed the status of the project to Protected (which does not require variables)? Check using the Administrator client, project properties. If the project is protected, the command button on the General tab will be captioned "Unprotect Project" rather than "Protect Project".
If the project is not protected then check the operating system permissions of objects within the project directory on the server.
Thanks Ray,
Nope, it wasn't a protection issue. Some users were able to work so it seemed to depend upon login. A restart of the WAS service resolved the issue. IBM seems to think it was due to the affected users having sessions timing out. (timeout was set at 2 hours). I am running tests on this at the moment. The error log had quite a few 'session expireds'.
It's possible that these sessions were stuck in limbo, but I am mystified as to why logging out and then logging back in wouldn't have resolved it.