Global memory

Hi ,
could any one tell me ,whether we can pass internal table by using SPA AND GPA(SAP MEMORY).
REGARDS
SANJEEV

You can use 'export to memory' and 'import from memory' statements in your report programs to pass internal tables from original program to called program. The SPA GPA statements are useful to pass data to screens of called program.

Similar Messages

How do we Use Internal table in Global Memory ?

Hi All ,
Can anyone help me with how to create and use an internal table in SAP global memory ?
Regards,
Ranjita

Hi,
Try with GET PARAMETER AND SET PARAMETER
Refer the below link,
Export Import Internal tables across two z programs
Regards,
Vijay

Oracle Rdb JDBC: Insufficient global memory

Environment:
IA64 OpenVMS 8.3
Java RTE version 1.5
Oracle RDB version 7.2-2
SQL/services version 7.3
JDBC server for RDB version 7.3
JDBC-Thin driver version 7.3
The problem:
we have a JDBC dispatcher with 20 executor processes.
We have a client application that performs connect/disconnect to the database before/after each sql select statement.
Sometimes the query doesn't terminate successfully and we get the following error in
the JDBC log file:
RDB$CLIENT_ID_0000038D C00000000*T 201010-21 12:19:13.409 : [email protected] msg : INIT_V713 send>>>>>>>>>>>>> System Error : Insufficient global memory
any help?

I would start with RDB administration/configuration documents. It's a DBMS server issue,
not JDBC. Though it may or may not help, in principal, if yo can keep and re-use connections
instead of repeatedly opening and closing, it is usually faster and less burdensome on the DBMS...

Flash global memory keeps setting its self to 0

flash global memory sets its self to zero for web pages i have visited. the pages i have visited i want to have memory for them so they can have there flash cookies so the page displays properly and remembers my previous settings. latest version of flash, latest version of firefox

linux os symlinked flash to the firefox plugin directory.

MaxDB Global Memory

Ho do i know how much memory is reserved for Database or how much memory is used by MaxDB. Is there any parameter like Oracle SGA.
Thanks in advance.

> But again how to find out how much of my physical memory is used by DB. Out of 5G suppose say it uses 2 G of physical memory & 3 G of virtual .
>
> How to find that.
Depends on your operating system.
This is something that only the operating system knows and manages.
It is totally transparent to the processes.
On UNIX/Linux you may check ps or top commands, on Windows the taskmanager or the sysinternals process monitor should do.
In any case, the goal has to be that the database process memory is always kept in RAM and never paged. Otherwise the DB Cache wouldn't make much sense, would it?
The database 'knows' better, which data to keep in memory and which to put back to disk than the operating system does.
Therefore: better have a smaler DB cache but be sure that this one fits into your RAM.
regards,
Lars

Memory speed after upgrade

I recently bought an 11,3 iMac with the Core i7 2,93Ghz CPU and 4GB of RAM.
The system profiler reported the RAM working at 1333MHz which is right.
I then bought another 2x2GB modules with the same specifications (DDR3 1333MHz), but after installing the memory, the System Profiler reports all RAM modules working at 1067MHz.
Did anyone else experience this or could it be that System Profiler is just reporting the wrong speed?
How can I be sure of what is really happening?
Thanks in advance.

Update:
I tried to boot the system with the new modules installed only. System Profiler reported 1067 MHz for both. PRAM resetting did not make a difference.
I then put back the original ones and everything was back to normal.
I guess they just mislabeled the new RAM modules and they are indeed 1067 Mhz forcing the other modules to work at the same speed...
Trying to work this out with the vendor (Global Memory UK). Meanwhile, already ordered a new pair from Crucial.

Race conditions - can you actually lose the data in memory?

I've seen posts where a race condition can actually destroy the contents of a global memory. I understand about not getting the right information if your read just beats your write, but can it actually lose the data altogether? This would mean you have to semaphore every time you write to a global if you have something polling on it to guarantee the data doesn't get lost. I've never seen this in any example programs - its hard to believe!

I think the idea is merely that when you write to a global (or any)
variable the previous contents are overwritten. If you intended to read the
global before the write but the write ends up happening first then you lose.
"mikema111" wrote in message
news:[email protected]..
> I've seen posts where a race condition can actually destroy the
> contents of a global memory. I understand about not getting the right
> information if your read just beats your write, but can it actually
> lose the data altogether? This would mean you have to semaphore every
> time you write to a global if you have something polling on it to
> guarantee the data doesn't get lost. I've never seen this in any
> example programs - its hard to be
lieve!

