Feedback requested on Siebel configuration

It has been decided from upon high in damamgement that a consultant company WILL be installing an application s/w package produced by Siebel onto a SUNW,Ultra-250 running Solaris 8 acquired specifcally host this application. The system has 1GB RAM and a pair of mirrored (RAID-1) 18GB disks. I am to install Oracle V8.1.6.3 and configure Oracle according the following specifications as supplied by the consultants immediately below.

I'm looking for feedback from others on this list, because some of the values are nothing close to what I'd use based upon my experience.

TIA & HAND!

FYI: For inital installation, the Siebel processes are quite intensive and the DBA will need to allocate enough space for system storage, rollback or temporary space, and log files. Most importantly, the roll backs are used to recover from undo operations and any errors in Siebel. If you allocate too little space for the system, performance will be affected and the system may be halted. Once the install is done, space allocation can be minimized so as not to waste space and have optimum utilization.

Maintenance Warehouse Specific Parameters

Rollback Segments:

        1 main rollback segment 1.2 GB
        4 more roll back segments at 250 MB each

Users Space:            500 MB
Temp:                   200 MB
Index:                  500 MB
System storage:         200 MB
Log file:               Default should be ample

We'll need the datafiles set to automatically extend; - For data and index tablespace, set the initial extent to one block and set the next extent to 100 KB
- For the Temp tablespace set both initial and next extents to be a multiple of SORT_AREA_SIZE+ 1 block.

Max Extends: 5%

Oracle Configuration Parameters

The init.ora file contains parameters that control the operation of the Oracle database. The settings of these parameters have a major impact on the performance of Siebel applications.

NOTE: Use the following settings only as guidelines for your initial configuration. Your final settings will vary based on the server hardware configuration, the number of users, and the type of workload. In the init.ora file, Oracle provides default parameter values for small, medium, and large database configurations. Unless the configuration parameters are specified in the following settings, set them to the large database values.

OPTIMIZER_MODE. Your Siebel application provides better response time using the rule-based optimizer rather than the cost-based optimizer.

DB_BLOCK_BUFFERS. The minimum recommended value is 10,000 blocks
(assuming a block size of 2 KB). This yields 20 MB of block buffers. If significant
I/O activity occurs, you can increase this value, provided that enough RAM is available.

SHARED_POOL_SIZE. Start with a minimum value of 20 MB.

(A DBA should adjust this value upward based on the hardware (available physical
memory) and
performance. Siebel applications make heavy demands on the dictionary cache for columns. In Oracle, you cannot explicitly set the size of the column cache. Instead, column cache is set as a fixed percentage of the shared pool size. By setting a large shared pool size, you effectively set a large column cache size. Consult your Oracle documentation for guidelines and more information.)

DB_FILE_MULTIBLOCK_READ_COUNT. This value should be set between 16 and 32 blocks, and adjusted as necessary. You may want to set an initial value of 32.

SORT_AREA_SIZE. Set to 512,000
(This value is specified in bytes, and may be adjusted according to
the number of users, the amount of RAM available, and the size of sorted queries. You should start with an initial value of 512,000.)

SORT_AREA_RETAINED_SIZE. Set to 65,536

(This value is specified in bytes, and determines how
much sort area is retained for each user process. You should start with an initial value of 65,536.)

OPEN_CURSORS. Set to 1,500
(This parameter may be adjusted according to observed usage
patterns. The minimum open cursor requirement for Oracle support in Siebel 6.x is 1,500. If you set this value lower, Oracle may return an error to the application that prevents you from continuing.)

USE_ISM. This value may be set to FALSE by the Oracle installer. On some platforms, Oracle recommends that you set the USE_ISM value to FALSE to avoid software anomalies. If the version of Oracle you are using does not have these anomalies, the recommended setting for your Siebel application is TRUE. Refer to Oracle World Wide Support for specific information regarding this parameter on your database platform.

DB_BLOCK_SIZE. Set to 4 KB.

NLS_DATE_FORMAT. This parameter is set to DD-MON-YY by default. To ensure year 2000 compliance, you should reset it to DD-MON-RR,or to the appropriate national date format, substituting RR for YY.

NLS_LANGUAGE. Set to 100.

SESSIONS. Certain Siebel operations require multiple connections. If you change this parameter, make sure it is set to a number greater than 1.

-- 
Charlie Mengler               Maintenance Warehouse  
charliem_at_mwh.com              10641 Scripps Summit Ct   
858-831-2229                  San Diego, CA 92131    
The future is here. It is just not evenly distributed.
-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Charlie Mengler
  INET: charliem_at_mwh.com

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L


(or the name of mailing list you want to be removed from).  You may

also send the HELP command for other information (like subscribing).