Path: text.usenetserver.com!out02a.usenetserver.com!news.usenetserver.com!in02.usenetserver.com!news.usenetserver.com!postnews.google.com!y71g2000hsa.googlegroups.com!not-for-mail
From: hpuxrac <johnbhurley@sbcglobal.net>
Newsgroups: comp.databases.oracle.server
Subject: Re: San-Based replication VS DataGuard replication
Date: Sat, 4 Oct 2008 12:02:21 -0700 (PDT)
Organization: http://groups.google.com
Lines: 22
Message-ID: <d9fba190-01c7-4956-b39f-c227d8c92763@y71g2000hsa.googlegroups.com>
References: <29638136-ed11-405f-84c2-bc07283254d7@k7g2000hsd.googlegroups.com> 
 <1222494010.972896@bubbleator.drizzle.com> <d34dd8ae-131b-4d64-9447-f6640cbe3568@m36g2000hse.googlegroups.com> 
 <64aee97b-0b2a-4e04-a99c-c4e3e77f1196@t42g2000hsg.googlegroups.com> 
 <1222987500.264251@bubbleator.drizzle.com>
NNTP-Posting-Host: 76.243.183.40
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Trace: posting.google.com 1223146942 9697 127.0.0.1 (4 Oct 2008 19:02:22 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Sat, 4 Oct 2008 19:02:22 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: y71g2000hsa.googlegroups.com; posting-host=76.243.183.40; 
 posting-account=_6ry2goAAAB8CmCVzS5u_8_rocyBncPn
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.3) 
 Gecko/2008092417 Firefox/3.0.3,gzip(gfe),gzip(gfe)
Xref: usenetserver.com comp.databases.oracle.server:448413
X-Received-Date: Sat, 04 Oct 2008 15:02:22 EDT (text.usenetserver.com)

On Oct 2, 6:45=A0pm, DA Morgan <damor...@psoug.org> wrote:
> hpuxrac wrote:
> > There is absolutely no sense in the statement "You can not make SAN
> > replication synchronous"
>
> Actually there is: Oracle is not going to rollback a transaction
> because the SAN can not replicate it. If you would like to name
> and contact information for the product manager at Oracle contact
> me off-line.

Why don't you read up on synchronous replication?

Oracle tries to write something ( say it is a log file block or
anything ) ... storage device A receives the write ... it transmits it
to storage device B ... storage device B acknowledges back to A that
it has the write ... before giving IO ack to oracle.

It is done block by block and has nothing to do with Oracle
transactions.

Sounds like you are just making up stuff.

