Xref: alice comp.databases.oracle.server:60845
Path: alice!news-feed.fnsi.net!netnews.com!newshub.northeast.verio.net!news.new-york.net!uunet!ffx.uu.net!an02.austin.ibm.com!ausnews.austin.ibm.com!not-for-mail
From: Doug Cowles <dcowles@bigfoot.com>
Newsgroups: comp.databases.oracle.server
Subject: Re: Import indexfile=blah - What about constraints ?
Date: Sun, 08 Aug 1999 20:31:16 -0400
Organization: IBM Austin 
Lines: 22
Message-ID: <37AE2154.DB7CD537@bigfoot.com>
References: <933846153.8689.0.nnrp-06.c2de6f3d@news.demon.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 4.04 [en] (Win95; U)

Yes..this annoys me also.  You need to run a separate script to get all the
constraints..

Neil Cudd wrote:

> I'm trying to export a schema from my prod'n db and import into my test
> server after modifying the initial extent allocation (short on disk space
> !).
>
> I did an import with indexfile='filename' to get the table and index DDL and
> modified all the initial allocations - no problemo. But I've just noticed
> that no constraint ddl was generated with the indexfile='filename'.
> Unfortunately all my primary keys were created as constraints !
>
> Any ideas greatly appreciated.
>
> Regards,
>
> neil.