About Oracle Memory Utilization is 99.54%

近期通过Oracle Enterprise Manager发现显示 Oracle Memory Utilization 一直在98%以上，
如下所示
Alert History for Last 24 Hours
Severity Timestamp Message Details
Nov 1, 2012 2:50:43 AM Memory Utilization is 99.54% -
Oct 31, 2012 10:40:43 PM Memory Utilization is 95.96% -
Oct 31, 2012 9:30:43 PM Memory Utilization is 99.09% -
Oct 31, 2012 5:30:43 PM Memory Utilization is 98.43% -
Oct 31, 2012 2:55:43 AM Memory Utilization is 99.64%
请教一下，这个Oracle Memory Utilization显示的百分比是Oracle已经使用的内存占总物理内存的百分比吗？99%意味着什么？如果不是，怎么样查看Oracle占用的总内存大小？

EXCLUSIVE segments Inuse Pin Pgsp Virtual
1655678 6504 0 426438
PageSize Inuse Pin Pgsp Virtual
s 4 KB 1644750 24 0 415510
m 64 KB 683 405 0 683
Vsid Esid Type Description PSize Inuse Pin Pgsp Virtual
11110f1 - clnt /dev/fslv02:24632 s 1139343 0 - -
10f0e2f 4 work working storage sm 58014 0 0 58014
11010f0 - clnt /dev/fslv02:24628 s 34831 0 - -
10a1b6a 5 work working storage sm 27216 0 0 27216
1111031 11 work text data BSS heap sm 26764 0 0 26764
1131193 3 work working storage sm 19483 0 0 19483
1000f00 10 clnt text data BSS heap, s 11599 0 - -
/dev/fslv01:10258
1021182 - clnt /dev/fslv02:24624 s 10629 0 - -
1161056 - clnt /dev/fslv02:24622 s 10603 0 - -
1151175 - clnt /dev/fslv02:24623 s 10072 0 - -
10c11cc 2 work process private sm 8918 4 0 8918
10d10ed - clnt /dev/fslv02:24629 s 7692 0 - -
10a0f0a 11 work text data BSS heap sm 5486 0 0 5486
11a115a 11 work text data BSS heap sm 3800 0 0 3800
10f118f 11 work text data BSS heap sm 3800 0 0 3800
1021c82 11 work text data BSS heap sm 3773 0 0 3773
11c0c7c 11 work text data BSS heap sm 3063 0 0 3063
10611c6 11 work text data BSS heap sm 3004 0 0 3004
1061466 11 work text data BSS heap sm 2916 0 0 2916
1031463 11 work text data BSS heap sm 2678 0 0 2678
1081a08 11 work text data BSS heap sm 2665 0 0 2665
11a0dba 11 work text data BSS heap sm 2424 0 0 2424
10e10ae 11 work text data BSS heap sm 2368 0 0 2368
1041a64 11 work text data BSS heap sm 2306 0 0 2306
10f13cf 11 work text data BSS heap sm 2301 0 0 2301
11c1d5c 11 work text data BSS heap sm 2256 0 0 2256
1041f64 11 work text data BSS heap sm 2077 0 0 2077
1141ed4 11 work text data BSS heap sm 2055 0 0 2055
11a13fa 11 work text data BSS heap sm 2041 0 0 2041
1041b84 11 work text data BSS heap sm 2028 0 0 2028
1151cd5 11 work text data BSS heap sm 2023 0 0 2023
10118a1 11 work text data BSS heap sm 2010 0 0 2010
1001dc0 11 work text data BSS heap sm 2000 0 0 2000
10e1fae 11 work text data BSS heap sm 1979 0 0 1979
1191619 11 work text data BSS heap sm 1977 0 0 1977
1091d09 11 work text data BSS heap sm 1976 0 0 1976
1081ac8 11 work text data BSS heap sm 1976 0 0 1976
1011801 11 work text data BSS heap sm 1975 0 0 1975
1131973 11 work text data BSS heap sm 1973 0 0 1973
10a164a 11 work text data BSS heap sm 1973 0 0 1973
11a1b9a 11 work text data BSS heap sm 1973 0 0 1973
1101f50 11 work text data BSS heap sm 1972 0 0 1972
11e169e 11 work text data BSS heap sm 1957 0 0 1957
10b214b 11 work text data BSS heap sm 1956 0 0 1956
10c194c 11 work text data BSS heap sm 1948 0 0 1948
1141e14 11 work text data BSS heap sm 1946 0 0 1946
11c1efc 11 work text data BSS heap sm 1943 0 0 1943
1151bb5 11 work text data BSS heap sm 1940 0 0 1940
11e1a5e 11 work text data BSS heap sm 1893 0 0 1893
11d12bd 11 work text data BSS heap sm 1892 0 0 1892
1101970 11 work text data BSS heap sm 1881 0 0 1881
11b17fb 11 work text data BSS heap sm 1878 0 0 1878
11f203f 11 work text data BSS heap sm 1877 0 0 1877
1091949 11 work text data BSS heap sm 1876 0 0 1876
1141f34 11 work text data BSS heap sm 1876 0 0 1876
10a1aea 11 work text data BSS heap sm 1867 0 0 1867
1121c92 11 work text data BSS heap sm 1865 0 0 1865
11613f6 11 work text data BSS heap sm 1864 0 0 1864
10b1a2b 11 work text data BSS heap sm 1864 0 0 1864
1171b17 11 work text data BSS heap sm 1861 0 0 1861
1052045 11 work text data BSS heap sm 1860 0 0 1860
1141d94 11 work text data BSS heap sm 1859 0 0 1859
10a0f8a 11 work text data BSS heap sm 1849 0 0 1849
1161f96 11 work text data BSS heap sm 1848 0 0 1848
11f205f 11 work text data BSS heap sm 1846 0 0 1846
11d15fd 11 work text data BSS heap sm 1844 0 0 1844
11a1aba 11 work text data BSS heap sm 1833 0 0 1833
1061446 11 work text data BSS heap sm 1832 0 0 1832
1151c75 11 work text data BSS heap sm 1831 0 0 1831
1091e29 11 work text data BSS heap sm 1828 0 0 1828
1111ed1 11 work text data BSS heap sm 1827 0 0 1827
11117b1 11 work text data BSS heap sm 1821 0 0 1821
1011961 11 work text data BSS heap sm 1818 0 0 1818
1161bb6 11 work text data BSS heap sm 1813 0 0 1813
11821b8 11 work text data BSS heap sm 1810 0 0 1810
1031d23 11 work text data BSS heap sm 1795 0 0 1795
10621c6 11 work text data BSS heap sm 1787 0 0 1787
1191579 11 work text data BSS heap sm 1783 0 0 1783
11b15fb 11 work text data BSS heap sm 1780 0 0 1780
1111eb1 11 work text data BSS heap sm 1780 0 0 1780
1172157 11 work text data BSS heap sm 1779 0 0 1779
1022002 11 work text data BSS heap sm 1779 0 0 1779
1031ea3 11 work text data BSS heap sm 1764 0 0 1764
1081c08 11 work text data BSS heap sm 1764 0 0 1764
11f1f1f 11 work text data BSS heap sm 1764 0 0 1764
10920e9 11 work text data BSS heap sm 1747 0 0 1747
10e1bae 11 work text data BSS heap sm 1739 0 0 1739
11c207c 11 work text data BSS heap sm 1736 0 0 1736
11f217f 11 work text data BSS heap sm 1730 0 0 1730
1071007 11 work text data BSS heap sm 1725 0 0 1725
1022162 11 work text data BSS heap sm 1719 0 0 1719
1051f65 11 work text data BSS heap sm 1718 0 0 1718
11f20bf 11 work text data BSS heap sm 1707 0 0 1707
1042064 11 work text data BSS heap sm 1703 0 0 1703
1011b81 11 work text data BSS heap sm 1699 0 0 1699
10a1aca 11 work text data BSS heap sm 1686 0 0 1686
10a1dca 11 work text data BSS heap sm 1680 0 0 1680
11d141d 11 work text data BSS heap sm 1649 0 0 1649
10e10ee - clnt /dev/fslv02:24630 s 1558 0 - -
11a1efa 11 work text data BSS heap sm 1495 0 0 1495
1161cf6 11 work text data BSS heap sm 1494 0 0 1494
1122132 11 work text data BSS heap sm 1490 0 0 1490
11c0c9c 11 work text data BSS heap sm 1432 0 0 1432
1051085 11 work text data BSS heap sm 1426 0 0 1426
11a1c9a 11 work text data BSS heap sm 1398 0 0 1398
1141274 2 work process private sm 1382 4 0 1382
1060e26 11 work text data BSS heap sm 1335 0 0 1335
1140f74 11 work text data BSS heap sm 1309 0 0 1309
1171db7 11 work text data BSS heap sm 1291 0 0 1291
1052145 11 work text data BSS heap sm 1283 0 0 1283
10c112c 11 work text data BSS heap sm 1222 0 0 1222
1181178 11 work text data BSS heap sm 1204 0 0 1204
11b105b 11 work text data BSS heap sm 1197 0 0 1197
1190f99 11 work text data BSS heap sm 1189 0 0 1189
1120d72 11 work text data BSS heap sm 1189 0 0 1189
10d0f0d 10 clnt text data BSS heap, s 806 0 - -
/dev/fslv01:11421
11f1b9f 11 work text data BSS heap sm 634 0 0 634
1020ea2 80000000 work private load text sm 606 0 0 606
11b11fb - clnt /dev/fslv01:10788 s 417 0 - -
11012f0 1 clnt code,/dev/fslv01:7107 s 356 0 - -
1001060 80000000 work private load text sm 335 0 0 335
11b0f5b 8001000a work private load data sm 332 0 0 332
1152195 80000000 work private load text sm 332 0 0 332
11c205c 80000000 work private load text sm 331 0 0 331
1001940 80000000 work private load text sm 331 0 0 331
11c1b7c 80000000 work private load text sm 331 0 0 331
1041f04 80000000 work private load text sm 331 0 0 331
10f1c4f 80000000 work private load text sm 331 0 0 331
11a1dfa 80000000 work private load text sm 331 0 0 331
1102090 80000000 work private load text sm 331 0 0 331
11f1aff 80000000 work private load text sm 331 0 0 331
11c19bc 80000000 work private load text sm 331 0 0 331
10210a2 80000000 work private load text sm 331 0 0 331
11520d5 80000000 work private load text sm 331 0 0 331
10c19cc 80000000 work private load text sm 331 0 0 331
1041b64 80000000 work private load text sm 331 0 0 331
10d158d 80000000 work private load text sm 331 0 0 331
1121eb2 80000000 work private load text sm 331 0 0 331
11f18ff 80000000 work private load text sm 331 0 0 331
1181ff8 80000000 work private load text sm 331 0 0 331
1151155 80000000 work private load text sm 331 0 0 331
1051fc5 80000000 work private load text sm 331 0 0 331
1132153 80000000 work private load text sm 331 0 0 331
10e1e6e 80000000 work private load text sm 331 0 0 331
1091989 80000000 work private load text sm 331 0 0 331
11b141b 80000000 work private load text sm 331 0 0 331
10b15eb 80000000 work private load text sm 331 0 0 331
11817d8 80000000 work private load text sm 331 0 0 331
1051145 80000000 work private load text sm 331 0 0 331
10a146a 80000000 work private load text sm 331 0 0 331
11f1fbf 80000000 work private load text sm 331 0 0 331
1092189 80000000 work private load text sm 331 0 0 331
1071b47 80000000 work private load text sm 331 0 0 331
1131bb3 80000000 work private load text sm 331 0 0 331
11716d7 80000000 work private load text sm 331 0 0 331
1172137 80000000 work private load text sm 331 0 0 331
11c1a7c 80000000 work private load text sm 331 0 0 331
11318b3 80000000 work private load text sm 331 0 0 331
1151d55 80000000 work private load text sm 331 0 0 331
11e205e 80000000 work private load text sm 331 0 0 331
10f188f 80000000 work private load text sm 331 0 0 331
1061ea6 80000000 work private load text sm 331 0 0 331
1161c36 80000000 work private load text sm 331 0 0 331
1161f16 80000000 work private load text sm 331 0 0 331
11c0f3c 80000000 work private load text sm 331 0 0 331
11720d7 80000000 work private load text sm 331 0 0 331
1021fa2 80000000 work private load text sm 331 0 0 331
1191979 80000000 work private load text sm 331 0 0 331
1192119 80000000 work private load text sm 331 0 0 331
1001fe0 80000000 work private load text sm 331 0 0 331
11e1cbe 80000000 work private load text sm 331 0 0 331
1091ee9 80000000 work private load text sm 331 0 0 331
11d217d 80000000 work private load text sm 331 0 0 331
1002140 80000000 work private load text sm 331 0 0 331
11f1cff 80000000 work private load text sm 331 0 0 331
11a1c7a 80000000 work private load text sm 331 0 0 331
11c217c 80000000 work private load text sm 331 0 0 331
1171117 80000000 work private load text sm 331 0 0 331
1031703 80000000 work private load text sm 331 0 0 331
10d13cd 80000000 work private load text sm 331 0 0 331
1021e02 80000000 work private load text sm 331 0 0 331
1011d61 80000000 work private load text sm 331 0 0 331
1151ff5 80000000 work private load text sm 331 0 0 331
1001ce0 80000000 work private load text sm 331 0 0 331
11e193e 80000000 work private load text sm 331 0 0 331
1081ec8 80000000 work private load text sm 331 0 0 331
1001a00 80000000 work private load text sm 331 0 0 331
1101930 80000000 work private load text sm 331 0 0 331
1001580 80000000 work private load text sm 331 0 0 331
10a1baa 80000000 work private load text sm 331 0 0 331
1111ef1 80000000 work private load text sm 331 0 0 331
1042184 80000000 work private load text sm 331 0 0 331
10d0f6d 80000000 work private load text sm 331 0 0 331
1171f77 80000000 work private load text sm 331 0 0 331
10b16cb 80000000 work private load text sm 331 0 0 331
11413f4 80000000 work private load text sm 331 0 0 331
11220f2 80000000 work private load text sm 331 0 0 331
11818b8 80000000 work private load text sm 331 0 0 331
1121cb2 80000000 work private load text sm 331 0 0 331
1091aa9 80000000 work private load text sm 331 0 0 331
1051005 80000000 work private load text sm 330 0 0 330
10f102f 80000000 work private load text sm 330 0 0 330
10a112a 80000000 work private load text sm 330 0 0 330
11609f6 80000000 work private load text sm 330 0 0 330
10d100d 80000000 work private load text sm 330 0 0 330
11c0d5c 80000000 work private load text sm 330 0 0 330
11f1d3f 80000000 work private load text sm 328 0 0 328
11620d6 80000000 work private load text sm 328 0 0 328
1081208 80000000 work private load text sm 328 0 0 328
11e17de 80000000 work private load text sm 328 0 0 328
1090e69 80000000 work private load text sm 327 0 0 327
1191059 80000000 work private load text sm 327 0 0 327
1000fa0 80000000 work private load text sm 327 0 0 327
1130f53 80000000 work private load text sm 327 0 0 327
1080ee8 80000000 work private load text sm 327 0 0 327
11b115b 80000000 work private load text sm 327 0 0 327
1130eb3 80000000 work private load text sm 327 0 0 327
1130f13 80000000 work private load text sm 327 0 0 327
10d118d 80000000 work private load text sm 327 0 0 327
11e113e 80000000 work private load text sm 327 0 0 327
1031083 80000000 work private load text sm 325 0 0 325
10c10ac 80000000 work private load text sm 325 0 0 325
1051265 - clnt /dev/fslv01:10524 s 324 0 - -
10f112f f work working storage sm 281 0 0 281
10c10ec - clnt /dev/fslv02:24633 s 187 0 - -
1081ca8 8001000a work private load data sm 146 0 0 146
11d1dfd 8001000a work private load data sm 146 0 0 146
1191679 8001000a work private load data sm 146 0 0 146
1111e11 8001000a work private load data sm 146 0 0 146
10b0e8b 8001000a work private load data sm 146 0 0 146
1081ce8 8001000a work private load data sm 146 0 0 146
1151055 8001000a work private load data sm 146 0 0 146
11d117d 8001000a work private load data sm 146 0 0 146
11a14da 8001000a work private load data sm 146 0 0 146
11f1b1f 8001000a work private load data sm 146 0 0 146
10b1acb 8001000a work private load data sm 146 0 0 146
1082108 8001000a work private load data sm 146 0 0 146
1191cb9 8001000a work private load data sm 146 0 0 146
1160f96 8001000a work private load data sm 146 0 0 146
1171c97 8001000a work private load data sm 146 0 0 146
1031a03 8001000a work private load data sm 146 0 0 146
11d195d 8001000a work private load data sm 146 0 0 146
11519d5 8001000a work private load data sm 146 0 0 146
11d165d 8001000a work private load data sm 146 0 0 146
11d1d9d 8001000a work private load data sm 146 0 0 146
1191019 8001000a work private load data sm 146 0 0 146
10b170b 8001000a work private load data sm 146 0 0 146
10e1bee 8001000a work private load data sm 146 0 0 146
11b1ffb 8001000a work private load data sm 146 0 0 146
1090de9 8001000a work private load data sm 146 0 0 146
1051d85 8001000a work private load data sm 146 0 0 146
1061006 8001000a work private load data sm 146 0 0 146
1131833 8001000a work private load data sm 146 0 0 146
1011d21 8001000a work private load data sm 146 0 0 146
1111471 8001000a work private load data sm 146 0 0 146
1191139 8001000a work private load data sm 146 0 0 146
11d20fd 8001000a work private load data sm 146 0 0 146
11719d7 8001000a work private load data sm 146 0 0 146
10b1eab 8001000a work private load data sm 146 0 0 146
1031da3 8001000a work private load data sm 146 0 0 146
1051685 8001000a work private load data sm 146 0 0 146
11f215f 8001000a work private load data sm 146 0 0 146
10712e7 8001000a work private load data sm 146 0 0 146
1031dc3 8001000a work private load data sm 146 0 0 146
1171b77 8001000a work private load data sm 146 0 0 146
10c178c 8001000a work private load data sm 146 0 0 146
10b1f0b 8001000a work private load data sm 146 0 0 146
10620a6 8001000a work private load data sm 146 0 0 146
1041c24 8001000a work private load data sm 146 0 0 146
11a213a 8001000a work private load data sm 146 0 0 146
1101d70 8001000a work private load data sm 146 0 0 146
1142074 8001000a work private load data sm 146 0 0 146
1151eb5 8001000a work private load data sm 146 0 0 146
11513f5 8001000a work private load data sm 146 0 0 146
1021c02 8001000a work private load data sm 146 0 0 146
11720f7 8001000a work private load data sm 146 0 0 146
11a105a 8001000a work private load data sm 146 0 0 146
1121b52 8001000a work private load data sm 146 0 0 146
11a1e9a 8001000a work private load data sm 146 0 0 146
1101030 8001000a work private load data sm 146 0 0 146

