SBL-GEN-03001: Error allocating (null)

Hi Friends,

Yesterday i came across this rare Siebel Assignment Manager error: SBL-GEN-03001: Error allocating (null) OR SBL-GEN-03001: Error allocating DynArrCreate Organization Skill Items Arr

Logs files were showing up following dump:
GenericLog    GenericError    1    000000024bc70cd4:0    2010-04-15 09:39:12    (asgnrule.cpp (8327) err=3001 sys=2640) SBL-GEN-03001: Error allocating DynArrCreate Organization Skill Items Arr

GenericLog    GenericError    1    000000024bc70cd4:0    2010-04-15 09:39:12    (asgnrule.cpp (929) err=3001 sys=0) SBL-GEN-03001: Error allocating DynArrCreate Organization Skill Items Arr

Due to this, Siebel Assignment Manager component was not getting started & constantly crashing. If you start, it will again stop & crash after few minutes.

This behaviour is particularly related to Physical Memory availability to the Assignment Manager component.
You can setup following log level for your Assignment Manager component to have a quick informative trace regarding the issue:

   1. Object Assignment = 4
   2. Rules Evaluation = 5
   3. Loading = 4
   4. Assignment Manager Generic = 4
   5. SQL Tracing = 2
   6. SQL Parse and Execute = 4
   7. Task Configuration = 4
   8. Component Tracing = 3

In our environment, this issue came up suddenly so it definitely wasnt an Siebel Product issue but something to do with our environment changes.
Further tracing of the logs lead to us that the amount of rules loading was causing the Assignment manager cache to go out of bounds of the total available physical memory on Siebel Application Server.

The only way to resolve this was to follows below steps:
1) Stop Assignment Manager & Batch Assignment components.
2) Delete rulecache.dat file under $SIEBEL_ROOT/siebsrvr/bin
3) Delete or expire all unwanted Assignment rules
4) Start Assignment Manager & Batch Assignment components
5) Allow the new rulecache.dat file to be generated.
6) Now check log to see if Assignment Manager component is still shutting down.

90% of cases, this should resolve the issue. But if you still face the same problem, you need to start investigating from your trace log. Particularly the last queries fired just before you find SBL-GEN-03001 errors being dumped in the log file.

You may also notice 0KB crash_xx.txt files under $SIEBEL_ROOT/siebsrvr/bin until you resolve this issue.
Enjoy!

Keywords:
siebel crm,siebel customer relationship management,siebel solutions,siebel support,siebel supportweb,siebel systems, assignment manager, crash.txt, FDRs, etc