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

SEVERE: EM is not configured for this database

Hi Friends,

I was doing this Oracle 10gR1 database upgrade to Oracle 10gR2 using DBUA (Database Upgrade Assistant) when my upgrade failed due to this error:


[Thread-54] [10:25:54:325] [BasicStep.configureSettings:304]  messageHandler being set=oracle.sysman.assistants.util.UIMessageHandler@6014f7
[Thread-54] [10:25:54:325] [SummarizableStep.setUpgradeStatus:620]  **++Set Upgrade status to:=1
oracle.sysman.assistants.util.step.StepExecutionException: Enterprise manager configuration failed due to the following error -
EM is not configured for this database. No EM-specific actions can be performed.
Refer to the log file at C:\OracleHomes\db10gr2\cfgtoollogs\dbua\emrep\upgrade1\emConfig.log for more details.
You can retry configuring this database with Enterprise Manager later by manually running C:\OracleHomes\db10gr2\bin\emca script.
    at oracle.sysman.assistants.util.em.EMConfigStep.executeImpl(EMConfigStep.java:141)
    at oracle.sysman.assistants.util.step.BasicStep.execute(BasicStep.java:210)
    at oracle.sysman.assistants.util.step.BasicStep.callStep(BasicStep.java:251)
    at oracle.sysman.assistants.dbma.backend.EMConfigStep.executeStepImpl(EMConfigStep.java:101)
    at oracle.sysman.assistants.dbma.backend.SummarizableStep.executeImpl(SummarizableStep.java:174)
    at oracle.sysman.assistants.util.step.BasicStep.execute(BasicStep.java:210)
    at oracle.sysman.assistants.util.step.Step.execute(Step.java:140)
    at oracle.sysman.assistants.util.step.StepContext$ModeRunner.run(StepContext.java:2468)
    at java.lang.Thread.run(Thread.java:534)
[Thread-54] [1:7:4:273] [EMConfigStep.handleNonIgnorableError:197]  EMConfig Error:=Error ignored: Could not complete the Enterprise Manager configuration.
Enterprise manager configuration failed due to the following error -
EM is not configured for this database. No EM-specific actions can be performed.
Refer to the log file at C:\OracleHomes\db10gr2\cfgtoollogs\dbua\emrep\upgrade1\emConfig.log for more details.
You can retry configuring this database with Enterprise Manager later by manually running C:\OracleHomes\db10gr2\bin\emca script.

[Thread-54] [1:7:4:273] [EMConfigStep.executeStepImpl:161]  EM Configuration Step Complete..
[Thread-54] [1:7:4:273] [SummarizableStep.executeImpl:175]  execute impl:Enterprise Manager Configuration = DONE Sucessfully
[Thread-54] [1:7:4:273] [BasicStep.configureSettings:304]  messageHandler being set=oracle.sysman.assistants.util.UIMessageHandler@6014f7

At first, i thought its over! My database is gone...but a few research down the line gave me a breather :)
I was upgrading my Oracle Enterprise Manager (OEM) Grid Control Database from 10.1.2.0 to 10.2.1.0. A Grid Control Database installation does not have a separate DBConsole installed as the Database is also managed by the OEM itself.

So in my particular case, i could simply press OK & then move ahead. The upgrade was almost complete & nothing else was required.

I just reconfigured the LSNRCTL & NET SERVICE NAME using Net Configuration Tool & rebooted my server & my new database was up & running.

However, if you are not upgrading a GC Repository Database, but an actual standalone database, this error should not be ignored as your DB Console would not be upgraded due to it.
You must followup with Oracle & find out why the upgrade for DBConsole failed.

Hope this info helps!

Keywords:
Oracle Database, Oracle 10GR1, Oracle 10GR2, Oracle Enterprise Manager, OEM, Grid Control, GC Repository Upgrade, Database Upgrade, DB Console, LISTENER.ORA, TNSNAMES.ORA, SQLNET.ORA, Listener Control, TNS Listener, DBUA, EMCA etc

Ektron eWebEditPro5: Run time Error '0'

Hi Friends,

If you recently moved to any Siebel Maintenance fix packs 8.0.0.6 and above then you might face an annoying issue with Siebel HTML Editor a.k.a Ektron eWebEditPro Editor!

After you apply the fix pack for Siebel Web Server Extension (SWSE), it upgrades the existing eWebEditPro editor from v4 to v5.

After this upgrade a necessary configuration change is not mentioned in the Maintenance Configuration Section, due to which you will notice that any template tried to be opened in the new HTML Editor results into a blank load & if you right click in the editor it results into a error popup window titled eWebEditProLibCtl5 saying, "Run time error '0'"

 In order to resolve this, you will need to edit the webeditorctrl.htm file under /$SIEBEL_SWSE_ROOT/public/enu/webeditor/