Similar Messages

Oracle Memory utilization gradually increasing up to the max in short span

Hi All,
Our Oracle database running in windows 2000,having max sessions of 1500
attains it max_memory 850m once 1500 sessions reached.
--Shared pool memory(SQL AREA,LIBRARY CACHE,SHAREDPOOL MISCELL.,) gradually increasing.
Oracle database version:9.2.0.5
Server Type: Shared Server
Os memory: 1Gb
Oracle memory: sga-750m,pga(max) -110 allocated by oracle when no of sessions increasing.
Pls tell me why it is happening?

Hi Priyanka,
Its know problem in solaris zones , 40 GB Memory is allocated to global zone & you db server zone has been assigned a part of it .
Get is touch with you Solaris admin to know exact memory allocated to db zone , as per my knowledge they must be shared across multiple zones
use below from Os prompt
prstat -ZThanks,
Ajay More
http://www.moreajays.com

Cisco Router Memory Utilization

Hi,
We have a Cisco SA520 Router (Firmware 2.1.18)
We are only using this for about 1 month now. Router seems ok its just
I am worried about the Memory utilization which reach to 62% (144/234 MB)
Is this something to worry about?
How can I utilize this by lowering down the usage?
Pardon me I am just to new Cisco devices.
Many Thanks.
AC