SAP 64bit Linux application server (Linux on Power) memory config issues

Hello Everyone,
Let me give some background. I have been tasked with replacing our AIX6.1 SAP application server with new Linux on Power servers (SLES11SP3)
Our current production BW application servers (AIX) are running fine given their current setup. We are fine implementing the same size of the AIX systems on the new Linux systems, but we now have more room to grow in the fur, however when I tried to implement the Linux server using the same memory sizing I am getting runtime errors: "TSV_TNEW_PAGE_ALLOC_FAILED" with a specific user created program and process chain. The AIX servers do not run into this issue running the exact same program. When this process runs, it utilizes 3 BTC process for the program.
Using the note 941735, I have tried to correctly setup the system using STD memory implementation, however I have a feeling that I am missing something or setup something incorrectly which is causing the above issue. Looking in ST02 here is the SAP buffer parameters for two of the systems. Perhaps someone might notice something that I am not see or point me in the right direction. Please let me know if more parameters from the profile are needed. Thanks!
AIX system (existing):
ztta/roll_area              6500000    Byte Roll area per workprocess (total)
ztta/roll_first             1          Byte First amount of roll area used in a dialog WP
ztta/short_area             3200000    Byte Short area per workprocess
rdisp/ROLL_MAXFS            32768      8 kB Maximum roll file size
rdisp/ROLL_SHM              16384      8 kB Part of roll file in shared memory
rdisp/PG_SHM                16384      8 kB Part of paging file in shared memory
rdisp/PG_LOCAL              150        8 kB Paging buffer per workprocess
em/initial_size_MB          2027       MB   Initial size of extended memory
em/blocksize_KB             4096       kB   Size of one extended memory block
em/address_space_MB         4092       MB   Address space reserved for ext. mem. (NT only)
em/global_area_MB           256        MB   Extended global memory
ztta/roll_extension         2000000000 Byte Max. extended mem. per session (external mode)
abap/heap_area_dia          2000000000 Byte Max. heap memory for dialog workprocesses
abap/heap_area_nondia       2000000000 Byte Max. heap memory for non-dialog workprocesses
abap/heap_area_total        2000000000 Byte Max. usable heap memory
abap/heaplimit              250000000 Byte Workprocess restart limit of heap memory
abap/use_paging             0               Paging for flat tables used (1) or not (0)
abap/shared_objects_size_MB 20         MB   Shared objects
Linux system (new):
ztta/roll_area              6500352    Byte Roll area per workprocess (total)
ztta/roll_first             1024       Byte First amount of roll area used in a dialog WP
ztta/short_area             3200000    Byte Short area per workprocess
rdisp/ROLL_MAXFS            131072     8 kB Maximum roll file size
rdisp/ROLL_SHM              32768      8 kB Part of roll file in shared memory
rdisp/PG_SHM                16384      8 kB Part of paging file in shared memory
rdisp/PG_LOCAL              150        8 kB Paging buffer per workprocess
em/initial_size_MB          4092       MB   Initial size of extended memory
em/blocksize_KB             4096       kB   Size of one extended memory block
em/address_space_MB         4096       MB   Address space reserved for ext. mem. (NT only)
em/global_area_MB           256        MB   Extended global memory
ztta/roll_extension         2000683008 Byte Max. extended mem. per session (external mode)
abap/heap_area_dia          2000683008 Byte Max. heap memory for dialog workprocesses
abap/heap_area_nondia       2000683008 Byte Max. heap memory for non-dialog workprocesses
abap/heap_area_total        2000683008 Byte Max. usable heap memory
abap/heaplimit              250609664 Byte Workprocess restart limit of heap memory
abap/use_paging             0               Paging for flat tables used (1) or not (0)
abap/shared_objects_size_MB 20         MB   Shared objects

Yes sapconf has been installed. sapconf however only sets the kernel settings.
I was able to resolve the issue by having Zero Admin tool using 'es/implementation = map' and setting the PHYS_MEMSIZE to the desired amount. Then commenting out all the values that are defaulted in the 32bit version of the memory management guide for linux and let it size many of the values. Then I simply copied those from st02. I updated the profile with those values to override default for 'es/implementation = std' and commented out PHYS_MEMSIZE as it is not needed. In a nut shell, the following parameters were updated.
es/implementation = std
em/address_space_MB = 4096
em/blocksize_KB = 4096
em/initial_size_MB = 14320
em/max_size_MB = 14326
rdisp/PG_MAXFS = 131072
rdisp/PG_SHM = 16384
rdisp/ROLL_MAXFS = 131072
rdisp/ROLL_SHM = 131072
ztta/roll_area = 6500352
ztta/roll_extension = 4000000000
ztta/roll_extension_dia = 4000000000
ztta/roll_extension_nondia = 4000000000
ztta/roll_first = 1

