Siebel Search Administration Guide > Troubleshooting the Setup of Siebel Search >

Visibility Troubleshooting


This topic lists frequently asked questions on visibility.

Are the records you are indexing related to categories?

Most search categories are set up to apply access catalog category visibility. If a record is found when indexing that is not associated with any category, then it will not be indexed.

Catalog categories need to be active and should have valid Start and End dates.

How to check. Go to the Administration Screen for the record being indexed (for example, Solution Administration), and check whether the records are associated with categories. If not, two things must happen. The records must be associated with categories, then the index must be recreated or refreshed. You may also modify the search category to remove the access group visibility. See Indexing Fields to Enforce Catalog Category Visibility for information on modifying visibility for a search index.

Do you get zero records for one search category while other search categories return records?

If no records show up for any index, then this may be because none of the indices contain any records.

You may also have incorrect Advanced Search Settings. The settings to look for are Character Set and Term Generator:

    • In SearchServer, the character set should always be UTF8.
    • If a linguistic filter is specified in the Term Generator property, make sure that the SPELL option is not specified. This has been deprecated in Search Server 5.3, but was supported in 4.0. For example, word!ftelp/inflect/spell must be changed to just word!ftelp/inflect

How to check. Choose a search category and search for asterisk (*). You should get a full list of all records available in the index. You can also check in the search administration view whether each search index contains any records.

Is the Search Filter specification eliminating the records you expect to see?

Search categories often have search specifications applied to them as part of their Siebel Tools definition. These search specifications will filter out records from results if they do not meet the required search specification.

How to check. First perform an Index Refresh operation, as any modified records that have not been refreshed in the indices, may be filtered out.

If the expected records are still not being displayed, open Siebel Tools, and go to the Search Engine > Search Definition > Search Definition Category to see if there is a search specification. Compare this specification to the records you were expecting to see as search results. Also, you will need to perform an Index Refresh operation to display any new or modified records.

Why is index generation taking so long?

Requirements. Make sure that the index setting Log Control is not set. It is important that the logging level be only what is required for problem solving (remove this setting if no problems are encountered). This is because excessive logging reduces database text reader performance and may consume considerable disk space.

How to check. The .dil files generated for each index operation will be small (a few kilobytes).

Why do search categories not show up when connecting remotely to a search server using a client connector?

It is important to make sure that both the Hummingbird Connect Manager and Hummingbird Connector services are started. Also the account used to log on to the service must be a valid user/system account with the proper rights set. It is also important to make sure that the directories specified in the FULTEMP and FULCREATE variables in the client connector have read/write access. Search Server writes to these directories. See the Planning and Installation Guide of the Search Server Documentation for more details.

How to check. To verify that the server and client are configured properly, run ExecSQL and execute the script tbls.fte. This file comes with the Search Server installation. This script will list each table found on the local node by path, followed by the names of each remote node and their respective tables.

NOTE:  ExecSQL is a command line utility that you can use to execute SearchSQL statements and run scripts. See the Data Preparation and Administration Guide of the Search Server documentation for more information on using this utility.

Siebel Search Administration Guide Copyright © 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices.