hboswel1_at_bellsouth.net wrote:
>I have a nightly export/import job that runs, to place some data on a
>database server that sits outside our firewall. The export parfile
>has these parameters:
>
>COMPRESS=Y
>GRANTS=Y
>INDEXES=Y
>ROWS=Y
>CONSTRAINTS=Y
>TRIGGERS=Y
>
>
>The import parfile has these commands:
>
>INDEXES=Y
>GRANTS=Y
>CONSTRAINTS=Y
>ROWS=Y
>IGNORE=Y
>ANALYZE=N
>
>
>The schema being exported/imported has some jobs associated with it,
>that I don't want exported or imported, but that's happening. How do
>I prevent this? I haven't found mention on jobs in the exp/imp
>documentation, and a Metalink search didn't turn anything up.
>
>Thanks,
>Harry Boswell
If all that is needed is the data, use the TABLE=(<table list>) method instead of a FULL export..
Received on Mon Aug 09 2004 - 11:09:19 CDT
