dtrace discuss - Sep 2007 - plockstat/dtrace core dump - S10U3 again

Hello,

I have encountered problem described in
http://www.opensolaris.org/jive/thread.jspa?messageID=127449
(plockstat core dump).
- does anybody know which patch fixes it ?
- is the temporary solution mentioned at the above URL (echo
  segvn_lpg_disable/W 1 | mdb -kw) safe for production servers ?
  We have many databases (Oracle) running on the server and 
  I wouldn''t like to see any problems .... :-)


Regards
przemol

-- 
http://przemol.blogspot.com/


























----------------------------------------------------------------------
Mobilne wiadomo?ci w Twojej kom?rce
>>> http://link.interia.pl/f1b9c

Hi Przemol,

przemolicc at poczta.fm wrote:
> I have encountered problem described in
> http://www.opensolaris.org/jive/thread.jspa?messageID=127449
> (plockstat core dump).
> - does anybody know which patch fixes it ?
> - is the temporary solution mentioned at the above URL (echo
>   segvn_lpg_disable/W 1 | mdb -kw) safe for production servers ?
>   We have many databases (Oracle) running on the server and 
>   I wouldn''t like to see any problems .... :-)
It''s fixed in nevada (e.g. the latest Solaris Developer Express), but 
not yet in Solaris 10. I am intending to fix this in Solaris 10 update 5.

I''m reluctant to endorse the workaround mentioned for production 
environments. If this is causing you pain, and you have a service 
contract with Sun, then you can log a call to get an interim patch 
(known as an "IDR").

Regards,

Robert

> Hi Przemol,
> 
> przemolicc at poczta.fm wrote:
> > I have encountered problem described in
> >
> http://www.opensolaris.org/jive/thread.jspa?messageID> 127449
> > (plockstat core dump).
> > - does anybody know which patch fixes it ?
> > - is the temporary solution mentioned at the above
> URL (echo
> >   segvn_lpg_disable/W 1 | mdb -kw) safe for
> production servers ?
> >   We have many databases (Oracle) running on the
> server and 
> >   I wouldn''t like to see any problems .... :-)
> 
> It''s fixed in nevada (e.g. the latest Solaris
> Developer Express), but 
> not yet in Solaris 10. I am intending to fix this in
> Solaris 10 update 5.
> 
> I''m reluctant to endorse the workaround mentioned for
> production 
> environments. If this is causing you pain, and you
> have a service 
> contract with Sun, then you can log a call to get an
> interim patch 
> (known as an "IDR").
Thank you very much, Robert. I''ll check the IDR way ...

Regards
przemol


--
This message posted from opensolaris.org