How to display value in memory

How to display value in memory, except call function 'LIST_FROM_MEMORY' .
Thanks.

Hi
See this
may be useful
SAP memory is a memory area to which all main sessions within a SAPgui have access. You can use SAP memory either to pass data from one program to another within a session, or to pass data from one session to another. Application programs that use SAP memory must do so using SPA/GPA parameters (also known as SET/GET parameters). These parameters can be set either for a particular user or for a particular program using the SET PARAMETER statement. Other ABAP programs can then retrieve the set parameters using the GET PARAMETER statement. The most frequent use of SPA/GPA parameters is to fill input fields on screens
SAP global memory retains field value through out session.
set parameter id 'MAT' field v_matnr.
get parameter id 'MAT' field v_matnr.
They are stored in table TPARA.
ABAP memory is a memory area that all ABAP programs within the same internal session can access using the EXPORT and IMPORT statements. Data within this area remains intact during a whole sequence of program calls. To pass data
to a program which you are calling, the data needs to be placed in ABAP memory before the call is made. The internal session of the called program then replaces that of the calling program. The program called can then read from the ABAP memory. If control is then returned to the program which made the initial call, the same process operates in reverse.
ABAP memory is temporary and values are retained in same LUW.
export itab to memory id 'TEST'.
import itab from memory Id 'TEST'.
Here itab should be declared of same type and length.
http://www.sap-img.com/abap/difference-between-sap-and-abap-memory.htm
ABAP Memmory & SAP Memmory
http://www.sap-img.com/abap/difference-between-sap-and-abap-memory.htm
http://www.sap-img.com/abap/type-and-uses-of-lock-objects-in-sap.htm
Reward points for useful Answers
Regards
Anji

Memory Analysis for a program

Hi All,
In production sometimes a data load fails because of the less ABAP memory available.
For a perticular load ABAP memory goes till 4 Gb and more and after that load fails with short dump.
This time i change a start routine logic and split a complex start routine logic in two programs.
Now i want to check about what memory my new programs are taking.
1. One of the programs is in start routine itself .
2. Second program is SE38 program.
How I can see the memry consumption while data load.
thanks
Mukesh

HI
SAP memory is for cross-transaction Applications and ABAP/4 memory is transaction-specific. So you can use SQL Trace to see the back ground process tables and details for the same Transaction.
The SAP memory, otherwise known as the global memory, is available to a user during the entire duration of a terminal session. Its contents are retained across transaction boundaries as well as external and internal sessions. The contents of the ABAP/4 memory are retained only during the lifetime of an external session. You can retain or pass data across internal sessions.
The SET PARAMETER and GET PARAMETER statements allow you to write to, or read from, the SAP memory. The EXPORT TO MEMORY and IMPORT FROM MEMORY statements allow you to write data to, or read data from, the ABAP memory.
ABAP memory is a memory area that all ABAP programs within the same internal session can access using the EXPORT and IMPORT statements. Data within this area remains intact during a whole sequence of program calls. To pass data to a program which you are calling, the data needs to be placed in ABAP memory before the call is made. The internal session of the called program then replaces that of the calling program. The program called can then read from the ABAP memory.
Put function group memory in ABAP-MEMORY-- BAL_GLB_MEMORY_IMPORT Get function group memory from ABAP
Hope it helps

Problem in ABAP memory

Hi Experts,
This is problem about ABAP memory.
I have two programs. Program-A & Program-B
Program-A sets value to variable and EXPORT command is used to set this variable in memory.
EXPORT variable TO DATABASE indx(st) ID 'KEYVALUE'.
Program-B gets variable using IMPORT command from memory.
IMPORT variable FROM DATABASE indx(st) ID 'KEYVALUE'.
User runs Program-A in SE38. Program-A calls Program-B using a button click event (SUBMIT).
The scenario is..
User1 executes the Program-A,
which set the variable = User1 in memory.
User2 executes the Program-A,
which set the variable = User2 in memory.
User2 clicks button to call Program-B,
which imports variable = User2 from memory.
User1 clicks button to call Program-B,
which imports variable = User2 from memory.
(But User1 expects the variable = User1).
So User1 gets wrong variable value set by another User.
How to handle this situation?. How to set memory variables user specific? I will appriciate all helpful answers.
Thanks in advance
Hari.