Find out the below code:



and replace it with below code:



After you do this, make sure you do a CLEAR CACHE in your browser else it will still show Javascript errors like:

This happens as the old webeditorctrl.htm file is used from browser cache for loading eWebEditPro Editor.
So ensure you do a clear cache without fail!

Hope this helps resolve patching issue.

Keywords:
siebel crm,siebel customer relationship management,siebel solutions,siebel support,siebel supportweb,siebel systems, SWSE, eWebEditPro, Ektron, HTML Editor, Marketing, WYSIWYG HTML Editor, WYSIWYG, etc.

eCopy Paperworks & Sharepoint Implementation

Hi Friends,

I am going around researching about Enterprise Document Management system & currently evaluating eCopy Paperworks.

It is a very good document management software which has lots of builtin connectors to source documents from different sources!
Check the official website: http://www.ecopy.com/Products-eCopy-PaperWorks.asp

The most interesting part of this software is the connector for Microsoft Sharepoint. Shareponit is probably implemented in most of the organizations as part of Intranet & eCopy Paperworks allows you to leverage existing Sharepoint platform for document management.

Red Sox have implemented eCopy Paperworks with Sharepoint & we have a video from Nuance explaining the details on You Tube:



Enjoy!

Keywords:
eCopy, PCDocs, Web Docs, Sharepoint, Microsoft, Red Sox, Paperworks, Enterprise Document Management, Paperless, Digital Document, Nuance, Scanner, Document Scan, eCopy Paperworks, etc.

Exception in thread "main" java.lang.NoClassDefFoundError: oracle/bi/analytics/management/StandardConsoleAgent

Hi Friends,

This is my newest experiment going on with OBIEE Management Pack in Oracle Enterprise Manager (OEM) Tool (Oracle Management Server (OMS)) & OBIEE Application.

OBIEE Management Pack needs to read the performance values exposed over JMX. In order to start this utility, we need to configure the runagent.sh or runagent.cmd under /$OBIEE_ROOT/systemsmanagement/

Following is the sample runagent.sh file setup for a OBIEE Setup on Unix Platform:

#!/bin/sh
# this is a template of runagent.sh to be used on Unix.
# The installer will fill in JAVA_HOME, SAROOTDIR, and SATEMPDIR

export JAVA_HOME="/usr/java/jdk1.5.0_19"
export SAROOTDIR=/$OBIEE_ROOT/
export SADATADIR=/$OBIEE_DATA/
export SATEMPDIR=/$OBIEE_DATA/tmp
export UNIXPERFDIR=${SATEMPDIR}

java_cmd="${JAVA_HOME}/bin/java -Djava.library.path=${SAROOTDIR}/server/Bin -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=9980 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -classpath analytics-jmx.jar:lib/xmlparserv2.jar oracle.bi.analytics.management.StandardConsoleAgent"

${java_cmd}

Now if you carefully observe, if you invoke the script from your home directory, the classpath will fail to resolve & give error like:
Exception in thread "main" java.lang.NoClassDefFoundError: oracle/bi/analytics/management/StandardConsoleAgent

Above issue is purely due to the way classpath parameter is given in java_cmd: -classpath analytics-jmx.jar:lib/xmlparserv2.jar oracle.bi.analytics.management.StandardConsoleAgent

The analytics-jmx.jar & xmlparsev2.jar are not resolved as absolute path locations are not given here. So you need to manually change your directory till /$OBIEE_ROOT/systemsmanagement/ & then invoke runagent.sh file to start the JMX Performance counters successfully.

The JMX Performance Counters needs to be exposed constantly so that OBIEE Management Pack reads correct values. To achieve this, you need to start the runagent.sh file in background mode. e.g.-bash-3.00$ runagent.sh &  or-bash-3.00$ nohup runagent.sh & so even after you logoff your session, the utility keeps running & gathers correct values.

Enjoy!

Keywords:
OBIEE, Siebel Analytics, Business Intelligence, Oracle Enterprise Manager Grid Control, OMS, Oracle Management Server, OEM, Grid Control, JMX, JAVA, OBIEE Performance, etc

8.0.0.8/8.0.0.9 Fix Pack Installer Hangs

Hi Friends,

On Linux/Unix Platforms, if you try to start 8.0.0.8 or 8.0.0.9 Fix Pack Installer in console mode (./setuplinux -console), you might see that the installer hangs after you proceed the instance to be patched step!

