SGA ROT in 10g

Hi Oraculars,
What is ROT for SGA_MAX_SIZE on windows 2003 environment recommanded by Oracle?
Tanks,

user12159566 wrote:
I am asking basic Rule of SGA settings.Are you asking how to size the SGA or how to set SGA_MAX_SIZE? Those are two rather different animals.
SGA_MAX_SIZE controls the maximum size you can increase your SGA to without needing to restart the database. It doesn't have anything to do with the actual size of the SGA. So it's reasonably safe to set it to the amount of RAM on the box so long as you understand that you would never want the SGA to actually get that big since that would mean that whatever RAM the PGA and the operating system required would all have to be paged which would likely cause performance to be disasterously slow.
What version of Oracle are you using? Are you using automatic memory management? What memory-related parameters are you setting?
If you are using 11.2, the simplest option is generally to set MEMORY_TARGET to the amount of RAM on the box minus whatever the operating system needs to run and to let Oracle work out how much to allocate to the SGA and how much to allocate to the PGA. In 10.2, MEMORY_TARGET wasn't available so you would generally set a separate PGA_TARGET and SGA_TARGET but that required a bit of an understanding of the system to be able to guess at how to allocate memory between the two. In versions earlier than that, things get more complicated. And it also gets more complicated if you prefer in later versions to size individual memory components manually rather than relying on automatic memory management.
Justin

