This can happen if you have a large diary/unlimited text field. If you are using Oracle, there are some configuration parameters you need to set to handle large clobs. the same is true of attachments, but you have stated there are none.
Use this select statement to find the size of the diary field values: select length(audit_trail) from hpd_helpdesk where audit_trail is not null order by length(audit_trail) desc substituting your db view/columns, of course. In the ar.conf file, check for the presense of these values: Db-Max-Text-Size Db-Max-Attach-Size (if you had been using attachments) Pulling values that exceed these config parameters (or the default value for the parameter) will cause arserverd to crash. Axton Grams On 9/15/06, McKenzie, James J C-E LCMC HQISEC/L3 <[EMAIL PROTECTED]> wrote:
** Nyall: I would have to look into this, but we did this at one place that I worked at because we did have diary problems. I think it took a stored procedure and then calling that procedure and then sorting the top ten. We would run this and get the results as a mail message with them. We sent it to a local mailbox on a UNIX system. James Mckenzie ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Nyall McCavitt Sent: Friday, September 15, 2006 8:38 AM To: [email protected] Subject: Re: request crashing user tool - malloc failed To: [email protected] Subject: Re: request crashing user tool - malloc failed ** Hi, I think that you are along the correct lines here except that I don't expect that for these particular entries that there would be any large diary entries but as I am rusty on SQL then I am not sure of the exact Oracle commands required to verify the size of the relevant fields. Any pointers would be gratefully received. I have checked that the relevant T,H and B tables are consistent with the number of entries in each. Thanks. Nyall McKenzie, James J C-E LCMC HQISEC/L3 wrote: ** Nyall and Raido: I'm willing to state that the affected action has a very large diary or attachment associated with it. If you attempt to export the record from your database, Oracle can handle the data collection, but Remedy cannot. Thus, you see a large increase in memory usage and then the crash. If you care to explore, you can look at the CLOB storage for that record and find the record is very large. Don't know how this happens as the limit for a diary field under Oracle is 1MB of text. If you need help, I think that I can provide a little bit of it. __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