Further investigation led me to find out that the Fix Pack installer tries to install mandatory Oracle Configuration Manager (OCM) before the actual Siebel Patch Installation begins... As the OCM installation is launched in a separate typical Oracle 11g Database Installer type setup, it fails to launch in console mode due to which the entire setup lies in a hung state :(

The only current workaround is to start the start Fix Pack installer in UI mode so that the mandatory OCM installation completes successfully and you are allowed to proceed ahead for Siebel Patch Installation!

Read about another 8.0.0.8/8.0.0.9 Fix Pack Setup issue you might come across:
http://geektalkin.blogspot.com/2010/04/setupproductinstall-utility-err-unable.html

Keywords:
siebel crm,siebel customer relationship management,siebel solutions,siebel support,siebel supportweb,siebel systems,8.0.0.8, 8.0.0.9, Fix Pack, Siebel Patch, OCM, Oracle Configuration Manager, etc.

Installshield Installer JRE issue

Hi Friends,

Java based installshield installer comes with its own bundled JRE. If this bundled JRE gets corrupted, then you will be in a great pain to start the installer as it will report errors like:

This application requires a Java Run Time Environment (JRE)
         to run. Searching for one on your computer was not successful.
          Please use the command line switch -is:javahome to specify
          a valid JRE.  For more help use the option -is:help.

Even though you try to specify a valid JAVA HOME using -is:javahome option, still the installer will fail to start & keep giving me the same error, the reason being installshield needs a very specific JRE & it wont accept any JRE passed as an -is:javahome option!

Such particular issue is encountered with Siebel Uninstallers on Linux/Unix platform.
Siebel product uninstallers exist in /$SIEBEL_ROOT/_uninst/uninstall.ksh

You need to start the uninstaller by passing the product name as an option:
E.g. If we need to uninstall Siebel Web Server Extensions (SWSE), then we would invoke the uninstaller as:
./uninstall.ksh eappweb

Now, if you receive the JRE issue, then there is pre-extracted Installshield JRE which is corrupted.
Such JRE exists in the Product directory which you are trying to uninstall:
e.g. /$SIEBEL_ROOT/_uninst/eappweb/_jvm

In order to fix this issue, the only option you have is to restore the _jvm directory from backup or copy the contents of _jvm from a different machine having similar Siebel Setup & overwrite the contents in the corrupted JRE directory.

While i was researching on this issue, i came across solution for IBM Product Installshield Installers, was to setup the below Environment variable to successfully bypass this error:
set JAVA_COMPILER=NONE
or
export JAVA_COMPILER=NONE

Hope this info helps if you come across installshield issues.

Keywords:
siebel crm,siebel customer relationship management,siebel solutions,siebel support,siebel supportweb,siebel systems, Installshield, JAVA, JRE, JVM, Uninstaller, JAVA_COMPILER, etc.

Setup.product.install, Utility, err, unable to launch (SBL-STJ-00152)

Hi Friends,

As Siebel 8.0 is evolving, we have new annoying bugs to face!
From Siebel 8.0.0.8 Fix Pack onwards, you might face an error like:

(Mar 29, 2010 5:57:33 AM), Setup.product.install, Utility, err, unable to launch: "\\server1\d$\Siebel_Install_Image\8.0.0.9\Windows\Server\Siebel_Enterprise_Server/Disk1/install/setup.exe -waitforcompletion -nowait ORACLE_HOME="d:\sba80/gtwysrvr" -defaultHomeName -responseFile \\server1\d$\Siebel_Install_Image\8.0.0.9\Windows\Server\Siebel_Enterprise_Server/Disk1/stage/response/NTOCMCD.rsp" error code: "-1"(SBL-STJ-00152)
(Mar 29, 2010 5:58:41 AM), Setup.product.install, InstalledProductsPanel, err, Not able to stop the server. Please stop the server
manually and run patch installation again.(SBL-STJ-00101)

If you note, i was trying to apply 8.0.0.9 Fix Pack from a network shared location. Like always,  i expected this to work perfectly fine as with earlier Patch Installs, but this time it errored out!

Well, further investigation led me to find out that, the Fix Pack installer tries to install mandatory Oracle Configuration Manager (OCM) before the actual Siebel Patch Installation begins...
The OCM installation is launched in a separate typical Oracle 11g Database Installer type setup, which fails to launch when we have invoked the parent Siebel Patch setup from a network shared location!

In order to workaround this issue, you need to copy the extracted Patch Installer, like for Siebel Enterprise Server to a local machine drive where you are trying to apply the patch.

As of now, this is no mechanism to bypass OCM installation, though OCM has nothing to do with Siebel Patching Process as such.

If you do not want OCM, post-installation, re-run Oracle Installer & deinstall the OCM. Oracle has acknowledged that OCM installation should be optional, so lets see when they add the optional functionality in the installer.

Till then breathe a sigh & proceed with the Patch Installation :-)

Keywords:
siebel crm,siebel customer relationship management,siebel solutions,siebel support,siebel supportweb,siebel systems, SBL-STJ-00152, SBL-STJ-00101, 8.0.0.8 Fix Pack, 8.0.0.9 Fix Pack, Oracle Configuration Manager, OCM, etc.