For sga_target

we are using 11G DB. our database sga_target = 0.so we can assume that ASSM is disbled. what wud be the oracle recomended size of enable ASSM. where as sga_max_size = 3054M.
also what is the utlity of ASSM in 11G.how can we check?
thanks in advance..

please go thorugh our DB reading of those views.
SQL> select * from v$memory_target_advice;
MEMORY_SIZE MEMORY_SIZE_FACTOR ESTD_DB_TIME ESTD_DB_TIME_FACTOR    VERSION
        876                .25          696              1.0006          0
       1752                 .5          696                   1          0
       2628                .75          696                   1          0
       3504                  1          696                   1          0
       4380               1.25          696                   1          0
       5256                1.5          696                   1          0
       6132               1.75          696                   1          0
       7008                  2          696                   1          0
8 rows selected.
  SGA_SIZE SGA_SIZE_FACTOR ESTD_DB_TIME ESTD_DB_TIME_FACTOR ESTD_PHYSICAL_READS
       572             .25          899              1.2935              218739
      1144              .5          708              1.0187              108602
      1716             .75          695                   1               97708
      2288               1          695                   1               97708
      2860            1.25          695                   1               97708
      3432             1.5          695                   1               97708
      4004            1.75          695                   1               97708
      4576               2          695                   1               97708
8 rows selected.Now please suggest......
Thanks once again..
Edited by: piku on Feb 16, 2011 9:16 PM

