Re: Oracle/Veritas Data Corruption - Complicated!

Have you talked to Oracle/Sun about this? In particualr there were some serious problems with SUN and ISM, and perhaps that is the problem...Have you applied the latest patch sets?

RF

In article <94eh33$mo2$1_at_doppler.a2000.nl>,   "Smiley" <ahijstek_at_hotmail.com> wrote:
> I think I understand what you are saying:
> 1. You created a *new* Oracle-database on the EMC?
> 2. The 150-users were using the production-database runing on the
 A3500?
> 3. During creation on EMC, you saw these problems?
>
> If this is the case, I've seen this before, not specific with
 creation of
> databases
> but datacorruption going to EMC (I saw this happen with Sun E10K's and
> Sun 6500).
>
> In most cases the EMC isn't able to handle the load, the Sun wants to
 send
> a lot of data to EMC, but the EMC isn't able to handle it. At that
 time, the
> connection from the Sun-box to the Oracle-database on EMC is lost,
> with the corruption to follow.
>
> Solution: there's a setting within the Sun-box you can reduce,
 avoiding
> sending too much data. Talk to a Sun-engineer, he probably knows what
 I
> mean.
>
> My 2 thoughts,
> Smiley
>
> "kineticguy" <none_at_spam.noway.net> wrote in message
> news:YXM96.2656$5R4.388269_at_news.uswest.net...
> > First the particulars:
> >
> > Sun Solaris 2.7 (RISC)
> > Oracle 7.3.4.4
> > Veritas Volume Manager 3.0.2c
> >
> > For the last three years, we have routinely made backup/test
 databases by:
> >
> > 1. Full export a production database
> > 2. Create the database on another set of drives by building the
 exact
> > same object names (datafiles, rollback segments) but different
 datafiles
> > 3. Import the exported database.
> >
> > This has always worked smoothly. This was done with a Sun A3500
 array.
> > (All disk is raw under Volume Manager control).
> >
> > Two weeks ago we hooked up an EMC Clariion 4500. We started to
 create a
> > copy of a database during the day when there were 150 users on the
> > production databases. During the creation of the tablespaces for
 the COPY
> > of the database, a few random datafiles corrupted on the production
> > database. Not all of them, just a few. To make matters more
 confusing,
 the
> > first four datafiles were fine, the last four corrupted. Off to
 tape we
> > went with a down production database.
> >
> > This problem only seems to occur when high IO is going on in the
 system
> > (Enterprise 5000). The A3500 is connected via SCSI, the Clariion
 4500 via
> > Fibre Channel.
> >
> > The vendors are stumped! Anyone have any ideas?
> >
> > Thanks!
> >
> >
>
>

Sent via Deja.com
http://www.deja.com/ Received on Mon Jan 22 2001 - 13:34:05 CST