Bookshelf Home | Contents | Index | Search | PDF

Upgrade Guide for Microsoft Windows > Preupgrade Tasks > Verifying Database Server Configuration >

Oracle Database Server Configuration

---

Before upgrading an Oracle database, complete the following procedures:

• Read Siebel System Requirements and Supported Platforms to determine the supported version and any required patches.
• Upgrade your Oracle database and client software to the supported version, using Oracle's tools and documented procedures.
• Verify that the system tablespace has sufficient room for growth, since new objects are created during the upgrade.

Tablespaces

Allow for growth of the database during the upgrade. Make sure that tablespaces have enough free space to accommodate expected growth as estimated in Table 7 for DB2 UDB, Table 8 for Oracle, and Table 9 for MS SQL Server.

pctincrease. For upgrades, you should have a high value pctincrease for the tablespaces that contain application tablespaces and indexes.

pctfree. Before you start the upgrade, rebuild some of your larger tables with a large value of pctfree for the larger tables (30 or higher). Examples of large tables are:

• s_contact
• s_evt_act
• s_srv_req
• s_src
• s_org_ext
• s_addr_org

NOTE:  You must increase pctfree before the upgrade because many new columns are added to these tables in Release 7.x. Migrating data into the new columns during the upgrade is likely to cause row chaining, which causes performance degradation.

Database Parameters

See the current version of Oracle Administration Guide to determine recommended database parameters for your implementation.

If the database server is a multiple-CPU machine, you can take advantage of parallel index creation. However, if you are executing a Siebel Database Upgrade on an Oracle database server with only one CPU, you must change the Oracle Parallel Index setting in the master upgrade configuration (ucf) file from Y to N. This step must be performed after Siebel Database Configuration and before execution of the Siebel Upgrade Wizard. If this action is not taken, then certain statements that are executed during the upgrade will fail.

• Development environment upgrades. For development environment upgrades, the Oracle Parallel Index parameter (in the master configuration file) defaults to the value N.
  • If your database server is a single-CPU machine, the value of this parameter must be set to N, or the operation will fail.
  • If your database server has more than one CPU, you can change this parameter to Y to yield significance performance benefits.
• Production environment upgrades. Siebel eBusiness Applications assume that parallelism is supported for production environment upgrades; therefore, for production environment upgrades, the Oracle Parallel Index parameter (in the master configuration file) defaults to a value of Y.

The master configuration file is located in the SIEBSRVR\bin directory. The file that you must modify depends on the Siebel version that you are upgrading from, and whether you are upgrading the Siebel database schema or your custom database schema. For example, for upgrades of the Siebel database schema in a development environment from Release 6.0.1 to Release 7.x, you must edit the master configuration file called master_upgrep_dev_601.ucf.

The DBA should set appropriate values according to the Oracle documentation for the following init.ora parameters, depending on the number of CPUs on the database server:

• parallel_max_servers

  NOTE:  The parameter parallel_max_servers must be set greater than 1 to enable parallelism.

• parallel_min_servers
• db_block_lru_latches

The other init.ora parameters that the DBA should choose are:

• sort_area_size
• sort_area_retained size
• log_buffers

For more information, see your Oracle documentation.

Rollback Segments

Verify that you have only one large rollback segment on line that is appropriately sized so that the largest of transactions can be accommodated. Take all other rollback segments off line.

The upgrade may affect some of the largest tables in your implementation of Release 7.x, causing them to grow by as much as 40%.

The shared pool size should be sufficiently large.

Bookshelf Home | Contents | Index | Search | PDF