INIT.ORA Parameters for R12

##############################################################################

#

# 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 8K. 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_trig_enabled

# 

# 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

#########

# 

# o7_dictionary_accessibility parameter

#

# This parameter must be set to FALSE for Oracle E-Business Suite Release 12.

#

########

o7_dictionary_accessibility = FALSE #MP

#########

#

# NLS and character set parameters

# 

# Some NLS parameter values are marked as being mandatory 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_date_format = DD-MON-RR #MP

nls_numeric_characters = ".,"

nls_sort = binary #MP

nls_comp = binary #MP

nls_length_semantics = BYTE #MP

#########

# 

# Multi-Threaded Server (MTS) parameters

# 

# Most Oracle E-Business Suite customers do not need to use MTS,

# and the default configuration disables MTS.

# 

# If MTS is used, it can have a dramatic effect on the SGA, as

# session memory, including sort and cursor areas, resides in the

# SGA. 

# 

#########

#########

# 

# 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.

#

#########

# audit_trail = TRUE # Uncomment if you want to enable audit_trail.

########

# 

# Dump parameters

# 

# The main dump parameters specify the location of the trace and core

# files, and will normally point to the appropriate trace directories.

# 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.)

# 

########

user_dump_dest = /ebiz/prodr12/udump

background_dump_dest = /ebiz/prodr12/bdump

core_dump_dest = /ebiz/prodr12/cdump

max_dump_file_size = 20480 #Limit default trace file size to 10 MB.

########

#

# Timed statistics

#

# On most platforms, enabling timed statistics has minimal effect

# on performance. It can be enabled or disabled dynamically at

# both system and session level.

#

# Timed statistics is required for use of SQL Trace and Statspack.

#

########

#

timed_statistics = TRUE

########

# Trace file accessibility parameter 

# 

# As the database machine should be in a secure environment,

# setting this parameter to TRUE is recommended in order to

# facilitate 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 = TRUE

#########

#

# 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 10g 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.

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%).

# 

########

shared_pool_size = 600M

shared_pool_reserved_size = 60M

_shared_pool_reserved_min_alloc = 4100

########

#

# cursor_space_for_time parameter

# 

# Cursor space for time is an optimization strategy that

# results in holding pins on cursors and their associated

# frames/buffers for longer periods of time. The pins are held

# until the cursor is closed, instead of at the end-of-fetch

# (normal behavior). This reduces library cache pin traffic,

# which reduces library cache latch gets. Setting cursor space 

# for time to TRUE can be useful for large Oracle E-Business

# Suite environments, where library cache latch contention

# (specifically due to pin gets) can be a performance issue. 

# 

# Cursor space for time requires at least a 50% increase in the

# size of the shared pool because of the frames/buffers. If AWR

# or Statspack reports show that the waits for library cache latch

# gets are significant, and the latch gets are due to pin

# requests, then cursor space for time can be used to improve

# performance.

# 

# It is important to note that library cache latch contention can

# be caused by numerous different factors, including the use of

# non-sharable SQL (i.e. literals), lack of space, frequent

# loads/unloads, invalidation, patching, gathering statistics

# frequently and during peak periods, and pin requests.

# Cursor space for time is designed to optimize the pin requests

# only, and will not reduce latch contention for other issues.

#

########

# cursor_space_for_time = FALSE # Disabled by default.

#########

# 

# PL/SQL parameters

# 

# The utl_file_dir parameter must be set as:

# utl_file_dir = <directory> ...

# 

########

utl_file_dir = /ebiz/prodr12/utl_file_dir

########

# 

# 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.

# 

# Starting from 10gR1, 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 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 (optionally,

# multiple destinations in 10gR2 or 11g) may be specified.

# 

########

LOG_ARCHIVE_DEST_1 = 'LOCATION=/disk1/arc' 

LOG_ARCHIVE_DEST_2 = 'SERVICE=standby1'

########

# 

# 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. 

# 

########

parallel_max_servers = 8 # Max. value should be 2 x no. of CPUs.

parallel_min_servers = 0

########

# 

# 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

_sqlexec_progression_cost = 2147483647 #MP

#########

# 

# Oracle Real Application Clusters (Oracle RAC) 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

olap_page_pool_size = 4194304

###############################################################################

#

# End of Common Database Initialization Parameters Section 

#

###############################################################################

#############################################################################

# 

# Oracle E-Business Suite Release 12

# Release-Specific Database Initialization Parameters for 10gR2 

# 

#############################################################################

#########

# 

# Compatibility parameter

# 

# Compatibility should be set to the current release.

# 

##########

compatible = 10.2.0 #MP

#########

#

# System-managed undo parameters 

#

# Oracle E-Business Suite Release 12 requires the use of system managed undo.

# This is much more efficient than rollback segments, and reduces the chances

# of snapshot too old errors. In addition, it is much easier to manage and

# administer system managed undo than manually managing rollback segments.

#

########

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 Database 10g-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.

# 

#########

plsql_optimize_level = 2 #MP

plsql_code_type = native

plsql_native_library_dir = /ebiz/prodr12/plsql_nativelib

plsql_native_library_subdir_count = 149

#########

#

# Other parameters

#

# _kks_use_mutex_pin

#

# 10gR2 facilitates the use of mutexes to lock resources in a lightweight

# fashion with higher granularity.

#

# On the HP-UX (PA-RISC) platform only, this parameter must be set to FALSE if using 10gR2.

#

#########

_kks_use_mutex_pin=FALSE # Set to FALSE on HP-UX (PA-RISC) only; otherwise, remove this parameter.

###############################################################################

#

# End of Release-Specific Database Initialization Parameters Section for 10gR2

#

###############################################################################

_always_anti_join

_always_semi_join

_complex_view_merging