AC,
Please go ahead and upgrade to the latest firmware 2.1.51 Memory utilization shouldn't be a problem. After the upgrade please keep an eye on the memory and report back.
Thanks,
Jasbryan
Cisco Support Engineer
.:|:.:|:.

Follow up on an old thread about memory utilization

This thread was active a few months ago, unfortunately its taken me until now
for me to have enough spare time to craft a response.
From: SMTP%"[email protected]" 3-SEP-1996 16:52:00.72
To: [email protected]
CC:
Subj: Re: memory utilization
As a general rule, I would agree that memory utilzation problems tend to be
developer-induced. I believe that is generally true for most development
environments. However, this developer was having a little trouble finding
out how NOT to induce them. After scouring the documentation for any
references to object destructors, or clearing memory, or garbage collection,
or freeing objects, or anything else we could think of, all we found was how
to clear the rows from an Array object. We did find some reference to
setting the object to NIL, but no indication that this was necessary for the
memory to be freed.
I believe the documentation, and probably some Tech-Notes, address the issue of
freeing memory.
Automatic memory management frees a memory object when no references to the
memory
object exist. Since references are the reason that a memory object lives,
removing
the references is the only way that memory objects can be freed. This is why the
manuals and Tech-Notes talk about setting references to NIL (I.E. freeing memory
in an automatic system is done by NILing references and not by calling freeing
routines.) This is not an absolute requirement (as you have probably noticed
that
most things are freed even without setting references to NIL) but it accelerates
the freeing of 'dead' objects and reduces the memory utilization because it
tends
to carry around less 'dead' objects.
It is my understanding that in this environment, the development tool
(Forte') claims to handle memory utilization and garbage collection for you.
If that is the case, then it is my opinion that it shoud be nearly
impossible for the developer to create memory-leakage problems without going
outside the tool and allocating the memory directly. If that is not the
case, then we should have destructor methods available to us so that we can
handle them correctly. I know when I am finished with an object, and I
would have no problem calling a "destroy" or "cleanup" method. In fact, I
would prefer that to just wondering if Forte' will take care of it for me.
It is actually quite easy to create memory leaks. Here are some examples:
Have a heap attribute in a service object. Keep inserting things into
the heap and never take them out (I.E. forgot to take them out). Since
service objects are always live, everything in the heap is also live.
Have an exception handler that catches exceptions and doesn't do
anything
with the error manager stack (I.E. it doesn't call task.ErrMgr.Clear).
If the handler is activated repeatedly in the same task, the stack of
exceptions will grow until you run out of memory or the task terminates
(task termination empties the error manager stack.)
It seems to me that this is a weakness in the tool that should be addressed.
Does anyone else have any opinions on this subject?
Actually, the implementation of the advanced features supported by the Forte
product
results in some complications in areas that can be hard to explain. Memory
management
happens to be one of the areas most effected. A precise explanation to a
non-deterministic process is not possible, but the following attempts to
explain the
source of the non-determinism.
o The ability to call from compiled C++ to interpreted TOOL and back
to compiled C++.
This single ability causes most of the strange effects mentioned in
this thread.
For C++ code the location of all variables local to a method is not
know
(I.E. C++ compilers can't tell you at run-time what is a variable
and what
isn't.) We use the pessimistic assumption that anything that looks
like a
reference to a memory object is a reference to a memory object. For
interpreted
TOOL code the interpreter has exact knowledge of what is a reference
and what
isn't. But the TOOL interpreter is itself a C++ method. This means
that any
any memory objects referenced by the interpreter during the
execution of TOOL
code could be stored in local variables in the interpreter. The TOOL
interpreter
runs until the TOOL code returns or the TOOL code calls into C++.
This means
that many levels of nested TOOL code can be the source of values
assigned to
local variables in the TOOL interpreter.
This is the complicated reason that answers the question: Why doesn't a
variable that is created and only used in a TOOL method that has
returned
get freed? It is likely that the variable is referenced by local
variables
in the TOOL interpreter method. This is also why setting the
variable to NIL
before returning doesn't seem to help. If the variable in question is a
Array than invoke Clear() on the Array seems to help, because even
though the
Array is still live the objects referenced by the Array have less
references.
The other common occurrence of this effect is in a TextData that
contains a
large string. In this case, invoking SetAllocatedSize(0) can be used
to NIL
the reference to the memory object that actually holds the sequence of
characters. Compositions of Arrays and TextData's (I.E. a Array of
TextData's
that all have large TextDatas.) can lead to even more problems.
When the TOOL code is turned into a compiled partition this effect
is not
noticed because the TOOL interpreter doesn't come into play and
things execute
the way most people expect. This is one area that we try to improve
upon, but it is complicated by the 15 different platforms, and thus
C++ compilers,
that we support. Changes that work on some machines behave
differently on other
machines. At this point in time, it occasionally still requires that
a TOOL
programmer actively address problems. Obviously we try to reduce
this need over
time.
o Automatic memory management for C++ with support for multi-processor
threads.
Supporting automatic memory management for C++ is something that is
not a very
common feature. It requires a coding standard that defines what is
acceptable and
what isn't. Additionally, supporting multi-processor threads adds
its own set of
complications. Luckily TOOL users are insulated from this because
the TOOL to C++
code generator knows the coding standard. In the end you are
impacted by the C++
compiler and possibly the differences that occur between different
compilers and/or
different processors (I.E. Intel X86 versus Alpha.) We have seen
applications that
had memory utilization differences of up to 2:1.
There are two primary sources of differences.
The first source is how compilers deal with dead assignments. The
typical TOOL
fragment that is being memory manager friendly might perform the
following:
temp : SomeObject = new;
... // Use someObject
temp = NIL;
return;
When this is translated to C++ it looks very similar in that temp
will be assigned the
value NULL. Most compilers are smart enough to notice that 'temp' is
never used again
because the method is going to return immediately. So they skip
setting 'temp' to NULL.
In this case it should be harmless that the statement was ignored
(see next example for a different variation.) In more
complicated examples that involve loops (especially long
lived event loops) a missed NIL assignment can lead to leaking the
memory object whose
reference didn't get set to NIL (incidentally this is the type of
problem that causes
the TOOL interpreter to leak references.)
The second source is a complicated interaction caused by history of
method invocations.
Consider the following:
Method A() invokes method B() which invokes method C().
Method C() allocates a temporary TextData, invokes
SetAllocatedSize(1000000)
does some more work and then returns.
Method B() returns.
Method A() now invokes method D().
Method D() allocates something that cause the memory manager to look
for memory objects to free.
Now, even though we have returned out of method C() we have starting
invoking
methods. This causes us to use re-use portions of the C++ stack used to
maintain the history of method invocation and space for local variables.
There is some probability that the reference to the 'temporary' TextData
will now be visible to the memory manager because it was not overwritten
by the invocation of D() or anything invoked by method D().
This example answers questions of the form: Why does setting a local
variable to
NIL and returning and then invoking task.Part.Os.RecoverMemory not
cause the
object referenced by the local variable to be freed?
In most cases these effects cause memory utilization to be slightly
higher
than expected (in well behaved cases it's less than 5%.) This is a small
price to pay for the advantages of automatic memory management.
An object-oriented programming style supported by automatic memory
management makes it
easy to extended existing objects or sets of objects by composition.
For example:
Method A() calls method B() to get the next record from the
database. Method B()
is used because we always get records, objects, of a certain
type from
method B() so that we can reuse code.
Method A() enters each row into a hash table so that it can
implement a cache
of the last N records seen.
Method A() returns the record to its caller.
With manual memory management there would have to be some interface
that allows
Method A() and/or the caller of A() to free the record. This
requires
that the programmer have a lot more knowledge about the
various projects
and classes that make up the application. If freeing doesn'
happen you
have a memory leak, if you free something while its still
being used the
results are unpredictable and most often fatal.
With automatic memory management, method A() can 'free' its
reference by removing
the reference from the hash table. The caller can 'free' its
reference by
either setting the reference to NIL or getting another
record and referring
to the new record instead of the old record.
Unfortunately, this convenience and power doesn't come for free. Consider
the following,
which comes from the Forte' run-time system:
A Window-class object is a very complex beast. It is composed of two
primary parts:
the UserWindow object which contains the variables declared by the
user, and the
Window object which contains the object representation of the window
created in
the window workshop. The UserWindow and the Window reference each
other. The Window
references the Menu and each Widget placed on the Window directly. A
compound Window
object, like a Panel, can also have objects place in itself. These
are typically
called the children. Each of the children also has to know the
identity of it's
Mom so they refer to there parent object. It should be reasonably
obvious that
starting from any object that make up the window any other object
can be found.
This means that if the memory manager finds a reference to any
object in the Window
it can also find all other objects in the window. Now if a reference
to any object
in the Window can be found on the program stack, all objects in the
window can
also be found. Since there are so many objects and the work involved
in displaying
a window can be very complicated (I.E. the automatic geometry
management that
layouts the window when it is first opened or resized.) there are
potentially many
different reference that would cause the same problem. This leads to
a higher than
normal probability that a reference exists that can cause the whole
set of Window
objects to not be freed.
We solved this problem in the following fashion:
Added a new Method called RecycleMemory() on UserWindow.
Documented that when a window is not going to be used again
that it is
preferably that RecycleMemory() is invoked instead
of Close().
The RecycleMemory() method basically sets all references
from parent to
child to NIL and sets all references from child to
parent to NIL.
Thus all objects are isolated from other objects
that make up
the window.
Changed a few methods on UserWindow, like Open(), to check
if the caller
is trying to open a recycled window and throw an
exception.
This was feasible because the code to traverse the parent/child
relationship
ready existed and was being used at close time to perform other
bookkeeping
operations on each of the Widgets.
To summarize:
Automatic memory management is less error prone and more productive but
doesn't come totally for free.
There are things that the programmer can do that assists the memory
manager:
o Set object reference to NIL when known to be correct (this
is the
way the memory is deallocated in an automatic system.)
o Use methods like Clear() on Array and SetAllocatedSize()
on TextData to
that allow these objects to set their internal
references to NIL
when known to be correct.
o Use the RecycleMemory() method on windows, especially very
complicated
windows.
o Build similar type of methods into your own objects when
needed.
o If you build highly connected structures that are very
large in the
number of object involved think that how it might be
broken
apart gracefully (it defeats some of the purpose of
automatic
management to go to great lengths to deal with the
problem.)
o Since program stacks are the source of the 'noise'
references, try
and do things with less tasks (this was one of the
reasons that
we implemented event handlers so that a single task
can control
many different windows.)
Even after doing all this its easy to still have a problem.
Internally we have
access to special tools that can help point at the problem so that
it can be
solved. We are attempting to give users UNSUPPORTED access to these
tools for
Release 3. This should allow users to more easily diagnose problems.
It also
tends to enlighten one about how things are structured and/or point out
inconsistencies that are the source of known/unknown bugs.
Derek
Derek Frankforth [email protected]
Forte Software Inc. [email protected]
1800 Harrison St. +510.869.3407
Oakland CA, 94612

I beleive he means to reformat it like a floppy disk.
Go into My Computer, Locate the drive letter associated with your iPod(normally says iPod in it, and shows under removable storage).
Right click on it and choose format - make sure to not have the "quick format" option checked. Then let it format.
If that doesnt work, There are steps somewhere in the 5th gen forum( dont have the link off hand) to try to use the usbstor.sys to update the USB drivers for the Nano/5th gen.

Memory utilization presented in Application Server Control

Hi
I have Oracle Application Server 10g R3 Patch Set 5 application server, which work in cluster. On mian page in Oracle Application Server Control I have memory column, where I can see information about memory utilization. I wonder about this information. For example, I have heap size set for 2 GB and application uses 300MB, but I have on main page Application Server Control 900 MB memory utilization for OC4J container. Why is so difference between use heap space memory (only 300 MB), and this information 900 MB? But sometimes, memory in Server Control rises to 2 GB, but application uses 300 MB heap space still. Why does occur this situation (much difference between uses heap space and memory presented on Server Control)?
Thanks awfully for help.
Regards
Edited by: Luk004 on 2012-01-16 03:30

> Central Instance : 1.2GB is physical memory is free out of 12GB.
> App1 Instance: 400MB is physical memory is free out of 10GB.
> App2 Instance: 2GB is physical memory is free out of 14GB.
>
> Right now, no background for dialog process are running in any of the three instances but still ocuupy lot of physical memory.
>
> Questions: How to calculate memory in ECC and where could be the rest of memory defined in system? No process is running and all memory seem to be consumed.
Memory is allocated
- by the operating system itself
- by the database (SGA_TARGET)
- by the application server buffers (ST02 et al)
- by the operating system as filesystem cache (if you e. g. use VxFS you may configure the memory consumption)
To see where the memory is being used, use OS tools like 'glance' or 'top'.
Markus

Agent resident memory utilization ALERT question

Hi all,
Every night during the incremental db backups (and during the weekly full db backup) i get an alert for the "Agent resident memory utilization" level. I did find this similiar post but it didnt' help me out much (Agent memory utilization under Linux
I want to know if i should be concerned with this alert and how i can tune to get rid of it. Does anyone know how to handle this?? I found the following in the oracle documentation about this alert:
1 Agent
The oracle_emd target is a representation of the Oracle Management Agent. The Oracle Management Agent is the Management Agent used by Oracle Enterprise Manager. This target type exposes useful information required to monitor the performance of the Management Agent.
Most of the help topics in this helpset use the term Management Agent to refer to the Oracle Management Agent.
1.1 Agent Process Statistics
The EMD Process Statistics provides information about the performance and resource consumption of the Management Agent process. This metric is collected by default on an interval of 1038 seconds. A value that can be changed in the default collection for the oracle_emd target.
1.1.1 Agent Resident Memory Utilization (KB)
The amount of resident memory used by the agent and all of its child processes in KB.
I also get nightly alert for Commit waits but i don't think they are related. Can someone please shed some light on this alert for me? Here is the full alert that i'm getting:
Name=localhost.localdomain:3938
Type=Agent
Host=localhost.localdomain
Metric=Resident Memory Utilization (KB)
Timestamp=Sep 13, 2006 2:08:14 AM EDT
Severity=Warning
Message=Agent resident memory utilization in KB is 223304
Rule Name=Agents Unreachable
Rule Owner=SYSMAN

If your Agent is really getting up to the Warning or Critical Threshold set for the agent resident memory utilization" metric, you can increase the numbers. by default, the Agent "Resident Memory Utilization (%) is set to 20% (Warning) and 30%(Critical) while "Resident Memory Utilization (KB) is 128000 (Warning) and 256000 (Critical)
From Targets > All Targets > Select the Agent > Click Metric and Policy Settings at the bottom of the screen > Edit the Resident Memory Utilization as required.
Or Instead changing the Threshold, on the same Edit screen, you can simply change the "Number of Occurrences" before an alert is triggered.
Meanwhile it is important to check whether the use of such amount is normal.

Oracle memory gets trimmed every 6 hours

We have a very strange behaviour in our SAP R/3 Enterprise 4.7 production system (SAP_BASIS 620).
SAP runs on Windows Server 2003 Enterprise Edition.
10 GB RAM, PAE enabled (Physical Address Extension).
The affected server is the database server, which also runs some working processes (DIA, BTC and UPD).
There are also 6 Windows application servers (x32, x64 and Itanium).
After a normal SAP start, all Windows processes bit by bit allocate their memory.
oracle.exe starts with a Mem Usage 236 MB (VM Size 1.900 MB).
You can see this in Windows Task Manager.
After about 30 minutes oracle.exe reaches its average value of about 2 GB.
The value ranges from 1,9 GB up to 2,5 GB.
Then, about every 6 hours the following happens:
oracle.exe deallocates its memory completely !
No answer in SAPGUI, no reaction on the console for about 5 Minutes.
Then when i get the first look at the Task manager, i see that oracle.exe allocated about 80 MB.
In the next 20 minutes Mem Usage raises up to the average value of about 2 GB.
During this time, the performance comes up again step by step.
Not only Oracle is affected, at least every disp+work process also frees all allocated mamory.
But it seems as if Oracle would be the first to free up its memory and then drags down the SAP Kernel processes.
We have no changes made to the SAP Kernel, we did not apply any Windows updates.
SAP operated error-free for the last 2 years in this configuration.
The only thing we did, was to apply several SAP Support Packages (Basis + Application).
This behaviour occured the next day after we imported those packages.
So we have to suspect these packages, although the symptoms point to a problem with the SAP kernel, Oracle or the Windows memory mamagement.
SAP Support adviced us to reduce the load on the server, so we suspended some work processes.
Result: no improvement.
Next we reduced the Oracle cache size by 250 MB.
Result: the situation became even worse, the error occured every hour.
So we icreased the cache size up to 1,36 GB.
Result: could be an improvement, not sure yet.
I am wondering what must happen, that all processes on a Windows Server deallocate their memory.
Can a ABAP-Report provoke this error ?
Has anybody else ever seen such a behaviour ?
Any ideas ?

Thx for your interest in this issue.
For clarification:
- Database version is 9.2.0.7.0
- We will upgrade to 64 Bit in the next months, but we still need a solution for our 32 Bit system.
- We did not add new application servers. These servers were up and running before and after the problem occured.
- I don't think that Oracle restarts. There are no ORA-entries in the Oracle Log and there is no Oracle-Usertrace.
The system slows down, because every byte, that is backed up in the paging file (as far as i know in MS terms this is called "standby list"), has become invalid and must be read from disk.
Not only Oracle is affected, every process trimmed its working set.
For example Terminal Services is unresponsive for about 4 minutes.
In the end all processes continue their work, but it takes some time until their working set has been restored from the paging file.
No errors occur, no Dumps, no EventLog or SystemLog entries.
There are just some TIMEOUTs, caused by the unresponsiveness of the server in the first minutes of the memory crash.
@Markus:
Yes, i also think that we reached some kind of Oracle memory limit.
Since we increased the Oracle cache size, the frequency of the error has been significantly reduced.
But still i am wondering what funny things can happen.
I would expect Oracle to crash, Windows to bluescreen, SAP to dump.
But freeing the memory of all processes is something completely new to me.
Edited by: Leonhard Bernhart on Jan 8, 2008 5:10 PM
Edited by: Leonhard Bernhart on Jan 8, 2008 5:11 PM

Re: memory utilization

Thanks to all who responded to my question about memory utilization. There
were some good suggestions that I will follow up on. I am very grateful for
the help.
As a general rule, I would agree that memory utilzation problems tend to be
developer-induced. I believe that is generally true for most development
environments. However, this developer was having a little trouble finding
out how NOT to induce them. After scouring the documentation for any
references to object destructors, or clearing memory, or garbage collection,
or freeing objects, or anything else we could think of, all we found was how
to clear the rows from an Array object. We did find some reference to
setting the object to NIL, but no indication that this was necessary for the
memory to be freed.
It is my understanding that in this environment, the development tool
(Forte') claims to handle memory utilization and garbage collection for you.
If that is the case, then it is my opinion that it shoud be nearly
impossible for the developer to create memory-leakage problems without going
outside the tool and allocating the memory directly. If that is not the
case, then we should have destructor methods available to us so that we can
handle them correctly. I know when I am finished with an object, and I
would have no problem calling a "destroy" or "cleanup" method. In fact, I
would prefer that to just wondering if Forte' will take care of it for me.
It seems to me that this is a weakness in the tool that should be addressed.
Does anyone else have any opinions on this subject?

Index rebuild = Drop and recreate, this complete recreated index will be in the memory till completion of the full operation.
The lazy writer process periodically checks the available free space in the buffer cache between two checkpoints. If a dirty data page (a page read and/or modified) in the buffer hasn’t been used for a while, the lazy writer flushes it to disk and then marks
as free in the buffer cache
If SQL Server needs more memory and the buffer cache size is below the value set as the Maximum server memory parameter for the SQL Server instance, the lazy writer will take more memory
If SQL Server is under memory pressure, the lazy writer will be busy trying to free enough internal memory pages and will be flushing the pages extensively. The intensive lazy writer activity affects other resources by causing additional physical disk I/O activity
and using more CPU resources
To provide enough free space in the buffer, pages are moved from the buffer to disk. These pages are usually moved at a check point, which can be:
automatic (occurs automatically to meet the recovery interval request)
indirect (occurs automatically to meet the database target recovery time)
manual (occurs when the CHECKPOINT command is executed)
internal (occurs along with some server-level operations, such as backup creation)
At a checkpoint, all dirty pages are flushed to disk and the page in the buffer cache is marked for overwriting
“For performance reasons, the Database Engine performs modifications to database pages in memory—in the buffer cache—and does not write these pages to disk after every change. Rather, the Database Engine periodically issues a checkpoint on each database. A
checkpoint writes the current in-memory modified pages (known as dirty pages) and transaction log information from memory to disk and, also, records information about the transaction log.”
Raju Rasagounder Sr MSSQL DBA

Daily and weekly repoort about Oracle DB status/statistics to management

Hi,
My management asked me to send them a daily and weekly repoort about Oracle Databases status/statistics etc. I like to know which kind of report mostly other DBA use.
Thanks in advance

- A - wrote:
Thanks sb92075
They want some thing like...
1-) CPU and RAM utilization. easy OS statistics
2-) Database Statisticslike what exactly?
3-) Database Performance which metrics show "database performance"?
4-) Database Storageeasy OS statistics
Edited by: sb92075 on May 27, 2012 10:03 PM

