Components of SGA?

I'm aware of
1) sga_max_size should be >= Total SGA.
2) Size of the Total SGA = (shared_pool_size+large_pool_size+java_pool_size+db_keep_cache_size+db_recycle_cache_size+db_2k_cache_size+db_4k_cache_size+db_8k_cache_size+db_16k_cache_size+db_32k_cache_size+db_cache_size)
Whether size of the PGA and/or size of the log_buffer have to account for Size of the Total SGA?
Is there any thumb rule for sizing the PGA?
Thanks in advance.

Your main link is
http://tahiti.oracle.com
which is a searchable interface to all documentation.
Kindly do not ask anyone to do something you can easily do yourself.
Sybrand Bakker
Senior Oracle DBA

Similar Messages

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

Setting the SGA Size

Hi,
In one of the forums , I found this artical which explains how different components of SGA was allocated keeping in mind about the available RAM.I would like to know whether the approach impemented here can be considered while installing databases
hardware with 1GB of memory and installing Oracle 9i on this server. This server will be a dedicated Oracle server with only one instance on it.
In estimating the parameters required in init.ora file, I will do a heuristic approach. I assume that I have 1GB of RAM and I will be installing one Oracle instance on the hardware!
I will allocate somewhere in the region of 60-75% of RAM to my SGA i.e. Total SGA = RAM x 0.7 = 1000MB * 0.7 = 700MB
For a multi purpose database I will opt for a database block size "db_block_size" of 8192 bytes (see notes below)
I will give database buffer cache "db_buffer_cache" 45% share of SGA i.e. 700MB * 0.4 =315 MB.
Remember db_buffer_cache = db_block_buffers x db_block_size
For 315MB of db buffer cache, using the above formula I will have 315*1024*1024/8192 = 40320 "db_block_buffers".
I will give "shared_pool" 45% of SGA = 315MB and 5% to "shared_pool_reserved_size" = 16MB.
For "large_pool_size" I will choose initial value of 20MB. This should be large enough for RMAN etc.
For "java_pool_size" size I will allocate 20MB to start with.
I will allocate 512KB to "sort_area_size" and will set "sort_area_retained_size" = 0.
For "log_buffer, I will consider a range of 512KB-1MB max (see notes below). I will go for 512KB to start with.
So in summary I will have
db_block_size =8192
shared_pool_size =330301440 # 315MB
shared_pool_reserved_size =16515072 # 15M
large_pool_size =20971520 # 20MB
java_pool_size =20971520 # 20MB
log_buffer =524288 # 512KB
sort_area_size =524288 # 512KB
sort_area_retained_size =0 # 0 K
db_block_buffers =40320

Hi,
I already mentioned that I went across the article from one of the forums.I pasted it here to know about the internal allocation of memory to the db_cache_size and the shared_pool_size.Since in the article,the db_cache_size and shared pool size are equally allocated and all other memory structures allocated on a specific basis,so can this allocation by means of some selected random percentage of memory can be implemented?

Sga size decreases or not

Hi i set the parameters SGA_TARGET and SGA_MAX_SIZE. as transactions increases the size of SGA will increase but will it decreases when number of transactions comes down?
thanks in advance

i set the parameters SGA_TARGET and SGA_MAX_SIZE. as transactions increases the size of SGA
SGA size will not increase unless you set SGA_TARGET to a higher number from its current setting. What will grow or shrink is some of the components of SGA like the buffer cache or shared pool.
Please read this: http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/create.htm#sthref383

Kernel para and sga,pga sizing

Hello,
OS-HP-UX(configured to use high sga /no restrictions)
Current database is running without any issue
Due to increase in physical ram i plan to increase sga and pga(ram is increase about 3 times)
My question:
1)should i also increase sga and pga in same propotion (3 times then existing)
or use 70% ROT formula
2)whatever figure i arrive by analysis for increasing sga,do i need to change kernel parameters also
(does i requre to change kernel parameter every time ram and sga is increased)
Please suggest
Thanks

