We have this really odd circumstance with a user that is using DEM's. When he attempts to access tdpur4230m000, it can take 4-13 minutes to open this session. When I access it as a menu user, I access it in seconds. We have recreated his user and it will work fine for a while, then it is back to several minutes to open the session again. Has anyone seen this?

I try to stay clear from DEM if I can help it, but this seems a shared memory issue rather than DEM.

We have several users using this same role combination role with no issue. It appears to only affect 2 users. So I had ruled out shared memory.

Hello skheeb :)

Does this happen with any other session besides this one? This work a while and then starts happening again is wierd. Does it ever run normally after it starts slowing down? What is using resources when the process is running? (DB, Driver, bshell -- there are no processes spinning are there)

-- Jim

Hi Jim,

Tina usually ends up deleting his user and recreating it to get it to work. It will behave itself for a couple of weeks and then start acting up again. I can log in using this session and not have an issue, but if I log in as his user, I can see that it is taking as long as 15 minutes for his user. I have never seen anything like this before. It really has us baffled.

Sheri

Hi Sheri,

I know I asked these questions in my last post, but can you answer these?

1. Does this happen with any other session besides this one?
2. Does it ever run normally after it starts slowing down?
3. What is using resources when the process is running? (DB, Driver, bshell -- there are no processes spinning are there) During the fifteen minute interval can you interrogate the bshell and see any ticks incrementing on specific process?

-- Jim