Hi! This is the ezmlm program. I'm managing the
suse-oracle suse.com mailing list.
I'm working for my owner, who can be reached
at suse-oracle-ownersuse.com.
Messages to you from the suse-oracle mailing list seem to
have been bouncing. I've attached a copy of the first
bounce
message I received.
If this message bounces too, I will send you a probe. If the
probe bounces,
I will remove your address from the suse-oracle mailing
list,
without further notice.
I've kept a list of which messages from the suse-oracle
mailing list have
bounced from your address.
Copies of these messages may be in the archive.
To retrieve a set of messages 123-145 (a maximum of 100 per
request),
send an empty message to:
<suse-oracle-get.123_145suse.com>
To receive a subject and author list for the last 100 or so
messages,
send an empty message to:
<suse-oracle-indexsuse.com>
Here are the message numbers:
13400
13401
13402
13403
13404
13405
--- Enclosed is a copy of the bounce message I received.
Return-Path: <>
Received: (qmail 11462 invoked from network); 2 Jul 2007
12:23:11 -0000
Received: from unknown (HELO Relay2.suse.de)
(195.135.221.8)
by 0 with SMTP; 2 Jul 2007 12:23:11 -0000
Received: from Relay2.suse.de (localhost [127.0.0.1])
by Relay2.suse.de (Postfix) with ESMTP id 3E57921F7C
for <suse-oracle-return-13400-bond=yahoo.comlists.suse.com>; Mon, 2 Jul 2007 12:19:35 +0200
(CEST)
Received: from mx1.suse.de ([195.135.220.2])
by Relay2.suse.de (Relay2 [149.44.160.89]) (amavisd-new,
port 10025)
with ESMTP id 25967-09
for <suse-oracle-return-13400-bond=yahoo.comlists.suse.com>;
Mon, 2 Jul 2007 12:19:32 +0200 (CEST)
Received: from starfire.yahoo.com (starfire.yahoo.com
[66.98.192.98])
by mx1.suse.de (Postfix) with ESMTP id 9D22A124AC
for <suse-oracle-return-13400-bond=yahoo.comsuse.com>; Mon, 2 Jul 2007 12:19:32 +0200 (CEST)
Received: by starfire.yahoo.com (Postfix)
id 33A71208124; Mon, 2 Jul 2007 05:19:49 -0500 (CDT)
Date: Mon, 2 Jul 2007 05:19:49 -0500 (CDT)
From: MAILER-DAEMONyahoo.com (Mail Delivery System)
Subject: Undelivered Mail Returned to Sender
To: suse-oracle-return-13400-bond=yahoo.comsuse.com
Auto-Submitted: auto-replied
MIME-Version: 1.0
Content-Type: multipart/report;
report-type=delivery-status;
boundary="0FC9C208121.1183371589/starfire.yahoo.com&qu
ot;
Content-Transfer-Encoding: 8bit
Message-Id: <20070702101949.33A71208124starfire.yahoo.com>
X-Virus-Scanned: by amavisd-new at Relay2.suse.de
X-Spam-Status: No, hits=0.5 tagged_above=-20.0 required=5.0
tests=BAYES_50,
MY_LINUX, MY_SUSE, RAZOR2_CF_RANGE_51_100,
RAZOR2_CF_RANGE_E4_51_100,
RAZOR2_CHECK, SPF_HELO_PASS
X-Spam-Level:
This is a MIME-encapsulated message.
--0FC9C208121.1183371589/starfire.yahoo.com
Content-Description: Notification
Content-Type: text/plain; charset=us-ascii
This is the mail system at host starfire.yahoo.com.
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached
below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can
delete your own text from the attached returned message.
The mail system
<bondyahoo.com>: cannot update mailbox /var/mail/bond
for user bond. error
writing message: File too large
--0FC9C208121.1183371589/starfire.yahoo.com
Content-Description: Delivery report
Content-Type: message/delivery-status
Reporting-MTA: dns; starfire.yahoo.com
X-Postfix-Queue-ID: 0FC9C208121
X-Postfix-Sender: rfc822;
suse-oracle-return-13400-bond=yahoo.comsuse.com
Arrival-Date: Mon, 2 Jul 2007 05:19:49 -0500 (CDT)
Final-Recipient: rfc822; bondyahoo.com
Original-Recipient: rfc822;bondyahoo.com
Action: failed
Status: 5.2.2
Diagnostic-Code: x-unix; input/output error
--0FC9C208121.1183371589/starfire.yahoo.com
Content-Description: Undelivered Message
Content-Type: message/rfc822
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: amavisd-new at yahoo.com
Received: from starfire.yahoo.com ([127.0.0.1])
by localhost (starfire.yahoo.com [127.0.0.1]) (amavisd-new,
port 10024)
with ESMTP id SYvkOVzTPiXq for <bondyahoo.com>;
Mon, 2 Jul 2007 05:19:46 -0500 (CDT)
Received: from lists.suse.com (lists.suse.de
[195.135.221.131])
by starfire.yahoo.com (Postfix) with SMTP id DF8BD208124
for <bondyahoo.com>; Mon, 2 Jul 2007 05:19:45
-0500 (CDT)
Received: (qmail 9967 invoked by alias); 2 Jul 2007 12:22:55
-0000
Mailing-List: contact suse-oracle-helpsuse.com; run by ezmlm
Precedence: bulk
List-Post: <mailto:suse-oraclesuse.com>
List-Help: <mailto:suse-oracle-helpsuse.com>
List-Unsubscribe:
<mailto:suse-oracle-unsubscribe-bond=yahoo.comsuse.com>
List-Subscribe: <mailto:suse-oracle-subscribesuse.com>
X-MIME-Notice: attachments may have been removed from this
message
X-Mailinglist: suse-oracle
X-Message-Number-for-archive: 13400
Delivered-To: mailing list suse-oraclesuse.com
Received: (qmail 9958 invoked from network); 2 Jul 2007
12:22:55 -0000
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 2 Jul 2007 12:18:55 +0200
Message-ID: <A75E2ACD99AC1B4DA3AAF9BD9CD5721501AF3419tlrbeantmbx02.ERF.THOMSON.COM>
In-Reply-To: <465F0924.4040700cheetahmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [suse-oracle] re: connection timeout and nic
outage
Thread-Index: AcejqlsPOP3yiDbaRzerhwWM4/P7yQY4PvKg
From: <herta.vandeneyndethomson.com>
To: <psantoscheetahmail.com>, <suse-oraclesuse.com>
X-OriginalArrivalTime: 02 Jul 2007 10:18:57.0502 (UTC)
FILETIME=[668B97E0:01C7BC92]
X-Virus-Scanned: by amavisd-new at Relay2.suse.de
Subject: RE: [suse-oracle] re: connection timeout and nic
outage
Probably a bit late, but you can combine TAF with FAN (Fast
Application
Notification).
http://download.oracle.com/docs/cd/B1930
6_01/rac.102/b14197/hafeats.htm#
BABECAFD
Kind regards,
Herta
-----Original Message-----
From: Peter Santos [mailto:psantoscheetahmail.com]=20
Sent: Thursday, May 31, 2007 19:43
To: suse-oraclesuse.com
Subject: [suse-oracle] re: connection timeout and nic
outage
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Guys,
In 10g RAC/Linux how should the query timeout be dealt
with when
there is a nic failure. I
understand the concept of NIC bonding, but that is not an
option
that we are considering.
Anyway, my question is how you've dealt with connection
timeouts. In my example, I have TAF
connection setup with the "BASIC" option. Here is
the simple
test case.
1. sqlplus (using descriptor with TAF configured) into
some instance.
2. run a select sys_context('USERENV','INSTANCE_NAME')
from dual;
=09
>> go to node from step 2 and do "ifdown
eth0"
3. re-execute query from step 2 .. this should hang ...
I see the VIP failover almost immediately, but my
connection
will hang on that SELECT for about 15 minutes.
After that it WILL failover to another instance and I can
re-execute the query.
What I've been trying to get out of Oracle Support is an
answer
on shortening the "hang" time. I can't seem
to make any progress on this ... Has anyone tested this
sort of
thing?
- -peter
=09
=09
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGXwkkoyy5QBCjoT0RApcZAJ9dIngwD8V0PtSeq9a6WjLoxgUHUgCe
OM+F
k0U6vcu5Bs20ZibM2cBRcjc=3D
=3Du6hm
-----END PGP SIGNATURE-----
--=20
To unsubscribe, email: suse-oracle-unsubscribesuse.com
For additional commands, email: suse-oracle-helpsuse.com
Please see
http://www.suse.com/oracl
e/ before posting
--
To unsubscribe, email: suse-oracle-unsubscribesuse.com
For additional commands, email: suse-oracle-helpsuse.com
Please see http://www.suse.com/oracl
e/ before posting
--0FC9C208121.1183371589/starfire.yahoo.com--
|