Oracle memory

The Oracle 10g database on AIX installation document asks to pre-check the server, it should have at least 1Gig memory. My question is that at least 1Gig is only oracle itself that will take away at least 1Gig from my total memory of the box? So SGA and PGA are included in this amount of oracle itself or extra usage of the memory?
For example, the box has 4Gig memory, I see 58% is used, that means oracle itself takes about 1Gig and sga_max=1Gig + pga_aggregate_target=0.5Gig, is this correct?

Dear Betty,
The Oracle will eat up your shared pool size in the server mostly as shared memory.
So if you want to calculate the Oracle memory parameters for the server consider:
Total Server Memory = SGA_MAX_SIZE + PGA_SIZE + DEDICATED_USER_CONNECTIONS + OTHER_SERVER_APP
The DEDICATED_USER_CONNECTIONS will appear if your users are set to dedicated mode on their tnsnames. If so, you should consider this additional space that Oracle will request to server in order to create this user connections.
The AIX processes memory is not that easy to see what is really occupied, what is free, what is cached and how many users can connect to the server. You should use pmap to map the process private area, shared area and calculate how much is used, shared and free.
The other thing is that the SGA should be pinned on RAM, so the database will take up all the space when going up and your server will avoid the 'allocating new pages' issues. So you should set up the sga_lock=true parameter if you want to lock the SGA into memory.
Cheers,
Ricardo Rodriguez

