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).
Unable to Copy, Save or Compile any jobs in a Project
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 66
- Joined: Mon Feb 21, 2005 10:40 am
- Location: Paris
-
- Participant
- Posts: 251
- Joined: Mon Jun 09, 2008 5:52 am
-
- Premium Member
- Posts: 66
- Joined: Mon Feb 21, 2005 10:40 am
- Location: Paris
-
- Premium Member
- Posts: 892
- Joined: Thu Oct 16, 2003 5:18 am
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
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".Charles Nagy wrote:No project wide variables were altered.
If the project is not protected then check the operating system permissions of objects within the project directory on the server.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Premium Member
- Posts: 66
- Joined: Mon Feb 21, 2005 10:40 am
- Location: Paris
Thanks Ray,ray.wurlod wrote: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".Charles Nagy wrote:No project wide variables were altered.
If the project is not protected then check the operating system permissions of objects within the project directory on the server.
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.