On 11/01/10 15:38, Robin Cotgrove wrote:
Thanks Jim.

We'll run those 2 dtrace if and when it happens again. Box has been rebooted 
and issue (which was seen 2 days in a row) has not re-occured. The workload has 
not changed. The virtual stays ~flat-lined all the time on the box because of 
the nature of the workload. The issue seems to re-occur every 60 days, so I 
think something is leaking, but I'm still convinced it's not system virtual 
memory.

Interesting what you say about the ISM/DISM stuff. The way we stopped DISM 
being used for Oracle 10g was setting the SGA MAX and TARGET to equal values in 
the init.ora etc..  and that stopped an ORACLE process per sid called 
ora_dism_xxxxxxxx on startup. Things behaved much better once we did that. We 
believed we were experiencing a known Solaris bug around DISM leak. We have 
since patched the system but not re-enabled the use of DISM.
Hi
Just out of interest could you check the permissions on oradism

ls -l $OH/bin/oradism

it should have root ownership and sticky bit set.
-bash-3.00$ ls -l oradism
-rwsr-x---   1 root     oinstall 1320256 Sep 11 09:48 oradism
-bash-3.00$

Have seen the very odd case of people tarring an OH as oracle user and extracting as oracle user and losing the root bit/sticky bit, which means oradism is effectively broke. I haven't read the thread in entirety but certainly things like performance will suffer, also for DISM as it's not pinned entirely in memory at all times, it must be backed with SWAP. Also to use ISM set SGA_MAX_SIZE to be either equal to or smaller than the constituents of the entire SGA, not SGA_MAX.

But for DISM, swap is vital though, very very vital in the long run.

If you have the alert logs from when it was running with DISM, grep for WARNING and see if any relate to dism, also if trying DISM check the GRANSTATE in x$ksmge view to see if all allocations are locked.

Also is this x86/sparc, what type of box, are the oracle binaries actually local etc.

Enda
_______________________________________________
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org

Reply via email to