What you are using is global memory, if you don't want other sessions to see it, then you have to use a memeory id instead. This will work when submittin program b using the SUBMIT statement.
export variable to memory id 'ZRICHTEST'.
import variable from memory id 'ZRICHTEST'.
Or you can simply make your KEYVALUE unique by giving the USERID as part of it.
Regards,
Rich Heilman

How can i view the variables of the session memory

Hi experts
How can i view the variables of the session memory.Such as I want display the variables of memory which id is 'BULRN' in ABAP debug.
In program i can use import from memory id visit the momery of session,but i don't know the name of variables which store in momery of my session.

Its not possible to view in the debug mode..
SAP memory is a memory area to which all main sessions within a SAPgui have access. You can use SAP memory either to pass data from one program to another within a session, or to pass data from one session to another. Application programs that use SAP memory must do so using SPA/GPA parameters (also known as SET/GET parameters). These parameters can be set either for a particular user or for a particular program using the SET PARAMETER statement. Other ABAP programs can then retrieve the set parameters using the GET PARAMETER statement. The most frequent use of SPA/GPA parameters is to fill input fields on screens
SAP global memory retains field value through out session.
set parameter id 'MAT' field v_matnr.
get parameter id 'MAT' field v_matnr.
They are stored in table TPARA.
ABAP memory is a memory area that all ABAP programs within the same internal session can access using the EXPORT and IMPORT statements. Data within this area remains intact during a whole sequence of program calls. To pass data
to a program which you are calling, the data needs to be placed in ABAP memory before the call is made. The internal session of the called program then replaces that of the calling program. The program called can then read from the ABAP memory. If control is then returned to the program which made the initial call, the same process operates in reverse.
ABAP memory is temporary and values are retained in same LUW.
export itab to memory id 'TEST'.
import itab from memory Id 'TEST'.
Here itab should be declared of same type and length.

PGA memory problem - Oracle 10.2.0.4 on windows 2003

Hi,
I have recently started work at a new company and we are running Oracle 10g (10.2.0.4, Enterprise Edition) on Windows 2003 (Standard Edition). The server has 4Gb of RAM (and we have modified boot.ini to inclue the /3Gb switch).
RE: SGA/PGA, we have the following Oracle parameters set:
sga_target 1G
pga_aggregate_target 194M
The employees tell me that they frequently "have to reboot the database" because of ORA-4030 and ORA-4031 problems. Looking at taskmgr on the server, Oracle is using "too much" memory (~3Gb). New sessions cannot connect etc. and they restart the database. Being a DBA (experience in UNIX, not Windows) I'm not so keen on this "solution" and am trying to find out what's happening.
When this problem occurred yesterday, before allowing the reboot, I bought myself some time to have a little dig around in the database. In v$sesstat I saw one process that had a value of over 1GB for "session pga memory". Memory usage on the server for oracle.exe was (as predicted) ~1GB over the "expected" 1.2Gb value (of SGA+PGA agg target). So, part 1 of my question is:
- Is this "normal" behaviour for Oracle to allow a process to go so wild on the PGA?
(I understood that Oracle would attempt to maintain total PGA memory close to the value of PGA_AGGREGATE_TARGET. I believe I read in the documentation that it could allow PGA memory to increase "up to 20% over this value" but please don't quote me on that, I can't find it again..)
Part 2 to this problem is that sessions "collect" in the database and do not release their PGA memory, leading to the slow build up of memory until the errors are encountered. I believe Dead Connection Detection (DCD) not to be working here (sql_net.expire_time=1 is set on the server but appears to do nothing). I've started reading docs/notes on this and it seems that DCD is not reliable on Windows. Metalink Doc 151972.1 suggests testing and adjusting some underlying TCP/IP serttings in the O/S kernel (I'm not even sure how to do this in Windows yet, let alone if it's something I want to get involved with!). So:
- I'm wondering if anyone has any tips for this (killing off dead connections, getting DCD working in Windows 2003 etc.)? Any experiences, tips welcome here!!
Thanks in advance.
Regards,
Ados