Memory utilization on hp-ux

I'm on hp-ux 11.23 Itanium using dbconsole 10.2.0.4. My machine is underutilized most of the time. Periodically, I get memory utilization alerts that I'm using more than 99% of memory. The memory utilization chart shows it burbling around 97-98%, sometimes peaking downwards to 95%. swapinfo tells me I'm using 24% or thereabouts. The help for memory utilization is less than helpful as to how the metric is actually calculated. I can't help thinking it's just plain wrong. Anyone have any idea how to reconcile this? Anyone know how it is calculated?
From memory utilization screen:
Last Known Value 99.56
Average Value 98.96
High Value 99.66
Low Value 95.18
Warning Threshold 95
Critical Threshold 98
Threshold Occurrences 6
Looks like the defaults in the help screen (warning threshold 99, tested every 24 hours) are wrong.

OK, I discovered the Paging Activity screen under All Metrics. There were lots of numbers, so I picked the largest one and clicked on it (Pages Scanned by Page Stealing Daemon (per second)). It showed this nice little graph, bounced around all over the place during the day and flatlined during the night, and the help page said it used pstat_getvminfo(), so I poked around on the net about that. Then when I went back to the Paging activity page, all but two of the numbers (Page-in Requests (per second) and Pages Paged-in (per second)) were zero. WTF?