880991 wrote:
Ok some questions based on your reply:
1)then how any gain in upgrading memory above 4 GB if shmmax cannot be more then 4 GB (32 bit OS),then
SGA also cannot be > 4GB (As per documents SHMMAX should be > SGA)Because the SGA doesn't have to be in one segment. Which version of Oracle are you looking at? It makes a difference!
http://kevinclosson.wordpress.com/2009/07/27/little-things-doth-crabby-make-part-x-posts-about-linux-hugepages-makes-some-crabby-it-seems/
>
2)I read if Operating system is linux can use SGA above 4GB,in fact one of friend told they implemented SGA
4GB on linux configuring VLM/Huge pages,so in that case ( VLM ) needs to set SHMMAX > 4GB (as per memory ROT) of VLM take cares of SGA > 4GB even if SHMMAX is not setintrestingly my friend also mentioned that in there server VLM is set and shmmax is set < 4 GB and SGA > 4GB
still it works without problem when checking SGA usage in dyanamic views its shown as using above 4 GB
,it contradicts what i read in documents,how this is working ,anyone have idea?[url http://download.oracle.com/docs/cd/B28359_01/server.111/b32009/appi_vlm.htm]No contradiction.
Also VLM implementation is restricted to Linux or it can be on set on Unix as well and if its set do all components
of SGA benefit or only buffer cache?
ThanksIt varies, some unix are quite different than others. Specific answers can only be given to specific configurations. I really have to wonder when you are asking about hp-ux and 32 bit.

DOUBT REGARDING SGA

Hello,
can u plz explain the difference between SGA_TARGET and SGA_MAX_SIZE
parameters
if i specified sql>sho sga
Total System Global Area 1401424024 bytes
Fixed Size 456856 bytes
Variable Size 738197504 bytes
Database Buffers 629145600 bytes
Redo Buffers 33624064 bytes
in the above Total System Global Area indicates what? i mean this value
is equal to SGA_MAX_SIZE
can u plz suggest
Regards,

In an Oracle database, the SGA (System Global Area) is the part of the RAM used by the Oracle processes. This part of memory is shared by all Oracle processes. All necessary information necessary for the instance operation are present here.
In general, the SGA consists of the following:
•     Dictionary Cache: Information about data dictionary tables, such as information about account, datafile, segment, extent, table and privileges
•     Redo Log Buffer: Information about committed transactions that are not yet written to online redo log files.
•     Shared pool: The parsed cache of common used SQL statements and the data dictionary cache containing tables, views and triggers
•     JAVA pool: For parsing Java statements.
SGA_TARGET
============
The SGA_TARGET initialization parameter reflects the total size of the SGA and includes memory for the following components:
•     Fixed SGA and other internal allocations needed by the Oracle Database instance
•     The log buffer
•     The shared pool
•     The Java pool
•     The buffer cache
•     The keep and recycle buffer caches (if specified)
•     Nonstandard block size buffer caches (if specified)
•     The Streams pool
SGA_MAX_SIZE
=============
Oracle Database can set limits on how much virtual memory the database uses for the SGA. It can start instances with minimal memory and allow the instance to use more memory by expanding the memory allocated for SGA components, up to a maximum determined by the SGA_MAX_SIZE initialization parameter.
Note: For optimal performance in most systems, the entire SGA should fit in real memory.
Kindly read more about Oracle Memory Architecture
http://download.oracle.com/docs/cd/B19306_01/server.102/b14220/memory.htm#sthref1257
With Regards,

To find out the min and max memory been used by each parameter under SGA_MA

Hi,
Can any please tell me how to find out the min and max memory been used by each parameter under SGA_MAX and SGA_TARGET ? below is the db CRMS65T. If any such script is there please provide me
SQL> select name from v$database;
NAME
CRMS65T
SQL> show parameter sga
NAME                                 TYPE        VALUE
lock_sga                             boolean     FALSE
pre_page_sga                         boolean     FALSE
sga_max_size                         big integer 1000M
sga_target                           big integer 1000MThanks in advance

Can any please tell me how to find out the min and max memory been used by each parameter under SGA_MAX and SGA_TARGET ? below is the db CRMS65T. If any such script is there please provide meI guess your question is, each memory components of SGA? if so
SQL> select * from v$sgainfo;
NAME                                  BYTES RES
Fixed SGA Size                      2088504 No
Redo Buffers                       18882560 No
Buffer Cache Size                 616562688 Yes
Shared Pool Size                  301989888 Yes
Large Pool Size                     4194304 Yes
Java Pool Size                      4194304 Yes
Streams Pool Size                         0 Yes
Granule Size                        4194304 No
Maximum SGA Size                  947912704 No
Startup overhead in Shared Pool   125829120 No
Free SGA Memory Available                 0Also check
SQL> select COMPONENT,CURRENT_SIZE,MIN_SIZE,MAX_SIZE,USER_SPECIFIED_SIZE from v$sga_dynamic_components;
shared pool                                                         301989888 301989888          0           209715200
large pool                                                            4194304    4194304          0             4194304
java pool                                                             4194304    4194304          0             4194304
streams pool                                                                0          0          0                   0
DEFAULT buffer cache                                                616562688 616562688          0           603979776
KEEP buffer cache                                                           0          0          0                   0
RECYCLE buffer cache                                                        0          0          0                   0
DEFAULT 2K buffer cache                                                     0          0          0                   0
DEFAULT 4K buffer cache                                                     0          0          0                   0
DEFAULT 8K buffer cache                                                     0          0          0                   0
DEFAULT 16K buffer cache                                                    0          0          0                   0
DEFAULT 32K buffer cache                                                    0          0          0                   0
ASM Buffer Cache                                                            0          0          0           603979776
13 rows selected.
SQL>Edited by: CKPT on Sep 19, 2011 8:55 AM

ORACLE error ORA-04031: unable to allocate 16 bytes of memory

Error
UDI-04031: operation generated ORACLE error 4031
ORA-04031: unable to allocate 16 bytes of shared memory ("shared pool","SELECT j
generated during import operation, using documentation about migration from 10g XE to 11g XE.

Hello,
you could try to override the automatic memory management and setup your SGA to be larger by setting SGA_TARGET. If that doesn't help yet, you could even try to configure the memory size for the components in SGA manually, but I guess this won't be necessary.
After your import is done, I'd recommend to use automatic memory management again.
See the XE 2 Day DBA for details, especially the section on [url http://download.oracle.com/docs/cd/E17781_01/server.112/e18804/memory.htm#ADMQS174]Managing Memory. It's not a complete guide, but a rough introduction, but it'll probably help you understand the memory concepts in the database.
Keep in mind that you may only assign 1 GB of memory in total when you setup your memory manually.
-Udo

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

Oracle SGA components manual allocation

All,
Phyical memory : 420G My database version : 11.2.0.3 running on linux machine.
Memory_target = 200G . I would like to allocate this value to following SGA components. I don't want to automatic memory management enabled. Can you please guide me how to split 200G for following components. Is there any percentage for each components ?
db_cache_size
db_recycle_cache_size
db_keep_cache_size
large_pool_size
java_pool_size
shared_pool_size
pga_aggregate_target
streams_pool_size
log_buffer
Thanks

There is no 'default' settings for the components. Oracle tell you, when you create a database with DBCA, that the values provided by that tool are for a sample database and you should tune them to how you see fit.
This is what I would do (assuming this is a test environment, of course):
- If you're using HugePages, disable it.
- Run with AMM but give some key components a 'minimum' value (such as SGA, PGA, shared_pool, etc) so it's not too crazy. Setting everything at 0 can have performance issues with some databses, strangely.
- Run an entire workload cycle (day, week, etc) - enough batch processing to mimic a realistic workload on Production
- Check out the dynamic views/AWR reports to see what the database advises with the various components.
- If you want to use HugePages, then set the SGA and PGA to whatever you've determined from the AWR reports. You can choose whether to specify minimum values for the SGA components.
- If you're not using HugePages, you really should use AMM. What I do is give the SGA and PGA minimum values and allow the database to decide which one gets the 'extra' memory that's left over. That way, the SGA doesn't drop to an impossibly small size and cause everything to crap out.
Mark

Constant change in SGA components up-down

hello,
we are developement database oracle 10gR2 on windows plateform
ASMM is on.
i am surprised to know that our smart oracle is doing a lot of shrink and grow on SGA components specially shared pool and db buffer cache
is it ok or some thing wrong?
i checked another development DB and found that it should be infrequent..
do i need to turn of the ASMM?
the out put from a query shown this
WHEN            COMPONENT                                                        OPER_TYPE     INITIAL_SIZE/1024      FINAL_SIZE/1024
May-16:19:53:17 DEFAULT buffer cache                                             STATIC        3031040                3014656
May-16:19:53:17 large pool                                                       GROW          0                      16384
May-16:19:53:17 DEFAULT buffer cache                                             INITIALIZING 3031040                3014656
May-16:19:53:17 ASM Buffer Cache                                                 STATIC        0                      0
May-16:19:53:17 DEFAULT 32K buffer cache                                         STATIC        0                      0
May-16:19:53:17 DEFAULT 16K buffer cache                                         STATIC        0                      0
May-16:19:53:17 DEFAULT 8K buffer cache                                          STATIC        0                      0
May-16:19:53:17 DEFAULT 4K buffer cache                                          STATIC        0                      0
May-16:19:53:17 DEFAULT 2K buffer cache                                          STATIC        0                      0
May-16:19:53:17 RECYCLE buffer cache                                             STATIC        0                      0
May-16:19:53:17 KEEP buffer cache                                                STATIC        0                      0
May-16:19:53:17 DEFAULT buffer cache                                             STATIC        0                      3014656
May-16:19:53:17 streams pool                                                     STATIC        0                      0
May-16:19:53:17 java pool                                                        STATIC        0                      16384
May-16:19:53:17 large pool                                                       STATIC        0                      16384
May-16:19:53:17 shared pool                                                      STATIC        0                      688128
May-16:20:30:59 shared pool                                                      GROW          688128                 704512
May-16:20:30:59 DEFAULT buffer cache                                             SHRINK        3014656                2998272
May-17:10:50:40 DEFAULT buffer cache                                             SHRINK        2998272                2981888
May-17:10:50:40 streams pool                                                     GROW          0                      16384
May-17:10:50:42 DEFAULT buffer cache                                             SHRINK        2981888                2965504
May-17:10:50:42 streams pool                                                     GROW          16384                  32768
May-17:11:04:38 shared pool                                                      GROW          704512                 737280
May-17:11:04:38 DEFAULT buffer cache                                             SHRINK        2965504                2932736
May-17:11:05:08 shared pool                                                      GROW          737280                 770048
May-17:11:05:08 DEFAULT buffer cache                                             SHRINK        2932736                2899968
May-17:11:06:01 DEFAULT buffer cache                                             SHRINK        2899968                2883584
May-17:11:06:01 shared pool                                                      GROW          770048                 786432
May-17:11:20:38 DEFAULT buffer cache                                             SHRINK        2883584                2850816
May-17:11:20:38 shared pool                                                      GROW          786432                 819200
May-28:15:24:06 DEFAULT buffer cache                                             SHRINK        2850816                2818048
May-28:15:24:06 shared pool any suggations/advice/help??
thank you

I saw this a lot on an highly OLTP system once at 10gR2. My SGA was thrashing wildly between buffer cache and shared pool due to a bug in AMM and it was causing performance impact (cursor S pin on X) for no apparent reason. This was particularly prevalent when I moved from a two to a three node cluster.
If you check out v$sga_resize_ops and see if you see a lot of thrashing (sometimes once every three seconds on one instance for 3 hours, then it'd switch to another instance), then my solution was to hardcode the various settings and disable AMM. However, in your case, you're resizing fairly irregularly - probably due to either an undersized component or workload changes. AMM is meant to do what you're describing - is it causing you any issue or is it something that you've noticed and are curious about?

Initial sizing of sga memory components.

Hi to all,
I want to know that how many granules be allocated to each sga components initially when we use automatic memory menagement. Let's say SGA _target is 1g. version 10.2.0
thnxs in advance.

The SGA comprises a number of memory components, which are pools of memory used to satisfy a particular class of memory allocation requests. Examples of memory components include the shared pool (used to allocate memory for SQL and PL/SQL execution), the java pool (used for java objects and other java execution memory), and the buffer cache (used for caching disk blocks). All SGA components allocate and deallocate space in units of granules. Oracle Database tracks SGA memory use in internal numbers of granules for each SGA component.
The memory for dynamic components in the SGA is allocated in the unit of granules. Granule size is determined by total SGA size. Generally speaking, on most platforms, if the total SGA size is equal to or less than 1 GB, then granule size is 4 MB. For SGAs larger than 1 GB, granule size is 16 MB. Some platform dependencies may arise. For example, on 32-bit Windows NT, the granule size is 8 MB for SGAs larger than 1 GB. Consult your operating system specific documentation for more details.
You can query the V$SGAINFO view to see the granule size that is being used by an instance. The same granule size is used for all components in the SGA.
If you specify a size for a component that is not a multiple of granule size, Oracle Database rounds the specified size up to the nearest multiple. For example, if the granule size is 4 MB and you specify DB_CACHE_SIZE as 10 MB, the database actually allocates 12 MB.

SGA components

hai
SGA contains many other structures apart from shared pool buffer etc.
and they are as given below
-lock and latch management
-statistical data
the question is that what basically these terms mean and what meaning they are having here in oracle.

Search the docu set please -- you'll get definitions, context and even something to reference. These are examples from two quick searches:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14220/consist.htm#sthref2142
http://download.oracle.com/docs/cd/B19306_01/server.102/b14211/instance_tune.htm#sthref1030
http://download.oracle.com/docs/cd/B19306_01/server.102/b14211/instance_tune.htm
http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/stats002.htm#i375475
http://download.oracle.com/docs/cd/B19306_01/server.102/b14211/stats.htm

ASMM - sga dynamic components and standby

Are SGA dynamic modifications "transferred" from the primary to the standby?
i.e: if __shared_pool is resized in primary will this also trigger standby?
Trying to determine if dynamic pools may somehow end up being different upon switchover/failover or if it's possible that upon switchover standby's dynamic shared_pool size results smaller than that of former primary

Absolutely, yet there are some things DG broker does upon switch over. Was wondering if somehow standby would be "updated" upon switcher...
But then again, it's SGA as a hole may be smaller to begin with...
Were you to tell if the following is true or false:
"After activation standby database may have a SGA configuration different than that of primary"
what would you say?
Hole intention here is to determine whether after a switch over it's possible to start getting ORA-04031 on account of dynamic pools being different
and oracle struggling to re-size them...
Suppose we have a 6Gb SGA... primary has been working full steam for say 2 months and dynamic pools are set by oracle in the following way:
shared_pool...3Gb
cache...3Gb
Now if standby has not acknowledged those dynamic changes, it may be using values of it's own... maybe a larger cache... say
shared_pool...1Gb
cache...5Gb
Now we switch-over and if sga settings are not "synced", then new primary will have 2Gb less of shared pool...
Application kicks in, shared pool runs low... Oracle will have to move 1 or 2Gbs from cache to shared pool, this will cause serious latching and most likely ORA-04031
so is that likely to happen?

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

Components of SGA?

Similar Messages

Maybe you are looking for