RedBack 3.... Hmm - you really need to upgrade to 4.2.5 (unless you are using IDE mode which is EOL....
However: 1. Check the size of WWSTATE - make it big and wide and static 2. How much stuff there? - and how big? Stop RedBack and purge it 3. And while there clear WWLOG as well 4. Set Garbage Collection parameters to purge > a reasonable time (say 2 hours) and run once in a blue moon (effectively never) 5. Run RedBack.GC from a PHANTOM at regular (say hourly) intervals Note: There have been issues with Garbage Collection in the past and this is the broad-stroke way of dealing with it Otherwise there are some older common issues which also break things: 1. Using the OPEN rather than OPEN2 method and inappropriate use of file handles 2. Using Stateful RBOS (RB3 is either IDE or stateful RBOs) are you storing connection objects in Session Variables? This is a recipe for issues and to do with the way that MS deal with Session variables .... in short don't use them. (OPEN2 is the method to use and cache the rbohandle and sessionid, NOT a connection object). 3. Are you using an old MDAC? - not THIS problem but 2.7 or 2.8 please. 4. Do you have absolutely HUGE records (by anyone's definition) in WWSTATE? This suggests you are hitting the same session (as referenced by the object handle) over and over again and it never times out. As a result WWSTATE never gets purged. Bottom line: 1. Check MDAC 2. Check WWSTATE 3. Use the GC workaround but *upgrade* to 4.2.5 4. Check your web side application code usage (ASP etc...) 5. Check the number of files in the RedBack log file directory and their sizes (act appropriately if you feel the need to say "gosh") 6. Check &PH& in the RedBack accounts you have activated while you are there 7. If problems persist check the RBOs themselves for performance using RBOSCOPE and perfrgw... and avoid hanging around on record locks and the "usuals" (file sizing etc...) Regards JayJay ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
