Re: Effect of listener on existing connections?

From: AGT <>
Date: Tue, 17 Jun 2008 08:41:58 -0700
Message-Id: <>

On Tue, 17 Jun 2008 08:17:40 +0200, Robert Klemme wrote:

> On 16.06.2008 23:48, wrote: 

>> In any case, we haven't figured out how to replicate the scenario yet
>> - it only occurs in the production environment, and never showed up
>> during our testing. We typically tested a months worth of operation
>> at an accelerated rate (anywhere from 4x to 40x the normal speeds, so
>> tests finished in 2 - 7 days). We could start running some tests at
>> 1x speeds, but given the intermittent rate of failure, it would be
>> hard to draw any conclusions from a non-zone-based system that didn't
>> fail after running for a month or two.
Sounds like
>> We may as well kick off a several-month simulation, though, in case we
>> start to see this problem occur with regularity.
You could or see below
> I don't know Solaris too well but is there any chance to have some 
> monitoring run on the production box that exhibited the error over the 
> course of a week and try to capture circumstances of the error surfacing 
> that way?

What if it all happens in millisecond or less... Hard to capture that. Even with dtrace

> Maybe you can collect some network statistics along with > other data and later analyze it and find the error.

Theres many a release of "Solaris" for many HW platforms. All of them must be patched regularly especially if 'something funny is going on". One of my clients utterly refuses to patch the OS claiming that would introduce a "change" yet they patch everything else Oracle without question.. As I said I have serious doubts that zoning or ZFS would cause this, but a missing kernel/driver patch or a simple tweak in /etc/system might make the ghost go away. For near instant rollback I suggest enabling live upgrade - just in case a "change" is problematic Received on Tue Jun 17 2008 - 10:41:58 CDT

Original text of this message