Are The General Configuration Recommendations on Siebel Database Upgrade Guide Valid for Oracle Database 19c or Above?
(Doc ID 2936721.1)
Last updated on OCTOBER 01, 2024
Applies to:
Siebel CRM - Version 19.1 and laterInformation in this document applies to any platform.
Goal
Are the following notes in the Siebel Database Upgrade Guide still applicable for Oracle Database 19c or above?
UNDO_MANAGEMENT=MANUAL
Siebel bookshelf recommendation:
Set the UNDO_MANAGEMENT parameter to MANUAL before the repository merge. This turns off Automatic Undo Management (AUM). You can turn AUM back on after the repository merge, as desired.
For more information on how AUM affects upgrade, see 477025.1 (Article ID) on My Oracle Support. This document was previously published as Siebel Alert 848.
SORT_AREA_SIZE
Siebel bookshelf recommendation:
Set this parameter to a minimum of 1524288. This significantly reduces the time required to complete a repository merge.
See Siebel Performance Tuning Guide for other parameter settings.
PCTINCREASE
Siebel bookshelf recommendation:
For upgrades, compute a high enough value for pctincrease on tablespaces that contain application tables and indexes so that upgrading does not create large numbers of extents.
PCTFREE
Siebel bookshelf recommendation:
Rebuild some of your larger tables with a large value for pctfree (30 or higher). Table size depends on which Siebel Business Applications you have deployed. For example, if you are upgrading Siebel Financial Services, then S_ASSET is a
large table and S_ADDR_ORG is not used.
You must increase pctfree before the upgrade because many new columns are added to tables during the upgrade. Migrating data into the new columns during the upgrade is likely to cause row chaining, which degrades upgrade performance.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |
References |