memory still allocated after the job execution

Hello everybody,

We have recently migrated our Production system from Oracle to MaxDB, and encounter several occurrences of the message hereunder every day.   The OS is Win2008 Std x64 SP2, the DB version 7.7.07.09...

From what I saw, the errors are often - though not always - related to processes from the "BI light" add-on that was implemented on our ECC system.

Is this something we should worry about, and if so, any idea on how to fix?

Moreover, I detected these errors after a Production DB kernel abort we had yesterday.  The crash had something of what's described in Re: MaxDB 7.6.05.09 Kernel aborts - EXCEPTION:'Access violation' (0xc0000005) , but I'm not sure if there's any relation with the message hereunder...

Thread  0x122 Task    146  2010-02-24 03:01:56 ERR SrvTasks      46:  183392 bytes are still allocated after the job execution.,_FILE=SrvTasks_Job.cpp,_LINE=296                                                                      DESCRIPTION:                                                                      A job must only use memory via the server task allocator while it is executed by the server task. If the job is terminated, then it must not use further server task memory.                                                                      ACTION:                                                                      Please contact MaxDB-Support.                           2010-02-24 03:01:56     SrvTasks      17:  Servertask Info: because CheckAllocatorUsage                           2010-02-24 03:01:56     SrvTasks      10:  Job 0 (Prefetch Table Coordinator) [executing] WaitingT-- Result=OK                           2010-02-24 03:01:56 ERR SrvTasks      21:  The errorlist is not empty but result is OK after executing the job.,_FILE=SrvTasks_Task.cpp,_LINE=160

Thanks in advance for any clarifications on this subject,

Peter