DBAsupport.com Forums - Powered by vBulletin
Results 1 to 4 of 4

Thread: Performance Problem

  1. #1
    Join Date
    Jan 2007
    Posts
    9

    Performance Problem

    We have Two databases which resides on two diff systems and the configuartion of the systems are:

    1St System:
    Xeon(TM) CPU :3 GHZ
    TOTAL RAM:2GB
    AVAILABLE RAM:34382
    Total System Global Area 1180854300 bytes
    Fixed Size 75804 bytes
    Variable Size 310693888 bytes
    Database Buffers 870006784 bytes
    Redo Buffers 77824 bytes

    2nd System:
    Xeon(TM) :3GHz
    Total RAM:1gb
    Available RAM:228040
    Total System Global Area 1180575772 bytes
    Fixed Size 75804 bytes
    Variable Size 310415360 bytes
    Database Buffers 870006784 bytes
    Redo Buffers 77824 bytes

    Copyright (c) 1991, 2000 by Oracle Corporation
    #
    ##############################################################################
    # 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.
    #
    ###############################################################################

    db_name = "JMMS"

    instance_name = JMMS

    service_names = JMMS

    db_files = 1024

    control_files = ("G:\oracle\oradata\JMMS\control01.ctl", "G:\oracle\oradata\JMMS\control02.ctl", "G:\oracle\oradata\JMMS\control03.ctl")

    open_cursors = 300
    max_enabled_roles = 30
    db_file_multiblock_read_count = 8

    #db_block_buffers = 200340
    db_block_buffers = 106202

    #shared_pool_size = 154706380
    #shared_pool_size = 290003763

    shared_pool_size = 145001881

    large_pool_size = 614400
    java_pool_size = 0

    log_checkpoint_interval = 10000
    log_checkpoint_timeout = 1800

    processes = 250

    parallel_max_servers = 5

    #log_buffer = 327680
    log_buffer = 32768

    #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 5M 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_1 = "location=E:\oracle\oradata\JMMS\archive"
    # log_archive_format = %%ORACLE_SID%%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 = ( RBS0, RBS1, RBS2, RBS3, RBS4, RBS5, RBS6 )

    # Global Naming -- enforce that a dblink has same name as the db it connects to
    global_names = true

    # 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

    oracle_trace_collection_name = ""
    # define directories to store trace and alert files
    background_dump_dest = G:\oracle\admin\JMMS\bdump
    #Uncomment this parameter to enable resource management for your database.
    #The SYSTEM_PLAN is provided by default with the database.
    #Change the plan name if you have created your own resource plan.# resource_manager_plan = system_plan
    user_dump_dest = G:\oracle\admin\JMMS\udump

    db_block_size = 8192

    remote_login_passwordfile = exclusive

    os_authent_prefix = ""

    distributed_transactions = 10
    compatible = 8.1.0
    sort_area_size = 65536
    sort_area_retained_size = 65536

    and the following are the parameters that i set for the First System Init.ora file

    #
    # Copyright (c) 1991, 2000 by Oracle Corporation
    #
    ##############################################################################
    # 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.
    #
    ###############################################################################

    db_name = "MTFDB"

    instance_name = MTFDB

    service_names = MTFDB

    #db_files = 1024
    db_files = 25

    control_files = ("F:\oracle\oradata\MTFDB\control01.ctl", "F:\oracle\oradata\MTFDB\control02.ctl", "F:\oracle\oradata\MTFDB\control03.ctl")

    open_cursors = 300
    max_enabled_roles = 30
    db_file_multiblock_read_count = 8

    db_block_buffers = 106202

    shared_pool_size = 290003763

    large_pool_size = 614400
    java_pool_size = 0

    log_checkpoint_interval = 10000
    log_checkpoint_timeout = 1800

    processes = 350

    parallel_max_servers = 5

    log_buffer = 32768

    #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 5M 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_1 = "location=E:\oracle\oradata\MTFDB\archive"
    # log_archive_format = %%ORACLE_SID%%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 = ( RBS0, RBS1, RBS2, RBS3, RBS4, RBS5, RBS6, RBS7, RBS8, RBS9, RBS10, RBS11 )

    # Global Naming -- enforce that a dblink has same name as the db it connects to
    # global_names = true

    # 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

    oracle_trace_collection_name = ""
    # define directories to store trace and alert files
    background_dump_dest = F:\oracle\admin\MTFDB\bdump
    #Uncomment this parameter to enable resource management for your database.
    #The SYSTEM_PLAN is provided by default with the database.
    #Change the plan name if you have created your own resource plan.# resource_manager_plan = system_plan
    user_dump_dest = F:\oracle\admin\MTFDB\udump

    db_block_size = 8192

    remote_login_passwordfile = exclusive

    os_authent_prefix = ""

    distributed_transactions = 10
    compatible = 8.1.0
    sort_area_size = 65536
    sort_area_retained_size = 65536
    utl_file_dir = *

    pls suggest me some steps to shoot up the performance of the Second system database when compared to the First System database

  2. #2
    Join Date
    Jun 2006
    Location
    Chennai, INDIA
    Posts
    72

    Wink

    Hi,
    It could be helpful to understand if you post more details about your issue. BTW U can use stats pack to get an idea about your system like load etc.

  3. #3
    Join Date
    Apr 2001
    Location
    Bangalore, India
    Posts
    727
    Sort area size 64K.. What is the value of "sorts (disk)" from V$sysstat
    Thomas Saviour(royxavier@yahoo.com)
    Technical Lead (Databases)
    Thomson Reuters (Markets)

    http://ora600tom.wordpress.com/

  4. #4
    Join Date
    Jan 2007
    Posts
    9

    Performnace Problem

    The following are the parameters that we set for the Sort.


    sorts (memory) 64 25009

    sorts (disk) 64
    263

    sorts (rows) 64 15456674

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width