Re: Question on Backup and Recovery Software comments.

In article <Pine.OSF.4.02.9905162233100.25-100000_at_gonzo.wolfenet.com>,   Jeremiah Wilton <jeremiah_at_wolfenet.com> wrote:

<snip>

> Consider that in the event of a logical corruption or an "oops," a user
> could recover the database in a separate location or with a different SID
> from the running production system. The user could even recover only the
> tablespace with the problem segments, plus the rollback and system
> tablespaces, saving space over restoring the whole database. The problem
> segments could then be exported and imported into the running production
> system. That way the user gets both point-in-time transactional
> coherence, and the whole database doesn't need to be taken down for
> recovery.
>
> --
> Jeremiah Wilton http://www.wolfenet.com/~jeremiah
>
>

Sounds dangerous to me. Suppose your travel agent books you into a certain cabin on a cruise ship. Then someone at the cruise line's IT dept. corrupts the reservations database. Using your off-line recovery there is a period of time where your cabin is shown "available." In the mean time, another travel agent sells me your cabin. Then the DBA completes the recovery. Next week, we both show up at the pier with a confirmed reservation for the same cabin ... --

Ed Stevens
(Opinions are not necessarily those of my employer)

-----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own Received on Mon May 17 1999 - 07:47:15 CDT