Siebel Admin

Siebel Database Sizing Guidelines

One of the most important factors to determine about the database is its overall size. In the planning, users will need to allocate space for system storage, rollback segments/containers, temporary storage space, log files, and other system files required by the RDBMS, as well as space for Siebel data and indexes. If users allocate too little space for the system, performance will be affected and, in extreme cases, the system itself may be halted.

Determining the Siebel User id using the Oracle process id to find who is running the longrunning SQLs

This document will explain a procedure that may be used to associate a specific Oracle database session from the V$SESSION table with a specific Siebel user session. This is typically done to troubleshoot specific issues (for example a database process that is using unusually high resources) or to support levels of user auditing not currently available through the Siebel user interface.

Adding Internet Explorer Support for Siebel 8

The following configuration changes need to be made on the Siebel Application Server for each Siebel installation, so that it knows the capabilities of the IE8 browser. This configuration step is mandatory for all Siebel versions whenever IE8 is used in any environment, regardless of patch level:

Performance of SQL Queries

To check the performance of the application we get the spool and run the queries against the database to check the time it is taking. This check does not return the correct value of the time taken by query when executed through Siebel application. The reason being  when the query is executed Siebel application sets certain parameters at each session level.  Until you set the parameters in the database before execution of the query, correct performance cannot be evaluated.

Setting Expiry Date on Static Components for Improving Performance

Objective:To improve the performance of the Siebel Application and reduce the load on the Web Server.
 
Problem / Analysis:  The “start.swe” component is the one that has all the data for building any Siebel page. The remaining components are the static components (that is the .gif and .js) that are used for building the Web Page.

Overcome Error while Checkout

A common error encountered while doing an object Checkout/Get is –
Siebel-ERR-1109: Unable to read value from export file (Data length (4) > Column definition (1));
 
Solution :
 
Siebel Tools error during checkout / get are almost associated with the local repository having a different schema. In general,  to resolve this issue, we generate a new database template and do a database extract.

Object Locking using Developer logins

Unable to enable object lock with other configured administrator user than SADMIN. For each project you can specify whether or not developers are allowed to check out and check in individual objects within the project. To allow developers to check out and check in objects, you set the project's Allow Object Locking property to TRUE. To modify the Allow Object Locking property, you must use the SADMIN user ID to log in and you must be logged into a server data source.