cc: bsloan@SOUTHWIND.NET, ars_list@hotmail.com,
geoff.endresen@attws.com, aqeel@redconnect.net, rohrer.jay@tci.com,
melissa.klien@aexp.com, cvasquez@frk.com, patrick.zandi@rl.af.mil

Subject: [SUMMARY] RE: File System Full ..


Thanks to all who replied to my email about File System Full and Timeouts.
I received many helpful suggestions on areas to check and have summarized
them. The problems I was experiencing turned out to be a combination of
some of the items listed.

Thanks again.

SUMMARY Areas to check for causes to File System Full
(These are interpreted from the original emails. My apologies for any
mangled replies.)

1. Turn off unqualified query searches.
2. Check for adequate temp space for database (10 to 25 percent of all
tables)
3. Check the trace files for database. These should be on seperate drive
from Remedy.
4. Check for too many multiple port assignments using rpcinfo. Check the
port assignments during normal operation to determine normal range.
5. Check reboot schedule of server to determine if interval is adequate.
6. Check the logs in /use/ar/db directory for size and possible insight to
problem.
7. Check the ftindex directory. FTS should preferably be placed on a
separate drive.
8. Check the ~/arweb/sessions directory for multiple log files.
9. Check the Admin tool for status of the log options.
10. Check the shared cache configuration. Be sure it is not too large.
11. Check the /tmp directory for overflow logging from Remedy.
12. Check the *.lck files in the /usr/ar/db directory.
13. Check all API for any logging and process errors.
14. Check all cron and backup jobs.


To Unsubscribe send e-mail to:
body of text is: unsubscribe arslist