... with the caveat of somewhat complicating the recovery process.
On Sat, 2004-01-10 at 13:49, DENNIS WILLIAMS wrote:
Ryan - I don't see where you received a direct answer to this question. To
use RMAN to back up to tape you must license what Oracle terms a MML (media
management library).
I can understand the concern about ingesting large amount of data. We ingest
about 200 GB a night. To get around the archiving problem we make a
noarchivelog 'staging' instance, to run our loads. Then we use transportable
tablespaces to move the data to production. Its alot quicker and easier to
Would it be incorrect to assume that you never do inserts
into newly loaded partitions, or updates that could increase
the length of rows?
1 pctfree could be problematic in that case.
Jared
On Sat, 2004-01-10 at 05:04, Ryan wrote:
I can understand the concern about ingesting large amount of
its read only data in production. we monitor for chained rows on our staging
environment and do table reorgs as necessary. Our staging server only
ingests data over night, so we have all day for reorgs. Or we can just do
them on weekends. We may do a handful every few months. We just run a script
Gene - As a part of putting the database back in archivelog mode, I hope you
take another backup.
Dennis Williams
DBA
Lifetouch, Inc.
[EMAIL PROTECTED]
-Original Message-
Sent: Friday, January 09, 2004 4:44 PM
To: Multiple recipients of list ORACLE-L
I put all databases in archive
Ryan - I don't see where you received a direct answer to this question. To
use RMAN to back up to tape you must license what Oracle terms a MML (media
management library). However, you can use RMAN to back up to disk without
any additional purchase. My sys admin evaluated the cost of the MML piece
Would it be incorrect to assume that you never do inserts
into newly loaded partitions, or updates that could increase
the length of rows?
1 pctfree could be problematic in that case.
Btw, if you're sure that rows won't grow, it use even pctfree 0 instead of
1. One thing you have to have in
On 2004.01.10 16:49, DENNIS WILLIAMS wrote:
Gene - As a part of putting the database back in archivelog mode, I hope you
take another backup.
Actually, taking backup should be a part of every major intervention on the database.
Changing the database mode from noarchivelog to archivelog most
Yeah, I configured RMAN on a system. Then the users didn't want me to turn
off cold backups. My response was that a DBA wouldn't say there was such a
thing as too many backups, so we do both.
Specifically with noarchivelog/archivelog, if you try to recover using a
backup from before you turned
Mohammed - When is this database updated? Once/week? Daily? Continuously? If
there is a failure, what is the consequence of returning to the last backup?
How much critical data will be lost? How will recovery times be affected
with/without archive logging? How much does your sys admin know about
Well, recovery might be just a wee bit faster then re-loading few gigs of data
using SQL. Also, developers on that DW might lose any work that they haven't done
the night before. This is a production database, which means that it absolutely
must be in archive log mode. One of the big reasons is
why do you do a cold backup? why not just use RMAN?
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Friday, January 09, 2004 4:34 PM
Mohammed - When is this database updated? Once/week? Daily? Continuously?
If
there is a failure, what is the
My personal opinion is all production databases should be in archivelog
mode. Period. End of story.
Less down time, more recovery optionsit's all good.
Having said that, given a specific business case, with a specific set of
requirements, one could argue for noarchivelog mode, and you
Hi Dennis,
On average, we load data weekly. The load time is no
more 40 minutes to an hour. Like I said, we're small
at the moment. We're at about 70GB which includes
temp and undo and growing at the rate of about 2GB a
month.
Consequence of a failure has been discussed with the
developers
Yes but...
The developers use Cognos tools for all their
development. Nobody writes any PL/SQL, triggers etc.
So again, all that the developers might lose is data
that they loaded which can be easily recovered by
re-running the ETL process.
What I'm trying to say is that the environment from
I put all databases in archive mode, i.e. dev, test, and production.
I can use test db's to test backup/recovery scenario's. The only time they
are not in archive mode is when I am doing a major load
(import,sqlload,etc). After I am done loading data, I put them back into
archive mode. What
Let's assume RMAN is not an option since we don't have
a license or busget to use a third party backup tool
like Legato or Veritas with RMAN (used in a previous
life with Legato NetWorker. Loved it!!)
So now I'm left with archive log mode. Archive logs
backed up nightly and a full backup once a
I never heard about the required license from veritas and legato. Can
someone else confirm that this is necessary? They actually charge you more
money to do use another product with veriftas and legato?
What is a 'BCV'?
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL
BCV = Business Continuity Volume
On 2004.01.09 19:39, Ryan wrote:
I never heard about the required license from veritas and legato. Can
someone else confirm that this is necessary? They actually charge you more
money to do use another product with veriftas and legato?
What is a 'BCV'?
-
Hi Ryan,
Not for RMAN. I meant a license for Veritas or
Legato.
See Mladen's reply re: BCV (basically EMC takes a
snapshot of the mount points onto corresponding mount
points i.e. a 1-to-1 mapping for each mount point onto
a BCV mount point)
Hope that clears up the confusion.
mohammed
---
To:Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
cc:
Subject:Re: Backups in a DW Environment
I never heard about the required license from veritas and legato. Can
someone else confirm that this is necessary? They actually charge you more
money to do use another
Subject: Re: Backups in a DW
Environment
The license is for the
software that interfaces Veritas NetBackup to RMAN. RMAN has an API and NBU has an API. The
intersection of the 2 will set you
back about $1500 US IIRC.Jared
"Ryan" [EMAIL
Mohammed,
Comments inline...
on 1/9/04 2:24 PM, mkb at [EMAIL PROTECTED] wrote:
Have a question on backups in a DW environment.
Our DW is somewhat small at the moment but projected
to grow. I seem to be having a hard time trying to
convince the sys admin that I don't want archive
Let me explain, because I have a little bit of experience with it.
a) BCV's are replicated disks which are synchronized using TimeFinder.
and then separated from the source. The phrase splitting BCV's means
producing an exact disk copy of the original disks, similarly to what dd can
24 matches
Mail list logo
