Evolution of init.ora parameters

Hi Gurus,
Can someone name the milestones (or important) in the evolution of parameters in init.ora file. I knew for every release certain parameters are relegated, or replaced and few are introduced as new and ofcourse for some the default values are changed. I want to understand the most important changes Oracle has come up at 8i, 9i, 10g and 11g releases.
Regards,
Elvis

For your reference on Oracle Initialization Parameters.
Oracle 7 - List of Initialization Parameters
http://download.oracle.com/docs/cd/A57673_01/DOC/server/doc/SAD73/ch2.htm#Parameters
Oracle 8i - List of Initialization Parameters
http://www.oracle.com/pls/tahiti/tahiti.initora
Oracle 9i - List of Initialization Parameters
http://www.oracle.com/pls/db92/db92.initora?remark=homepage
Oracle 10g - List of Initialization Parameters
http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams.htm#g1195420
Oracle 11g - List of Initialization Parameters
http://download.oracle.com/docs/cd/B28359_01/server.111/b28320/initparams.htm#g1195420
Oracle Metalink Notes on Initialization Parameters
Note ID: 268581.1 - Obsolete / Deprecated Initialization Parameters in 10G
Oracle EBS Applications:
Note ID: 216205.1 - Database Initialization Parameters for Oracle Applications Release 11i
Note ID: 396009.1 - Database Initialization Parameters for Oracle Applications Release 12
Note ID: 100709.1 Subject: Top 8 init.ora Parameters Affecting Performance
Regards,
Sabdar Syed.

