oh god I was teasing about flashback query! I don't really think it's
robust enough for production recoveries. Technically you don't need
server-managed undo to use flashback query, it will work with manually
managed rollback segments. But you have less of a chance for the data
to still be in the
It is pretty easy to restore and recover a single table to an
arbitrary point in time from a physical backup. I don't think Oracle
needs to provide an extra feature.
You restore a small subset of the database (system, rollbacks and the
tablespace with the table in it), offline drop the datafiles
isn't that supposed to be flashback query? :)
--- Gene Sais <[EMAIL PROTECTED]> wrote:
> maybe 10i will allow table pt in time recovery :)
>
> >>> [EMAIL PROTECTED] 05/25/02 05:53PM >>>
> you mean the export? it's a lot easier to recover a single table from
> an export and let everyone else ke
maybe 10i will allow table pt in time recovery :)
>>> [EMAIL PROTECTED] 05/25/02 05:53PM >>>
you mean the export? it's a lot easier to recover a single table from
an export and let everyone else keep working. AFAIK, Oracle still
doesn't do table-level recovery, the lowest granularity is tablespac
you mean the export? it's a lot easier to recover a single table from
an export and let everyone else keep working. AFAIK, Oracle still
doesn't do table-level recovery, the lowest granularity is tablespace.
I could be wrong.
Also, exports are good at letting you clone users and application
schem
ED]]On Behalf Of Meomeo NguyenSent:
Friday, May 24, 2002 1:54 PMTo: Multiple recipients of list
ORACLE-LSubject: Re: Database backup question.Thank
You
Thank you all for your
responses. You all really confused me about this
issue. The whole database backups can be consistent or
Meomeo,
Your confusion will be eliminated by acquiring 'Oracle Backup and
Recovery Handbook' by Rama Velpuri.
Read it: do all of the examples.
There is *no* other way.
Jared
On Friday 24 May 2002 13:53, Meomeo Nguyen wrote:
> Thank you all for your responses. You all really confused me abo
b/c the dba has to develop and test on occassion :). i like all dbs the same. oracle
is much friendlier to various recoveries in archivelogmode. besides, i generate <
.01% of the archives i generate in prod. i can afford a few mb. again, this is my
strategy, one of many. whether its best
Thank you all for your responses. You all really confused me about this issue. The whole database backups can be consistent or inconsistent. To perform a consistent whole databse backup is the only valid backup option for databases running in NOARCHIVELOG mode. In contrast, an inconsistent back
Kevin Lange wrote:
>
> If you truely mean that ALL of your databases are in ArchiveLog Mode, why
> would you do that to your Test and Dev databases ?
>
> -Original Message-
> Sent: Friday, May 24, 2002 2:33 PM
> To: Multiple recipients of list ORACLE-L
>
> my backup strategy, fwiw:
>
>
If you truely mean that ALL of your databases are in ArchiveLog Mode, why
would you do that to your Test and Dev databases ?
-Original Message-
Sent: Friday, May 24, 2002 2:33 PM
To: Multiple recipients of list ORACLE-L
my backup strategy, fwiw:
prod - cold monthly, hot 2x week, exp we
my backup strategy, fwiw:
prod - cold monthly, hot 2x week, exp weekly.
test - cold, hot, exp occassional, always can refresh from prod.
dev - cold & hot occassional, exp daily.
all dbs are in archivelogmode!
gene
>>> [EMAIL PROTECTED] 05/24/02 03:04PM >>>
lets not forget the classic "exp".
1
lets not forget the classic "exp".
1. Production database (where you can't lose a single
transaction) - ARCHIVEMODE absolutely
2. Development database (few hrs of transactions ok to
lose) - cold backups
3. Development database (no schema changes, say an
application is being developed with a too
Good choice...archivelog mode will make your life as a DBA much easier.
Have a look at doing hot backups with rman.
Regards,
Ruth
- Original Message -
To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]>
Sent: Friday, May 24, 2002 1:12 PM
>
> Hi Tim and Connor,
> Thanks you a
Hi Tim and Connor,
Thanks you all for your very helpful feedback. I do appreciate it very much. In fact, we are in development at this point, so the database is small and transaction volume is very low. Therefore, my choice for primary backup method is the cold backups. However, to safeguard a
15 matches
Mail list logo