Similar Messages

  • SGA in Oracle 10g

    The following parameters are set in prod db.
    I would like to know whether oracle will take from sga_target or individual parameters in oracle 10g
    You suggesting would be highlyl appreciated
    (MB)
    shared_pool_size =      419430400     400
    large_pool_size =      16777216     16
    java_pool_size =      318767104     304
    db_cache_size =      536870912     512
    sga_target      2315255808     2208
    sga_max_size     3674210304     3504

    user446367 wrote:
    SGA_TARGET parameter set and individual (DB_CACHE_SIZE, SHARED_POOL_SIZE, LARGE_POOL_SIZE, and JAVA_POOL_SIZE) also which one will get effectBoth! For example, if you have SGA_TARGET set to 8gb and also have set the individual parameters, their values set will act as the minimum values for them and their sum total still can't be ever more than the value set in the SGA_TARGET.
    HTH
    Aman....

  • Increase SGA in Oracle 10g

    Hi everyone,
    I am Ann. I am not a DBA, because the main DBA and Developer is on maternity leave have to step up to look after an Oracle Application Forms and Reports and Oracle database (version 10.1).
    Recently, people complaints the apps is slow.
    So I open the Enterprise Manager, and check the Performance Adviser, it shows one issue
    Finding          The buffer cache was undersized causing significant additional read I/O.
    Impact (minutes)          5.31
    Impact (%)     
    13.13
    The recommendation is Increase SGA target size by increasing the value of parameter "sga_target" by 928 M. (there is a button Implement next to the message).
    The findings path is
    The buffer cache was undersized causing significant additional read I/O.
    13.13     
    Wait class "User I/O" was consuming significant database time.     16.27     
    About the server, we use OpenSuse. I also log into the server as root.
    Type free command to get info about memory and here is the details
    borg:~ # free
    total used free shared buffers cached
    Mem: 6101512 6001288 100224 0 180376 4636256
    -/+ buffers/cache: 1184656 4916856
    Swap: 12586916 1728548 10858368
    I just want to know is it safe to run the implement button to increase the SGA target size.
    I know that I have to shutdown and restart the instance.
    Many thanks,
    Ann

    >
    I just want to know is it safe to run the implement button to increase the SGA target size.
    >
    You shouldn't do anything until
    1. You confirm that there is, in fact, a problem
    2. You determine exactly what the problem is
    3. You determine the cause, or causes, of the problem
    4. You identify, and rank, possible solutions to the problem
    5. You test possible solutions in a dev/text environment to make sure your process works as expected.
    6. You script a method to 'undo' any changes you make
    >
    Recently, people complaints the apps is slow.
    >
    So what! People always complain that apps are slow. While it's fine to take note of that don't make a knee-jerk reaction to it.
    Gather more information.
    1. Slow in what way? entering data? running reports? batch jobs?
    2. Slow when? first thing in the morning? mid-day when all users are on the system? all the time?
    3. How long has it been slow? Just started? A couple of days? a few weeks?
    4. What does the main DBA say about the reported slowness? Have you called to ask? Why not? They are on maternity leave not climbing the alps or Himalayas. Call them and ask them if they were aware of reported problems.
    5. Did you ask the main DBA what you should look at? Why not?
    Tell us more information. What are the memory parameters now?
    Open a sql*plus session and then run and post the results of
    1. SHOW PARAMETER SGA_TARGET
    2. SHOW SGA
    3. SHOW PARAMETER POOL

  • Sga size in 10g r2

    Dear Oracle gurus
    oracle version 10.2.0.3.0 (64bit)
    I am running 2 instances on
    SUSE Linux Enterprise Server 11 (having 24 gb memory)
    1)first instance:-
    sga_max_size 4016M
    sga_target 4016M
    pga_aggregate_target 1595M
    2) second instance:-
    sga_max_size 1536M
    sga_target 1536M
    pga_aggregate_target 1595M
    I am planning to increase sga to 8 gb for first instance.
    Any advice
    Thanks for your time.

    880674 wrote:
    Oracle Gurus,
    Thanks to everybody for the reply .
    Please help.
    I really want to learn performance tuning but I am starter so my basic are not that great.
    Please suggest my good book for performance tuning.As Pavan said, start with the Performance manual. That has the basics. Then you should check out Jonathan Lewis' optimizer book to understand how to work out what the optimizer is doing, Cary Milsap's book on figuring out what is really wrong, and Troubleshooting Oracle Performance by Antognini. Note that most performance problems aren't magically fixed by playing with the SGA or other instance parameters. You are much better off leaving the instance parameters where they are and checking what is actually slowing you down. There are many variables involved, and sometimes fixing a bottleneck can lead to a worse bottleneck.
    >
    let me explain my problem again so that I can get your attention or support
    I have 1 job which takes 5 hr on production .I cloned that db to new and fast box(24gb memory) ,same job completed with in 40 min.I thought that increasing
    SGA will give us more performance gain ,so I tried to increase sga to 12 gb from 4gb .
    I faced ORA-27102 error.So I followed ID 301830.1
    and set kernel.shmall = 4194304
    kernel.shmmax = 12884901888
    When I modified the etc/sysctl.conf file and modified the shmall and shmmax to allow 12 gig sga for Oracle, the execution time increased by 15 min;I am not sure what is causing this.feel like shooting myself.No need to shoot yourself, you just need to use the tools available to know what is wrong. There are various things you can look at and tweak, but following a methodology like Cary's can get you right to the problem to fix. Sometimes even the statspack can point at the real problem.
    It could be you are running into memory wastage because you are or are not using hugepages, not leaving enough PGA for users to do their thing, who knows?
    The instrumentation knows.
    >
    Please help/advice
    SQL> startup force;
    ORA-27102: out of memory
    Linux-x86_64 Error: 28: No space left on device
    SQL> startup
    ORA-27102: out of memory
    Linux-x86_64 Error: 28: No space left on deviceThis should give you a clue that "more" does not necessarily mean "better."

  • Increase SGA size with ORA-02095.

    Hi Experts,
    I want to increase SGA for oracle 10G in window 2003 . however, I got error as
    SQL> alter system set sga_max_size=1700M,scope=spfile;
    alter system set sga_max_size=1700M,scope=spfile
    ERROR at line 1:
    ORA-02095: specified initialization parameter cannot be modified
    SQL> alter system set SGA_TARGET=1700M scope=SPFILE;
    System altered.
    SQL> alter system set sga_max_size=1700M,scope=spfile;
    alter system set sga_max_size=1700M,scope=spfile
    ERROR at line 1:
    ORA-02095: specified initialization parameter cannot be modified
    Now I just increase SGA_target as 1700M How to increase SGA_MAX_SIZE?
    Thanks
    JIM
    Edited by: user589812 on Mar 23, 2009 8:42 AM

    SQL> alter system set sga_max_size=1700M,scope=spfile;
    alter system set sga_max_size=1700M,scope=spfile
    ERROR at line 1:
    ORA-02095: specified initialization parameter cannot be modified
    take out comma,
    alter system set sga_max_size=1700M scope=spfile;

  • SGA dynamic or not ?

    Hi Forum,
    when is SGA dynamic ? One SAP note says that the use of parameter db_cache_size make SGA dynamically sizing its buffers. Others say that parameter sga_target
    <> 0 decides on dynamic or not. If db_cache_size is set but sga_target is 0, what does this mean ?
    Kind regards
    hakort

    DB_CACHE_SIZE itself is a dynamic parameter. Even if you mention SGA_TARGET as 0, its still can be changed dynamically with alter system command. The dynamic word has been used at several places in oracle docs. By making db_cache_size dynamic, any changes done to it are immediately effected. But this doesn't mean that the entire SGA has become dynamic.
    With dynamic sga(started from 10g onwards), 5 parameters, which are mentioned by Laura are made dynamic and are collectively set by the SGA_TARGET parameter. This leaves the entire SGA over Oracle's discretion that how to allocate/deallocate memory among these parameters. This setting works only when the SGA_TAGET is set to some non-zero value. Once set to 0, Oracle reverts back to the manual SGA where the parameters can be changed by you dynamically but the entire SGA is still controlled by you. By entire SGA I mean the 5 parameters and the other non-dynamic parameters like Log_buffer and so on.
    HTH
    Aman....

  • (Oracle 10g) MMAN 백그라운드 프로세스를 통한 자동 공유 메모리 관리

    제품 : ORACLE SERVER
    작성날짜 : 2005-05-19
    (Oracle 10g) MMAN 백그라운드 프로세스를 통한 자동 공유 메모리 관리
    ========================================
    PURPOSE
    이 문서에서는 Oracle database 10g의 Self Managing 기능 중의 하나인
    자동 공유 메모리 관리 기능에 대하여 알아보고 SGA_TARGET 이라는
    새로운 파라미터와 MMAN이라는 새로운 백그라운드 프로세스에 대하여
    소개하기로 한다.
    Explanation
    1. 개요
    SGA_TARGET 파라미터를 이용한 자동 SGA 튜닝이 어떻게 이루어지는지
    그 원리를 알아보도록 한다.
    자동 SGA 튜닝은 Oracle database 10g의 ADDM을 가능하게 하는 요소인
    메모리 advisor가 그 기능을 수행한다.
    자동 공유 메모리 관리 기능이 갖는 장점은 다음과 같은 몇 가지가 있다.
    첫째, workload가 변함에 따라 자동으로 공유 메모리가 적용이 된다.
    둘째, 메모리의 활용률을 극대화한다.
    세째, out-of-memory라는 메모리 부족 발생으로 인한 에러를 예방할 수 있다.
    즉, 오라클의 공유 메모리 영역 중 Shared pool size, Buffer cache size,
    Large pool size, Java pool size를 매뉴얼하게 셋팅할 필요가 없다.
    가용한 메모리의 사용을 보다 효과적으로 해주는 것 뿐만 아니라,
    메모리 자원을 얻는 데 필요한 비용을 줄여줄 수 있다.
    무엇보다 dynamic하고 flexible한 메모리 관리 구조를 통하여
    오라클 데이타베이스 관리를 단순화시켜 준다.
    2. MMAN 백그라운드 프로세스
    공유 메모리의 자동 튜닝을 위하여 MMAN이라는 백그라운드 프로세스가
    새로이 등장하였다.
    MMAN이라는 백그라운드 프로세스가 5분 마다 주기적으로 수집한
    작업 부하(Workload) 정보를 바탕으로 동적으로 구성이 된다.
    메모리는 가장 필요한 곳으로 동적으로 할당이 된다.
    SPFILE을 사용하면 MMAN이 변경한 파라미터들의 정보가 자동으로
    SPFILE에 저장이 된다.
    그러므로, 가능한 Oracle 9i 이상부터는 SPFILE 의 사용을 권장한다.
    왜냐 하면 다음과 같은 세 가지 장점이 있기 때문이다.
    첫째, 각 부분 크기의 권장안을 인스턴스 종료 후에도 보관할 수 있다.
    둘째, 저장되어진 각 파라미터들의 사이즈는 데이타베이스 기동 시 할당이 된다.
    세째, 각 파라미터들의 최적의 값을 찾는 데 드는 비용을 줄일 수 있다.
    이렇게 MMAN 이라는 프로세스에 의해서 자동 공유 메모리 관리 기능이
    구현이 되는 것이다.
    3. SGA_TARGET 파라미터를 통한 자동 공유 메모리 관리
    자동 공유 메모리 관리 기능을 사용하게 되면 오라클 SGA 관련 네 가지
    파라미터들을 DBA가 일일이 셋팅할 필요가 없다.
    오라클의 공유 메모리 크기는 SGA_TARGET 이라는 파라미터 하나로 다 조절이 된다.
    SHARED_POOL_SIZE, DB_CACHE_SIZE, LARGE_POOL_SIZE, JAVA_POOL_SIZE 라는
    파라미터들을 구성하는 데 관여하지 않아도 된다는 뜻이다.
    과거에는 이러한 파라미터들을 너무 낮게 잡게 되면 성능도 저하될 뿐만 아니라
    out-of-memory error인 ORA-4031 ERROR를 자주 만나게 되었고 메모리 낭비도 있었다.
    그러나, Oracle database 10g의 New Feature는 SGA_TARGET이라는 새로운
    파라미터만 셋팅하여도 되게 설계되었다.
    SGA_TARGET이라는 파라미터는 해당 인스턴스에 필요한 SGA의 최대 크기를 나타낸다.
    이 파라미터는 SGA 내의 모든 메모리들을 포함한다.
    즉, Automatic하게 사이즈가 결정되는 파라미터, 매뉴얼하게 결정되는 파라미터,
    startup 시에 할당되는 internal metadata 할당을 다 포함한다.
    10g 이전 버젼처럼 SGA의 TOTAL 크기를 정확히 컨트롤하는 것이 어렵지가 않다는 뜻이다.
    SGA_TARGET 파라미터를 셋팅할 때에는 다음을 염두에 두어야 한다.
    1) SGA 영역 중 자동 구성으로 조절되지 않는 영역이 있는데
    Redo Log buffer 와 Fixed SGA 영역, BUFFER KEEP, RECYCLE과 관련된 파라미터,
    STREAMS POOL 관련 파라미터들이다.
    2) SGA_TARGET 파라미터가 0으로 셋팅되면 자동 공유 메모리 기능은 DISABLE된다.
    SGA_TARGET 파라미터의 DEFAULT 값은 0이다.
    SGA_TARGET 파라미터가 0이 아닌 어떤 값으로 셋팅이 되어 있어도
    SHARED_POOL_SIZE 또는 DB_BLOCK_BUFFERS 와 같은 파라미터들은 여전히
    셋팅할 수는 있다.
    3) SGA_TARGET 파라미터가 설정되어 있지 않거나 0 으로 셋팅되어 있을 경우,
    자동 튜닝 파라미터들은 10g 이전 버젼에서와 같이 관리된다.
    단, 예외는 있다. SHARED_POOL_SIZE가 그 경우인데, 내부적인 STARTUP 시
    소모되는 오버헤드는 포함이 된다. 이 부분이 SHARED_POOL_SIZE에 포함이 된다.
    Oracle 10g 이전 버젼에서는 이 부분이 SHARED_POOL_SIZE에 포함되지 않았으나
    10g부터는 포함되게 되어 SHARED_POOL_SIZE를 좀 더 크게 잡아야 한다.
    구체적으로 10g에서는 SHARED_POOL_SIZE를 32m 정도 더 크게 잡아야 한다.
    예를 들어, Oracle 9i에서 SHARED_POOL_SIZE를 256M를 사용했었다면,
    Oracle 10g에서는 같은 효과를 얻으려면 288M 정도로 잡아야 한다.
    4) SGA_TARGET 파라미터가 0이 아닌 값으로 셋팅이 되어 있는 경우
    자동으로 튜닝되는 SGA 파라미터들은 모두 기본적으로 0으로 셋팅이 된다.
    이러한 파라미터들은 자동 공유 메모리 관리 알고리즘에 의하여 자동으로
    사이즈가 결정이 된다.
    그러나, 만약 이러한 자동 튜닝 파라미터들이 0이 아닌 어떤 값으로
    셋팅이 되어 있다면 명시한 값은 자동 튜닝 알고리즘에 의해 최저값을
    나타낸다.
    예를 들어, SGA_TARGET 파라미터가 8G로 셋팅되어 있고, SHARED_POOL_SIZE가
    1G로 셋팅되어 있다면 SHARED_POOL_SIZE는 절대 1G 아래로 떨어지지
    않음을 뜻한다.
    V$SGA_Dynamic_components 뷰를 조회하면 자동 튜닝 component들의
    실제 사이즈를 확인할 수 있다.
    SELECT component, current_size/1024/1024
    FROM v$sga_dynamic_components;
    4. 수동으로 튜닝되는 SGA 파라미터 설정
    SGA의 몇몇 구성 파라미터들은 자동으로 튜닝되지 않아서 매뉴얼하게 튜닝을 해야 한다.
    다음은 수동으로 튜닝되는 SGA 파라미터들이다.
    - KEEP 및 RECYCLE 버퍼 캐시
    - 멀티 블록 사이즈 캐시(DB_nK_cache_size)
    - 로그 버퍼
    - 스트림즈 POOL
    수동으로 튜닝되는 파라미터들은 반드시 사용자에 의해 명시되어져야 한다.
    이런 파라미터들은 10g 이전 버젼에서와 같이 정밀하게 크기가 제어되어야 한다.
    매뉴얼하게 튜닝되는 이러한 파라미터들은 SGA_TARGET에는 포함되지만,
    자동으로 튜닝되지는 않는다.
    예를 들어, SGA_TARGET 이 8G이면 MANUAL하게 수동으로 조절되는 파라미터들의
    사이즈의 합을 1G로 잡으면 7G는 자동으로 오라클이 알아서 설정한다.
    5. SGA_TARGET 파라미터의 설정 변경
    SGA_TARGET 파라미터의 RESIZING이란 SGA_TARGET 파라미터의
    설정 변경을 의미한다.
    SGA_TARGET 초기화 파라미터의 특징은 다음과 같다.
    첫째, 운영 중에 동적으로 변경이 가능하다.
    둘째, SGA_MAX_SIZE 내에서 크기를 증가시킬 수 있다.
    세째, 모든 구성 요소의 최저값의 합까지 크기를 감소시키는 것이 가능하다.
    또한, SGA_TARGET 파라미터의 설정은 오직 자동으로 튜닝할 수 있는
    파라미터들에만 영향을 준다.
    예를 들어, SGA_MAX_SIZE가 10G이고, SGA_TARGET이 8G로 가정을 한다.
    만약, DB_KEEP_CACHE_SIZE가 1G로 셋팅이 된다고 하면 SGA_TARGET 을
    최대 9G까지 늘릴 수 있다.
    추가적인 1G는 SGA_TARGET에 의해 조절되는 자동 튜닝 파라미터들에게 분배가 된다.
    DB_KEEP_CACHE_SIZE 는 영향을 받지 않는다는 뜻이다.
    이것은 SGA_TARGET 파라미터를 줄일 때에도 해당된다.
    6. 자동 공유 메모리 관리 비활성화
    이 기능을 비활성화하려면 SGA_TARGET 파라미터를 0으로 설정하면 된다.
    이렇게 SGA_TARGET 파라미터를 0으로 설정하게 되면 자동 튜닝 파라미터들은
    그 당시의 값으로 설정된다.
    그리고, 전체 SGA 크기에는 영향을 미치지 않는다.
    예) 변경 전 값
    SGA_TARGET=8G
    SHARED_POOL_SIZE=1G
    변경 후 값
    SGA_TARGET=0
    SHARED_POOL_SIZE=2G
    DB_CACHE_SIZE=4G
    LARGE_POOL_SIZE=512M
    JAVA_POOL_SIZE=512M
    SGA_TARGET이 8G로 셋팅되어 있고, SHARED_POOL_SIZE 파라미터가 1G로
    설정되어 있다가 SGA_TARGET을 0으로 변경하면 자동 튜닝 파라미터들은
    그 당시의 값으로 셋팅되고 전체 SGA 크기는 이전 SGA 크기를 초과하지 않는다.
    SHARED_POOL_SIZE가 2G로 셋팅이 된 것은 내부적으로 측정하여 결정된 수치이다.
    7. 동적 SGA 파라미터의 수동 변경
    자동 튜닝되는 파라미터를 수동으로 변경할 경우 다음과 같은 영향을 가진다.
    1) 만약 파라미터의 새로이 반영되는 값이 현재의 값보다 클 경우에는 즉시 반영이 된다.
    그러나, 새로이 반영되는 값이 현재의 값보다 작을 경우에는 현재의 값에는
    즉시 변화가 없고 최저값으로 셋팅이 된다.
    2) 자동으로 튜닝되는 파라미터들을 수동으로 변경하였을 경우에는
    SGA의 자동 튜닝 부분에 영향을 준다.
    RESIZE 수행 시에 사용되는 메모리는 자동 튜닝 파라미터들로부터
    더해지거나 감해질 뿐 매뉴얼하게 조절되는 파라미터들에는 영향을 주지 않는다.
    Example
    다음은 자동 튜닝 파라미터 설정 시 V$PARAMETER 조회 결과 예이다.
    SGA_TARGET=8G
    DB_CACHE_SIZE=0
    JAVA_POOL_SIZE=0
    LARGE_POOL_SIZE=0
    SHARED_POOL_SIZE=0
    SELECT name, value, isdefault
    FROM V$PARAMETER
    WHERE name LIKE '%size%';
    만약 SGA_TARGET 파라미터가 0이 아닌 값으로 셋팅이 되어 있는 경우
    자동 튜닝되는 파라미터들은 값을 명시하지 말라는 뜻이다.
    V$PARAMETER 뷰를 조회하였을 때 자동으로 튜닝되는 이러한 SGA 파라미터들의
    값은 모두 0이다.
    이것이 정상이고, isdefault 컬럼 값은 TRUE 이다.
    즉, 자동 공유 메모리 관리 기능을 구현할 때에는 이 파라미터들은
    매뉴얼하게 설정을 하지 않으면 된다.
    Reference Documents
    Oracle Database 10g New Features

  • Min Shared_pool_size

    HI ALL,
    Can i know Minimum shared_pool_size in 8.1.7.4 bec we are planning to upgrade my old prod server.
    Ravi

    Hi Ravi, there are additional memory required for internal Oracle 10g mechanism, such as for AWR, ASH buffer, etc. and you need to take into account different SGA calculation in 10g. In your case, I would agree with suggestion above to use SGA_TARGET parameter to make your life easier. Set this parameter to at least 10% larger than your current 8i total SGA size.
    There is a blog specifically on Oracle 10g shared pool:
    http://sysdba.wordpress.com/2006/03/30/how-to-calculate-the-minimum-size-of-the-shared-pool-in-oracle-10g/

  • How can i increase sga size in oracle 10g

    Hello friends
    how can i increase my sga size in oracle 10g
    Regards
    Vicky
    Edited by: Vignesh Chinnasamy on 31-Jul-2012 02:28

    HI
    **SQL> Show parameter sga ;**
    NAME                                 TYPE        VALUE
    lock_sga                             boolean     FALSE
    pre_page_sga                         boolean     FALSE
    sga_max_size                         big integer 2G
    sga_target                           big integer 2G
    **SQL> show parameter memory;**
    NAME                                 TYPE        VALUE
    hi_shared_memory_address             integer     0
    shared_memory_address                integer     0
    **[root@mte ~]# ulimit -a**
    core file size          (blocks, -c) 0
    data seg size           (kbytes, -d) unlimited
    file size               (blocks, -f) unlimited
    pending signals                 (-i) 1024
    max locked memory       (kbytes, -l) 32
    max memory size         (kbytes, -m) unlimited
    open files                      (-n) 1024
    pipe size            (512 bytes, -p) 8
    POSIX message queues     (bytes, -q) 819200
    stack size              (kbytes, -s) 10240
    cpu time               (seconds, -t) unlimited
    max user processes              (-u) 278528
    virtual memory          (kbytes, -v) unlimited
    file locks                      (-x) unlimited
    *[root@mte ~]#*

  • Oracle 10G and SGA

    Hi,
    i've a question about Oracle 10G and their SGA. When I do in SQLplus show sga, I get for example:
    SQL> show sga
    Total System Global Area 167772160 bytes
    Fixed Size 1247900 bytes
    Variable Size 58721636 bytes
    Database Buffers 104857600 bytes
    Redo Buffers 2945024 bytes
    when finding other parameter I get always '0', this was not in other releases...
    SQL> show parameter pool
    shared_pool_size big integer 0
    java_pool_size big integer 0
    large_pool_size big integer 0
    olap_page_pool_size big integer 0
    SQL> show parameter db_cache
    NAME TYPE VALUE
    db_cache_advice string ON
    db_cache_size big integer 0
    It seems that I have no control over setting those parameters, I remember at installation time it gave a % of the pc memory would be used, has it something to do with that? Can you chose between the automatic SGA-management and setting it by yourself?
    thanks
    greets

    Hi,
    I also find some trace files under my udump-dir, has this also to do with the SGA?
    Dump file c:\oracle\admin\orcl\udump\orcl_ora_3052.trc
    Wed Nov 16 15:42:40 2005
    ORACLE V10.2.0.1.0 - Production vsnsta=0
    vsnsql=14 vsnxtr=3
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
    With the OLAP and Data Mining options
    Windows XP Version V5.1 Service Pack 2
    CPU : 1 - type 586
    Process Affinity : 0x00000000
    Memory (Avail/Total): Ph:173M/502M, Ph+PgF:817M/1229M, VA:1755M/2047M
    Instance name: orcl
    Redo thread mounted by this instance: 0 <none>
    Oracle process number: 12
    Windows thread id: 3052, image: ORACLE.EXE (SHAD)
    *** SERVICE NAME:() 2005-11-16 15:42:40.974
    *** SESSION ID:(50.1) 2005-11-16 15:42:40.974
    kccsga_update_ckpt: num_1 = 8, num_2 = 0, num_3 = 0, lbn_2 = 0, lbn_3 = 0
    and:
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
    With the OLAP and Data Mining options
    Windows XP Version V5.1 Service Pack 2
    CPU : 1 - type 586
    Process Affinity : 0x00000000
    Memory (Avail/Total): Ph:210M/502M, Ph+PgF:931M/1229M, VA:1781M/2047M
    Instance name: orcl
    Redo thread mounted by this instance: 0 <none>
    Oracle process number: 0
    Windows thread id: 3596, image: ORACLE.EXE (SHAD)
    KCCDEBUG_LEVEL = 0
    Dynamic strand is set to TRUE
    Running with 1 shared and 10 private strand(s). Zero-copy redo is FALSE
    these comes every time after restarting the instance. Does this means that I will have hundreds of files after a time?

  • How to change SGA and PGA in 10g r2 RAC

    Hi,
    How to change SGA and PGA in 10g r2 RAC, its Linux.

    Hi,
    Here is the way i followed to change SGA and PGA in RAC.
    Action Plan to change the memory parameter in the production environment(5/21/2010)
    Note:
    =====
    Practice should be done in the DEV/TST environment before moving to Production;
    Although the procedure could be applied in the testing environment the changing values
    used in the testing environment should be modified since RAM number are not the
    same between the testing servers and production servers.
    1.     Make changes to these two parameters in one of
         the prod instance, e.g. PROD1
         ====================================================
         login as sysdba on sqlplus
    Change :
    alter system set sga_target=28G scope=spfile sid='*';
    Change :
    alter system set pga_aggregate_target=4G scope =spfile sid='*';
         sql>alter system set pga_aggregate_target=4G scope=both;
         sql>show parameter pga_aggregate_target;      
              -- should see the altered number on both instances
    Change:
    sql>alter system set sga_max_size=28G scope=spfile sid='*';
    sql>alter system set sga_max_size=28G scope=spfile ;
    sql>alter system set sga_target=28G scope=spfile;
    3.     shutdown database PROD (two instances should be shut down)
         $>srvctl stop database -d PROD
         $>. /$ORA_CRS_HOME/bin/crs_stat -- to check for the database status
    4.     bring up database PROD (two instance should be brought up)
         $>srvctl START database -d PROD
         $>. /$ORA_CRS_HOME/bin/crs_stat -- to check for the database status
         login into both instances as sysdba to check
         sql>show parameter pga_aggregate_target
         sql>show parameter sga_max_size
              -- should see the altered number still there in both instances
              -- from step 1
         -- After confirming above two parameters are altered on both instances,
         -- then issue the syntax below in one instance
    5)     check everything is ok

  • Sga in 10g

    hi all ,,,
    i have test server which is unix5.10 the databaseinstall on it is 10g
    i have rman in my system is 8g
    sga_max_size=1g
    sga_target=1g
    i have dmp in production database is 11g i want to imported in test server so as document say increase the sga to improve the performance
    of import as i saied i have 8g ram i increase the sga max=4g i restart the database and then i increase the target sga to 4g but the command is not completed
    take more than 10miniutes so i exit from the session and i restart the server
    reboot
    now i use this but see
    billdb00:oraccbs:/ccbs/appl/oracle$ ssh [email protected]
    ssh: connect to host 10.1.151.19 port 22: Connection refused
    can you please help me how to start the server ???is the server is turn off???can i start it in safe more and decrase the sga and then start in normal way????
    please advice

    861100 wrote:
    hi all ,,,
    i have test server which is unix5.10 the databaseinstall on it is 10g
    i have rman in my system is 8g
    sga_max_size=1g
    sga_target=1g
    i have dmp in production database is 11g i want to imported in test server so as document say increase the sga to improve the performance
    of import as i saied i have 8g ram i increase the sga max=4g i restart the database and then i increase the target sga to 4g but the command is not completed
    take more than 10miniutes so i exit from the session and i restart the server
    reboot
    now i use this but see
    billdb00:oraccbs:/ccbs/appl/oracle$ ssh [email protected]
    ssh: connect to host 10.1.151.19 port 22: Connection refused
    can you please help me how to start the server ???is the server is turn off???can i start it in safe more and decrase the sga and then start in normal way????
    I am completely lost , sorry. We can't tell you that the machine (server?) is off or not . Its you who have to tell us. There is no safe mode with oracle db and if it is your machine you are talking about, we are having a completely off-topic discussion. Please check and post what's the current, exact situation of your db . And second, don't bump up the thread. Its not Oracle Support .
    Aman....

  • Oracle SGA Real Time Consumption Information(9i,10g and 11g)

    Hello,
    I need to prepare a comparative analysis report of SGA for an Oracle Production Instance
    The analysis would show the pre-allocated memory to SGA components v/s real time consumption of memory by these SGA components. I need to do this for each of following components.
    SGA itself
    Fixed Size
    Variable Size
    Database Buffers
    Redo Buffers
    The pre-allocated memory to above SGA components can be obtained by querying v$sga. But from where do I get its real time(current) memory conusmption in Oracle Production environment.
    In addition to above, i need the same information (pre-allocated and real time consumption) for following.
    Keep buffer cache
    Recycle buffer cache
    Specific block size caches
    Shared pool
    Large pool
    Java pool
    streams pool
    Which tables do I need to consider in order to derive 1)pre-allocated memory and 2)real time consumption for above mentioned SGA components
    Please advice.
    Thank you for your time in reading this post.
    Thanks,
    Ruchir

    Hi,
    Have a look at v$sgastat. Also, use statspack in 9i and AWR reports on 10g. Also, the size of the caches won't grow unless they are used. The parameters you have specified within the parameter file, like sga_target (10g onwards) and possibly the other pools if you have specified them, will show you what the caches can grow to.
    For example, you could just log onto the DB and do show parameter sga_ or shared_pool and you will seee values for these. Also, it depends whether you are running in automatic memory management mode - where the sga_target parameter is set - or manual. 9i will be manual, but 10g could be auto. In manual case, 9i, check out the parameters individually.
    Also, read the docs about the parameters shown and you will see what it says abotu them. There will be lots in the docs about performance tuning and monitoring of the instance. You might even learn some other interesting facts while reading through the docs...
    Hope this helps,
    Rob
    http://www.ora00600.com

  • 10g SGA

    Hi Brother,
    I am using Oracle 10g and would like to set the SGA to auto ( now is manual set the buffer cache...etc. ) and Can I change when the DB is online? or I must restart the DB?
    Thanks

    You must change sga_target and sga_max_size initialization parameter.
    A sga_target can change online if you are using spfile. anyway sga_target is sub set of sga_max_size. (can not set sga_target > sga_max_size )
    And sga_max_size can not change online.... So You have to stop/start instance exactly.
    you can read more concept at tahiti.oracle.com
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14220/memory.htm#sthref1244
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14220/memory.htm#sthref1257

  • (10g)SGA_TARGET 파라미터를 이용한 AUTOMATIC MANAGMENT SGA COMPONENTS

    제품 : ORACLE SERVER
    작성날짜 : 2004-04-26
    PURPOSE
    이 문서는 SGA_TARGET 이라는 새로운 파라미터를 이용하여 Automatic
    management SGA Components에 대하여 알아보기로 한다.
    Explanation
    SGA_TARGET 파라미터를 이용한 Automatic management SGA Components에 대하여
    설명하기로 한다.
    Automatic management SGA Components using SGA_TARGET
    Oracle 10g부터 다음과 같은 각각의 SGA component에 대한 값들을 manual하게
    설정할 필요가 없다.
    shared_pool_size
    log_buffer
    java_pool_size
    large_pool_size
    buffer_cache_size
    위 SGA 파라미터들의 사이즈를 측정하고 initSID.ora file에 그 값을 설정할
    필요가 없음을 의미한다. 사실 SGA 크기를 정의하는 위 파라미터들을 설정하지
    않아도 된다.
    다만 10g 에서는 SGA_TARGET 이라는 새로운 파라미터만 셋팅하면 된다.
    SGA_TARGET 이라는 파라미터는 해당 instance에 필요한 SGA의 최대 크기를
    가리킨다.
    SGA_TARGET을 152M 로 잡았다고 가정하자. 이것은 SGA가 커질 수 있는 최대 크기가
    152M 라는 의미이다. Shared pool, buffer cache, large pool, java pool 과 같은
    SGA component들은 이 maximum 사이즈 내에서 할당될 것이다.
    오라클은 이러한 component들의 초기 값을 자동으로 계산하고 필요에 따라
    자동으로 resize한다.
    즉, SGA_TARGET 만 셋팅되어 있으면 shared pool, buffer cache, large pool,
    java pool에 대하여 값을 명확히 지정할 필요가 없다.
    Example
    SGA_TARGET=152M 로 잡았다고 가정한다.(block size is 8K).
    SQL> show parameter sga_target
    NAME TYPE VALUE
    sga_target big integer 152M
    오라클은 다음과 같이 SGA component들의 사이즈를 정의한다.
    SQL> show sga
    Total System Global Area 159383552 bytes
    Fixed Size 769328 bytes
    Variable Size 72270544 bytes
    Database Buffers 62914560 bytes
    Redo Buffers 23429120 bytes
    여기서 주목할 점은 다음과 같다.
    1) SGA_TARGET을 셋팅하면 SGA_MAX_SIZE 의 값은 또한 SGA_TARGET 으로 셋팅된다.
    즉, SGA_TARGET = SGA_MAX_SIZE.
    SQL> show parameter sga
    NAME TYPE VALUE
    lock_sga boolean FALSE
    pre_page_sga boolean FALSE
    sga_max_size big integer 152M
    sga_target big integer 152M
    2) SGA_TARGET 의 값을 SGA_MAX_SIZE보다 더 크게 설정할 수 없다.
    즉, SGA_TARGET <= SGA_MAX_SIZE.
    SQL> alter system set sga_target=160M;
    alter system set sga_target=160M
    ERROR at line 1:
    ORA-02097: parameter cannot be modified because specified value is invalid
    ORA-00823: Specified value of sga_target greater than sga_max_size
    Reference Documents
    <Note:256913.1>
    Oracle Database Concepts 10g Release 1 (10.1)
    Part No. B10743-01
    Chapter 8: Memory Architecture

    842638 wrote:
    hi experts.. please answer the question
    Im on 10.2.0 linux....
    sga_target=200m
    sga_max_size=400m
    if automatic components take 180MB out of 200MB and lets say manaul components take 10M. so is the remaing 10MB wasted? yes or noWhy wasted? Only after giving memory to the manual components, whatever is left would be given to the automatic components. So nothing would be wasted by this approach.
    HTH
    Aman....

Maybe you are looking for

  • Memory upgrade failed -satellite P205

    Satellite P205-S6287 has 2 GB RAM and specs say two slots and should support 4 GB max. I installed new RAM and laptop turns on very briefly, no screen, just power on light and a disk rumble for 1-2 seconds then nothing else with both RAM slots loaded

  • How can i make a full screen image on a one page website

    I am making a one page website with 5 items. I want with each item a fullscreen (responsive) image. Can i do that in Adobe muse?

  • How do I convert a JPEG file to an Adobe Reader (PDF) file?

    Please help me. I have scanned an image of a text in a book.  The scanned image is automatically uploaded into a JPEG file.  How do I convert this into a PDF file?

  • Error in RFC Sender Adapter

    Hello Experts, Right now i m working on the scenario SRM -> XI -> 3rd party system. Here i want to send data from SRM to XI, and for that i m using Sender RFC Adapter. I have configured RFC Sender channel in XI and created RFC Destination into the SR

  • JSP Form to many pages

    Hi, I have the following application structure: PersonalDetails.jsp Attributes: UserName, FirstName Surname etc.. AccountDetails.jsp Attributes: Address, Payment Information etc.. RegistrationConfirmation To manage the user registration, I am using o