Siebel Installation Guide for Microsoft Windows > Configuring the RDBMS > Configuring an Oracle Database for Siebel Business Applications >

Guidelines for Ongoing Oracle Database Administration

After your Siebel Business Applications installation is up and running, monitor the following areas on a regular basis:

• Insertion rates on tables. You probably will want to set the INI_TRANS value for tables with high insertion rates to a value higher than 1; a typical setting is 4.

  This parameter determines how many simultaneous inserts can occur on the database blocks that store data for those tables and, therefore, can affect performance in an intensive data-entry environment. Use multiple freelists for the table S_DOCK_TXN_LOG, because this table receives numerous inserts.

• SGA cache hits. Determine whether SGA parameters have to be adjusted for your system.
• The extents used by each object. A large number of extents on a table or index creates response time degradation for transactions that access the table or index.
• Siebel tables that are subject to frequent INSERT and DELETE operations. This transaction mixture can cause some database tables to become fragmented over time.

  If you are using Siebel Remote, then your DBA must monitor space utilization and fragmentation of the following tables, and perform regular database maintenance procedures as recommended for an Oracle Database. Monitor the following tables in particular, because they will have frequent changes when transaction logging is enabled:

  • S_SRM_REQUEST
  • S_DOCK_TXN_LOG
  • S_DOCK_TXN_LOGT
  • S_DOCK_TXN_SET
  • S_DOCK_TXN_SETT
  • S_DOCK_INST
  • S_DOCK_INIT_ITEM

    Your DBA might also choose to monitor all of the tables and indexes in the Siebel schema, reorganizing them when required.

This topic is part of Configuring an Oracle Database for Siebel Business Applications.