RE: Oracle's Updates Subscription Service

Thanks
for the input, Ross.
<SPAN
class=830032422-01032001> 
As far
as data corruption goes, it's neither semantic nor physical (well, there can be some semantic corruption in certain circumstances, but they're being worked on. We call them "bugs" here.)   :>)
<SPAN
class=830032422-01032001> 
Our
developers seem to have inadvertantly gotten a grasp on the concept of an atomic transaction, and have coded many, many of them. As you know, MySQL does not do referential integrity, so all of our referential integrity is done at the application level. What appears to be happening is that during periods of heavy load the MySQL daemon occasionally gets confused in the midst of an "atomic" transaction and parts of the transaction are committed to the database while parts aren't. In fact, during periods of heavy load the MySQL daemon just gives up the ghost and dies. This is what we believe causes the data corruption.
<SPAN
class=830032422-01032001> 
BTW,
there's no concept of a rollback in MySQL, either. That can be a problem when a transaction doesn't complete.   :>)
<SPAN
class=830032422-01032001> 
Could
we really be seeing semantic or physical corruption and not realizing it? Well, maybe. But, we've moved our biggest, most active customers from MySQL to Oracle and their data corruption problems disappear. <SPAN
class=830032422-01032001> 
MySQL
definitely has its place in the world, and it had a place in ours back before we had customers beating on our databases. But, we're growing up now, and like all grown-up guys we're looking for bigger, more expensive toys. Oracle certainly fits that bill.   :>)
<SPAN
class=830032422-01032001> 
--Walt
Weaver
 
Bozeman, Montana, USA
<FONT
size=2><FONT color=#0000ff
face=Arial> -----Original Message-----From: Mohan, Ross [mailto:MohanR_at_STARS-SMI.com]Sent: Thursday, March 01, 2001 2:21 PMTo: Multiple recipients of list ORACLE-LSubject: RE: Oracle's Updates Subscription Service

<FONT color=#0000ff face=Arial

  size=2>Walt,
<FONT color=#0000ff face=Arial

  size=2> 
  Love
  that last line. But, i'll resist the temptation to bite the bait.   

<FONT color=#0000ff face=Arial

  size=2> 
  For
  you other stuff, i've embedded some newbie comments
<FONT color=#0000ff face=Arial

  size=2>below...stuff you've likely seen, heard, or thought about   before.
<FONT color=#0000ff face=Arial

  size=2> 
<FONT color=#0000ff face=Arial

  size=2>thx
<FONT color=#0000ff face=Arial

  size=2> 
<FONT color=#0000ff face=Arial

  size=2>Ross   

    <FONT face="Times New Roman"
    size=2>-----Original Message-----From: Weaver, Walt     [mailto:wweaver_at_rightnow.com]Sent: Thursday, March 01, 2001 3:27     PMTo: Multiple recipients of list ORACLE-LSubject: RE:     Oracle's Updates Subscription Service     In
    addition, since MySQL has no concept of a transaction or rollback, data     corruption is a constant problem. <SPAN     class=100241021-01032001> 
    <SPAN
    class=256273719-01032001><SPAN
    class=100241021-01032001> 
    <SPAN
    class=256273719-01032001>||  Huh? 
    Semantic corruption due to lack of developer transaction control is one     thing. Actual, physical corruption
    <SPAN
    class=256273719-01032001>is a CONTROLLER or     DISK problem. Or izzit something else? Your developers should be able to     manage
    <SPAN
    class=256273719-01032001>transactions on the     client, hell, all Oracle does is put x-action control in the db so the     developers need to
    <SPAN
    class=256273719-01032001>think less ( "less",     not "not at all") about it......  If you are talking about a hardware     problem, you gotta fix
    <SPAN
    class=256273719-01032001>that...if it is     semantic..i.e. code stepping on 'in flight' data, have a real sit down with     your developers.....
    <SPAN
    class=256273719-01032001><SPAN
    class=100241021-01032001>  Received on Thu Mar 01 2001 - 17:16:43 CST