user647632 wrote:
(By the way, can anyone recommend how to sort the formatting of these results please?!!)You can find all by clicking the Oracle Forum FAQ
</br>
Here is my PGASTAT result. Have a look at the values.
SQL> column name format a60
column value format 9,999,999,999,999,999
select * from gv$pgastat order by inst_id,name;
SQL> SQL>
   INST_ID NAME                                                                          VALUE UNIT
         1 PGA memory freed back to OS                                         202,362,322,944 bytes
         1 aggregate PGA auto target                                             1,831,209,984 bytes
         1 aggregate PGA target parameter                                        2,147,483,648 bytes
         1 bytes processed                                                     287,247,907,840 bytes
         1 cache hit percentage                                                             68 percent
         1 extra bytes read/written                                            133,790,002,176 bytes
         1 global memory bound                                                     214,743,040 bytes
         1 max processes count                                                              48
         1 maximum PGA allocated                                                 1,708,733,440 bytes
         1 maximum PGA used for auto workareas                                   1,112,871,936 bytes
         1 maximum PGA used for manual workareas                                       271,360 bytes
   INST_ID NAME                                                                          VALUE UNIT
         1 over allocation count                                                             0
         1 process count                                                                    42
         1 recompute count (total)                                                     136,756
         1 total PGA allocated                                                     328,158,208 bytes
         1 total PGA inuse                                                         196,502,528 bytes
         1 total PGA used for auto workareas                                        81,608,704 bytes
         1 total PGA used for manual workareas                                               0 bytes
         1 total freeable PGA memory                                                96,927,744 bytes
19 rows selected.
SQL>
SQL> column BYTES_PROCESSED format 9,999,999,999,999,999
column EST_RW_EXTRA_BYTES format 9,999,999,999,999,999
SQL> SQL> select inst_id,round(pga_target_for_estimate/1024/1024) as target_size_MB,
2                bytes_processed,estd_extra_bytes_rw as est_rw_extra_bytes,
3                estd_pga_cache_hit_percentage as est_hit_pct,
4                estd_overalloc_count as est_overalloc
5 from gv$pga_target_advice order by inst_id,target_size_mb;
   INST_ID TARGET_SIZE_MB        BYTES_PROCESSED     EST_RW_EXTRA_BYTES EST_HIT_PCT EST_OVERALLOC
         1            256        285,418,388,480        188,648,610,816          60             4
         1            512        285,418,388,480        131,006,145,536          69             0
         1           1024        285,418,388,480         92,476,995,584          76             0
         1           1536        285,418,388,480         91,536,565,248          76             0
         1           2048        285,418,388,480         72,373,725,184          80             0
         1           2458        285,418,388,480         68,650,139,648          81             0
         1           2867        285,418,388,480         68,650,139,648          81             0
         1           3277        285,418,388,480         68,650,139,648          81             0
         1           3686        285,418,388,480         68,650,139,648          81             0
         1           4096        285,418,388,480         68,650,139,648          81             0
         1           6144        285,418,388,480         68,650,139,648          81             0
   INST_ID TARGET_SIZE_MB        BYTES_PROCESSED     EST_RW_EXTRA_BYTES EST_HIT_PCT EST_OVERALLOC
         1           8192        285,418,388,480         68,650,139,648          81             0
         1          12288        285,418,388,480         68,650,139,648          81             0
         1          16384        285,418,388,480         68,650,139,648          81             0
14 rows selected.
SQL>
SQL> show parameters pga
NAME                                 TYPE        VALUE
pga_aggregate_target                 big integer 2G
SQL> show parameters sga_max
NAME                                 TYPE        VALUE
sga_max_size                         big integer 2G
SQL> show parameters sga_target
NAME                                 TYPE        VALUE
sga_target                           big integer 2G
SQL>

Oracle 9i Automatic PGA Memory Management