Hyper-V VMs memory utilization

Hi,
Please let me know the WMI class (query) to check the memory utilization for all the VMs under the Hyper-V host.
Thanks & Regards,
Raamesh Keerthi N J

Hi ,
I would recommend you to use powershell command " Get-vm " to get the memory usage of the VM .
As for using WMI to get the VM's memory usage(I am assuming you are using server2012r2 ) , please try the command below :
$RequestInfo = 1,103,112
$VmInfo = Get-WmiObject -namespace root\virtualization\v2 -class msvm_virtualsystemmanagementservice
$VmInfo.getsummaryinformation($null,$RequestInfo).summaryinformation
For the WMI class syntax please refer to following article :
http://blogs.msdn.com/b/virtual_pc_guy/archive/2013/04/29/powershell-script-to-tell-you-if-you-need-to-update-your-integration-services.aspx
If you have further more question about WMI , please post it here :
http://social.technet.microsoft.com/Forums/en-us/home?forum=ITCG&filter=alltypes&sort=lastpostdesc
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

ABOUT ORACLE TUTORIAL

Am new to oracle.?can anyone please give me a brief idea about oracle.

Can you please tell me the diffrence between
"developer" and "Database Administration DBA"The biggest difference is probably:
- The DBA has a database
- The Developer uses a database
Other differences:
- The DBA is the person who carries backup tapes to the safe room.
- The Developer never does that.
- The DBA is the one who tells the Developer that he cannot have a login for the server OS
- The Developer is the one who just wants to use server side utils, like tkprof
- The DBA is the one who tells the Developer that synonyms are harmful
- The Developer is the one who uses them to encapsulate remote objects
- The DBA is the one who thinks roles are broken since all privs must be known at compile time
- The Developer is the one who must give up on using roles, since he cannot create them
- The DBA is the one who tells the Developer not to care about tablespaces while ordering him to use separate index tablespaces
- The Developer couldn't care less and knows about the myths
- The DBA is the one who complaints about full table scans
- The Developer sometimes design for partition pruning
- The DBA is the one who pokes around in a Toad gui when administering HIS database
- The Developer develops scripts
- The DBA reviews the Developers work, and tells him it's too complicated
- The Developer develops more scripts (Equally complicated)
- The DBA answers questions in General forum
- The Developer answers questons in PL/SQL forum
All out of memory, and of course more nonsense could be written.
Maybe not funny, but I'm sure you get my point:
Being qualified to handle a technology has nothing to do with job title.
It has everything to do with level of education, experience, interest and care.
Just passing through, trolling.
Happy week-end ;)
Peter

