Skip to main content
Skip table of contents

Error Monitoring for Oracle Siebel CRM (Configure)


Guide to configuring the analysis of impactful errors and filtering out the insignificant ones. In other words, this guide helps in understanding how Germain can concentrate on errors that impact Siebel CRM Users or Business Processes while excluding the numerous benign ones.

This assumes you have already deployed 1) Germain UX - RUM JS and 2) Germain UX - Engine for your Siebel CRM instance.

Tag Errors that Affect Siebel Users (Configure)

Check how to tag Siebel Errors that affect Users and ignore the others.

Tag OM Errors to watch out for (Configure)

Germain UX allows to map all Siebel custom error codes to their corresponding display messages visible to your end users. To configure this mapping please follow the below steps:

  • Extract all of your Siebel Error codes using errmsg.exe Siebel’s utility (available only on Windows platforms). Siebel keeps these codes in the resource catalogs (,,,, …) in the %SIEBEL_ROOT%\bin\%language_folder%. Example below shows how to extract these codes from Siebel resource catalog in English language format:

    %SIEBEL_ROOT%\bin\errmsg.exe /l ENU enu\ > errors.txt
  • Review errors.txt output file and find all of your custom errors, e.g.

    SBL-GEN-02011 Error parsing Siebel message file header: incorrect facility name
  • Once all custom error code extracted from the errors.txt file, insert them into SIEBEL_ERROR_CODE_MAPPING table available in your Germain UX Datastore. Example below for MySQL database:

INSERT INTO SIEBEL_ERROR_CODE_MAPPING (CODE,MESSAGE) VALUES ('SBL-GEN-02011','Error parsing Siebel message file header: incorrect facility name');


Please go here to see KPIs for Siebel Errors.


A number of dashboards are preconfigured for Siebel CRM, here are just a few main ones, but there might be more.

  • Go to Germain Workspace > Left Menu > Dashboards > All

  • Search for any “Siebel…” dashboards, such as:
    Siebel User Experience
    Siebel Availability

  • Search for portlets called “…Error…” or create them or we can help.

Component: Engine

Feature Availability: 2014.1 or later

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.