Similar Messages

  • SGA_TARGET question

    Oracle's 10.2 documentations states the following about SGA_TARGET.
    SGA_TARGET specifies the total size of all SGA components. If SGA_TARGET is specified, then the following memory pools are automatically sized:
    Buffer cache (DB_CACHE_SIZE)
    Shared pool (SHARED_POOL_SIZE)
    Large pool (LARGE_POOL_SIZE)
    Java pool (JAVA_POOL_SIZE)
    Streams pool (STREAMS_POOL_SIZE)
    If these automatically tuned memory pools are set to non-zero values, then those values are used as minimum levels by Automatic Shared Memory Management. You would set minimum values if an application component needs a minimum amount of memory to function properly.
    The following pools are manually sized components and are not affected by Automatic Shared Memory Management:
    Log buffer
    Other buffer caches, such as KEEP, RECYCLE, and other block sizes
    Fixed SGA and other internal allocations
    The memory allocated to these pools is deducted from the total available for SGA_TARGET when Automatic Shared Memory Management computes the values of the automatically tuned memory pools.
    Under the area that illustrates what is not affected by ASMM it has "Fixed SGA and other internal allocations".
    Can anyone tell me exactly what these are??

    Find your answer in this metalink doc
    How to determine SGA Size (7.x, 8.x, 9.x, 10g)
    Doc ID: Note:1008866.6

  • SGA_MAX_SIZE & SGA_TARGET

    If anyone can explain to me the relationship of these 2 parameters? Chapter 8 Database Concepts doesn't clearly define how and if they are used in tandem.
    Matt

    Let me simplify it a bit ...
    From the links I provided:
    SGA_MAX_SIZE has a default. Therefore it does not need to be set.
    SGA_TARGET has a default. it does not need to be set. The default is 0, meaning NOTHING is automatically handled.
    In the Reference manual description for SGA_TARGET, it provides a link to the Concepts manual. That link is there to provide more detailed information, so we follow it ...
    The SGA_MAX_SIZE and SGA_TARGET are in the table of contents of the Concepts manual. Following that, we find
    It is significant that SGA_TARGET includes the entire memory for the SGA, in contrast to earlier releases in which memory for the internal and fixed SGA was added to the sum of the configured SGA memory parameters. Thus, SGA_TARGET gives you precise control over the size of the shared memory region allocated by the database. If SGA_TARGET is set to a value greater than SGA_MAX_SIZE at startup, then the latter is bumped up to accommodate SGA_TARGET.
    Note:
    Do not dynamically set or unset the SGA_TARGET parameter. This should be set only at startup.
    There is a lot of additional supporting information in the Concepts manual as well.
    Message was edited by: Hans Forbrich
    Corrected the interpretation of SGA_TARGET default.

  • Issue creating a database: SGA_MAX_SIZE and SGA_TARGET

    Hello:
    While creating a custom database, I am running into issues with the values I specify for SGA_MAX_SIZE and SGA_TARGET.
    The install manual for the product I am creating the database for says that SGA_MAX_SIZE should be >= SGA_TARGET_SIZE. It also wants a minimum of 1Gig for SGA_Target
    The Database Configuration Assistant defaulted to 0.64GB for SGA_TARGET and 0.168 for SGA_MAX_SIZE (This is clearly against the instruction in the installation manual).
    Who is right? Me or the vendor?
    I read some threads that indicate that the vendor may be wrong.
    venki

    Follow the vendor's instructions.
    DBCA has never in its existence made a correct decision yet. It puts all control files and redo logs into one directory.
    It doesn't create multiple members for the log file groups.
    And its memory management is based on a simple algorithm that has nothing to do with any specific reality.
    DBCA is intended for creating a generic database for generic purposes ... and that it does very very well.

  • SGA_TARGET

    Hi,
    I have one quick question regarding the SGA_TARGET parameter.
    This is my sga allocation so far:
    Total System Global Area 2147483648 bytes
    Fixed Size 2140320 bytes
    Variable Size 2124240736 bytes
    Database Buffers 16777216 bytes
    Redo Buffers 4325376 bytes
    My RAM size is 16GB and i would be creating many other applications as well. now i have the following sga parameters:
    SQL> sho parameter sga;
    NAME TYPE VALUE
    lock_sga boolean FALSE
    pre_page_sga boolean FALSE
    sga_max_size big integer 2G
    sga_target big integer 0
    Now my worry is the sga_target i want to make use but i have given old parameters as well and i am getting the error
    Error:     ORA-00381 (ORA-381)
    Text:     cannot use both new and old parameters for buffer cache size
         specification
    now my db* parameter settings are:
    SQL> sho parameter db;
    NAME TYPE VALUE
    db_16k_cache_size big integer 0
    db_2k_cache_size big integer 0
    db_32k_cache_size big integer 0
    db_4k_cache_size big integer 0
    db_8k_cache_size big integer 0
    db_block_buffers integer 2048
    db_block_checking string FALSE
    db_block_checksum string TRUE
    db_block_size integer 8192
    db_cache_advice string ON
    db_cache_size big integer 0
    NAME TYPE VALUE
    db_create_file_dest string
    db_create_online_log_dest_1 string
    db_create_online_log_dest_2 string
    db_create_online_log_dest_3 string
    db_create_online_log_dest_4 string
    db_create_online_log_dest_5 string
    db_domain string PFIZER.COM
    db_file_multiblock_read_count integer 16
    db_file_name_convert string
    db_files integer 1024
    db_flashback_retention_target integer 1440
    NAME TYPE VALUE
    db_keep_cache_size big integer 0
    db_name string EAMS01
    db_recovery_file_dest string
    db_recovery_file_dest_size big integer 0
    db_recycle_cache_size big integer 0
    db_unique_name string EAMS01
    db_writer_processes integer 2
    dbwr_io_slaves integer 0
    rdbms_server_dn string
    standby_archive_dest string ?/dbs/arch
    standby_file_management string MANUAL
    and my init parameters are:
    EAMS01.__streams_pool_size=33554432
    *._allow_level_without_connect_by=TRUE
    *.aq_tm_processes=1
    *.ARCHIVE_LAG_TARGET=900
    *.audit_file_dest='/u03/oracle/admin/EAMS01/adump'
    *.audit_trail='TRUE'
    *.background_dump_dest='/u03/oracle/admin/EAMS01/bdump'
    *.control_files='/u04/oradata/EAMS01/control01.ctl','/u04/oradata/EAMS01/control02.ctl','/u04/oradata/EAMS01/control03.ctl'
    *.core_dump_dest='/u03/oracle/admin/EAMS01/cdump'
    *.db_block_buffers=550# SMALL
    *.db_domain='PFIZER.COM'
    *.db_file_multiblock_read_count=16# SMALL
    *.db_files=1024# SMALL
    *.db_name='EAMS01'
    *.global_names=TRUE
    *.java_pool_size=96M
    *.job_queue_processes=15
    *.large_pool_size=32M
    *.log_archive_dest='/u04/arch/EAMS01'
    *.log_archive_format='EAMS01_%t_%s_%r.arc'
    *.log_archive_max_processes=5
    *.log_checkpoint_interval=10000
    *.log_checkpoints_to_alert=TRUE
    *.max_dump_file_size='10240'# limit trace file size to 5 Meg each
    *.NLS_DATE_FORMAT='YYYY-MM-DD'
    *.nls_length_semantics='CHAR'
    *.NLS_TERRITORY='AMERICA'
    *.open_cursors=768
    *.open_links=128
    *.open_links_per_instance=128
    *.optimizer_features_enable='10.2.0.3'
    *.parallel_max_servers=5# SMALL
    *.pga_aggregate_target=500M
    *.processes=512# SMALL
    *.query_rewrite_enabled='TRUE'
    *.query_rewrite_integrity='STALE_TOLERATED'
    *.remote_login_passwordfile='EXCLUSIVE'
    *.resource_limit=TRUE
    *.service_names='EAMS01.pfizer.com'
    *.sga_max_size=2G
    *.shared_pool_size=500000000# SMALL
    *.streams_pool_size=33554432
    *.timed_statistics=TRUE
    *.undo_management='AUTO'
    *.user_dump_dest='/u03/oracle/admin/EAMS01/udump'
    now what the parameters i am missing or need to edit sga_target so that oralce will use empirically over
    time. Thank you.
    -- Raman.

    Hi..
    >
    # symptom: ORA-00381: cannot use both new and old parameters for buffer cache size specification
    # cause: Both db_block_buffers and db_cache_size parameters are defined in the init.ora (instance parameter file). The db_block_buffers parameter has been deprecated and has been maintained only for backward compatibility. The db_cache_size parameter is one of the size parameters which defines the size of the cache for buffers. These parameters cannot be combined. Setting this along with the Dynamic SGA parameters errors out.
    >
    For sga_target refer to [http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams193.htm#REFRN10256]
    which quotes
    >
    SGA_TARGET specifies the total size of all SGA components. If SGA_TARGET is specified, then the following memory pools are automatically sized:
    *Buffer cache (DB_CACHE_SIZE)
    * Shared pool (SHARED_POOL_SIZE)
    * Large pool (LARGE_POOL_SIZE)
    * Java pool (JAVA_POOL_SIZE)
    * Streams pool (STREAMS_POOL_SIZE)
    If these automatically tuned memory pools are set to non-zero values, then those values are used as minimum levels by Automatic Shared Memory Management. You would set minimum values if an application component needs a minimum amount of memory to function properly.
    >
    So, the what ever the value are set for the parameter will act as minimum value when sga_target is set.
    HTH
    Anand

  • ALTER SYSTEM SET SGA_TARGET

    Hi,
    in 10g R2 should I stop/start database when I change sGA_TARGET :
    ALTER SYSTEM SET SGA_TARGET=value [SCOPE={SPFILE|MEMORY|BOTH}]
    Thank you.

    user522961 wrote:
    OK.
    When I query V$PARAMETER I have the OLD value for SGA_TARGET. It is normal because the value in V$PARAMETER comes from starting and spfile. How can I be sur that now oRACLE uses the new value for SGA_TARGET effectively ?
    Thanks again.Not sure I understand your question. If you set SGA_TARGET with SCOPE=MEMORY or BOTH, it should be in effect immediately.
    SQL> alter system set sga_target=253M scope=both;
    System altered.
    SQL> select value bytes, value/1048576 MB from v$parameter where name = 'sga_target';
    BYTES              MB
    268435456         256
    SQL> show parameter sga
    NAME                                 TYPE        VALUE
    lock_sga                             boolean     FALSE
    pre_page_sga                         boolean     FALSE
    sga_max_size                         big integer 512M
    sga_target                           big integer 256M
    SQL> alter system set sga_target=257M scope=both;
    System altered.
    SQL> select value bytes, value/1048576 MB from v$parameter where name = 'sga_target';
    BYTES              MB
    272629760         260
    SQL> show parameter sga
    NAME                                 TYPE        VALUE
    lock_sga                             boolean     FALSE
    pre_page_sga                         boolean     FALSE
    sga_max_size                         big integer 512M
    sga_target                           big integer 260M
    SQL>

  • Setting SGA_MAX_SIZE without setting SGA_TARGET

    RDBMS Version: 10.2.0.4
    OS : Solart 5.10
    We are currently facing some performance issues in one of our DBs.
    This DB has SGA Components individually set. For eg: DB_CACHE_SIZE is set to 2gb.
    I've noticed that
    SGA_MAX_SIZE = 6GB
    SGA_TARGET = Not setShould we set both SGA_TARGET, SGA_MAX_SIZE to take advantage of 10gR2's Automatice shared Memory Management?

    sga_max_size sets the maximum value for sga_target.see MOSC Notes 295626.1, 396940.1, 270065.1 and 256913.1.
    SGA_TARGET parameter is new with Oracle 10g. It specifies the total amaount of SGA memory available to an instance. Setting this parameter makes Oracle distribute the available memory among various components - such as shared pool (for SQL and PL/SQL), Java pool, large_pool and buffer cache - as required. This new feature is called Automatic Shared Memory Management. With ASMM, the parameters java_pool_size, shared_pool_size, large_pool_size and db_cache_size need not be specified explicitely anymore. sga_target cannot be higher than sga_max_size.
    SGA_MAX_SIZE != SGA_TARGET when?
    http://www.orafaq.com/wiki/Sga_target
    Thanks

  • SGA_TARGET and DB_CACHE_SIZE

    In my oracle 10g database SGA_TARGET has been enabled and DB_CACHE_SIZE also set
    It will take from SGA_TARGET or DB_CACHE_SIZE ?

    Dear user!
    SGA_TARGET and DB_CACHE_SIZE behave like that:
    DB_CACHE_SIZE:
    - Meaning:
    DB_CACHE_SIZE specifies the size of the DEFAULT buffer pool for buffers with the primary block size (the block size defined by the DB_BLOCK_SIZE initialization
    parameter).
    - Defaultvalue:
    If SGA_TARGET is set: If the parameter is not specified, then the default is 0 (internally determined by the Oracle Database). If the parameter is specified, then
    the user-specified value indicates a minimum value for the memory pool.
    If SGA_TARGET is not set, then the default is either 48 MB or 4MB * number of CPUs * granule size, whichever is greater
    SGA_TARGET
    SGA_TARGET specifies the total size of all SGA components. If SGA_TARGET is specified, then the following memory pools are automatically sized:
    * Buffer cache (DB_CACHE_SIZE)
    * Shared pool (SHARED_POOL_SIZE)
    * Large pool (LARGE_POOL_SIZE)
    * Java pool (JAVA_POOL_SIZE)
    * Streams pool (STREAMS_POOL_SIZE)
    If these automatically tuned memory pools are set to non-zero values, then those values are used as minimum levels by Automatic Shared Memory Management. You would set minimum values if an application component needs a minimum amount of memory to function properly.
    The following pools are manually sized components and are not affected by Automatic Shared Memory Management:
    * Log buffer
    * Other buffer caches, such as KEEP, RECYCLE, and other block sizes
    * Fixed SGA and other internal allocations
    The memory allocated to these pools is deducted from the total available for SGA_TARGET when Automatic Shared Memory Management computes the values of the automatically tuned memory pools.
    I hope that these informations will help you to answer you question.
    Yours sincerely
    Florian W.

  • SOA-- Invoking OSB Service Getting Error :ORA-00084: global area must be PGA, SGA, or UGA

    Hello Friends,
    Really appreciate your help/inputs on the below Error Message encountered while running a Concurrent Program--using SOA:Same encountered in recently refreshed DEV instance, Can it be related to some Developement Instance Configuration related to SOA, as same working as expected in PROD.PLEASE ASSIST
    Need your inputs on the Error Message we are getting which Invoking OSB Service.
    "Error inside invoke_osb_service -> Error Code : -84Error Message :ORA-00084: global area must be PGA, SGA, or UGA "
    Can you please review and confirm if the same encountered before or assist on the same:
    XXFIN_AP_INVOICES_INT_IB_PKG.invoke_osb_service
    -- Define the SOAP request according the the definition of the web service being called
    l_soap_request := 
                '<?xml version = "1.0" encoding = "UTF-8"?>'
            || '<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:prox="http://OmnicareFinance/ProxyInput/">'
             ||   '<soapenv:Header/>'
             ||     '<soapenv:Body>'
             ||       '<prox:InboundProcess>'
             ||     '<Source_system>'||g_source_instance||'</Source_system>'
             ||     '<Run_mode>'||g_run_mode||'</Run_mode>'
             ||     '<Batch_key>'||g_batch_key||'</Batch_key>'
             ||     '<Request_id>'||g_request_id||'</Request_id>'
             ||     '<Invoice_Header_File_name>'||g_file_name||'</Invoice_Header_File_name>'
             ||     '<Invoice_Line_File_name>'||NULL||'</Invoice_Line_File_name>'
             ||     '<File_location>'||g_file_location||'</File_location>'
             ||       '</prox:InboundProcess>'
             ||     '</soapenv:Body>'
             ||   '</soapenv:Envelope>';
    Oracle Apps Log File
    -->Entering XXFIN_AP_INVOICES_INT_IB_PKG.invoke_osb_service
    -->   = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
    -->Response> status_code: "200"
    -->Response> reason_phrase: "OK"
    -->Response> http_version: "HTTP/1.1"
    -->Response From OSB: <?xml version="1.0" encoding="UTF-8"?>
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header xmlns:prox="http://OmnicareFinance/ProxyInput/"/><soapenv:Body xmlns:prox="http://OmnicareFinance/ProxyInput/"><prox:InboundProcessResponse><status>E</status></prox:InboundProcessResponse></soapenv:Body></soapenv:Envelope>
    -->OSB Response: E
    -->Error inside invoke_osb_service -> Error Code : -84Error Message :ORA-00084: global area must be PGA, SGA, or UGA
    -->   = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
    -->Entering XXFIN_AP_INVOICES_INT_IB_PKG.capture_error_info
    THANKS
    ANKUR

    Hi..
    >
    # symptom: ORA-00381: cannot use both new and old parameters for buffer cache size specification
    # cause: Both db_block_buffers and db_cache_size parameters are defined in the init.ora (instance parameter file). The db_block_buffers parameter has been deprecated and has been maintained only for backward compatibility. The db_cache_size parameter is one of the size parameters which defines the size of the cache for buffers. These parameters cannot be combined. Setting this along with the Dynamic SGA parameters errors out.
    >
    For sga_target refer to [http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams193.htm#REFRN10256]
    which quotes
    >
    SGA_TARGET specifies the total size of all SGA components. If SGA_TARGET is specified, then the following memory pools are automatically sized:
    *Buffer cache (DB_CACHE_SIZE)
    * Shared pool (SHARED_POOL_SIZE)
    * Large pool (LARGE_POOL_SIZE)
    * Java pool (JAVA_POOL_SIZE)
    * Streams pool (STREAMS_POOL_SIZE)
    If these automatically tuned memory pools are set to non-zero values, then those values are used as minimum levels by Automatic Shared Memory Management. You would set minimum values if an application component needs a minimum amount of memory to function properly.
    >
    So, the what ever the value are set for the parameter will act as minimum value when sga_target is set.
    HTH
    Anand

  • Can I adjust the parameter in XE's deb package?

    Dear all,
    I've just installed 10g XE on my Debian 3.1 system.
    But I found the following error in my log file.
    shuang:/usr/lib/oracle/xe/app/oracle/product/10.2.0/server/config/log# cat CloneRmanRestore.log | more
    LRM-00104: '%sga_target%' is not a legal integer for 'sga_target'
    ORA-01078: failure in processing system parameters
    TO_CHAR(SYSTIMEST
    20070307 10:28:26
    Allocating device....
    Specifying datafiles...
    Specifing datafiles...
    Restoring ...
    Restore done.
    PL/SQL procedure successfully completed.
    TO_CHAR(SYSTIMEST
    20070307 10:30:32
    shuang:/usr/lib/oracle/xe/app/oracle/product/10.2.0/server/config/log# cat cloneDBCreation.log | more
    GROUP 1 SIZE 51200K,
    ERROR at line 13:
    ORA-02236: invalid file name
    BEGIN dbms_backup_restore.zerodbid(0); END;
    ERROR at line 1:
    ORA-00210: cannot open the specified control file
    ORA-06512: at "SYS.X$DBMS_BACKUP_RESTORE", line 4168
    ORA-06512: at line 1
    ORA-01507: database not mounted
    ORACLE instance shut down.
    LRM-00104: '%sga_target%' is not a legal integer for 'sga_target'
    ORA-01078: failure in processing system parameters
    Create controlfile reuse set database "XE"
    ERROR at line 1:
    ORA-01034: ORACLE not available
    shuang:/usr/lib/oracle/xe/app/oracle/product/10.2.0/server/config/log# cat postDBCreation.log | morebegin
    ERROR at line 1:
    ORA-01034: ORACLE not available
    create spfile='/usr/lib/oracle/xe/app/oracle/product/10.2.0/server/dbs/spfileXE.ora' FROM pfile='/usr/lib/oracle/xe/app/oracle/product/10.2.0/server/config/scripts/init.ora'
    ERROR at line 1:
    ORA-01078: failure in processing system parameters
    ORA-32003: error occured processing parameter 'sga_target'
    ORA-01034: ORACLE not available
    ORA-27101: shared memory realm does not exist
    Linux Error: 2: No such file or directory
    ORA-01078: failure in processing system parameters
    LRM-00109: could not open parameter file '/usr/lib/oracle/xe/app/oracle/product/10.2.0/server/dbs/initXE.ora'
    select 'utl_recomp_begin: ' || to_char(sysdate, 'HH:MI:SS') from dual
    ERROR at line 1:
    ORA-01034: ORACLE not available
    shuang:/usr/lib/oracle/xe/app/oracle/product/10.2.0/server/config/log# cat postScripts.log | more
    CREATE OR REPLACE LIBRARY dbms_sumadv_lib AS '/usr/lib/oracle/xe/app/oracle/product/10.2.0/server/lib/libqsmashr.so';
    ERROR at line 1:
    ORA-01034: ORACLE not available
    create or replace directory DATA_PUMP_DIR as '/usr/lib/oracle/xe/app/oracle/admin/XE/dpdump/'
    ERROR at line 1:
    ORA-01034: ORACLE not available
    commit
    ERROR at line 1:
    ORA-01034: ORACLE not available
    BEGIN dbms_swrf_internal.cleanup_database(cleanup_local => FALSE); END;
    ERROR at line 1:
    ORA-01034: ORACLE not available
    commit
    ERROR at line 1:
    ORA-01034: ORACLE not available
    Would someone be kind enough to tell me how can I solve the problem?
    Thanks in advance.

    Have you tried exporting using the Save as PDF button on the lower left of the Print dialog box? I don't know if that will help, but it might.
    I have not tried that, but I will. I always thought that going through Distiller gave you better quality. That's how I was converting the .ps files before that were created out of Framemaker.
    Your page thumbnails are strange, though. Are you using Distiller to convert fonts to outlines or something? Text is suppose to stay as text to help thumbnail previews
    I'm not converting fonts to outlines. It's very strange... there must be a setting in Distiller somewhere that I have mis-marked... I'll be darned if I can find it though.
    I've included a shot of pages from a previous project, there is a distinct difference.

  • 5 GB  SGA on 8GB RAM  HP Server 64Bit

    Hi all
    Recently three months we installed Oracle 10g Database on HP Server (having 4 XEON Processors) with Windows 2003 (64 Bit) OS and we have 8GB RAM.
    We wished to have 5500M as the SGA Target but we could not configure more that 3800M on that machine as after that it would error and the database would not get start.
    error messages would be like - Out of memory
    OR
    ???? (not recollecting)
    Now we are running with only 3500M as sga_target and not utilizing the full available RAM with us. Of course we are using in addition 1500M for pga_aggregate_target without any problem. Even if we increase pga_aggregate_target to 3000M there is no problem but that is not desired to us. We wish to increase sga_target.
    We are getting excellent response timings on 3500M sga_target but as human nature would be , we wish to be more greedy and use the full available RAM with us i.e 8GB out of which we can safely use 7GB for Oracle instance. While deducting 1500M for pga_aggregate_target we would like to use 5500M for sga_target.
    Any help is appreciated.
    Suresh Bansal

    Excerpt from oracle docs.
    Benefits of Automatic Shared Memory Management
    Automatic Shared Memory Management simplifies the configuration of the SGA. Before Oracle Database 10G, buffer cache, shared pool, java pool, and large pool need to be manually specified for the database. Under sizing can lead to poor performance and out-of-memory errors (ORA-4031), while over sizing can waste memory. This feature enables you to specify a total memory amount to be used for all SGA Components (buffer cache, shared pool, java pool, and large pool). The Oracle database periodically redistributes memory between these components according to workload requirements. Before Oracle Database 10G, the user did not have exact control over the total size of the SGA since memory was allocated by Oracle for the fixed SGA, and for other internal metadata allocations over and above the total size of the user specified SGA parameters. The new SGA size parameter SGA_TARGET now includes all the memory in the SGA, including all the automatically sized components, manually sized components, and any internal allocations during startup.
    Configuring Automatic Shared Memory Management
    Automatic Shared Memory Management can be configured by using the SGA_TARGET initialization parameter. If you specify a non-zero value for SGA_TARGET, the following four memory pools are automatically sized:
    * Database buffer cache (Default pool)
    * Shared pool
    * Large pool
    * Java pool
    If you set SGA_TARGET to 0, Automatic Shared Memory Management is disabled. The default value of SGA_TARGET is 0.
    The individual parameters used before Oracle 10G releases to specify the sizes of the automatically sized components have not been made obsolete. The initialization parameters that size these pools (DB_CACHE_SIZE, SHARED_POOL_SIZE, LARGE_POOL_SIZE, and JAVA_POOL_SIZE) are now referred to as auto-tuned SGA parameters.
    The following buffers are now referred to as manually sized components:
    * Log buffer
    * Other buffer caches (KEEP/RECYCLE, other block sizes)
    * Streams pool (new in Oracle Database 10g)
    * Fixed SGA and other internal allocations
    Note: STATISTICS_LEVEL must be set to TYPICAL (default) or ALL to use Automatic Shared Memory Management.
    Jaffar

  • Assm question

    Hi experts,
    I was just studying some questions and answers about 11g, the book says "B" is the correct answer, however I think "C".
    What do you think ?
    In Oracle 11g, by default which one of the following conditions implicitly enables Automatic PGA
    Memory Management?
    A. Setting a nonzero value for SGA_TARGET
    B. Configuring Automatic Shared Memory Management
    C. Configuring Automatic Memory Management
    D. Setting a nonzero value for SGA_MAX_SIZE and PGA_AGGREGATE_TARGET
    E. None of the above
    Answer: B

    ASMM
    The Oracle Automatic Shared Memory Management is a feature that automatically readjusts the sizes of the main pools.
    refer to http://www.dba-oracle.com/t_automatic_shared_memory_management.htm
    So you are right . casue it's a 10g future and use to configure SGA.not PGA
    Edited by: Longfei Wei on Jan 26, 2011 8:31 AM

  • DBCA templates - PGA and SGA using "percentageMemTOSGA" parameter

    Hi all,
    I am trying to configure a DBCA template to perform silent database creations on servers at our client sites. The amount of RAM could vary from server to server. For this reason, I am specifying the following parameters:
    customSGA=false
    percentageMemTOSGA=70In principle, this works pretty well - my DB is created with a suitable value for SGA_TARGET based on the RAM available on the server. However, the value that it uses for PGA_AGGREGATE_TARGET is too small for our needs. From experience, we can get by with a smaller SGA, but we need a relatively large PGA.
    I have tried specifying the parameter "pga_aggregate_target" in the template (and thus trying to "override" the decision of DBCA) but DBCA ignores my "hard-coded" value for this and sets pga_aggregate_target according to (presumably) some calculation based on:
    - The amount of RAM available
    - The value of "percentageMemTOSGA"
    - Some "other" value which tells DBCA how to divide up the %age memory it will take between SGA and PGA
    So, my question is:
    Does anybody know how to effectively use both "percentageMemTOSGA", and:
    EITHER:
    * tell DBCA how to split the memory that it will use from RAM (in this case 70%) between pga_aggregate_target and sga_target (some parameter maybe like "percent_to_pga" and "percent_to_sga")
    OR (not as useful but better than no control):
    * specify explicitly a value (or percentage) for pga_aggregate_target, but leave the value of sga_target to be decided based on the percentageMemTOSGA
    I hope I've explained that well enough...
    Regards,
    Ados

    I've checked the help for dbca (I'm currently running from the command prompt in "silent" mode) and don't see anything about recording the creation - how would I do that? Or are you referring to using the GUI, creating a database, and then saving the template? If it's that, that's what I did first, then editing the template for my tests - I don't see the parameter(s) that I'm looking for in the template.Ados,
    I did the same what you did. Run dbca in GUI mode and generate template only now in template file I see there is a parameter to set these value. For your reference I am posting the content of that file:
    <?xml version = '1.0'?>
    <DatabaseTemplate name="orcl" description="" version="10.2.0.3.0">
    <CommonAttributes>
    <option name="ISEARCH" value="false"/>
    <option name="OMS" value="false"/>
    <option name="JSERVER" value="true"/>
    <option name="SPATIAL" value="true"/>
    <option name="ODM" value="true">
    <tablespace id="SYSAUX"/>
    </option>
    <option name="IMEDIA" value="true"/>
    <option name="XDB_PROTOCOLS" value="true">
    <tablespace id="SYSAUX"/>
    </option>
    <option name="ORACLE_TEXT" value="true">
    <tablespace id="SYSAUX"/>
    </option>
    <option name="SAMPLE_SCHEMA" value="true"/>
    <option name="CWMLITE" value="true">
    <tablespace id="SYSAUX"/>
    </option>
    <option name="EM_REPOSITORY" value="true">
    <tablespace id="SYSAUX"/>
    </option>
    <option name="HTMLDB" value="false"/>
    </CommonAttributes>
    <Variables/>
    <CustomScripts Execute="false"/>
    <InitParamAttributes>
    <InitParams>
    *<initParam name="pga_aggregate_target" value="808" unit="MB"/>*
    <initParam name="processes" value="150"/>
    <initParam name="db_recovery_file_dest_size" value="1024" unit="MB"/>
    <initParam name="control_files" value="(&quot;{ORACLE_BASE}/oradata/{DB_UNIQUE_NAME}/control01.ctl&quot;, &quot;{ORACLE_BASE}/oradata/{DB_UNIQUE_NAME}/control02.ctl&quot;, &quot;{ORACLE_BASE}/oradata/{DB_UNIQUE_NAME}/control03.ctl&quot;)"/>
    <initParam name="sga_target" value="1536" unit="MB"/>
    <initParam name="compatible" value="10.2.0.3.0"/>
    <initParam name="background_dump_dest" value="{ORACLE_BASE}/admin/{DB_UNIQUE_NAME}/bdump"/>
    <initParam name="job_queue_processes" value="10"/>
    <initParam name="db_name" value="orcl"/>
    <initParam name="user_dump_dest" value="{ORACLE_BASE}/admin/{DB_UNIQUE_NAME}/udump"/>
    <initParam name="dispatchers" value="(PROTOCOL=TCP) (SERVICE={SID}XDB)"/>
    <initParam name="audit_file_dest" value="{ORACLE_BASE}/admin/{DB_UNIQUE_NAME}/adump"/>
    <initParam name="db_domain" value=""/>
    <initParam name="open_cursors" value="300"/>
    <initParam name="db_block_size" value="8" unit="KB"/>
    <initParam name="db_recovery_file_dest" value="{ORACLE_BASE}/flash_recovery_area"/>
    <initParam name="undo_tablespace" value="UNDOTBS1"/>
    <initParam name="core_dump_dest" value="{ORACLE_BASE}/admin/{DB_UNIQUE_NAME}/cdump"/>
    <initParam name="remote_login_passwordfile" value="EXCLUSIVE"/>
    <initParam name="undo_management" value="AUTO"/>
    <initParam name="db_file_multiblock_read_count" value="16"/>
    </InitParams>
    <MiscParams>
    <databaseType>MULTIPURPOSE</databaseType>
    <maxUserConn>20</maxUserConn>
    <percentageMemTOSGA>40</percentageMemTOSGA>
    <customSGA>true</customSGA>
    <archiveLogMode>false</archiveLogMode>
    <initParamFileName>{ORACLE_BASE}/admin/{DB_UNIQUE_NAME}/pfile/init.ora</initParamFileName>
    </MiscParams>
    <SPfile useSPFile="true">{ORACLE_HOME}/dbs/spfile{SID}.ora</SPfile>
    </InitParamAttributes>
    <StorageAttributes>
    <DataFiles>
    <Location>{ORACLE_HOME}/assistants/dbca/templates/Seed_Database.dfb</Location>
    <SourceDBName>seeddata</SourceDBName>
    <Name id="1" Tablespace="SYSTEM" Contents="PERMANENT" Size="480" autoextend="true" blocksize="8192">{ORACLE_BASE}/oradata/{DB_UNIQUE_NAME}/system01.dbf</Name>
    <Name id="2" Tablespace="UNDOTBS1" Contents="UNDO" Size="25" autoextend="true" blocksize="8192">{ORACLE_BASE}/oradata/{DB_UNIQUE_NAME}/undotbs01.dbf</Name>
    <Name id="3" Tablespace="SYSAUX" Contents="PERMANENT" Size="240" autoextend="true" blocksize="8192">{ORACLE_BASE}/oradata/{DB_UNIQUE_NAME}/sysaux01.dbf</Name>
    <Name id="4" Tablespace="USERS" Contents="PERMANENT" Size="5" autoextend="true" blocksize="8192">{ORACLE_BASE}/oradata/{DB_UNIQUE_NAME}/users01.dbf</Name>
    </DataFiles>
    <TempFiles>
    <Name id="1" Tablespace="TEMP" Contents="TEMPORARY" Size="20">{ORACLE_BASE}/oradata/{DB_UNIQUE_NAME}/temp01.dbf</Name>
    </TempFiles>
    <ControlfileAttributes id="Controlfile">
    <maxDatafiles>100</maxDatafiles>
    <maxLogfiles>16</maxLogfiles>
    <maxLogMembers>3</maxLogMembers>
    <maxLogHistory>1</maxLogHistory>
    <maxInstances>8</maxInstances>
    <image name="control01.ctl" filepath="{ORACLE_BASE}/oradata/{DB_UNIQUE_NAME}/"/>
    <image name="control02.ctl" filepath="{ORACLE_BASE}/oradata/{DB_UNIQUE_NAME}/"/>
    <image name="control03.ctl" filepath="{ORACLE_BASE}/oradata/{DB_UNIQUE_NAME}/"/>
    </ControlfileAttributes>
    <RedoLogGroupAttributes id="1">
    <reuse>false</reuse>
    <fileSize unit="KB">51200</fileSize>
    <Thread>1</Thread>
    <member ordinal="0" memberName="redo01.log" filepath="{ORACLE_BASE}/oradata/{DB_UNIQUE_NAME}/"/>
    </RedoLogGroupAttributes>
    <RedoLogGroupAttributes id="2">
    <reuse>false</reuse>
    <fileSize unit="KB">51200</fileSize>
    <Thread>1</Thread>
    <member ordinal="0" memberName="redo02.log" filepath="{ORACLE_BASE}/oradata/{DB_UNIQUE_NAME}/"/>
    </RedoLogGroupAttributes>
    <RedoLogGroupAttributes id="3">
    <reuse>false</reuse>
    <fileSize unit="KB">51200</fileSize>
    <Thread>1</Thread>
    <member ordinal="0" memberName="redo03.log" filepath="{ORACLE_BASE}/oradata/{DB_UNIQUE_NAME}/"/>
    </RedoLogGroupAttributes>
    </StorageAttributes>
    </DatabaseTemplate>
    Regards.

  • Why do I get out of memory errors when 10GB memory is free?

    I am on HP UNIX 64bit 11.23 titanium, running Oracle 10.2.0.3. . My server has 24GB memory and of that 10GB is free (as seen in glance). When I doing oracle exp or rman commands, I get:
    ORA-04030: out of process memory when trying to allocate 1049112 bytes (KSFQ heap,KSFQ Buffers)
    I checked both rman and exp are 64bit executables, so they should be able to access all the memory on the system.

    I have just one parameter in init.ora sga_target which controls everything in SGA. hw two instance I was reporting porblem have sga_target of 256M and 192M, Problems happen off and on, but 9 to 10GN free memory is alwyas available on server.
    Her is more information on the problem:
    1.     I do not think problem is with ulimit, but something is definitely not set correctly. Ulimit -a
    time(seconds) unlimited
    file(blocks) unlimited
    data(kbytes) 4194300
    stack(kbytes) 131072
    memory(kbytes) unlimited
    coredump(blocks) 4194303
    parameters are reasonable.
    2.     I have 10GB free memory. I run simple java command
    Java
    it works.
    3.     Now I increase memory for sga_target for one of my Oracle instance from 256M to 512M. I only hav eon eparameter sga_traget which controls everything in SGA. There are many other Oracle instances on the server. My Oracle instance starts without problems.
    4.     I now run java, it gives me:
    Out of memory error, so Oracle has exhausted some memory (probably shared memory) which is needed by java. I still have 9-10GB memory on my server, so why java is not using this memory.
    5.     After iOracle instance starts, off and on Oracle backups fail with ORA- error (not enough memory) I reported earlier.
    I hope HP engineers can figure this out.

  • SGA_MAX_SIZE and SGA_TARGET how to set minimum for pools

    Hello, we are on 10.2.0.4, Solaris 5.10. We are using ASMM, so SGA_TARGET and SGA_TARGET size are set. Hence, buffer cache, shared pool, large pool and java pool are automatically sized. However, we do not have any minimum values for those. How do I determine what this minimum value should be?
    thank you!

    HI,
    Yes you need size the minimum value for shared pool, buffer cahce tec... else it will start consuming wholeThe documentaion
    states:
    You need not set the size of any of these components explicitly. By default the parameters for these components will appear to have values of zero. Whenever a component needs memory, it can request that it be transferred from another component by way of the internal automatic tuning mechanism. This transfer of memory occurs transparently, without user intervention.Can you please explain how would it start consuming the entire SGA?

Maybe you are looking for