RE: oracle handing memory allocation different between 11g and 12c?
Date: Tue, 16 Feb 2016 18:37:45 +0000
Message-ID: <2038d67a96e047a49e21e0a6642f56ff_at_wpvl1dag02.hcrec.com>
Stefan,
Can you tell me which version and release of Solaris you are using?
Matt
-----Original Message-----
From: Stefan Koehler [mailto:contact_at_soocs.de]
Sent: Tuesday, February 16, 2016 12:07 PM
To: Matt Adams
Cc: oracle-l_at_freelists.org
Subject: RE: oracle handing memory allocation different between 11g and 12c?
Hi Matt,
not quite sure what's wrong in your env. OSM and 12.1.0.2 works like a charm here :)
root_at_SOL:~# pmap -xs 1827
1827: ora_smon_S12DB
Address Kbytes RSS Anon Locked Pgsz Mode Mapped File …
0000000060000000 4096 4096 - 4096 2M rwxs- [ osm shmid=0x5000009 ] 0000000080000000 98304 98304 - 98304 - r-xs- [ osm shmid=0x500000a ] 00000000C0000000 3981312 3981312 - 3981312 2M rwxs- [ osm shmid=0x500000b ] 00000001C0000000 14336 14336 - 14336 2M rwxs- [ osm shmid=0x500000c ]…
Please DTrace the corresponding syscalls to get a better insight in your case.
root_at_SOL:~# dtrace -l
ID PROVIDER MODULE FUNCTION NAME … 256 syscall memcntl entry 257 syscall memcntl return 20833 fbt genunix memcntl entry 20834 fbt genunix memcntl return 78362 fbt shmsys shmget_osm entry 78363 fbt shmsys shmget_osm return 78364 fbt shmsys shmget entry 78365 fbt shmsys shmget return…
Best Regards
Stefan Koehler
Freelance Oracle performance consultant and researcher
Homepage: http://www.soocs.de
Twitter: _at_OracleSK
> Matt Adams <MAdams_at_TroverSolutions.com> hat am 16. Februar 2016 um 16:28 geschrieben:
>
> But in 12c, Oracle prefers using OSM over either ISM or DISM. That appears to be the cause the of the problems I’m having.
>
> Anybody else install 12c on solaris and have issues with OSM not working as expected?
>
> Matt
**** This communication may contain privileged and/or confidential information. If you are not the intended recipient, you are hereby notified that disclosing, copying, or distributing of the contents is strictly prohibited. If you have received this message in error, please contact the sender immediately and destroy any copies of this document. ****
†Ûiÿü0ÁúÞzX¬¶Ê+ƒün– {ú+iÉ^
Received on Tue Feb 16 2016 - 19:37:45 CET