Re: Partially Import from a dump file

Say your large table is called big_table. Create a table in your target database called big_table (fields do not matter, the table name should be the same. Like so - create table big_table (dummy_field number);) and import using ignore=n (you do not even have to specify it explicitly, it is the default). The import will error on the creation of the table, big_table and import the rest of the 149 tables. You can then import that one big table using tables=xxxx option in import.

Murali Sreedhar

mpir_at_bellsouth.net (Joe Maloney) wrote in message news:<d17bad25.0107131228.1c854015_at_posting.google.com>...
> Presumptavely, the db is in place.
>
> Get a list of the table names spooled from dba_tables ("select
> owner||'.'||tablename from dba_tables order by owner||'.'||tablename
> ") with a where clause for your owners.
>
> Edit the spool file into a par file for import, delete the unwanted
> table, start the import and go to lunch.
>
>
> Thomas Kyte <tkyte_at_us.oracle.com> wrote in message news:<9il8i7046t_at_drn.newsguy.com>...
> > In article <ztm37.113$H%4.4487_at_nreader1.kpnqwest.net>, "Gaby" says...
> > >
> > >Hi,
> > >I want to import all tables from a dump file, but i want to exclude one.
> > >I know the option from import 'tables=xxx'. I have, I don't know really, but
> > >ap 150 tables.
> > >So I want to import 149 and the last table seperate (it's the greatest table
> > >with many indexes).
> > >Can anyone help me?
> > >DB-Version = 8.1.7.0.0
> > >
> > >--
> > >Gaby
> > >gspiessl_at_gmx.at
> > >
> > >
> >
> > quick idea:
> >
> > put a trigger on the table that is simply:
> >
> > create or replace trigger T
> > before insert on that_table
> > begin
> > raise_application_error( -20001, 'go away' );
> > end;
> >
> >
> > imp will import the 149 tables successfully, hit this one and skip it and
> > "terminate with warnings" (or errors but who cares, it commits after each table)
> >
> >
> > drop trigger after importing.
Received on Mon Jul 16 2001 - 14:53:29 CDT