Siebel Bookshelf (v8.1,v8.0,v7.8,v7.7,v7.5,v7.0,v6.3,v6.2,v6.1,v6.0)

Hi Friends,

One common requirements we have in our day to day Siebel Activities is the Siebel Bookshelf. Its the ultimate knowledge power house regarding Siebel.

Below are the links you need for different Siebel Versions:

Siebel 8.1.x http://download.oracle.com/docs/cd/E14004_01/homepage.htm

Siebel 8.0.x http://download.oracle.com/docs/cd/B40099_02/homepage.htm

Siebel 7.8.x http://download.oracle.com/docs/cd/B31104_02/homepage.htm

Siebel 7.7.x http://download.oracle.com/docs/cd/E05553_01/homepage.htm

Siebel 7.5.x http://download.oracle.com/docs/cd/E05554_01/homepage.htm

Siebel 7.x http://download.oracle.com/docs/cd/E05555_01/homepage.htm

Siebel 7.x Mid-market Edition: http://download.oracle.com/docs/cd/E05565_01/homepage.htm

Siebel 6.x http://download.oracle.com/docs/cd/E05556_01/homepage.htm

Siebel Online Help Files and Help Development Kits

Enjoy!

Keywords:
Siebel Systems, Siebel CRM, Siebel System Requirements, Supported Platforms, Hardware, Software, Siebel SBA, Siebel SIA, Horizontal, Vertical, eAutomotive, OBIEE, Siebel Analytics, Siebel eBusiness and Industry Applications,MidMarket Edition, Universal Application Network (UAN), Siebel Retail Finance, Oracle Self-Service E-Billing, Oracle® Real-Time Decisions

Reset runtime Apache access.log & error.log

Hi Friends,

Today morning i got a page from our data center that one of the Production Apache based Webserver diskspace was almost full & most of the space was consumed by access.log & error.log!

Well, i knew this would happen some day since it has been a year we put these machines in Production, moreover we havent setup the log rotation for access.log & error.log.

Now, i had two tasks at my hand...
1) Take a quick backup of both the log files.
2) Reset/Clear the logs to size zero without bouncing the Apache Webserver services, i.e. at Runtime.

Solution:
1) Took a zipped backup on another disk in the same machine:
bash$ zip /d01/Apache_BK/access_log_20052010.zip access.log
bash$ zip /d01/Apache_BK/error_log_20052010.zip error.log

2) Reset/Clear the logs to size zero using /dev/null:
bash$ cp /dev/null access.log
bash$ cp /dev/null error.log

OR

bash$ cat /dev/null > access.log
bash$ cat /dev/null > error.log

Well, using /dev/null is very effective on Linux & Unix platforms, but if you are wondering if we have something similar to that in Windows, then the answer is yes!

C:\>type NUL > access.log
C:\>type NUL > error.log

Just hope that Windows havent locked the log file with an exclusive handle ;-)
If you have a lock on the file & need to reset the log file without restarting the Apache services, then your only option is to install Unlocker (http://ccollomb.free.fr/unlocker/)

Hope this tip helps as no one wants to bounce a Production system just for taking a log backup & resetting its size to zero :-D

Enjoy!

Keywords:
Oracle HTTP Server, Apache, OHS, /dev/null, NUL, access.log, error.log, zip, backup, etc

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.