There is also the show=y log=<some filename here> combination to imp
that will process all of an dump file and show exactly what is being
done, including constraints, indexes, tables, etc. Again, for this to
provide all DDL for an entire database the dump file must have been
generated with full=y; to provide the DDL for a specific user account
a dump created with owner=<some username here> would be sufficient.
"Howard J. Rogers" <dba_at_hjrdba.com> wrote in message news:<a7u1o3$ihv$1_at_lust.ihug.co.nz>...
> Someone posted about this the other day, and someone else was good enough to
> suggest visiting http://www.databee.com/ and download the freebie 'DataBee'
> software. You give it an export dump file, it extracts all the DDL for you
> (and formats it nicely, too). Procedures, triggers, the lot (assuming your
> dump file was a full=y one).
>
> I was rather impressed with it, I have to say.
>
> You can also use the indexfile attribute when running import, but that only
> gets you a text file containing create table and create index commands, not
> procedures, users and so forth. It doesn't help, either, that all the
> create table statements are remm'd out.
>
> Given that databee does a more comprehensive job, more neatly, and for free,
> I don't see myself bothering with an indexfile again in the near future.
>
> Regards
> HJR
> --
> ------------------------------------------
> Resources for Oracle : www.hjrdba.com
> ============================
>
>
> "Ryan Gaffuri" <rkg100_at_erols.com> wrote in message
> news:a7timk$28f$1_at_bob.news.rcn.net...
> > We do not have a source file of our DDL. Does anyone have a pre-built
> script
> > to extract it?
> >
> >
Received on Thu Mar 28 2002 - 00:23:25 CST
