Database Initialization Parameters for Oracle E-Business Suite Release 12

 

Copyright (c) 2025, Oracle. All rights reserved. Oracle Confidential. Database Initialization Parameters for Oracle E-Business Suite Release 12 (Doc ID 396009.1) To Bottom This document is the main reference for setting Oracle Database initialization parameters for use with Oracle E-Business Suite (EBS) Release 12. In This Document Using This Document Important Considerations Section 1: Common Database Initialization Parameters For All Releases Section 2: Release-Specific Database Initialization Parameters For Oracle AI Database 26ai Section 3: Release-Specific Database Initialization Parameters For Oracle Database 19c Section 4: Release-Specific Database Initialization Parameters For Oracle Database 12c Release 1 Section 5: Release-Specific Database Initialization Parameters For Oracle Database 11g Release 2 Section 6: Additional Database Initialization Parameters For Oracle E-Business Suite Release 12.2 Section 7: Exadata-Specific Database Initialization Parameters Section 8: Using System Managed Undo (SMU) Section 9: Temporary Tablespace Setup Section 10: Database Initialization Parameter Sizing The most current version of this document can be obtained in My Oracle Support Knowledge Document 396009.1. There is a change log at the end of this document. Note: To receive automatic notifications of updates, subscribe to the Hot Topics Notification feature in My Oracle Support, as described in Document 793436.2, Subscribing to Hot Topic E-Mails. Using This Document As you use to this document, bear in mind the following points: Section 1: Common Database Initialization Parameters For All Releases provides a common set of database initialization parameters that are applicable to all releases of Oracle Database. Following Section 1 are several release-specific sections, which list parameters and settings required for a particular release of Oracle Database. Combined, the parameters from Section 1 and the appropriate release-specific section formulate a complete set of database initialization parameters. Parameters may appear on a removal list for any of the following three reasons: Because they are obsolete. Because the default value is required and no other value may be set. To cater for cases where a non-default value has to be set to meet specific needs. Currently, there is only one such case, which is described in Section 8: Using System Managed Undo (SMU). The "X" notation used in the release-specific section denotes all patchset releases within that major version. For example, "11.2.0.X" refers to all releases of 11.2.0, such as 11.2.0.2, 11.2.0.3, and 11.2.0.4. Important Considerations Note: Oracle Database 12c Release 12.1.0.2 and Oracle Database 11g Release 11.2.0.4 are in Upgrade Support, the successor to Market Driven Support (MDS). We strongly recommend that you upgrade to Oracle Database 19c as soon as possible.  For more information on Upgrade Support and how to upgrade, see Document 2997711.1, Alert: Oracle E-Business Suite On-Premises Customers and Upgrade Support for Oracle Database Releases 12.1.0.2 and 11.2.0.4. Consider the following when reading this document. Note that line numbers are provided solely for reference; the order is non-sequential and does not imply priority. Any parameters not listed in either Section 1: Common Database Initialization Parameters For All Releases or the release-specific sections should be left at their default values. Consequently, such parameters do not need to be explicitly set in the initialization parameter file (init.ora). Hidden parameters in Oracle Database start with an underscore (“_”). Generally, hidden parameters are undocumented and are not shown in the v$parameter view unless they have been set explicitly in the init.ora file. They are usually provided as part of bug fixes or workarounds to address specific problems. Arbitrarily changing these parameters may lead to performance degradation or other problems. Therefore, is not advisable to set or modify any hidden parameters unless explicitly recommended either in this document, or by Oracle Support or Development. Oracle E-Business Suite Release 12.2 requires Oracle Database 11g Release 2 (11.2.0.4) Enterprise Edition as a minimum release level and edition. No earlier releases, or other editions of any release, may be used. Refer to Section 6: Additional Database Initialization Parameters For Oracle E-Business Suite Release 12.2. Oracle E-Business Suite Release 12 requires Oracle Database 11g Release 2 (11.2.0.4) Enterprise Edition as a minimum release level and edition. No earlier releases, or other editions of any release, may be used. Oracle E-Business Suite Releases 12.2 and 12.1.3 are certified on Oracle Database 19c with a single tenant (1 CDB : 1 PDB) configuration. For the 19c single tenant database configuration and settings, refer to Oracle Database, Database Administrator's Guide 19c.  Oracle E-Business Suite Release 12.2 is certified on Oracle AI Database 26ai with a single tenant (1 CDB : 1 PDB) configuration. For the Oracle AI Database 26ai single tenant database configuration and settings, refer to Oracle AI Database, Database Administrator's Guide 26ai. Oracle E-Business Suite Release 12.2 and 12.1.3 customers using Oracle Database 12c Release 1 Version 12.1.0.2 or later who are implementing Oracle Database In-Memory should refer to Oracle Database Administrator's Guide for the required set of database initialization parameters. Oracle E-Business Suite customers using Exadata with any of the certified combinations listed in the Certifications database on My Oracle Support and implementing Oracle E-Business Suite on Exadata machine, should refer to Section 7: Exadata-Specific Database Initialization Parameters and the "E-Business Suite" section in document MAA Best Practices - Oracle Applications Unlimited for the required set of Exadata-specific database initialization parameters and Exadata best practices. "Section 3: Database Best Practices" of Document 2528000.1, Oracle E-Business Suite Performance Best Practices, offers strategic guidance on performance best practices for all Oracle E-Business Suite environments, including platform-specific database initialization parameters, and is updated as new features and options become available. FIPS Parameters For Oracle AI Database 26ai, the following database parameter settings are not currently supported with Oracle E-Business Suite: DBFIPS_140=TRUE (in the database initialization parameter file or server parameter file) FIPS_140=TRUE (in the FIPS.ora file) Setting these parameters to TRUE will result in EBS runtime errors. You must therefore ensure that these parameters are not set or are set to FALSE for your Oracle E-Business Suite database. For Oracle Database 19c, the following database parameter setting is not currently supported with Oracle E-Business Suite: DBFIPS_140=TRUE (in the database initialization parameter file or server parameter file) Setting this parameter to TRUE may result in EBS runtime errors. You must therefore ensure that this parameter is not set or is set to FALSE for your Oracle E-Business Suite database. Linux HugePages and use of the USE_LARGE_PAGES Parameter We recommend configuring Linux HugePages on the database server to enhance SGA management. This ensures that the SGA remains pinned in memory, preventing page-in and page-out operations, and minimizing system resources needed for managing page table entries. Note that only the SGA (not the PGA), can utilize and benefit from HugePages. For instructions on enabling HugePages for EBS database instances, refer to Document 1392497.1, USE_LARGE_PAGES to Enable HugePages. Additionally, a change introduced in Oracle AI Database 26ai, Release Update (RU) 23.8 (April 2025) and Oracle Database 19c, RU 19.27 (April 2025) prevents the use of small pages for the SGA in database instances running on Oracle Exadata. Small pages are the default Linux memory pages with a size of 4 KB. For more information, refer to Document 3081878.1, Starting DBRU 19.27 and 23.8: Small Pages Are Not Allowed for RDBMS SGA in Exadata. To utilize HugePages, set the database initialization parameter use_large_pages=ONLY on each instance. This will ensure it starts only when sufficient HugePages are available, thereby preventing out-of-memory errors. The 'ONLY' value specifies that the instance will fail to start unless large pages can be used for the entire SGA. We recommend this configuration for optimal and consistent performance. For cloud services, it is also the default and mandatory setting for the Oracle Exadata Database Service and Base Database Service. EBS Database Parameter Checker (EDBPC) Utility Oracle recommends using the EBS Database Parameter Checker to help you ensure that all required database parameters have been set correctly in your EBS database. The EDBPC utility compares the database initialization parameters set in your EBS Release 12.2 system to the recommended settings as listed in Document 396009.1, Database Initialization Parameters for Oracle E-Business Suite Release 12. EDBPC then displays missing or incorrectly set parameters in a summary report designed to facilitate corrective actions on your part. To use EDBPC, always download the latest version using Patch 36625551 for the most recent parameter recommendations. For more information about EDBPC, refer to Document 3015099.1, Using the Oracle E-Business Suite Database Parameter Checker (EDBPC). For important supplementary guidance on the topics covered by this document in the context of your specific database version, refer as applicable to the following My Oracle Support knowledge documents: Document 2962871.1, Interoperability Notes: Oracle E-Business Suite Release 12.2 with Oracle AI Database 26ai Document 2552181.1, Interoperability Notes: Oracle E-Business Suite Release 12.2 with Oracle Database 19c Document 2580629.1, Interoperability Notes: Oracle E-Business Suite Release 12.1 with Oracle Database 19c Section 1: Common Database Initialization Parameters For All Releases This section lists the database initialization parameters that are common across releases of Oracle Database. You should refer to it in conjunction with the relevant release-specific section. Note: All parameters listed in this section should be set as stated, unless your particular release-specific section instructs otherwise. The parameter values provided in this document reflect a small instance configuration (See Section 10: Database Initialization Parameter Sizing). You should adjust the relevant parameters based on the number of active Oracle E-Business Suite users. In addition, you should investigate any parameters that are set but not mentioned in this document. ############################################################################## # # Oracle E-Business Suite Release 12 # Common Database Initialization Parameters # # The following represents the common database initialization # parameters file for Oracle E-Business Suite Release 12. # Release-specific parameters are included in the respective release # section. The release-specific parameters should be appended to the # common database initialization parameter file. # # There are numerous mandatory database initialization parameters. # Their settings must not be altered. The use of values other than # those provided in this document will not be supported unless Oracle # Support has specifically instructed you to alter these parameters # from their mandatory settings. # # Mandatory parameters are denoted with the #MP symbol as a # comment. This includes parameters such as NLS and optimizer # related parameters. # # The remaining (non-mandatory) parameters relate to either sizing or # configuration requirements that are specific to customer environments # or system capacity. A sizing table provides recommendations and # guidelines based on the number of deployed and active Oracle # E-Business Suite users. Customers can adjust these parameters as per # their environment and system resource capacity. # ############################################################################## ########## # # Database identification parameters. # # The database identification parameters define the name of the # database and the names of the database control files. # # The database name is established when the database is built, and # for most customers it matches the instance name. It should not # normally be necessary to change the database name, except for # the purposes of database cloning. # # There should be at least two control files, preferably three, # located on different volumes in case one of the volumes fails. # Control files can expand, hence you should allow at least 20M # per file for growth. # ######### db_name = prodr12 control_files = ('/disk1/prodr12_DB/cntrlprodr12_1.dbf', '/disk2/prodr12_DB/cntrlprodr12_2.dbf', '/disk3/prodr12_DB/cntrlprodr12_3.dbf') ######### # # Database block size parameter. # # The required block size for Oracle E-Business Suite is 8192 bytes. No other value may be used. # ######### db_block_size = 8192 #MP ######### # # Compatibility parameter. # # See the appropriate release-specific section of this document for details of setting # compatibility. # ######### ######### # # System Trigger parameter. # # The _system_trig_enabled parameter must be set to TRUE. # If _system_trig_enabled parameter is set to FALSE it will # prevent system triggers from being executed. # ######### _system_trig_enabled = TRUE #MP ######### # # NLS and character set parameters. # # Some NLS parameter values are mandatory and must be set to specific settings. # These are the only supported settings for these parameters for Oracle E-Business # Suite Release 12. They must not be changed to other values. # Other NLS parameters have been given default values, which can be changed as required. # ######### nls_language = american nls_territory = america nls_numeric_characters = ".," nls_comp = binary #MP nls_sort = binary #MP nls_date_format = DD-MON-RR #MP nls_length_semantics = BYTE #MP ######### # # Auditing parameter. # # There is a performance overhead for enabling the audit_trail # parameter. In addition, the database administrator will need # to implement a purge policy for the SYS.AUD$ table. # # Statement-level auditing should not be used. # # Allowed Values are { none | os | db [, extended] | xml [, extended] # ######### # audit_trail = DB # Uncomment if you want to enable audit_trail. ####### # # Diagnostic Parameters. # # As of Oracle Database 11g, the diagnostics for each database # instance are located in a dedicated directory that can be specified # via the DIAGNOSTIC_DEST initialization parameter. The format of # the directory specified by DIAGNOSTIC_DEST is as follows: # # <diagnostic_dest><diagnostic_dest>/diag/rdbms/<dbname>/<instname> # # Diagnostic files are located in their own subdirectories of the # DIAGNOSTIC_DEST directory, according to type: # # Trace files - <diagnostic_dest>/diag/rdbms/<dbname>/<instname>/trace # Alert logs - <diagnostic_dest>/diag/rdbms/<dbname>/<instname>/alert # Core files - <diagnostic_dest>/diag/rdbms/<dbname>/<instname>/cdumd # Incident dump files - <diagnostic_dest>/diag/rdbms/<dbname>/<instname>/incident/<incdir#> diagnostic_dest = ?/prod12 ######## # # Dump File Size parameter. # # The max_dump_file_size parameter can be used to specify the maximum # size of a dump file, to prevent a trace file using an excessive # amount of disk space. (This can also be changed at session level.) # ######## max_dump_file_size = 20480 #Limit default trace file size to 20 MB. ######### # # System-Managed Undo Parameters. # # Oracle E-Business Suite requires the use of System Managed Undo (SMU). # This is more efficient than manually managed rollback segments, # and reduces the chances of "snapshot too old" errors. It is also # easier to manage SMU than the rollback segments it replaces. # ######### undo_management=AUTO #MP undo_tablespace=APPS_UNDOTS1 ######### # # PL/SQL parameters. # # The following parameters are used to enable the PL/SQL global # optimizer as well as native compilation. # # PL/SQL native compilation is recommended for Oracle AI Database 26ai and # Oracle Database releases 19c, 12c, or 11g based Oracle E-Business Suite # environments such as Release 12. Interpreted mode is supported, # and can be used with Oracle E-Business Suite. However, native compilation is # recommended in order to maximize runtime performance and scalability. # # Compiling PL/SQL units with native compilation takes longer than using # interpreted mode, because of the need to generate and compile the native # shared libraries. # # If native compilation is to be used, uncomment the plsql_code_type = NATIVE # line below. Note that starting from 11g, the parameters plsql_native_library_dir # and plsql_native_library_subdir_count have no effect and are not needed, as # natively compiled code is now stored in the database, not a filesystem. # ######### #plsql_code_type = NATIVE #Uncomment if you want to use NATIVE compilation. ######## # Trace file accessibility parameter. # # Setting this parameter to FALSE is recommended, but it can be enabled # on non-production databases to facilitate easier trace file analysis. # Warning: Consider the security implications of setting this to TRUE # as trace files may include secure data in BIND variables. # ######## _trace_files_public = FALSE ######### # # Processes and sessions parameters. # # A database process can be associated with one or more database # sessions. For all technology stack components other than Oracle # Forms, there is a one-to-one mapping between sessions and processes. # # For Forms processes, there will be one database session per # open form, with a minimum of two sessions per Forms user (one # for the navigator form, and one for the active form). # # The sessions parameter should be set to twice the value of the # processes parameter. # ######### processes = 200 # Max. no. of users. sessions = 400 # 2 x no. of processes. db_files = 512 # Max. no. of database files. dml_locks = 10000 # Database locks. ######## # # Cursor-related parameters. # ######## cursor_sharing = EXACT #MP open_cursors = 600 session_cached_cursors = 500 ######## # # Cache parameters. # # For Oracle AI Database 26ai and Oracle Database releases 19c, 12c and 11g, # the automatic SGA tuning option (sga_target) is required. This avoids the # need for individual tuning of the different caches, such as the buffer cache, # shared pool, and large pool. Use of the automatic SGA tuning option also # improves manageability and overall performance. # # sga_target refers to the total size of the SGA. This includes # all the sub-caches, such as the buffer cache, log buffer, # shared pool, and large pool. The sizing table in the # section Database Initialization Parameter Sizing contains # sizing recommendations for sga_target. # # When the automatic SGA tuning option is used to dynamically size # the individual caches, it is recommended to use a Server Parameter # file (SPFILE) to store the initialization parameter values. # Using an SPFILE allows the dynamically-adjusted values to persist # across restarts. Refer to the Oracle Database Administrator's # Guide for information on how to create and maintain an SPFILE. # # db_block_checking can be enabled and set to LOW, MEDIUM or FULL. # Note this may incur an overhead of 1% - 10%. # ######## sga_target = 2G #MP db_block_checking = FALSE db_block_checksum = TRUE ######## # # Log Writer parameters. # # The log writer parameters control the size of the log buffer # within the SGA, and how frequently the redo logs are checkpointed # (when all dirty buffers written to disk and a new recovery point # is created). # # A size of 10MB for the log buffer is a reasonable value for # Oracle E-Business Suite. This represents a balance between # concurrent programs and online users. The value of log_buffer # must be a multiple of redo block size (normally 512 bytes). # # The checkpoint interval and timeout control the frequency of # checkpoints. # ######## log_checkpoint_timeout = 1200 # Checkpoint at least every 20 mins. log_checkpoint_interval = 100000 log_buffer = 10485760 log_checkpoints_to_alert = TRUE ######### # # Shared pool parameters. # # The shared pool should be tuned to minimize contention for SQL # and PL/SQL objects. For Release 12, a reasonable starting point # is a size of 600M and a 60M reserved area (10%). # # For Oracle AI Database 26ai or Oracle Database 19c either on-premises # or on an Oracle Cloud database service, and for a Oracle Database 12.1.0.2 # on an Oracle Cloud database service, the database architecture is # multitenant (CDB with a single PDB). In all such cases the shared_pool_size # parameter must be set at CDB level only. # # Remove shared_pool_size from the PDB parameter file if it is set. # ######## shared_pool_size = 600M shared_pool_reserved_size = 60M ######## # # Advanced Queuing (AQ) and Job Queue parameters. # # AQ requires the TM process to handle delayed messages. A number # of Application modules use AQ, including Workflow. Job Queues # enable advanced queue to submit background jobs. # # aq_tm_processes is auto-tuned. Omitting this parameter has not, however, # been tested with Oracle E-Business Suite. The minimum required value # is 1 and should be increased to resolve lengthy queues. # # Usually, job_queue_processes should typically be set to a value of 2 # for optimal performance. However, the value can be tuned to meet the # specific requirements of the Workflow module and customer needs, # based on the number of job queue processes needed to handle AQ # event messages and for Workflow notification mailers. # ######## aq_tm_processes = 1 job_queue_processes = 2 ######## # # Archiving parameters. # # Archiving parameters, including destination, may be specified in Oracle AI Database 26ai # and Oracle Database releases 19c, 12c, or 11g. Optionally, multiple destinations may be specified. # ######## log_archive_dest_1 = 'LOCATION=/disk1/arc' log_archive_dest_2 = 'SERVICE=standby1' ######## # # Events parameters. # # Events should only be set when explicitly requested by Oracle Support or Development. # Refer to the appropriate release-specific section for events that may be set. # ######## ######### # # Optimizer parameters. # # The following optimizer parameters must be set as below, and may # not be changed. No other values are supported. # # Refer also to the release-specific section for any additional # optimizer parameters which must be set. # ######### _sort_elimination_cost_ratio =5 #MP _like_with_bind_as_equality = TRUE #MP _fast_full_scan_enabled = FALSE #MP _b_tree_bitmap_plans = FALSE #MP optimizer_secure_view_merging = FALSE #MP _optimizer_autostats_job = FALSE #MP Turn off automatic statistics. ######## # # Parallel Execution parameters. # # Parallel execution is used by some Oracle E-Business Suite concurrent programs, # including DBI programs and Gathering Statistics. AD will also use parallel # execution when creating large indexes. # # It is recommended to set the parameter parallel_degree_policy to MANUAL, the default value. # This disables automatic degree of parallelism. Statement-queuing and in-memory parallel # execution SQL statements with a parallel hint can allocate parallel execution processes up # to the value of parallel_max_servers. # ######## parallel_max_servers = 8 # Max. value should be 2 x no. of CPUs. parallel_min_servers = 0 parallel_degree_policy = MANUAL #MP ######### # # Parallel execution and Oracle Real Application Clusters (Oracle RAC) parameters. # # It is recommended to set the parameters PARALLEL_FORCE_LOCAL # on each instance, to ensure that parallel requests do not span instances. # As of 11gR2, Oracle E-Business Suite customers must set the value of this # parameter to TRUE and then are no longer required to set parallel_instance_groups # and instance groups for the purpose of preventing inter-instance sql # parallelism in Oracle RAC environments. # ######### parallel_force_local=TRUE #MP ######### # # Oracle Real Application Clusters parameters. # # The following Oracle RAC related parameters should be set when running # E-Business Suite in an Oracle RAC environment. # Set cluster_database = FALSE if not using RAC ######### cluster_database = TRUE #MP ######### # # Parallel Execution and Oracle RAC parameters. # # It is recommended to set the parameters instance_groups and # parallel_instance_group on each instance, to ensure that parallel # requests do not span instances. # For example, on instance1, set instance_groups=apps1 and # parallel_instance_group=apps1. On instance2, set # instance_groups=apps2 and parallel_instance_group=apps2, and so on. # ######### ######### # # Private memory area parameters. # # The automatic memory manager is used to manage the PGA memory. This # avoids the need to manually tune the settings of sort_area_size and # hash_area_size. # The automatic memory manager also improves performance and scalability, # as memory is released back to the operating system. # ######### pga_aggregate_target = 1G workarea_size_policy = AUTO #MP ######### # # Direct I/O and Asynchronous I/O parameter. # # Direct I/O bypasses OS layer caching. If Direct I/O and asynchronous are enabled on your OS, # and your Linux kernel version is uek-2.6.39-200.29.3.el6uek or later (see Doc ID 1487957.1), # use SETALL for optimal performance. Otherwise, use the value that matches your system: # none | directIO | asynch # Note: SETALL is mandatory for Oracle E-Business Suite on Oracle Public Cloud. # ######### filesystemio_options = SETALL ######## # # Database Password Case Sensitivity parameter. # # Oracle E-Business Suite 12.1.1 or higher supports Oracle Database case-sensitive database # passwords. The default value of this parameter is TRUE, i.e. passwords are case-sensitive at # the database level. # The default for Oracle E-Business Suite databases is FALSE i.e. passwords are case-insensitive # Although the parameter is deprecated in Oracle Database 12c and 19c, it still needs to be # explicitly set for Oracle E-Business Suite. To enable case-sensitivity of database passwords in # Oracle E-Business Suite, set the parameter to TRUE and follow the steps in My Oracle Support # Knowledge Document 1581584.1, Patch 12964564:R12.FND.B - Enabling the Oracle Database 11g # Case-Sensitive Password Feature for Oracle E-Business Suite Release 12.1.1+. # # Also, if you are on an Oracle E-Business Suite Release prior to 12.2, apply Patch 12964564. # To disable case-sensitivity, set the parameter to FALSE. # # This step of enabling case-sensitivity is now mandatory with Oracle AI Database 26ai, # since sec_case_sensitive_logon has been desupported. # ######## sec_case_sensitive_logon = FALSE ######### # # Disable Actualization for Grant parameter. # # Depending on your database version, before setting this parameter you may need to apply # a prerequisite patch as follows: # # - If you are on Oracle AI Database release 26ai or Oracle Database 19c, no patch is needed. # # - If you are on Oracle Database release 12cR1 or 11gR2, apply the associated database patch. #   (Bug 26654363 - EBR Granting Privileges Causes Invalidation). For more information, refer #   to My Oracle Support Knowledge Document 1594274.1, Oracle E-Business Suite Release 12.2: #   Consolidated List of Patches and Technology Bug Fixes. # # For all database versions, set the _disable_actualization_for_grant parameter to TRUE. # ######### _disable_actualization_for_grant = TRUE #MP ############################################################################### # # End of Common Database Initialization Parameters Section # ############################################################################### Section 2: Release-Specific Database Initialization Parameters for Oracle AI Database 26ai Note: Oracle AI Database 26ai replaces Oracle Database 23ai. 2.1 Required Parameters 2.2 Parameter Removal List for Oracle AI Database 26ai 2.1 Required Parameters The following list describes database initialization parameters required for Oracle AI Database 26ai. These parameters should be added to the common database initialization parameters provided in Section 1, so that the final database initialization parameters file includes the common section plus the contents of this release-specific section. ################################################################################# # # Oracle E-Business Suite Release 12.2 # Release-Specific Database Initialization Parameters for Oracle AI Database 26ai # ################################################################################# ######### # # Compatibility parameter. # # Compatibility should be set to the current release. # ######### compatible = 23.0.0 #MP ######### # # Optimizer parameters. # # In Oracle Database 12.2 or higher, the Parameter optimizer_adaptive_features has been obsoleted, # replaced and controlled by two new parameters, optimizer_adaptive_plans, which defaults to TRUE and # optimizer_adaptive_statistics, which defaults to FALSE. For more details Refer MOS DOC ID 2031605.1. # ########## optimizer_adaptive_plans = TRUE #MP optimizer_adaptive_statistics = FALSE #MP ######### # # PGA Aggregate Limit parameter. # # PGA_AGGREGATE_LIMIT feature in Oracle AI Database 26ai limits PGA memory usage # # The default value of PGA_AGGREGATE_LIMIT is set to the greater of 2 GB, # 200% of PGA_AGGREGATE_TARGET, and 3 MB times the PROCESSES parameter. # It will not exceed 120% of the physical memory size minus the total SGA size. # # PGA_AGGREGATE_LIMIT cannot be set below its default value. If a value of 0 is specified, # it means there is no limit to the aggregate PGA memory consumed by the instance. # If total PGA memory usage is over PGA_AGGREGATE_LIMIT value. The sessions or processes # that are consuming the most untunable PGA memory will be terminated. # # Recommended value for PGA_AGGREGATE_LIMIT is 0. # ########## pga_aggregate_limit = 0 #MP ######### # # Temp Undo Enabled parameter. # # TEMP_UNDO_ENABLED helps to reduce the amount of redo caused by DML on global temporary tables. # Setting to TRUE may cause serious issues, such as ORA-55526, for distributed transactions (Ref. Bug 20712819). # The recommended value for systems using distributed transactions is currently FALSE (Pending ER 24286334). # If not using distributed transactions, TRUE will improve performance by eliminating REDO on permanent UNDO. # ########## temp_undo_enabled = FALSE ######### # # Event parameter. # # Ensure the following event is set for Oracle E-Business Suite to work with Oracle AI Database 26ai. # This parameter needs to be set at the CDB level. When this event is set, # it will allow utl_file functions to accept a directory path as input on Oracle AI Database 26ai. # ########## event='10946 trace name context forever, level 8388608' #MP ######### # # PL/SQL parameters. # # When the permit_92_wrap_format parameter is set to TRUE, it allows Oracle Database Release 9.2 # wrapped versions of PL/SQL source text to be used in Oracle AI Database 26ai and # Oracle Database releases 19c, 12c, and 11g. # From Oracle Database 21c, the default value of permit_92_wrap_format has been changed to FALSE. # ##########- permit_92_wrap_format=TRUE #MP ######### # # container_data parameter. # # It is recommended to set the parameter container_data to CURRENT_DICTIONARY. When this parameter is set, # it will handle queries on extended data-linked objects within the PDB return rows from the PDB only. # This parameter needs to be set at the PDB level only. # ########## container_data = CURRENT_DICTIONARY ######### # # Unified Audit parameter. # # This parameter is required by Oracle E-Business Suite for Unified Auditing. When this parameter is set, # it will allow Unified Audit Trail with UB4 type session ID for Oracle E-Business Suite. # This parameter needs to be set at the PDB level only. # ########## _ub4_audit_sessionid=TRUE #MP ################################################################################################ # # End of Release-Specific Database Initialization Parameters Section for Oracle AI Database 26ai # ################################################################################################ 2.2 Parameter Removal List for Oracle AI Database 26ai If they exist, you should remove the following parameters from your database initialization parameters file for Oracle AI Database 26ai. Note: Parameters may appear on a removal list for any of the following three reasons: They are obsolete. The default value is required and no other value may be set. To cater for certain special cases where a non-default value has to be set to meet specific needs. Currently, there is only one such case, which is described in Section 8: Using System Managed Undo (SMU). _kks_use_mutex_pin _pdb_name_case_sensitive _shared_pool_reserved_min_alloc _sqlexec_progression_cost always_anti_join always_semi_join background_dump_dest core_dump_dest db_block_buffers db_cache_size db_file_multiblock_read_count drs_start enqueue_resources event="10932 trace name context level 32768" event="10933 trace name context level 512" event="10943 trace name context forever, level 2" event="10943 trace name context level 16384" event='10946 trace name context forever, level 8454144' event="38004 trace name context forever, level 1" exafusion_enabled exclude_seed_cdb_view global_context_pool_size hash_area_size instance_groups java_pool_size job_queue_interval large_pool_size max_enabled_roles o7_dictionary_accessibility olap_page_pool_size optimizer_adaptive_features optimizer_dynamic_sampling optimizer_features_enable optimizer_index_caching optimizer_index_cost_adj optimizer_max_permutations optimizer_mode optimizer_percent_parallel optimizer_secure_view_merging parallel_automatic_tuning parallel_instance_group parallel_degree_level parallel_io_cap_enabled parallel_server parallel_server_instances plsql_compiler_flags plsql_native_library_dir plsql_native_library_subdir_count plsql_optimize_level query_rewrite_enabled rollback_segments row_locking sec_case_sensitive_logon sort_area_size standby_archive_dest sql_trace sql_version timed_statistics undo_retention undo_suppress_errors use_indirect_data_buffers user_dump_dest utl_file_dir DBFIPS_140 FIPS_140 Section 3: Release-Specific Database Initialization Parameters for Oracle Database 19c 3.1 Required Parameters 3.2 Parameter Removal List for Oracle Database 19c 3.1 Required Parameters The following list describes database initialization parameters required for Oracle Database 19c. These parameters should be added to the common database initialization parameters provided in Section 1, so that the final database initialization parameters file includes the common section plus the contents of this release-specific section. #################################################################### # # Oracle E-Business Suite Release 12 # Release-Specific Database Initialization Parameters for 19c # #################################################################### ######### # # Compatibility parameter. # # Compatibility should be set to the current release. # ######### compatible = 19.0.0 #MP ######### # # Optimizer parameters. # # In Oracle Database 12.2 or higher, the Parameter optimizer_adaptive_features has been obsoleted, # replaced and controlled by two new parameters, optimizer_adaptive_plans, which defaults to TRUE and # optimizer_adaptive_statistics, which defaults to FALSE. For more details Refer MOS DOC ID 2031605.1. # ########## optimizer_adaptive_plans = TRUE #MP optimizer_adaptive_statistics = FALSE #MP ######### # # PGA Aggregate Limit parameter. # # PGA_AGGREGATE_LIMIT feature in 19c limits PGA memory usage # # The default value of PGA_AGGREGATE_LIMIT is set to the greater of 2 GB, # 200% of PGA_AGGREGATE_TARGET, and 3 MB times the PROCESSES parameter. # It will not exceed 120% of the physical memory size minus the total SGA size. # # PGA_AGGREGATE_LIMIT cannot be set below its default value. If a value of 0 is specified, # it means there is no limit to the aggregate PGA memory consumed by the instance. # If total PGA memory usage is over PGA_AGGREGATE_LIMIT value. The sessions or processes # that are consuming the most untunable PGA memory will be terminated. # # Recommended value for PGA_AGGREGATE_LIMIT is 0. # ########## pga_aggregate_limit = 0 #MP ######### # # Temp Undo Enabled parameter. # # TEMP_UNDO_ENABLED helps to reduce the amount of redo caused by DML on global temporary tables. # Setting to TRUE may cause serious issues, such as ORA-55526, for distributed transactions (Ref. Bug 20712819). # The recommended value for systems using distributed transactions is currently FALSE (Pending ER 24286334). # If not using distributed transactions, TRUE will improve performance by eliminating REDO on permanent UNDO. # ########## temp_undo_enabled = FALSE ######### # # Multitenant Architecture parameter. # # For on-premises, this parameter must be set to TRUE when the non-CDB name is in either lowercase or # mixed case. This ensures that the PDB will then be created with the same case. # Otherwise, for an uppercase PDB name, the default value of FALSE can be retained. # # For Oracle Cloud Infrastructure, uppercase PDB names are required therefore this parameter # must be set to FALSE. # # This parameter must be set to the correct value at CDB level before a PDB is created. # Once the PDB has been created, the value must not be changed unless specifically # directed by Oracle, for example in My Oracle Support Knowledge Document 2782130.1, # "Implementing Case-Insensitive Pluggable Database Names with Oracle E-Business Suite # Release 12.2 and 12.1 on Oracle Database 19c Multitenant Architecture". # ########## _pdb_name_case_sensitive = FALSE ######### # # Event parameter. # # Ensure the following event is set for Oracle E-Business Suite to work with Database Release 19c. # This parameter needs to be set at the CDB level. When this event is set, # it will allow utl_file functions to accept a directory path as input and # enable backward compatibility of user/all/dba_arguments behavior on 19c. # ########## event='10946 trace name context forever, level 8454144' #MP ############################################################################### # # End of Release-Specific Database Initialization Parameters Section for 19c # ############################################################################### 3.2 Parameter Removal List for Oracle Database 19c If they exist, you should remove the following parameters from your database initialization parameters file for Oracle Database 19c. Note: Parameters may appear on a removal list for any of the following three reasons: They are obsolete. The default value is required and no other value may be set. To cater for certain special cases where a non-default value has to be set to meet specific needs. Currently, there is only one such case, which is described in Section 8: Using System Managed Undo (SMU). _kks_use_mutex_pin _shared_pool_reserved_min_alloc _sqlexec_progression_cost always_anti_join always_semi_join background_dump_dest core_dump_dest db_block_buffers db_cache_size db_file_multiblock_read_count drs_start enqueue_resources event="10932 trace name context level 32768" event="10933 trace name context level 512" event="10943 trace name context forever, level 2" event="10943 trace name context level 16384" event="38004 trace name context forever, level 1" exafusion_enabled exclude_seed_cdb_view global_context_pool_size hash_area_size instance_groups java_pool_size job_queue_interval large_pool_size max_enabled_roles o7_dictionary_accessibility olap_page_pool_size optimizer_adaptive_features optimizer_dynamic_sampling optimizer_features_enable optimizer_index_caching optimizer_index_cost_adj optimizer_max_permutations optimizer_mode optimizer_percent_parallel parallel_automatic_tuning parallel_instance_group parallel_degree_level parallel_io_cap_enabled parallel_server parallel_server_instances plsql_compiler_flags plsql_native_library_dir plsql_native_library_subdir_count plsql_optimize_level query_rewrite_enabled rollback_segments row_locking sort_area_size standby_archive_dest sql_trace sql_version timed_statistics undo_retention undo_suppress_errors use_indirect_data_buffers user_dump_dest utl_file_dir DBFIPS_140 Section 4: Release-Specific Database Initialization Parameters for Oracle Database 12c Release 1 4.1 Required Parameters 4.2 Parameter Removal List for Oracle Database 12c 4.1 Required Parameters The following list describes database initialization parameters required for Oracle Database 12c Release 1. These parameters should be added to the common database initialization parameters provided in Section 1, so that the final database initialization parameters file includes the common section plus the contents of this release-specific section. #################################################################### # # Oracle E-Business Suite Release 12 # Release-Specific Database Initialization Parameters for 12c Release 1 # #################################################################### ######### # # Compatibility parameter. # # Compatibility should be set to the current release. # ######### compatible = 12.1.0 #MP ######### # # o7_dictionary_accessibility parameter. # # This parameter must be set to FALSE for Oracle Database Release 12.1.0.2. # ######## o7_dictionary_accessibility = FALSE #MP ######### # # PL/SQL parameters. # # The utl_file_dir parameter must be set as: # utl_file_dir = <directory> ... # ######## utl_file_dir = /ebiz/prodr12/utl_file_dir ######### # # Private memory area parameters. # ######### olap_page_pool_size = 4194304 ######### # # Optimizer parameters. # # Release 12 uses cost based optimization. The following optimizer # parameters must be set as shown, and should not be changed. # It is recommended to disable the adaptive optimizer features: adaptive plans, # automatic re-optimization, and SQL plan directives. # # For Windows platform, 12.1.0.2.170831 (Aug 2017) Bundle Patch or later is required. # For other platforms, 12.1.0.2.171017 (Oct 2017) Bundle Patch or later is required. # # Remove optimizer_adaptive_features from pfile or spfile, and replace it with # optimizer_adaptive_plans=FALSE #MP and optimizer_adaptive_statistics=FALSE #MP # For more details, refer to MOS Doc ID 1594274.1. # ######### optimizer_adaptive_features = FALSE #MP ######### # # PGA Aggregate Limit parameter. # # PGA_AGGREGATE_LIMIT feature in 12c limits PGA memory usage. # # The default value of PGA_AGGREGATE_LIMIT is set to the greater of 2 GB, # 200% of PGA_AGGREGATE_TARGET, and 3 MB times the PROCESSES parameter. # It will not exceed 120% of the physical memory size minus the total SGA size. # # PGA_AGGREGATE_LIMIT cannot be set below its default value. If a value of 0 is specified, # it means there is no limit to the aggregate PGA memory consumed by the instance. # If total PGA memory usage is over PGA_AGGREGATE_LIMIT value. The sessions or processes # that are consuming the most untunable PGA memory will be terminated. # # Recommended value for PGA_AGGREGATE_LIMIT is 0. # ########## pga_aggregate_limit = 0 #MP ######### # # Temp Undo Enabled parameter. # # TEMP_UNDO_ENABLED helps to reduce the amount of redo caused by DML on global temporary tables. # Setting to TRUE may cause serious issues, such as ORA-55526, for distributed transactions (Ref. # Bug 20712819). # The recommended value for systems using distributed transactions is currently FALSE (Pending ER # 24286334). # If not using distributed transactions, TRUE will improve performance by eliminating REDO on # permanent UNDO. # ########## temp_undo_enabled = FALSE ############################################################################### # # End of Release-Specific Database Initialization Parameters Section for 12c # ############################################################################### 4.2 Parameter Removal List for Oracle Database 12c Release 1 If they exist, you should remove the following parameters from your database initialization parameters file for Oracle Database 12c Release 1. Note: Parameters may appear on a removal list for any of the following three reasons: They are obsolete. The default value is required and no other value may be set. To cater for certain special cases where a non-default value has to be set to meet specific needs. Currently, there is only one such case, which is described in Section 8: Using System Managed Undo (SMU). _kks_use_mutex_pin _shared_pool_reserved_min_alloc _sqlexec_progression_cost always_anti_join always_semi_join background_dump_dest core_dump_dest db_block_buffers db_cache_size db_file_multiblock_read_count drs_start enqueue_resources event="10932 trace name context level 32768" event="10933 trace name context level 512" event="10943 trace name context forever, level 2" event="10943 trace name context level 16384" event="38004 trace name context forever, level 1" hash_area_size instance_groups java_pool_size job_queue_interval large_pool_size max_enabled_roles optimizer_dynamic_sampling optimizer_features_enable optimizer_index_caching optimizer_index_cost_adj optimizer_max_permutations optimizer_mode optimizer_percent_parallel parallel_instance_group plsql_compiler_flags plsql_native_library_dir plsql_native_library_subdir_count plsql_optimize_level query_rewrite_enabled rollback_segments row_locking sort_area_size sql_trace sql_version timed_statistics undo_retention undo_suppress_errors user_dump_dest DBFIPS_140 Section 5: Release-Specific Database Initialization Parameters for Oracle Database 11g Release 2 5.1 Required Parameters 5.2 Parameter Removal List for Oracle Database 11g Release 2 5.1 Required Parameters The following list describes database initialization parameters required for Oracle Database 11g Release 2. These parameters should be added to the common database initialization parameters provided in Section 1, so that the final database initialization parameters file includes the common section plus the contents of this release-specific section. #################################################################### # # Oracle E-Business Suite Release 12 # Release-Specific Database Initialization Parameters for 11gR2 # #################################################################### ######### # # Compatible parameter. # # Compatibility should be set to the current release. # ######### compatible = 11.2.0 #MP ######### # # o7_dictionary_accessibility parameter. # # This parameter must be set to FALSE for Oracle Database Release 11.2.0.4. # ######## o7_dictionary_accessibility = FALSE #MP ######### # # PL/SQL parameters. # # The utl_file_dir parameter must be set as: # utl_file_dir = <directory> ... # ######## utl_file_dir = /ebiz/prodr12/utl_file_dir ######### # # Private memory area parameters. # ######### olap_page_pool_size = 4194304 ############################################################################### # # End of Release-Specific Database Initialization Parameters Section for 11gR2 # ############################################################################### 5.2 Parameter Removal List for Oracle Database 11g Release 2 If they exist, you should remove the following parameters from your database initialization parameters file for Oracle Database 11g Release 2 (11.2.X). Note: Parameters may appear on a removal list for any of the following three reasons: They are obsolete. The default value is required and no other value may be set. To cater for certain special cases where a non-default value has to be set to meet specific needs. Currently, there is only one such case, which is described in Section 8: Using System Managed Undo (SMU). _kks_use_mutex_pin _shared_pool_reserved_min_alloc _sqlexec_progression_cost always_anti_join always_semi_join background_dump_dest core_dump_dest db_block_buffers db_cache_size db_file_multiblock_read_count drs_start enqueue_resources event="10932 trace name context level 32768" event="10933 trace name context level 512" event="10943 trace name context forever, level 2" event="10943 trace name context level 16384" event="38004 trace name context forever, level 1" hash_area_size instance_groups java_pool_size job_queue_interval large_pool_size max_enabled_roles optimizer_dynamic_sampling optimizer_features_enable optimizer_index_caching optimizer_index_cost_adj optimizer_max_permutations optimizer_mode optimizer_percent_parallel parallel_instance_group plsql_compiler_flags plsql_native_library_dir plsql_native_library_subdir_count plsql_optimize_level query_rewrite_enabled rollback_segments row_locking sort_area_size sql_trace sql_version timed_statistics undo_retention undo_suppress_errors user_dump_dest DBFIPS_140 Section 6: Additional Database Initialization Parameters For Oracle E-Business Suite Release 12.2 The parameters in this section only apply to Oracle E-Business Suite Release 12.2 on Oracle Database 11g Release 2 (11.2.0.4) and later, and should be used in addition to the parameters in the other relevant sections of this document. ######### # # Recyclebin parameter. # # The database recyclebin must be turned off to allow the cleanup phase of the # online patching cycle to be performed without having to connect as SYS. # # This feature may still be used at other times. # ######### recyclebin = off #MP ######### #  # Service Names parameter. # # To support online patching, Oracle E-Business Suite Release 12.2 introduces a # new database service. # # The service_names parameter specifies one or more names by which clients can # connect to an instance. The instance registers its service names with the # listener. When a client requests a service, the listener determines which # instances offer the requested service and then routes the client to the most # appropriate instance. # # On codelevels lower than AD-TXK Delta 9, the service name is always 'ebs_patch'. # From the AD-TXK Delta 9 codelevel, the service name is defined by the value # of the context variable 's_patch_service_name'. # # For Oracle AI Database 26ai or Oracle Database 19c with a single tenant (1 CDB : 1 PDB) # configuration, the value for the service_names parameter is auto-populated # when the CDB is created. You should not modify this parameter manually. # ######### service_names=%s_dbSid%, <s_patch_service_name or ebs_patch> # Based on AD/TXK Code level ######### #  # Local Listener parameter. # # The local_listener setting is part of the AutoConfig templates, and required # for listener registration of any non-default (1521) ports. # # For Oracle AI Database 26ai or Oracle Database 19c with a single tenant (1 CDB : 1 PDB) # configuration, set the parameter local_listener value as per the instructions in the # appropriate My Oracle Support knowledge document: # Document 2962871.1, Interoperability Notes: Oracle E-Business Suite Release 12.2 with Oracle AI Database 26ai # Document 2552181.1, Interoperability Notes: Oracle E-Business Suite Release 12.2 with Oracle Database 19c # ######### local_listener=%s_dbSid%_LOCAL ######### # # Result Cache parameter. # # For Oracle E-Business Suite 12.2.x, set the result_cache_max_size parameter to make optimal # use of result cache memory. # # The value of result_cache_max_size is the maximum amount of memory taken from the shared pool, # so it should be set in consideration with the setting of the shared_pool_size parameter. # # For higher concurrency environments that have more than 2000 active Oracle E-Business Suite # user accounts, a setting of 600M is recommended. # ######### result_cache_max_size = 600M Section 7: Exadata-Specific Database Initialization Parameters The Exadata-specific parameters listed in this section only apply to Oracle E-Business Suite Release 12.2 on Oracle Database 19c and later, and must be used in addition to the parameters in the other relevant sections of this document. ######### # # Real-Time Statistics for On-Premise Exadata and Exadata Cloud Service environments. # # If you are using Oracle AI Database 26ai (23.1.x-23.x.x) or Oracle Database 19c (19.1.x-19.9.x) # on Engineered Systems such as Exadata or ExaCS, ensure the following parameters are set to FALSE. # This will disable Real Time Statistics, and stop gathering optimizer realtime statistics # for conventional DMLs. # ######### _optimizer_gather_stats_on_conventional_dml = FALSE #MP _optimizer_use_stats_on_conventional_dml = FALSE #MP # The parameter optimizer_real_time_statistics is an Oracle Database 21c parameter that has # been backported to Oracle Database 19c RU 10 (19.10.x). If you are using Oracle Database # Release 19.10.x or higher on an Engineered System such as Exadata or ExaCS, ensure the # parameter is disabled (the default) by setting it to FALSE. optimizer_real_time_statistics = FALSE #MP ######### #  # Linux HugePages and USE_LARGE_PAGES parameter. # # HugePages must be preallocated before instance startup. # For details, refer to point 11 in the "Important Considerations" section, # titled "Linux HugePages and use of the USE_LARGE_PAGES Parameter". # Starting from Oracle AI Database 26ai (RU 23.8) and Oracle Database 19c (RU 19.27) on Exadata, # the default and mandatory setting is ONLY. # ######### use_large_pages = ONLY Section 8: Using System Managed Undo (SMU) As mentioned for the parameters related to system undo, the database releases certified for use with Oracle E-Business Suite Release 12 only support the use of system managed undo (SMU). SMU is more efficient than traditional rollback segments and reduces the possibility of "ORA-1555: Snapshot too old" errors. Note the following points about the undo_retention parameter: The values given for undo_retention are for guidance only. This parameter should be adjusted according to the elapse times of the concurrent jobs, and corresponding commit windows. There is no need to specify a value for undo_retention on Oracle Ai Database 26ai, Oracle Database releases 19c, 12c, or 11g systems, because it is set automatically as part of automatic undo tuning. Setting this parameter to a value higher than 900 (the default) is recommended if you experience "ORA-1555: Snapshot too old" errors. Automatic undo is not supported for LOBS. Section 9: Temporary Tablespace Setup It is recommended that the temporary tablespace for Oracle E-Business Suite users be created using locally managed temp files with uniform extent sizes of 128K. The 128K extent size is recommended because numerous modules, such as Pricing and Planning, make extensive use of global temporary tables which also reside in the temporary tablespace. Since each user instantiates a temporary segment for these tables, large extent sizes may result in space allocation failures. The following is an example of creating a locally managed temporary tablespace with temp files: SQL> drop tablespace temp; SQL> create temporary tablespace temp tempfile '/d2/prodr12/dbf/temp01.dbf' size 2000M reuse extent management local uniform size 128K; Section 10: Database Initialization Parameter Sizing This section provides sizing recommendations based on the active Oracle E-Business Suite user counts. General Notes on Sizing In the following table, "Development or Test Instance" refers to a small instance used only for development or testing, with no more than 10 users. The range of user counts provided above refers to active Oracle E-Business Suite users, not total or named users. For example, if you plan to support a maximum of 500 active Oracle E-Business Suite users, then you should use the sizing as per the range 101-500 users. The parameter values provided in this document reflect a small instance configuration, and you should adjust the relevant parameters based on the Oracle E-Business Suite user counts as listed in the table. Use the following table to size the relevant parameters: Table 1: Parameter Sizing Recommendations Parameter Name Development or Test Instance 11-100 Users 101-500 Users 501-1000 Users 1001-2000 Users processes 200 200 800 1200 2500 sessions 400 400 1600 2400 5000 sga_target 1 2G 2G 2G 3G 14G shared_pool_size 400M 600M 800M 1000M 2000M shared_pool_reserved_size 40M 60M 80M 100M 100M pga_aggregate_target 1G 2G 4G 10G 20G Total Memory Required 2 ~ 3 GB ~ 4 GB ~ 6 GB ~ 13 GB ~ 34 GB Table 1 Footnotes 1 For the sga_target parameter, the following notes apply: The parameter sga_target should be used on Oracle AI Database 26ai, Oracle Database releases 19c, 12c, or 11g systems. Also, it is not necessary to set the parameter undo_retention for Oracle AI Database 26ai, Oracle Database releases 19c, 12c, or 11g systems, since undo retention is set automatically as part of automatic undo tuning. Enabling the Automatic Memory Management (AMM) feature is supported in Oracle E-Business Suite, and has been found to be useful in scenarios where memory is limited, as it will dynamically adjust the SGA and PGA pool sizes. AMM is enabled by using the memory_target and memory_max_target initialization parameters. MEMORY_TARGET specifies the system-wide sharable memory for Oracle to use when dynamically controlling the SGA and PGA as workloads change. The memory_max_target parameter specifies the maximum size that memory_target may take. AMM has proven useful for small to mid-range systems as it simplifies both the configuration and management. However, many customers with large production systems have experienced better performance with manually sized pools (or large minimum values for the pools). On Linux, HugePages has resulted in improved performance; however, this configuration is not compatible with AMM. For large mission-critical applications systems, it is advisable to set sga_target with a minimum fixed value for shared_pool_size and pga_aggregate_target. 2 The total memory required refers to the amount of memory required for the database instance and associated memory, including the SGA and the PGA. You should ensure that your system has sufficient available memory in order to support the values provided above. The values provided above should be adjusted based on available memory, to prevent paging and swapping. Change Log

Database Initialization Parameters for Oracle E-Business Suite Release 12 (Doc ID 396009.1)