Indexing/Crawling Of a Custom Search Category Fails with SBL-OMS-00203 or HTTP 500 Errors (Doc ID 1642868.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel Advanced Search - Version 8.1.1.11 SIA [23030] and later
Siebel CRM - Version 8.2.2.3 SIA [23021] and later
Information in this document applies to any platform.

Symptoms

When Siebel Search has been configured with FTP Indexing mode, the index of any custom search category fails. The SearchDataProcessor fails with errors similar to the following

Error

SearchAdapter    SearchAdapterError    1    00000066533c156c:0    2014-04-02 09:02:09    osesindexadapter.cpp -> CSSOSESIndexAdapter::MakeDocumentId -> View Name is empty
GenericLog    GenericError    1    00000066533c156c:0    2014-04-02 09:02:09    Object manager error: ([0] Could not find '<?>' named '<?>'. This object is inactive or nonexistent.(SBL-DAT-00144) (0x750090))
GenericLog    GenericError    1    00000066533c156c:0    2014-04-02 09:02:09    ( (0) err=2818155 sys=7667856) SBL-OMS-00107: Object manager error: ([0] Could not find '<?>' named '<?>'. This object is inactive or nonexistent.(SBL-DAT-00144) (0x750090))
GenericLog    GenericError    1    00000066533c156c:0    2014-04-02 09:02:09    (bsvcmgr.cpp (1393) err=2818251 sys=0) SBL-OMS-00203: Error 7667856 invoking method "CreateFullIndex" for Business Service "Search Data Processor"
GenericLog    GenericError    1    00000066533c156c:0    2014-04-02 09:02:09    (bsvcmgr.cpp (1236) err=2818251 sys=0) SBL-OMS-00203: Error 7667856 invoking method "CreateFullIndex" for Business Service "Search Data Processor"
GenericLog    GenericError    1    00000066533c156c:0    2014-04-02 09:02:09    (smireq.cpp (425) err=2818251 sys=0) SBL-OMS-00203: Error 7667856 invoking method "CreateFullIndex" for Business Service "Search Data Processor"


When Siebel Search has been configured with HTTP Indexing approach, the SES crawler fails with below errors.

Error

11:42:29:840 INFO    crawler_4        HTTP status code: 500
11:42:31:159 INFO    crawler_4        HTTP status code: 500
11:42:32:435 INFO    crawler_4        HTTP status code: 500
11:42:33:436 FATAL    crawler_4        EQP-80309: Exception while opening a stream to the URI: http://mywebserver/eai_enu/start.swe?OSESRequest=true&UserName=SADMIN&FeedType=dataFeed&BatchId=1-6VM3
11:42:33:437 FATAL    crawler_4    EQP-80317: HTTP connect attempt failed after 3 attempts. Aborting connection attempt oracle.search.sdk.common.PluginException    oracle.search.plugin.rss.HTTPHandler:postToUrl:681    oracle.search.plugin.rss.HTTPHandler:getInputStream:215    oracle.search.plugin.rss.RSSSAXQueue:RSSSAXQueue_Cons:171    oracle.search.plugin.rss.RSSSAXQueue:<init>:148    oracle.search.plugin.rss.RSSControlQueue:initQueues:309    oracle.search.plugin.rss.RSSControlQueue:initNextQueue:327    oracle.search.plugin.rss.RSSMultiSAXQueue:getNextItem:110    oracle.search.plugin.rss.RSSCrawler:crawl:219    oracle.search.crawler.CrawlingThread:run:1690
11:42:33:437 WARN    crawler_4        username attribute present in contentLink element of data feed although the content is supposed to be inline
11:42:33:437 ERROR    crawler_4    oracle.search.sdk.common.PluginException: EQP-80317: HTTP connect attempt failed after 3 attempts. Aborting connection attempt oracle.search.sdk.crawler.PluginException    oracle.search.plugin.rss.RSSSAXQueue:RSSSAXQueue_Cons:184    oracle.search.plugin.rss.RSSSAXQueue:<init>:148    oracle.search.plugin.rss.RSSControlQueue:initQueues:309    oracle.search.plugin.rss.RSSControlQueue:initNextQueue:327    oracle.search.plugin.rss.RSSMultiSAXQueue:getNextItem:110    oracle.search.plugin.rss.RSSCrawler:crawl:219    oracle.search.crawler.CrawlingThread:run:1690
11:42:33:437 INFO    crawler_4        Releasing lock on http://mywebserver/eai_enu/start.swe?OSESRequest=true&UserName=SADMIN&FeedType=dataFeed&BatchId=1-6VM3


Steps to Reproduce
1. Siebel Search functionality has been configured: Siebel 8.1.1.11/8.2.2.4 and Oracle Secure Enterprise Search (OSES or SES) 11.1.2.2 are integrated
2. Search engine parameter "Visibility Support" is set to false.
3. Create a new search category, i.e.: 'Solutions'
4. Index this custom search category.
5. The index/crawling fails.
    a) When FTP Indexing mode is implemented, the SearchDataProcessor fails with SBL-DAT-00144, SBL-OMS-00107 and SBL-OMS-00203 errors.
    b) When HTTP Indexing is implemented, the SES crawler fails with HTTP 500 errors.

Note. The index/crawling is successful for all 'vanilla' search categories.



Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms