> -Original Message-
> We hope by
> eliminating redo log multiplex, but with OS mirroring we
> can speed up this loading process.
--
We deal with this by:
1. Hardware mirroring of archives.
2. Archives go to device on which no other I/O is present a
Hello Guang
>From your note about weekly one day long import I think that you are dealing
with DW.
1) Am I correct?
2) Are there other updates to the database while the import is in progress?
Yechiel Adar
Mehish
- Original Message -
To: Multiple recipients of list ORACLE-L <[EMAIL PROTECT
I script and test as well. But sometimes you can't think of every
possible problem.
My point wasn't to have a contest of who had worse problems or who had
a problem that the other didn't.
merely that sometimes hardware mirroring is not the be-all/end-all
solution.
We all could swap war stories
> -Original Message-
> Sorry if you took offense at some attempted humor.
--
No offense taken here. I've always worked in large environments where there
were multiple DBA's, sys admins, developers, and testers. One cannot be
easily offended and surv
e Administrator
[EMAIL PROTECTED] Quad/Tech International, Sussex, WI USA
> -Original Message-
> From: Rachel Carmichael [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, November 27, 2002 9:54 AM
> To: Multiple recipients of list ORACLE-L
> Subject: RE: redo log f
> I was amazed at the non-security that seems to be rampant out there,
> with mischievous people running around deleting files. I kept
reading
> about it and thinking you've got to be kidding.
Steven,
have you NEVER accidentally, at 3AM, after having been woken from a
sound sleep to a crisis tha
Hi:
I am the original poster and thanks for all your inputs on this topic. Now I
know more about what "might" happen if something goes wrong. The main
purpose of we thinking doing this was to gain some performance. We have a
weekly schema imp process which takes about a day to finish. We hope b
> -Original Message-
> have you NEVER accidentally, at 3AM, after having been woken from a
> sound sleep to a crisis that needs to be fixed RIGHT NOW,
> made a typo?
>
Actually no. But we usually script our actions and test the scripts prior
to doing anything in production. As a sys a
em/Database Administrator
[EMAIL PROTECTED] Quad/Tech International, Sussex, WI USA
> -Original Message-
> From: Stephen Lee [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, November 26, 2002 5:26 PM
> To: Multiple recipients of list ORACLE-L
> Subject: RE:
> -Original Message-
> We do redo log file multiplexing to protect against fat
> fingers and other odd-ball stuff that have caused problems
> for an entire file system. Call it an unreliable OS, poor SA
> (ok, maybe even DBA) practices
I do it because it's a CYA thing of doing it by th
Amen to that!
Stephen,
It seems like you keep this discussion on just for the sake of discussion.
And also, it seems like you live in some kind of "ideal" world, where
hardware and software is 100% error-free and is 100% "bullet-proof" and
"fool-proof", and SAs, DBAs, developers, etc... never make
>Now for those who are into this "worst scenario" thing let me ask you: What
>if I put your storage array between a 30HP air conditioning blower moter and
>a spot welder, and run a couple of paint shakers on top of the array to
>boot. What will your vaunted Oracle multiplexing do for you then? Hu
I suppose I should come clean on this deal and admit that we do indeed have
Oracle duplex the redo files. The only time we would not do this is if some
user with sufficient bureaucratic power has some suckwad app and was
demanding that everything be done to bump up performance. If it comes to
th
-Original Message
I believe the forgone conclusion you are talking about is that "mirroring
outside of Oracle MAY result in data loss" MAY is a very important word.
The multiplexing of redo logs across multiple disks and controllers is a
simple way protect your dat
I agree. And this is why Oracle has the capability to manage many redo log
members in the same group and many copies of the control file. It does not
offer the same for regular data files.
Regards,
Waleed
-Original Message-
Sent: Tuesday, November 26, 2002 6:05 PM
To: Multiple recipients
"While all this is true, this is all based on the forgone conclusion that
mirroring outside Oracle will result in file loss. It is that conclusion
with which I disagree."
I believe the forgone conclusion you are talking about is that "mirroring
outside of Oracle MAY result in data loss" MAY is a
> -Original Message-
> Of course, you'll need Tom Kyte's binary conversion program
> here to execute this very weak proof:
Yeah, well this didn't come from Stephen Hawking. And let's not forget the
part about "in the natural integers". Homey didn't take a bunch of 5000 and
6000 level
ink, Dan [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, November 26, 2002 2:25 PM
> To: Multiple recipients of list ORACLE-L
> Subject: RE: redo log file setup with mirrored drives
>
>
> Stephen,
> Nothing is gained by personal attacks in this forum.
> This forum is
&g
> -Original Message-
> Stephen,
> Nothing is gained by personal attacks in this forum.
Please enlighten me. Exactly what personal attack was made?
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Stephen Lee
INET: [EMAIL PROTECTED]
Fat City Network S
On Tue, 2002-11-26 at 10:50, Stephen Lee wrote:
And from another post ...
> > Because my OS/hardware IS reliable a corrupted
> > log file that is mirrored outside of Oracle will be corrupt -
> > the original is corrupt, so is the mirror.
>
> In one sentence you have claimed that your "OS/hard
, WI USA
> -Original Message-
> From: Fink, Dan [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, November 26, 2002 10:05 AM
> To: Multiple recipients of list ORACLE-L
> Subject: RE: redo log file setup with mirrored drives
>
[snip]
> not protect against the accidental d
Stephen,
Nothing is gained by personal attacks in this forum. This forum is
intended to be a learning experience for all (myself included). I suggest
that you review the archived list and examine the quality of posts by Kirti,
Jared, et.al. They speak for themselves.
BTW, 2 + 2 doe
I was going to let the differences of opinion stand, but I suppose this
requires an answer.
> -Original Message-
>
> Redo and archived redo logs are the most important files in
> the database.
> Lose a datafile? You can still recover the database.
> Lose all controlfiles? They can be r
2002 08:04 AM
Please respond to ORACLE-L
To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
cc:
Subject: RE: redo log file setup with mirrored drives
"Pending further evidence to the contrary, I'll take mirroring external to
Or
Also stand by that "corrupted write will be restricted to just the affected member"
Hence one can simply overwrite the BAD (Corrupted) member with the Good one
-Original Message-
Sent: Tuesday, November 26, 2002 9:40 PM
To: Multiple recipients of list ORACLE-L
Sure...
What I posted c
Sure...
What I posted came from my discussions with others and from various resources on
Metalink and from Oracle Training Classes. Note #45042.1 titled Archiver Best
Practices summarizes it all.
Agreed, that RAID and disk technologies have improved over the years, however, I would
still con
Addressing the corruption issue, Kirti's statement is not speculation. Because my
OS/hardware IS reliable a corrupted log file that is mirrored outside of Oracle will
be corrupt - the original is corrupt, so is the mirror. If I mirror my log files
using Oracle, logfile A may be corrupt, but
"Pending further evidence to the contrary, I'll take mirroring external to
Oracle as the better choice."
Redo and archived redo logs are the most important files in the database.
Lose a datafile? You can still recover the database.
Lose all controlfiles? They can be recreated.
Lose a single redo
If I may offer another view
> -Original Message-
> Having multiple redo log members has its advantages. The
> archiver process 'knows' these multiple members and it will
> optimize the archiving process,
Is there any supporting documentation about this "optimizing"? Are you
sayin
Having multiple redo log members has its advantages. The archiver process 'knows'
these multiple members and it will optimize the archiving process, but it does not
know about the mirrored copies of these logs. The other important thing to know is
that Oracle issues a separate write for these lo
Hi:
We have oracle 8173 running on Sun Solaris box. The current redo files are:
/oracle/oradata/RPT1/redo101.log
/oracle/oradata/RPT1/redo201.log
/oracle/oradata/RPT1/redo301.log
/oracle/u01/oradata/RPT1/redo102.log
/oracle/u01/oradata/RPT1/redo202.log
/oracle/u01/oradata/RPT1/redo302.log
The me
31 matches
Mail list logo