_index_join_enabled

_kks_use_mutex_pin # Unless using HP-UX (PA-RISC) - see "Other parameters" section above.

_new_initial_join_orders

_optimizer_cost_based_transformation

_optimizer_cost_model

_optimizer_mode_force

_optimizer_undo_changes

_or_expand_nvl_predicate

_ordered_nested_loop

_push_join_predicate

_push_join_union_view

_shared_pool_reserved_min_alloc

_sortmerge_inequality_join_off

_table_scan_cost_plus_one

_unnest_subquery

_use_column_stats_for_function

always_anti_join

always_semi_join

db_block_buffers

db_file_multiblock_read_count

db_cache_size

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

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

plsql_compiler_flags

query_rewrite_enabled

row_locking

sort_area_size

undo_retention

undo_suppress_errors

####################################################################

#

# Oracle E-Business Suite Release 12

# Release-Specific Database Initialization Parameters for 11gR1

#

####################################################################

#########

#

# Compatible

# 

# Set compatibility to the current release.

#

#########

compatible = 11.1.0

#######

#

# Diagnostic Parameters

#

# As of Oracle Database 11g Release 1, 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 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

# 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 Database 10g 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 in 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.

#########

#

# Optimizer Parameters

#

# Release 12 uses the Cost Based Optimizer (CBO). The following optimizer

# parameters must be set as shown, and should not be changed.

#

#########

_optimizer_autostats_job=FALSE #MP Turn off automatic statistics.

#########

# 

# Database Password Case Sensitivity

# 

# The default for Oracle E-Business Suite databases is FALSE i.e. passwords are case-insensitive

# 

# Oracle E-Business Suite now supports Oracle Database 11g case-sensitive database passwords

# This feature is available on E-Business Suite Rel 12.1.1 or higher

# To enable this feature apply patch 12964564 and set SEC_CASE_SENSITIVE_LOGON to TRUE

#

##########

sec_case_sensitive_logon = FALSE

###############################################################################

#

# End of Release-Specific Database Initialization Parameters Section for 11gR1

#

###############################################################################

_always_anti_join

_always_semi_join

_complex_view_merging

_index_join_enabled

_kks_use_mutex_pin

_new_initial_join_orders

_optimizer_cost_based_transformation

_optimizer_cost_model

_optimizer_mode_force

_optimizer_undo_changes

_or_expand_nvl_predicate

_ordered_nested_loop

_push_join_predicate

_push_join_union_view

_shared_pool_reserved_min_alloc

_sortmerge_inequality_join_off

_sqlexec_progression_cost

_table_scan_cost_plus_one

_unnest_subquery

_use_column_stats_for_function

always_anti_join

always_semi_join

background_dump_dest

core_dump_dest

db_block_buffers

db_cache_size

db_file_multiblock_read_count

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

java_pool_size

job_queue_interval

large_pool_size

max_enabled_roles

nls_language

optimizer_dynamic_sampling

optimizer_features_enable

optimizer_index_caching

optimizer_index_cost_adj

optimizer_max_permutations

optimizer_mode

optimizer_percent_parallel

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

timed_statistics

undo_retention

undo_suppress_errors

user_dump_dest

####################################################################

#

# Oracle E-Business Suite Release 12

# Release-Specific Database Initialization Parameters for 11gR2

#

####################################################################

#########

#

# Compatible

# 

# Compatibility should be set to the current release.

#

#########

compatible = 11.2.0

#######

#

# Diagnostic Parameters

#

# As of Oracle Database 11g Release 1, 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

#########

#

# 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 Database 10g 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 in 11g, the parameters plsql_native_library_dir and

# plsql_native_library_subdir_count have no effect and are 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.

#########

#

# Optimizer Parameters

#

# Release 12 uses cost based optimization. The following optimizer

# parameters must be set as shown, and should not be changed.

#

#########

_optimizer_autostats_job=FALSE #MP Turn off automatic statistics.

#########

# 

# Parallel Execution and 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, EBS 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 RAC environments.

#

#########

parallel_force_local=TRUE #MP

#########

# 

# Database Password Case Sensitivity

# 

# The default for Oracle E-Business Suite databases is FALSE i.e. passwords are case-insensitive

# 

# Oracle E-Business Suite now supports Oracle Database 11g case-sensitive database passwords

# This feature is available on E-Business Suite Rel 12.1.1 or higher

# To enable this feature apply patch 12964564 and set SEC_CASE_SENSITIVE_LOGON to TRUE

#

##########

sec_case_sensitive_logon = FALSE

###############################################################################

#

# End of Release-Specific Database Initialization Parameters Section for 11gR2

#

###############################################################################

_always_anti_join

_always_semi_join

_complex_view_merging

_index_join_enabled

_kks_use_mutex_pin

_new_initial_join_orders

_optimizer_cost_based_transformation

_optimizer_cost_model

_optimizer_mode_force

_optimizer_undo_changes

_or_expand_nvl_predicate

_ordered_nested_loop

_push_join_predicate

_push_join_union_view

_shared_pool_reserved_min_alloc

_sortmerge_inequality_join_off

_sqlexec_progression_cost

_table_scan_cost_plus_one

_unnest_subquery

_use_column_stats_for_function

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

java_pool_size

job_queue_interval

large_pool_size

max_enabled_roles

nls_language

optimizer_dynamic_sampling

optimizer_features_enable

optimizer_index_caching

optimizer_index_cost_adj

optimizer_max_permutations

optimizer_mode

optimizer_percent_parallel

parallel_instance_group

instance_groups

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

SQL>drop tablespace temp;

SQL>create temporary tablespace temp

tempfile '/d2/prodr12/dbf/temp01.dbf' size 2000M reuse

extent management local

uniform size 128K;