Similar Messages

  • Bestpractice init.ora parameters for data warehouse in 10gR2

    Hi,
    We moved our 1Tera data warehouse database to linux 64 bit , 8 cpu , 8GB memory, with ASM (non RAC).
    Could you please recommand best practice setting init.ora parameters in 10g
    DW to achive the best performace ?
    I set the following parameters:
    parallel_adaptive_multi_user=TRUE
    parallel_execution_message_size=2152
    parallel_min_server=0
    parallel_max_server=135
    parallel_threads_per_cpu=2
    db_file_multi_block_read_count=64
    pga=900m
    query_rewrite_enabled=true
    star_transformation_enabled=true
    db_block_size=32k
    sga_target=3g
    statistic_leve=typical
    undo_management=auto
    workarea_aize_policy=auto
    db_cache_advice=on
    disk_async_io=true
    2. What setting would you recommand regrading the following parameters in DW (and ASM):
    -- filesystemio_option :none | setall | directIO | asynch
    Thank You.

    You will get best practices from your production experiences and good advisors that oracle 10 has provided to you.
    http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14223/toc.htm

  • Init.ora parameters for banking application

    hi
    i would like know guidelines for setting
    init.ora parameters for database, to handle
    load of 2 million transactions per day,with
    RAC setup for high availability.
    thanks

    You will get best practices from your production experiences and good advisors that oracle 10 has provided to you.
    http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14223/toc.htm

  • Are there any init.ora parameters which can't be changed at all ?

    DB version: 11gR2
    We have the following two types of initialization parameters
    Dynamic - Which can be changed without a DB bounce (example CURSOR_SHARING)
    Static  - Which can be changed only with a DB bounce (example MEMORY_MAX_TARGET )
    Both types of init parameters mentioned above can be changed with or without a DB bounce. Are there any initialization parameters which cannot be changed at all  with or without a DB bounce?

    Max wrote:
    Oracle documentation which describes init.ora parameters is 'Oracle Database Reference 11gRelease 2'. It doesn't answer my question
    Maybe it does.
    from DB_BLOCK_SIZE
    The value for DB_BLOCK_SIZE in effect at the time you create the database determines the size of the blocks. The value must remain set to its initial value.

  • Oracle 9i vs Oracle11gR2 init.ora parameters

    Hi,
    Can you please let me know what are the added init.ora parameters in oracle11gR2 than when compared to oracle9i init.ora prams?
    Thanks
    KSG

    Hi;
    Can you please let me know what are the added init.ora parameters in oracle11gR2 than when compared to oracle9i init.ora prams?Lots of thing have been changed those 2 produtc, bacily 11g parameter perform more flexsibility.I belive its hard to define what exactly changed. Please see below links:
    9i init:
    http://www.oracle-base.com/articles/9i/PersistentInitializationParameters.php
    http://ss64.com/ora/syntax-initora.html
    http://www.scribd.com/doc/2166874/Initialization-Parameters-in-oracle-9i
    11ginit:
    http://download.oracle.com/docs/cd/B28359_01/server.111/b28310/create005.htm
    http://kevinclosson.wordpress.com/2007/08/27/oracle-database-11g-initialization-parameters-a-digest/
    Regard
    Helios

  • Init.ora parameters

    Hi,
    Which init.ora parameters are respond for write data from cache to redo logs files? It is possible to set this parameter as time or rather for cache usage?

    Dear,
    The purpose of redo generation is to ensure recoverability. This is the reason why, Oracle does not give the DBA a lot of control over redo generation. If the instance crashes, then all the changes within SGA will be lost. Oracle will then use the redo entries in the online redo files to bring the database to a consistent state.
    Best Regards,
    Francisco Munoz Alvarez
    www.oraclenz.com

  • What init.ora parameters needed for RMAN,

    Hi,
    We would like to implement RMAN at our site and like to know what are the parameters required in init.ora for using RMAN, where can I find more info regarding the tuning of these parameters ? Please reply..
    Thanks a lot in advance,
    Sreedhar

    Tammy,
    Thanks for your reply. I didn't post the exact question, let me do it again.
    I need to determine the 'large pool' size to be implemented for using RMAN. (We already have RMAN running).
    I need to know what parameters I need to set in init.ora for large_pool to work efficiently in conjunction with RMAN. How do I calculate the required size.
    I found some material on this, here, but it's confusing.
    By default LARGE POOL = 0, unless PARALLEL_AUTOMATIC_TUNING = TRUE, (in which case LP will be set automatically). Also, set LARGE_POOL_MIN_ALLOC to a non-zero value to enable a minimum allocation with LP.
    When I read document (ID 73079.1) it gets more confusing, as whether to take MULTIBLOCK-READ-COUNT value or db_file_direct_io_count into consideration.
    Any help is appreciated.
    Thanks again, Sreedhar
    null

  • Parameters in init.ora not changing in DB

    Oracle 9.0.0 Redhat 7.2
    Trying to set up utl_file_dir in the init.ora file and, although
    the entry in the init.ora looks correct (utl_file_dir=/tmp/xxx),
    the value for utl_file_dir in sqlplus (show parameters utl)
    never sees the value (ie always shows nothing). Same with other
    params in the init.ora. If I rename the init.ora file, the DB
    doesn't start, so I'm changing the correct file.
    Maybe Oracle is finding something it doesn't like in the
    init.ora file and aborting reading the file??
    Is there a way to see what oracle's doing with the init.ora file
    as it loads?
    Thx Martin ([email protected])

    There is a new feature with 9i that you can change init.ora
    parameters without bouncing the instance, these parameters are
    store in a file (spfile).
    See the documentation about this feature.
    Thomas

  • What are the recomended init.ora params?

    Hi,
    I am following the Doc ID: 298877.1 of MetaLink.
    Let we have
    50 captures processes on Central Servers which are capturing the "ABC" Schema (DDL's,DML's),
    50 propagations (Each capture process has it's own Propagation queue),
    50 apply (All 50 sites apply processes apply changes on central server).
    DEL Machine 2950: RAM=4GB :
    My capture process state is "Pause For Flow Control..".
    All sites and central server used same schema:
    My current setting are:(Which I selected)
    --> Compatible='10.2.0.1.0'
    --> SHARED_POOL_SIZE=140M
    --> PARALLEL_MAX_SERVERS=200
    --> JOB_QUEUE_PROCESSES=100
    --> OPEN_LINKS=30
    --> PROCESSES=500
    --> SESSIONS=70
    --> SGA_MAX_SIZE=500M
    --> STREAMS_POOL_SIZE=200M
    Can anyone help me to proper setting up the following init.ora parameters?
    --> SHARED_POOL_SIZE
    --> PARALLEL_MAX_SERVERS
    --> JOB_QUEUE_PROCESSES
    --> OPEN_LINKS
    --> PROCESSES
    --> SESSIONS
    --> SGA_MAX_SIZE
    --> STREAMS_POOL_SIZE
    Thanks,
    Faziarain
    Edited by: [email protected] on Aug 5, 2009 4:17 AM

    The recommended init parameters are clearly spelled out in the docs at http://tahiti.oracle.com and no doubt you can read them as well as we can.
    My only recommendation would be to patch to 10.2.0.4 first.
    PS: Some of the things you are asking about no one can possibly answer without knowing everything about how the system is used. For example
    the number of open database links? Are they used by anything else? How can we know. Number of session? How can we possibly know the number
    of connected sessions on your server? This is something you need to do yourself or ask your DBA to help you.

  • RMAN and init.ora

    What are init.ora parameters that controls behavior of RMAN in Oracle 10g r2. Thanks, R

    Could be the parameters that you set when you configure the backup of a database
    alter system set log_archive_format='orcl_%t_%s_%r.arc' scope=spfile;
    alter system set db_recovery_file_dest_size=800G scope=both;
    alter system set db_recovery_file_dest='+RECOVERY_1' scope=both;
    alter system set log_archive_dest_1='LOCATION=USE_DB_RECOVERY_FILE_DEST';
    - Karl Arao
    karlarao.wordpress.com
    karlarao.tiddlyspot.com

  • Recommended  init.ora values for PROD setup

    Hi All,
    -Assuming that I am using a 64-bit version of Oracle,
    -that there is nothing else running on the server,
    -that there will be no other databases on the server,
    -that I have substantially more data on disk than I have RAM,
    -and that I am using 11g. I want to setup a production database 11g. The server specs is OEL 5.6 with 12Gb Ram and a Quadcore CPU.
    There will be 200 users simultaneously accessing the database. I understand that 10g and 11g are "self-tuning".
    So in this regard do I need to still change values in the default init.ora?
    Can you give me sample PROD template of your init.ora?
    Or maybe since my RAM is 12Gb I will just set the "target SGA = 8Gb" and the database will now be good?
    Thanks,
    Yx
    Edited by: yxes2013 on 8.2.2013 16:21
    Adding Justin's assumptions

    I Thank you all :)
    You need to understand what the memory is used for. Please read the documentation on SGA and PGA components and parameters and how they impact performance.Yeah I read it already....but it does not clearly explain like what all you did here ;)
    Hmm interesting....I got lots of tips learned. So If I have 500Gb data (im sure it does not include index right?) Broken into the following:
    Table1 300Gb
    Table2 100Gb
    Table3 50Gb
    Table4 30Gb
    Table5 10Gb
    Table6 5Gb
    Others 5Gb ( comprised of hundreds of tables)
    Do I need to have my memory target SGA equal to 500Gb to attain a maximum performance? supposing memory is not a budget constraint?
    Supposing Table6 is the most frequentlly read/accessed and I want to load/cache it all in the memory so I do not need to index this table, how can I do it?
    What is the rule of thumb of PGA size against the size of the table? Maybe 20% sorting of the most accessed table?
    @Justin
    **10 sessions doing data warehouse queries will probably need more PGA than 1000 sessions doing OLTP queries.
    **I'd probably start with a MEMORY_TARGET of 10 or 11G. How about the approx. PGA size dear? :)
    @Hemant
    It is more the amount of data and some factoring for the number (volume) of changes to the data.
    The number of users matters in terms of sizing memory for server processes, and some allocation of the SHARED_POOL_SIZE, not for the DB_CACHE_SIZE component.
    If more users means more distinct SQL statements, the SHARED_POOL_SIZE usage would be greater.
    However, multiple users accessing the same version of the data will be "sharing" one buffer in memory for each block of data being accessed. It doesn't matter if 1 user is reading a block or 8 or 64 or 128 users are reading the same block -- in either case it is one buffer in memory.
    It is only if the block is frequently being changed and concurrently queried, might there be current and a few consistent versions of the buffer being maintained in the SGA.I think in 11g I do not need to set those because it is "self-tuning" right? All I need is the target SGA size. :)
    Given that I will perform a "benchmark" test/simulation on the DEV server. Is there a tool that will gather the right sizing of init.ora parameters? Can I extract it from AWR report?
    Thanks to all again,
    Yxz

  • Oracle 11g init.ora parameter settings

    Hi Friends,
    Oracle 11.2.0.1.0 on Suse Linux.
    Can you please let me know what are the things need to be followed while setting init.ora parameters for the database?
    And, can you please suggest me the best init.ora settings for the database?
    Thanks
    KSG

    Hi JL Sir,
    Thanks for your valuable guidance.
    We have finally come up with the init.ora parameters. Please review and guide me further.
    NAME VALUE
    tracefiles_public TRUE
    tracefile_identifier
    processes 100
    sessions 120
    timed_statistics TRUE
    timed_os_statistics 0
    resource_limit TRUE
    license_max_sessions 0
    license_sessions_warning 0
    cpu_count 2
    instance_groups
    event
    shared_pool_size 268435456
    sga_max_size 1075800904
    shared_pool_reserved_size 13421772
    large_pool_size 16777216
    java_pool_size 167772160
    java_soft_sessionspace_limit 0
    java_max_sessionspace_size 0
    pre_page_sga FALSE
    shared_memory_address 0
    hi_shared_memory_address 0
    use_indirect_data_buffers FALSE
    lock_sga FALSE
    spfile ?/dbs/[email protected]
    lock_name_space
    enqueue_resources 1542
    trace_enabled TRUE
    nls_language american
    nls_territory america
    nls_sort
    nls_date_language
    nls_date_format DD-MON-RR
    nls_length_semantics BYTE
    nls_nchar_conv_excp FALSE
    filesystemio_options asynch
    disk_asynch_io TRUE
    tape_asynch_io TRUE
    dbwr_io_slaves 0
    backup_tape_io_slaves FALSE
    resource_manager_plan
    cluster_interconnects
    file_mapping FALSE
    active_instance_count
    control_files /u020/oradata/mecdb/control01.ctl, /u021/oradata/mecdb/control02.ctl, /u026/or
    adata/mecdb/control03.ctl
    db_file_name_convert
    log_file_name_convert
    db_block_buffers 0
    db_block_checksum TRUE
    db_block_size 8192
    db_writer_processes 1
    db_keep_cache_size 0
    db_recycle_cache_size 0
    db_2k_cache_size 0
    db_4k_cache_size 0
    db_8k_cache_size 0
    db_16k_cache_size 0
    db_32k_cache_size 0
    db_cache_size 134217728
    buffer_pool_keep
    buffer_pool_recycle
    db_cache_advice ON
    max_commit_propagation_delay 700
    compatible 11.2.0
    remote_archive_enable true
    log_archive_start TRUE
    log_archive_dest /app/oracle/admin/mecdb/arch
    log_archive_duplex_dest
    log_archive_max_processes 2
    log_archive_min_succeed_dest 1
    standby_archive_dest ?/dbs/arch
    log_archive_trace 0
    fal_server
    fal_client
    log_archive_format mecdb_T%t_S%S.arc
    log_buffer 1048576
    log_checkpoint_interval 100000
    log_checkpoint_timeout 72000
    archive_lag_target 0
    log_parallelism 1
    db_files 1022
    db_file_multiblock_read_count 16
    read_only_open_delayed FALSE
    cluster_database FALSE
    parallel_server FALSE
    parallel_server_instances 1
    cluster_database_instances 1
    standby_file_management MANUAL
    gc_files_to_locks
    thread 0
    fast_start_io_target 0
    fast_start_mttr_target 0
    log_checkpoints_to_alert FALSE
    recovery_parallelism 0
    control_file_record_keep_time 7
    logmnr_max_persistent_sessions 1
    dml_locks 500
    row_locking always
    serializable FALSE
    replication_dependency_tracking TRUE
    instance_number 0
    transactions 132
    transactions_per_rollback_segment 5
    max_rollback_segments 30
    rollback_segments
    transaction_auditing TRUE
    undo_management AUTO
    undo_tablespace undo1
    undo_suppress_errors TRUE
    undo_retention 900
    fast_start_parallel_rollback LOW
    db_block_checking FALSE
    os_roles FALSE
    rdbms_server_dn
    max_enabled_roles 40
    remote_os_authent FALSE
    remote_os_roles FALSE
    O7_DICTIONARY_ACCESSIBILITY TRUE
    remote_login_passwordfile EXCLUSIVE
    dblink_encrypt_login FALSE
    license_max_users 0
    global_context_pool_size
    audit_sys_operations FALSE
    db_domain world
    global_names FALSE
    distributed_lock_timeout 60
    commit_point_strength 1
    instance_name mecdb
    service_names mecdb.world
    dispatchers
    mts_dispatchers
    shared_servers 0
    mts_servers 0
    max_shared_servers 20
    mts_max_servers 20
    max_dispatchers 5
    mts_max_dispatchers 5
    circuits 0
    mts_circuits 0
    shared_server_sessions 0
    mts_sessions 0
    local_listener mecdb_lsnr
    remote_listener
    mts_service mecdb
    mts_listener_address
    mts_multiple_listeners FALSE
    serial_reuse DISABLE
    cursor_space_for_time FALSE
    session_cached_cursors 0
    remote_dependencies_mode TIMESTAMP
    utl_file_dir *
    plsql_v2_compatibility FALSE
    plsql_compiler_flags INTERPRETED
    plsql_native_c_compiler
    plsql_native_linker
    plsql_native_library_dir
    plsql_native_make_utility
    plsql_native_make_file_name
    plsql_native_library_subdir_count 0
    job_queue_processes 1
    parallel_min_percent 0
    create_bitmap_area_size 8388608
    bitmap_merge_area_size 1048576
    cursor_sharing EXACT
    parallel_min_servers 0
    parallel_max_servers 5
    parallel_instance_group
    parallel_execution_message_size 2152
    hash_join_enabled TRUE
    hash_area_size 131072
    shadow_core_dump partial
    background_core_dump partial
    background_dump_dest /app/oracle/admin/mecdb/bdump
    user_dump_dest /app/oracle/admin/mecdb/udump
    max_dump_file_size 102400000
    core_dump_dest /app/oracle/admin/mecdb/cdump
    audit_file_dest /app/oracle/admin/mecdb/adump
    hpux_sched_noage 0
    oracle_trace_enable FALSE
    oracle_trace_facility_path ?/otrace/admin/fdf
    oracle_trace_collection_path ?/otrace/admin/cdf
    oracle_trace_facility_name oracled
    oracle_trace_collection_name
    oracle_trace_collection_size 5242880
    object_cache_optimal_size 102400
    object_cache_max_size_percent 10
    session_max_open_files 10
    open_links 4
    open_links_per_instance 4
    optimizer_features_enable 11.2.0
    fixed_date
    audit_trail DB
    sort_area_size 65536
    sort_area_retained_size 0
    db_name mecdb
    open_cursors 200
    ifile
    sql_trace FALSE
    os_authent_prefix ops$
    optimizer_mode CHOOSE
    sql92_security FALSE
    blank_trimming FALSE
    partition_view_enabled FALSE
    star_transformation_enabled FALSE
    parallel_adaptive_multi_user FALSE
    parallel_threads_per_cpu 2
    parallel_automatic_tuning FALSE
    optimizer_max_permutations 2000
    optimizer_index_cost_adj 100
    optimizer_index_caching 0
    query_rewrite_enabled false
    query_rewrite_integrity enforced
    sql_version NATIVE
    pga_aggregate_target 536870912
    workarea_size_policy auto
    optimizer_dynamic_sampling 1
    statistics_level TYPICAL
    aq_tm_processes 0
    hs_autoregister TRUE
    dg_broker_start FALSE
    drs_start FALSE
    dg_broker_config_file1 ?/dbs/[email protected]
    dg_broker_config_file2 ?/dbs/[email protected]
    olap_page_pool_size 33554432
    Thanks
    KSG
    Edited by: KSG on Apr 27, 2011 1:39 PM

  • Parameters in Init.ora for Materialized Views

    Fellow Experts,
    Are there any other parameters that I need to insert in the init.ora besides QUERY_REWRITE_ENABLED
    and
    QUERY_REWRITE_INTEGRITY
    once I create a materialize view ?
    Thanks.
    Ray.

    Oracle version 10.0.2 and the DDL that I'm planning to use might be simmilar to
    CREATE MATERIALIZED VIEW sales_by_month_by_state
    TABLESPACE example
    PARALLEL 4
    BUILD IMMEDIATE
    REFRESH COMPLETE
    ENABLE QUERY REWRITE
    AS SELECT t.calendar_month_desc, c.cust_state_province,
    SUM(s.amount_sold) AS sum_sales
    FROM times t, sales s, customers c
    WHERE s.time_id = t.time_id AND s.cust_id = c.cust_id
    GROUP BY t.calendar_month_desc, c.cust_state_province;

  • Unable to find the utl_file_directory option in init.ora

    Hi all these are the contents of init.ora file in nacedell server.i did'nt find any thing as utl_file_directory to update with my directory created through sql*plus using
    command
    create directory dir as 'c:\dir';
    here are the contents of init.ora file
    cat init.ora command is giving contents as
    # $Header: init.ora 06-aug-98.10:24:40 atsukerm Exp $
    # Copyright (c) 1991, 1997, 1998 by Oracle Corporation
    # NAME
    # init.ora
    # FUNCTION
    # NOTES
    # MODIFIED
    # atsukerm 08/06/98 - fix for 8.1.
    # hpiao 06/05/97 - fix for 803
    # glavash 05/12/97 - add oracle_trace_enable comment
    # hpiao 04/22/97 - remove ifile=, events=, etc.
    # alingelb 09/19/94 - remove vms-specific stuff
    # dpawson 07/07/93 - add more comments regarded archive start
    # maporter 10/29/92 - Add vms_sga_use_gblpagfile=TRUE
    # jloaiza 03/07/92 - change ALPHA to BETA
    # danderso 02/26/92 - change db_block_cache_protect to dbblock_cache_p
    # ghallmar 02/03/92 - db_directory -> db_domain
    # maporter 01/12/92 - merge changes from branch 1.8.308.1
    # maporter 12/21/91 - bug 76493: Add control_files parameter
    # wbridge 12/03/91 - use of %c in archive format is discouraged
    # ghallmar 12/02/91 - add global_names=true, db_directory=us.acme.com
    # thayes 11/27/91 - Change default for cache_clone
    # jloaiza 08/13/91 - merge changes from branch 1.7.100.1
    # jloaiza 07/31/91 - add debug stuff
    # rlim 04/29/91 - removal of char_is_varchar2
    # Bridge 03/12/91 - log_allocation no longer exists
    # Wijaya 02/05/91 - remove obsolete parameters
    # Example INIT.ORA file
    # This file is provided by Oracle Corporation to help you customize
    # your RDBMS installation for your site. Important system parameters
    # are discussed, and example settings given.
    # Some parameter settings are generic to any size installation.
    # For parameters that require different values in different size
    # installations, three scenarios have been provided: SMALL, MEDIUM
    # and LARGE. Any parameter that needs to be tuned according to
    # installation size will have three settings, each one commented
    # according to installation size.
    # Use the following table to approximate the SGA size needed for the
    # three scenarious provided in this file:
    # -------Installation/Database Size------
    # SMALL MEDIUM LARGE
    # Block 2K 4500K 6800K 17000K
    # Size 4K 5500K 8800K 21000K
    # To set up a database that multiple instances will be using, place
    # all instance-specific parameters in one file, and then have all
    # of these files point to a master file using the IFILE command.
    # This way, when you change a public
    # parameter, it will automatically change on all instances. This is
    # necessary, since all instances must run with the same value for many
    # parameters. For example, if you choose to use private rollback segments,
    # these must be specified in different files, but since all gc_*
    # parameters must be the same on all instances, they should be in one file.
    # INSTRUCTIONS: Edit this file and the other INIT files it calls for
    # your site, either by using the values provided here or by providing
    # your own. Then place an IFILE= line into each instance-specific
    # INIT file that points at this file.
    # NOTE: Parameter values suggested in this file are based on conservative
    # estimates for computer memory availability. You should adjust values upward
    # for modern machines.
    # You may also consider using Database Configuration Assistant tool (DBCA)
    # to create INIT file and to size your initial set of tablespaces based
    # on the user input.
    # replace DEFAULT with your database name
    db_name=DEFAULT
    db_files = 80 # SMALL
    # db_files = 400 # MEDIUM
    # db_files = 1500 # LARGE
    db_file_multiblock_read_count = 8 # SMALL
    # db_file_multiblock_read_count = 16 # MEDIUM
    # db_file_multiblock_read_count = 32 # LARGE
    db_block_buffers = 100 # SMALL
    # db_block_buffers = 550 # MEDIUM
    # db_block_buffers = 3200 # LARGE
    shared_pool_size = 3500000 # SMALL
    # shared_pool_size = 5000000 # MEDIUM
    # shared_pool_size = 9000000 # LARGE
    log_checkpoint_interval = 10000
    processes = 50 # SMALL
    # processes = 100 # MEDIUM
    # processes = 200 # LARGE
    parallel_max_servers = 5 # SMALL
    # parallel_max_servers = 4 x (number of CPUs) # MEDIUM
    # parallel_max_servers = 4 x (number of CPUs) # LARGE
    log_buffer = 32768 # SMALL
    # log_buffer = 32768 # MEDIUM
    # log_buffer = 163840 # LARGE
    # audit_trail = true # if you want auditing
    # timed_statistics = true # if you want timed statistics
    max_dump_file_size = 10240 # limit trace file size to 5 Meg each
    # Uncommenting the line below will cause automatic archiving if archiving has
    # been enabled using ALTER DATABASE ARCHIVELOG.
    # log_archive_start = true
    # log_archive_dest = disk$rdbms:[oracle.archive]
    # log_archive_format = "T%TS%S.ARC"
    # If using private rollback segments, place lines of the following
    # form in each of your instance-specific init.ora files:
    # rollback_segments = (name1, name2)
    # If using public rollback segments, define how many
    # rollback segments each instance will pick up, using the formula
    # # of rollback segments = transactions / transactions_per_rollback_segment
    # In this example each instance will grab 40/5 = 8:
    # transactions = 40
    # transactions_per_rollback_segment = 5
    # Global Naming -- enforce that a dblink has same name as the db it connects to
    global_names = TRUE
    # Edit and uncomment the following line to provide the suffix that will be
    # appended to the db_name parameter (separated with a dot) and stored as the
    # global database name when a database is created. If your site uses
    # Internet Domain names for e-mail, then the part of your e-mail address after
    # the '@' is a good candidate for this parameter value.
    # db_domain = us.acme.com # global database name is db_name.db_domain
    # FOR DEVELOPMENT ONLY, ALWAYS TRY TO USE SYSTEM BACKING STORE
    # vms_sga_use_gblpagfil = TRUE
    # FOR BETA RELEASE ONLY. Enable debugging modes. Note that these can
    # adversely affect performance. On some non-VMS ports the db_block_cache_*
    # debugging modes have a severe effect on performance.
    #_db_block_cache_protect = true # memory protect buffers
    #event = "10210 trace name context forever, level 2" # data block checking
    #event = "10211 trace name context forever, level 2" # index block checking
    #event = "10235 trace name context forever, level 1" # memory heap checking
    #event = "10049 trace name context forever, level 2" # memory protect cursors
    # define parallel server (multi-instance) parameters
    #ifile = ora_system:initps.ora
    # define two control files by default
    control_files = (ora_control1, ora_control2)
    # Uncomment the following line if you wish to enable the Oracle Trace product
    # to trace server activity. This enables scheduling of server collections
    # from the Oracle Enterprise Manager Console.
    # Also, if the oracle_trace_collection_name parameter is non-null,
    # every session will write to the named collection, as well as enabling you
    # to schedule future collections from the console.
    # oracle_trace_enable = TRUE
    # Uncomment the following line, if you want to use some of the new 8.1
    # features. Please remember that using them may require some downgrade
    # actions if you later decide to move back to 8.0.
    #compatible = 8.1.0
    $

    There are strange things in the file you posted, are you sure that's your init.ora ? where did you find it ?
    Moreover, you use "cat" to list the file, but you name "c:\dir" the directory : what is your OS ?
    Furthermore, if you use directories, then you don't need to set utl_file_dir in init.ora, and directories don't show up within parameters, you can see them by
    SQL> select * from all_directories;

  • How to establish a single init.ora file for 3 node RAC under ASM

    All,
    Our environment is a combination of several different memory sized SUN machines (V880, V490 & 250R).
    Setting up a single init.ora file that encompasses each of the nodes memory into the SGA sizing is our desired setup.
    Though we have established the file, the question is getting each NODE on the RAC to use that single parameter
    file to start its database instead of taking the default init.ora file in the default (asm/dbs) directory.
    As we have performed fail-over testing, upon the restart of instances they have restarted with wrong memory
    definitions that have hung the nodes when it took more memory then what was available and swap space began
    to grow.
    Steps to configure and enable this process is what I am looking for.
    Thanks
    Gerry

    Gerry,
    Here's what we do. Not sure if it is relevant to your situation ...
    (on each node)
    $ cat $ORACLE_HOME/dbs/initrac11d1.ora
    SPFILE='+DATA/rac11d/spfilerac11d.ora'
    (in ASM)
    $ asmcmd
    ASMCMD> ls -la +data/rac11d
    Type Redund Striped Time Sys Name
    Y CONTROLFILE/
    Y DATAFILE/
    Y ONLINELOG/
    Y PARAMETERFILE/
    Y TEMPFILE/
    N spfilerac11d.ora => +DATA/RAC11D/PARAMETERFILE/spfile.267.685170285
    The spfile has all parameters, qualified by node where applicable. For example :
    $ sqlplus / as sysdba
    SQL*Plus: Release 11.1.0.7.0 - Production on Wed May 6 19:00:45 2009
    Copyright (c) 1982, 2008, Oracle. All rights reserved.
    Connected to:
    Oracle Database 11g Release 11.1.0.7.0 - 64bit Production
    With the Real Application Clusters option
    SQL> create pfile='/tmp/sb.ora' from spfile;
    File created.
    SQL> Disconnected from Oracle Database 11g Release 11.1.0.7.0 - 64bit Production
    With the Real Application Clusters option
    $ cat /tmp/sb.ora
    *.archive_lag_target=1800
    *.audit_file_dest='/var/oracle/admin/rac11d/adump'
    rac11d1.dispatchers='(address=(protocol=tcp)(host=msdbc11-vip)(port=64000))'
    rac11d2.dispatchers='(address=(protocol=tcp)(host=msdbc12-vip)(port=64000))'
    *.global_names=TRUE
    rac11d1.instance_number=1
    rac11d2.instance_number=2
    rac11d1.undo_tablespace='UNDOTBS1'
    rac11d2.undo_tablespace='UNDOTBS2'
    Hope this helps,
    Steve

Maybe you are looking for