Schneider Electric GIS Tech Support

We have Designer and ArcFM running in different machines. The "designers" usually experiment a very poor performance of the system. The designs will draw really slow and any thing that is done would take a while.

We check the server and it is in good shape, nothing visible in the server that would impact the performace. Our ArcFM users normally do not have the same performance problems at the same time, and an analyze in the DB usually takes care of it. We upgraded one machine to 4gb of ram, and it did not improve performance.

We do compress everyday, clean orphan versions, analyze and delete PX states.

Are we missing something? If you experiment the same problem, have you find a solution?

Thank you

Check the value for MAXBLOBSIZE and make sure that it is set to at least 5000000.

If you are on 9.2 it is stored in sde.SDE_SERVER_CONFIG table.

For earlier versions it's in giomgr.defs on the ArcSDE server.

Similar but different, we had a problem come up last week where some (but not all) of our designs open extremely slowly - it takes about an hour and a half for them to open (and if you close without saving edits that takes a half hour). But then other designs open like normal. It has nothing to do with design size either, some really small ones have the problem and some big ones don't. Non-designer ArcFM editing performance is fine.

If anybody has experienced this or has any ideas, please post a reply. Thanks.

The MAXBLOBISE is 20000000, really high but that was recomended.

In relation to your questions, one thing we are doing based in Ian Fitzgeral, is to truncate the current states 49 and 48 from the MM_PX_CURRENT_STATE table. Also, we truncate the SDE_LOGS table for each user (when they are not connected). I would recoment to look at those two things if you have not, some designs still takes a while to open, but they do not take that long.

I've tried the MM_PX_STATES thing and that didn't help.

I did figure out the problem. Here's what happened: In April during an upgrade we also switched to new servers. Used MM's tool to redirect the designs and their stored displays. However the tool doesn't work for Raster layers. So the slow designs contain a layer that is looking at the old server from prior to the migration. Up until recently this wouldn't cause any problems, it would just have broken links. However, last week IT took the old server off the network and now ArcMap spends a very long time searching the network for a server that's not there. (Would be nice if ESRI had a timeout in there)

Fix is to put the old server back on the network temporarily, open problem designs, fix the broken link and save.
Thanks for the feedback.