Re: Bringing up a single tablespace of a large database
Date: 15 Mar 1995 15:07:05 -0600
Message-ID: <3k7ktp$ae6_at_Jester.CC.MsState.Edu>
Dave Crowson <dcrowson_at_amoco.com> says:
>In article <3k5o4b$8qg_at_Jester.CC.MsState.Edu> fwp_at_CC.MsState.Edu (Frank Peters) writes:
>>A few days ago one of our programmers wiped a single table (loaded some
>>new data with a replace option instead of an append option). This
>
>Depends on what sort of backups you've been
>doing...Hot/cold/online/full/incremental
>
>you have been doing backups haven't you ?
Yes. UNIX dumps of a shut down database. That's how I was able to restore the datafiles from before the mistake. Getting the files wasn't the problem. :-)
The problem was how to open the files without having to restore the entire database from before the error.
The trick was to "startup mount" and then do an "alter datafile 'foo' offline" for each datafile that was unavailable. Then an "alter database open" worked fine.
After that I had some trouble with the database trying to use some rollback segments even though they were in datafiles marked offline and even though the init.ora file specified a rollback_segments line with just rollback segments that were restored. Dropping all of the rollback segments that were unavailable solved this problem though I still don't understand why it wanted to use them.
After that I was able to export the table I needed and import it into our active production system.
Thanks to everyone who helped.
-- Frank Peters - UNIX Systems Group Leader - Mississippi State University fwp_at_CC.MsState.Edu - 601-325-7030 - FAX: 601-325-8921 <URL:http://www2.msstate.edu/~fwp/>Received on Wed Mar 15 1995 - 22:07:05 CET