Siebel

Siebel Connection pooling

Connection pooling in Siebel is very important for performance. Siebel Bookshelf contains a section on “Database Connection Pooling Usage Guidelines” that provides general recommendations with regards to connection pooling. Several factors should be considered when determining whether to use connection pooling in an implementation. For example, number of users, type of connections etc.
An implementation with connection pooling is characterized by the following behavior:

Siebel Application Bind variable vs. literals in queries

Siebel uses statements with bind variables throughout the application. Bind variables are good for performance, as Oracle does not need to hard-parse the query every time it is executed. However, in some cases, bind variables lead to major performance problems. One of the more significant problems we faced was the issue of bind variables in SQL LIKE predicates. By default Siebel uses bind variables in passing query criteria values entered by users.

Siebel session hints

When creating the database session, the Siebel database connector makes the following session level changes

It is important to always remember these session hints when analyzing or tuning the performance of Siebel queries. For example, if you are executing a problematic SQL from SQLPlus, or reviewing an execution plan, and you did not set the above session hints, the plan that Oracle will use will most likely differ from the plan the optimizer uses for Siebel.

indexing Siebel custom columns

In most implementations, a high number of indexes already exist on some of the tables (such as, S_OPTY) and you must be careful not to add too many indexes. A new index can fix one query but may slow down another. Moreover, each new index adds some overhead to the system and slows down DML statements (such as, Insert, Delete, and Update).

Siebel Predefined Queries (PDQ) – Reference

PDQ refers to Pre Defined Queries, as the name speaks for itself these are the saved queries in Siebel application. Generally, users can click on Query button and enter query criteria and click go button, and save the query by navigating to  Query Menu -> “Save Query As” There are two types of PDQs

ETL - Performance Improvement Tips

ETL jobs run every day to pull data from Transactional OLTP database Servers and Load Analytical OLAP warehouse data bases takes more time than its expected, Follwing are tips that will help you improve the ETL performance.
Following are the daily running ETLs along with the current (before applying Improvement Tips) timings:-

ETL Name

Siebel - Email/SMS/FAX template substitution

Scenario :

 Need to fill email/sms/fax template content substituted via scripting. Need to dynamically fetch Request ID and Timestamp value pertaining to the instance of the Outbound Communication Manager

What is available Out Of Box – you can use Send Email /SMS/Fax window to select the template to substitute the content. User has to manually copy the content

 Solution : 

Debugging Profile Attribute

There would have been umpteen number of situations where you might have felt the need for an easier way of debugging profile attributes than logging the values in a script, haven't you?.If yes, then here is a much simpler way and you can do this on the fly.
When the web client is up, replace the URL with the following script:
javascript: alert(theApplication().GetProfileAttr("gNewRecord"));where 'gNewRecord' is a profile attribute.
 

Recent content