I had a similar problem after importing new views to
remedy. In my case, the new views had special characters like accents that where
stored in the database as strange characters (because NLS_LANG where not well
defined). When remedy tried to start, it started a thread that run some init sql
queries. This query got the strange characters from the database and push it to
remedy. Remedy just killed the thread without freeing the memory and started
another thread to do the same queries, so once again remedy got stuck with that
characters and killed the thread again ..... after a while arserver.exe had
goten 1,7GB of memory and so the malloc error raised.
My suggestion is to check the thread and sql log files and
try to find out whats happening.
regards,
Alvaro
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Dave Barber
Sent: viernes, 12 de mayo de 2006 12:02
To: [email protected]
Subject: Malloc failed on server
I'm extracting data from our helpdesk form for testing migration to our 6.3
test system, I've selected a sample of data (tickets created before 2005, about
30,000 records).
Extracting via the user tool/reporting to an ARX file. Doesn't matter
which client I use (5/6.3/7), I get an ARERR [300] Malloc failed on
server. (I know, its a server error, so the client won't make much
difference). This is at record 15,001 that it fails.
Any suggestions? The server is running ARS 5.1.1, on Win2K.
1Gig of ram (its an old server).
I can take on the data that I have okay, but its concerning me that with
this restriction, I'm going to have to take on the forms history in 15000 record
chunks, which is a little irritating.
Thanks all,
Regards
Dave