About oracle instance

Heloo ....
I want to know informtaion about oracle instance.
What is Instance?
what is link between instance and database?
How to create instance?

You should check Oracle Concept for the answers.
http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14220/intro.htm#sthref83
An Oracle database is a collection of data treated as a unit.
The database has logical structures and physical structures. Because the physical and logical structures are separate, the physical storage of data can be managed without affecting the access to logical storage structures.
What is Instance?The combination of the background processes and memory buffers is called an Oracle instance.
what is link between instance and database?An Oracle database server consists of an Oracle database and an Oracle instance. Every time a database is started, a system global area (SGA) is allocated and Oracle background processes are started. The combination of the background processes and memory buffers is called an Oracle instance.
How to create instance? use DBCA create a database then you can start the instance.

About Oracle SOA Suite 10g Release 3 Distribution (32 or 64)???

Greetings,
I have a question about Oracle SOA Suite 10g Release 3 distribtution, is it 32 or 64 bit????
and if it was 32 bit, is that mean that the OC4J will use maximum 3GB memory and it cant use more????
and if this is true, is there a workaround to make the OC4J use memory more than 3GB (like 8GB or 16.....)
Your response is highly appreciated.

Yes it is possible, but be ware of the runing instances, the callback URL's expect the old IP adress in the endpoint. This is not possible to change.
Check my article:
http://orasoa.blogspot.com/2009/05/bpel-cloning.html
Marc

About Oracle Memory Utilization is 99.54%

Similar Messages

Maybe you are looking for