Handling Invalid/Unusable Siebel Index

Indexes are available on the Siebel base tables to improve performance and also to maintain the data integrity. The purpose of adding index is to help the database to search records quickly and efficiently. It’s very essential to make sure that Siebel Indexes are in active and valid state.

Scenario :

Apply and Activate on Local Database causes Tools Application to Hang

Connected to the local database with the user id and password for the local user; while applying with the correct ODBC connection and the process initiates for a minute, and then Siebel tools automatically closes; In another machine, the process initiates and the application hangs forever, tried giving many other options w.r.t different user id's and passwords but did not work. Also tried out with SIEBEL/Local user Password, DBA/Enterprise Server Name and all in vain.

Monitoring the status of Siebel Server components

Monitor the status of Siebel Server components that are essential to keep the application up and running has to be performed manually which will be person dependent task

 Solution :

 An automated batch job (VBS/Shell/BAT) that monitors the Siebel components that can be scheduled to run as per need.

Email notifications will be sent to the respective team alerting on the component state

Benefits :

Scheduled to run on demand

Enableing Cancel Query Timeout in Siebel CRM

The cancel query feature allows users to stop the slow or incorrect queries. If the query does not return records within a given number of seconds (the timeout period), a dialog box appears, which allows the user to cancel the query.

The cancel query feature is enabled through the CancelQueryTimeOut parameter in the [SWE] section of the application configuration file (CFG).

Generating Adhoc Reports - Actuate and Siebel

Generate reports in spreadsheet based on business scenarios on a periodical basis and sharing the reports to the respective teams.The task will be repetitive in nature which involves manual intervention

Solution :

An automated batch job (VBS/Shell/BAT) that can generate the reports in a pre-defined format with required business criteria (dynamically) by connecting to the intended database.

Server Request Broker and Server Request Processor

The Server Request Broker and Server Request Processor are two vital components for managing requests for component execution on the Siebel servers. These pre-defined components provided in Siebel are used to handle the requests on Siebel servers effectively by using optimum strategies of load balancing on both single and multi-server deployments.

EIM Data Loading : Oracle function - Bulk Collect

When loading data through EIM process, we normally use Pl/SQL procedures to fetch and process huge volume of records and  then load the data to EIM Interface tables. There are scenarios when the normal way of data loading into EIM tables take long time due to the bulk volume of records. Typical usage of SQL queries result in performance bottleneck issues due to the frequent context switches between the SQL and Pl/SQL engine

Implementation :

EIM Tuning to improve performance

Through EIM process we load bulk amount of data from an external system to Siebel base tables. The performance of these EIM jobs has to be maintained at optimum levels in order to reduce the load on the Siebel application and database servers. The following tips will help you in improving the EIM performance. Do a round of validation in development environment before running the EIM jobs on Production systems 

EIM Data Cleansing : Oracle function – Regular Expression

When loading data into Siebel through EIM, we do perform Data cleansing/massaging as per our 
 
business requirement. The cleansed data from Source is then loaded into the target EIM 
 
Interface tables
  Scenario:
Convert multiple spaces in address related columns to a single space for all records 
 
dynamically.
Recent content