Re: Full Export Problem

From: Ronald <ronr_at_wxs.nl>
Date: Mon, 2 Nov 1998 20:41:35 +0100
Message-ID: <01HW.B263C97F000A6E5C023A2F10@news.wxs.nl>

On Mon, 2 Nov 1998 17:50:20 +0100, stuco_at_mailcity.com wrote (in message <71knsc$k1$1_at_nnrp1.dejanews.com>):
>
> I have a data warehouse that is pretty big (50 GB and growing) and I am
> currently planning my export jobs. This is how I wish to proceed:
>
> export 1 SYS,SYSTEM export 2 Table set 1

> export 3 Table set 2 export 4 Table set 3

> . . . .

> . .
>
> I also wish to replace a 'Full" export with this strategy. My question is
> can a full export broken up into multiple smaller exports be used to fully
> recover from a database crash. In other words, can I totally rebuild a
> database without doing an export using ORACLE's FULL=Y parameter?

Why not ?
You have to separate the data from the definitions; exp indexes=no, constraints=no rows=yes for every fileset. One exp rows=no full=yes.

When importing first import the rows (including table definitions) and next import the one file containing all constraints & indexes.

I think this will work, only the tablespaces do have to exist before the first imp starts because that's not a full exports resultfile.

cheers
--
Ronald

---

mailto:ronr_at_wxs.nl
http://home.wxs.nl/~ronr/RonR.html (last update: june 8th, 1998) http://www.maccentral.com/news/9804/migration.shtml (forward migration home)

I think so I mac ! Received on Mon Nov 02 1998 - 13:41:35 CST