Platform: Linux VM's, 2 servers in the server groups, running Remedy 9.01 against a remote Oracle database.
So - we have a large number of users (500, give or take) and enter many incidents every day. I haven't pulled incident counts for a while but I'm sure we've got at least a couple of million. We have 4 environments - Development, Test, Customer test/training, and Production. In the first 3 server start time is nearly identical - right around the 7 minute mark. The secondary server comes up slightly faster. In production the server start times keep getting longer. Last time I checked it the time was 15 minutes - then 17, and now just about 20. This is during off hours with no users online and nothing else running that would affect it. During the day it can be even slower. We had seen this same thing before in another separate production version of Remedy 7.6.04 - the startup times were as long as 45 minutes just for the AR server to complete starting up - this is without any real errors or problems, with fast connection speeds. My question is - why? My understanding has always been that the AR server caches all workflow/forms on startup, but that amount of data is relatively static. Is it caching something else tied to user data that is not advertised? I haven't yet pulled in our DBA performance crew to look at the startup calls - I thought I'd start here first. And to be clear - there's no timeouts anywhere, no errors, nothing - it's a clean start...that keeps taking longer and longer. William Rentfrow wrentf...@stratacominc.com Office: 715-204-3061 or 701-232-5697x25 Cell: 715-498-5056 _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