Hello,
my team and me, we are facing difficulties to change the size of the PGA used by our server processes for HASH JOIN, SORT... operators,
here you can see the results of "select * from v$pgastat":
[pgastat dynamic view results|http://pastebin.com/m210314dc]
We have been increasing consecutively our pga_aggregate_target parameter from 1.7 Gb initially to 4Gb then at the end 6Gb, the value of "Global memory bound" and " aggregate pga auto target" on the link above are still equal to 0.
I have been reading threads on the forum and documentation see below, I understand how the global memory manager (CKPT) computest the sql memory target and then the global memory bound, as far as I understand I can only "play" on the pga_aggregate_target value in order to increase the size of our PGAs (I exclude to play with hidden parameters).
- Joze Senegacnik: Advanced Management of working areas in Oracle 9i/10g : http://tonguc.yilmaz.googlepages.com/JozeSenegacnik-PGAMemoryManagementvO.zip
- Dageville Benoit and Zait Mohamed: SQL memory management in oracle 9i
Here different information that could be usefull:
OS: solaris 10 (db running in a non global zone)
Arch: 64-bit sparcv9 kernel modules
Physical memory: 32 Gb (being shared between all non global zones)
Oracle version: 9.2.0.5 32bits
Values of init parameters and hidden parameters that could be relevant:
[init parameters|http://pastebin.com/m40340cf4]
[hidden parameters|http://pastebin.com/m50d74c53]
Maybe useful queries:
over work areas views, I use the following script:
[wa_analysis.sql|http://pastebin.com/d606ebd9b]
and the result of it:
[result of script wa_analysis.sql|http://pastebin.com/m5f49a2e5]

Joze Senegacnik wrote:
- either your sessions are using a lot of memory for storing variables like pl/sql arrays which is subtracted from automatic management: PGA_AGGREGATE_TARGET - (aggregated persistent area + a part of the run time area of all server processes)
- you are hitting a bug
- or maybe something elseI am really happy you come to this conclusion too, they are the same we made with my team and we have submitting to Oracle support via metalink SR 3-1216060641, we were asking if we hit the following bug (in note 1) or we leak about pl/sql or java... or else indeed,
note 1: PGA_AGGREGATE_TARGET Assigned Memory Is Left Unconsumed When Set High [ID 844542.1]
Joze Senegacnik wrote:
I would like to know:
1.) what were the values for global memory bound and autotarget immediately (or in short time) after the database restart or when you have increased them Just after the restart of the database and just after the change of P_A_T, we query v$pgastat immediately after and the value of global memory bound and auto target were equal to 0 byte,
2.) If you are able to change value of PGA_AGGREGATE_TARGET (P_A_T) to 10GB what happens with global memory bound and auto traget. They should be positive at least for a short time. As this is a dynamic parameter you can change it for a short time, run queries and set it back.We plan to do this tonight, we have an "heavy" ITIL change management procedures that allow us to make changes approved by change manager and only during night maintenance window on production system, I come back to you tomorrow. But we have been increasing from 1,7Gb to 4Gb to 6Gb, each time I have been querying v$sgastat in the next 2 mins and global memory bound and auto target were equal to 0 byte.
3.) Have you checked on the OS level how much memory are using server processes - do these numbers come along with what Oracle says. Not during problematic activities, meaning active work areas performing HASH-JOIN, SORT... operators,
unfortunately it is a production system, even if he performs poorly, we are not allowed to try or retry the poor queries, but if it comes again I'll do it,
during low activities, here the results paste with the scripts I used:
[pga processes info in oracle|http://pastebin.com/f2e540062]
I spooled the result rows of this previous script in /var/tmp/pga_processes.log then I loop over all processes pid and display pmap output anon info like this:
h5. cat /var/tmp/pga_processes.log | awk -F' ' '{print $5}' | xargs -n 1 -i pmap -x {}| grep -v 'Addres' |egrep 'Kb' 2>&1 > /var/tmp/pga_processes_os.log
then I merge line by line the two files with unix paste command, here the results:
[os and oracle pga informations|http://pastebin.com/f4135c8a6]
4.) How many server processes are running on you system in average/max and are you using just dedicated processes or also shared?in average 250, we are only using dedicated processes,
5.) At time of low activity is the global memory bound still 0 or becomes > 0. I have been querying every 15 min during more than 24 hours low activities, it still stay to 0,
5.) Are you experiencing paging/swapping on OS level?No, here orca figures for details:
[free memory|http://img509.imageshack.us/img509/5897/ohuron1asd2gauge1024xfr.png]
swap
[pagein pageout|http://img121.imageshack.us/img121/6946/ohuron1asd2gaugepginper.png]
[memory usage|http://img19.imageshack.us/img19/2213/ohuron1asd2gaugeppkerne.png]
6.) Please post the result of: select * from X$QESMMSGA ;during low activities, [results X$QESMMSGA|http://pastebin.com/f61df7093]
While you will be answering to my questions I'll try to figure out what we can do to properly diagnose the problem. As you are on 9i it is a little bit harder.I am really kind of your help, as we say in my country, "if you need tow arms one day to carry something, call me."
--Jeremy Baumont

SQL Server Memory usage is high

Hello,
One of our production SQL cluster is eating up more memory on server.
Here are the server specifications :
OS : Windows 2008 R2 Enterprise
SQL : SQL Server 2008 SP2 standard edition ( 2 node cluster )
Memory : 16 GB ( 8 Gb to SQL and rest to OS )
CPU : 8
This server is heavily used by CLR and linked server events.
I have seen the memory usage of databases , it's not using more than 7 GB and leaving 1 GB free in sql memory area ( from our Idera SQL dm
monitoring tool ). I'm suspecting CLR events are causing these spikes.
When i look at the task manager sqlserver.exe is using 15.7 Gb ( close to 16 GB )
Not sure how to see which process are using the memory.
Also we are seeing the below error messages in error log very frequently
10/27/2014 15:23:52,spid1s,Unknown,AppDomain 85 (xxxxxx) is marked for unload due to memory pressure.
I have looked at some blogs in internet, i didnt get any correct info. I have seen this is kind of bug in SQL 2005 32-bit system but we are
using 64 bit system.
http://support.microsoft.com/kb/969962
Can anyone please help me on this ?
Thanks in advance

Continuation of DBCC memorystatus output
CACHESTORE_TEMPTABLES (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 40
MultiPage Allocator 0
(7 row(s) affected)
CACHESTORE_NOTIF (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 16
MultiPage Allocator 0
(7 row(s) affected)
CACHESTORE_VIEWDEFINITIONS (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 16
MultiPage Allocator 0
(7 row(s) affected)
CACHESTORE_XMLDBTYPE (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 8
MultiPage Allocator 0
(7 row(s) affected)
CACHESTORE_XMLDBELEMENT (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 8
MultiPage Allocator 0
(7 row(s) affected)
CACHESTORE_XMLDBATTRIBUTE (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 8
MultiPage Allocator 0
(7 row(s) affected)
CACHESTORE_STACKFRAMES (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 0
MultiPage Allocator 8
(7 row(s) affected)
CACHESTORE_STACKFRAMES (node 64) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 0
MultiPage Allocator 8
(7 row(s) affected)
CACHESTORE_STACKFRAMES (Total) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 0
MultiPage Allocator 16
(7 row(s) affected)
CACHESTORE_BROKERTBLACS (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 48
MultiPage Allocator 0
(7 row(s) affected)
CACHESTORE_BROKERKEK (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 8
MultiPage Allocator 0
(7 row(s) affected)
CACHESTORE_BROKERDSH (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 8
MultiPage Allocator 0
(7 row(s) affected)
CACHESTORE_BROKERUSERCERTLOOKUP (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 8
MultiPage Allocator 0
(7 row(s) affected)
CACHESTORE_BROKERRSB (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 8
MultiPage Allocator 0
(7 row(s) affected)
CACHESTORE_BROKERREADONLY (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 32
MultiPage Allocator 0
(7 row(s) affected)
CACHESTORE_BROKERTO (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 8
MultiPage Allocator 0
(7 row(s) affected)
CACHESTORE_EVENTS (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 16
MultiPage Allocator 0
(7 row(s) affected)
CACHESTORE_CLRPROC (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 40
MultiPage Allocator 0
(7 row(s) affected)
CACHESTORE_SYSTEMROWSET (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 1856
MultiPage Allocator 0
(7 row(s) affected)
CACHESTORE_CONVPRI (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 48
MultiPage Allocator 0
(7 row(s) affected)
CACHESTORE_FULLTEXTSTOPLIST (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 32
MultiPage Allocator 0
(7 row(s) affected)
USERSTORE_SCHEMAMGR (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 16432
MultiPage Allocator 856
(7 row(s) affected)
USERSTORE_DBMETADATA (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 5592
MultiPage Allocator 0
(7 row(s) affected)
USERSTORE_TOKENPERM (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 3856
MultiPage Allocator 3960
(7 row(s) affected)
USERSTORE_OBJPERM (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 2328
MultiPage Allocator 0
(7 row(s) affected)
USERSTORE_SXC (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 656
MultiPage Allocator 0
(7 row(s) affected)
USERSTORE_SXC (node 64) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 8
MultiPage Allocator 0
(7 row(s) affected)
USERSTORE_SXC (Total) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 664
MultiPage Allocator 0
(7 row(s) affected)
OBJECTSTORE_LBSS (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 128
MultiPage Allocator 608
(7 row(s) affected)
OBJECTSTORE_SNI_PACKET (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 2008
MultiPage Allocator 56
(7 row(s) affected)
OBJECTSTORE_SNI_PACKET (node 64) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 0
MultiPage Allocator 56
(7 row(s) affected)
OBJECTSTORE_SNI_PACKET (Total) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 2008
MultiPage Allocator 112
(7 row(s) affected)
OBJECTSTORE_SERVICE_BROKER (node 0) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 424
MultiPage Allocator 0
(7 row(s) affected)
OBJECTSTORE_LOCK_MANAGER (node 0) KB
VM Reserved 32768
VM Committed 32768
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 4048
MultiPage Allocator 0
(7 row(s) affected)
OBJECTSTORE_LOCK_MANAGER (node 64) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 24
MultiPage Allocator 0
(7 row(s) affected)
OBJECTSTORE_LOCK_MANAGER (Total) KB
VM Reserved 32768
VM Committed 32768
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 4072
MultiPage Allocator 0
(7 row(s) affected)
Buffer Pool Value
Committed 1024000
Target 1024000
Database 793462
Dirty 36258
In IO 0
Latched 0
Free 171398
Stolen 59140
Reserved 0
Visible 1024000
Stolen Potential 913660
Limiting Factor 17
Last OOM Factor 0
Last OS Error 0
Page Life Expectancy 262733
(15 row(s) affected)
Process/System Counts Value
Available Physical Memory 69021696
Available Virtual Memory 8762135273472
Available Paging File 12716019712
Working Set 15196917760
Percent of Committed Memory in WS 100
Page Faults 897824874
System physical memory high 0
System physical memory low 0
Process physical memory low 0
Process virtual memory low 0
(10 row(s) affected)
Procedure Cache Value
TotalProcs 4573
TotalPages 53712
InUsePages 27
(3 row(s) affected)
Global Memory Objects Pages
Resource 412
Locks 509
XDES 219
SETLS 8
SE Dataset Allocators 16
SubpDesc Allocators 8
SE SchemaManager 1169
SE Column Metadata Cache 991
SQLCache 893
Replication 2
ServerGlobal 52
XP Global 2
SortTables 3691
(13 row(s) affected)
Query Memory Objects (internal) Value
Grants 0
Waiting 0
Available 756700
Current Max 756700
Future Max 756700
Physical Max 756700
Next Request 0
Waiting For 0
Cost 0
Timeout 0
Wait Time 0
(11 row(s) affected)
Small Query Memory Objects (internal) Value
Grants 0
Waiting 0
Available 12800
Current Max 12800
Future Max 12800
(5 row(s) affected)
Optimization Queue (internal) Value
Overall Memory 6723993600
Target Memory 5965963264
Last Notification 1
Timeout 6
Early Termination Factor 5
(5 row(s) affected)
Small Gateway (internal) Value
Configured Units 32
Available Units 32
Acquires 0
Waiters 0
Threshold Factor 380000
Threshold 380000
(6 row(s) affected)
Medium Gateway (internal) Value
Configured Units 8
Available Units 8
Acquires 0
Waiters 0
Threshold Factor 12
Threshold -1
(6 row(s) affected)
Big Gateway (internal) Value
Configured Units 1
Available Units 1
Acquires 0
Waiters 0
Threshold Factor 8
Threshold -1
(6 row(s) affected)
Memory Pool Manager Pages
Reserved Current 0
Reserved Limit 913664
(2 row(s) affected)
Memory Pool (internal) Pages
Allocations 59136
Predicted 248311
Private Target 0
Private Limit 0
Total Target 972800
Total Limit 972800
OOM Count 0
(7 row(s) affected)
MEMORYBROKER_FOR_CACHE (internal) Pages
Allocations 55358
Rate 0
Target Allocations 779847
Future Allocations 0
Overall 820800
Last Notification 1
(6 row(s) affected)
MEMORYBROKER_FOR_STEAL (internal) Pages
Allocations 3778
Rate 0
Target Allocations 728267
Future Allocations 0
Overall 820800
Last Notification 1
(6 row(s) affected)
MEMORYBROKER_FOR_RESERVE (internal) Pages
Allocations 0
Rate 0
Target Allocations 820800
Future Allocations 189175
Overall 820800
Last Notification 1
(6 row(s) affected)
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

Global memory

Similar Messages

Maybe you are looking for