expdp query parameters

From: Kumar Madduri <ksmadduri_at_gmail.com>
Date: Wed, 20 Apr 2011 07:08:17 -0700
Message-ID: <BANLkTinDwsYhqdZAQfNn55rKeE0fHQrDpA_at_mail.gmail.com>

Hi
I have prepared this parfile.
directory=linux_mig

            dumpfile=aexp%U.dmp
            filesize=8388608000
            full=y
            exclude=SCHEMA:"='MDDATA'"
            exclude=SCHEMA:"='OLAPSYS'"
            exclude=SCHEMA:"='ORDSYS'"
            exclude=SCHEMA:"='DMSYS'"
            exclude=SCHEMA:"='OUTLN'"
            exclude=SCHEMA:"='ORDPLUGINS'"
            job_name='linux_migration'
            #transform=oid:n
            *QUERY=applsys.wf_item_attribute_values:"where
item_type!='WFERROR'and name != 'EVENT_MESSAGE'"
            QUERY=DBA_OBJECTS:"where object_type='PACKAGE BODY' and
object_name like 'XLA_00%AAD%PKG'"*
            logfile=expdp_for_of1uat.log

My question is about whether I can have two QUERY clauses like above. I know I can use the multiple exclude and it is working. In addition, from a performance point of view ,would it be better to filter the dmp file like above (using the query clause) or just drop the * '
*XLA_00%AAD%PKG' packages from the source and recreate them after the export
is complete on the source. The 'XLA_00%AAD%PKG' are temporary and there is a script in oracle apps that creates them. But I was thinking it would be safe to exclude from the export, instead of dropping and recreating. I dont know the purpose of these 'XLA_00%AAD%PKG' but these are 200k plus package bodies and expdp and impdp does not like it it and it partially truncates the package body and this would be invalid on the target after import (even if not excluded )
Thank you
Kumar*
*

--
http://www.freelists.org/webpage/oracle-l

Received on Wed Apr 20 2011 - 09:08:17 CDT