- Installation Guide
- Installing and Patching Oracle Applications and Oracle Database
- Perform Oracle Database 19c Post-Upgrade Tasks
- Set Parameter Values
Set Parameter Values
- Log in to Oracle Database 19c.
- Set the following values:
- CLOB Changes = ALTER SYSTEM SET EVENT='44951 TRACE NAME
CONTEXT FOREVER, LEVEL 1024' scope=spfile;
Note:
Back up the earlier events and then append this event (if not already set) in the existing list of events, if any. - audit_trial: Check that this parameter uses the same value you used for Oracle Database 11g.
- Execute the following
commands:
alter session set container="CDB$ROOT" alter system set "_gc_persistent_read_mostly"=false scope=spfile;
- Add SQLNET.ALLOWED_LOGON_VERSION_SERVER=10: and SQLNET.ALLOWED_LOGON_VERSION_CLIENT=10 in SQLNET.ORA of grid home in all RAC Nodes
- Add SQLNET.INBOUND_CONNECTION_TIMEOUT=300 in SQLNET.ORA of grid home and PDB $TNS_ADMIN in all RAC Nodes (source the PDB environment file from ORACLE_HOME)
- Remove the encryption parameter. For details, see Use of Oracle Database Native Network Encryption with DMW (Document ID 2783451.1) on My Oracle Support.
The following table contains some more parameters that you must set.Table 3-1 Parameter Names and their Values
Parameter Name Parameter Value Set at Which Container Level (CDB/PDB)? db_16k_cache_size 16 GB Only at the CDB level db_keep_cache_size 12 GB Only at the CDB level java_pool_size At least 2 GB Note: Oracle DMW 3.0 and later uses Java database memory with job/install engine architecture.
Only at the CDB level open_links_per_instance 500 Only at the CDB level processes 5000 Only at the CDB level sga_max_size 126 GB (after checking free huge pages) Only at the CDB level use_large_pages ONLY Only at the CDB level _enable_NUMA_support FALSE Only at the CDB level _enable_NUMA_optimization FALSE Only at the CDB level _gc_persistent_read_mostly FALSE Only at the CDB level shared_pool_size 26 GB Reset the SHARED_POOL_SIZE to 0 (at the PDB level) by executing the following command from PDB:
alter system reset shared_pool_size scope=both;
Only at the CDB level _column_tracking_level 1 At CDB SPFILE _optimizer_dsdir_usage_control 0 At CDB SPFILE _optimizer_gather_stats_on_conventional_dml FALSE Both at PDB and CDB _optimizer_use_stats_on_conventional_dml FALSE Both at the PDB and CDB levels _optimizer_gather_stats_on_load FALSE Both at the PDB and CDB levels job_queue_processes 1000 Both at the PDB and CDB levels parallel_max_servers 64 Both at the PDB and CDB levels container_data CURRENT_DICTIONARY Both at the PDB and CDB levels db_cache_size 48 GB Both at the PDB and CDB levels open_cursors 1000 Both at the PDB and CDB levels open_links 50 Both at the PDB and CDB levels optimizer_features_enable DEFAULT Both at the PDB and CDB levels pga_aggregate_limit 60 GB Both at the PDB and CDB levels pga_aggregate_target 30 GB Both at the PDB and CDB levels _sql_plan_directive_mgmt_control 0 Both at the PDB and CDB levels java_jit_enable TRUE Both at the PDB and CDB levels For information on additional parameters and patches if you have installed the JULY 2022 CPU onward, see DMW Database Parameter Changes And Patches Required Before Applying The July 2022 CPU And October 2022 CPU (Doc ID 2910163.1) on My Oracle Support. - CLOB Changes = ALTER SYSTEM SET EVENT='44951 TRACE NAME
CONTEXT FOREVER, LEVEL 1024' scope=spfile;
Parent topic: Perform Oracle Database 19c Post-Upgrade Tasks