Impdp exclude index

hi all,
Good day...
DB version is 10.2.0.4
Table of 36gb is exported and while importing using impdp i gave
exclude=INDEX:\"IN\(\'GMF_LOT_COST_DETAILS_U1\')"But after this too..while importing it tries to import the index..as i could see the number of rows increasing in the index..why it is so? Does specifyiing exclude=index is enough!!!
thanks,
baskar.l

Hi,
Yes the index and table are in the same schema...
impdp gmf/gmf directory=exp_dir  dumpfile=gmf.dmp logfile=imp.log tables=gmf_lot_cost_details exclude=indexthanks,
baskar.l

Similar Messages

  • Oracle 10.2.0.3.0 - impdp - Unusable index exists on unique/primary ...

    Hi All,
    Oracle 10.2.0.3.0 - during impdp the following failure appears:
    Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
    ORA-39083: Object type CONSTRAINT failed to create with error:
    ORA-14063: Unusable index exists on unique/primary constraint key
    Failing sql is:
    ALTER TABLE "MY_SCHEMA"."MY_TABLE" ADD CONSTRAINT "MY_TABLE_PK" PRIMARY KEY ("ID")
    USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255
    STORAGE(INITIAL 1048576 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
    TABLESPACE "MY_TBS"
    Question:
    The dump file doesn't contain index tree, and impdp should just create index(es) as it appears in the metadata information.
    So what's the point to flush this error?

    Yes, the index is appearing on the dba_indexes table, however its state is 'UNUSABLE'.
    It looks impdp takes its state from origin metadata, puts into destination, and even is not trying to rebuild it.
    Of course, after running ALTER INDEX REBUILD its status was changed to VALID.
    So, what's the point impdp tells about its state? It can be hundreds of unusable indexes, why it's not just rebuilding it?

  • Impdp exclude tables getting error

    hi,
    i issued impdp like this
    $impdp dumpfile=xxxxx.dmp logfile=xxx.log directory=xxxxxx exclude=table:"IN('scott.emp','tiger.dept')" full=y version=10.2.0.3
    getting error
    "exclude badly formed"
    thanks in advance
    g

    Like oradba said, it is better to use a parameter file.
    Depending on your Operational System, special characters in the EXCLUDE clause may need to be escaped if you use the command line.
    Take a look here for more info: http://www.oracle-base.com/articles/10g/OracleDataPump10g.php#IncludeExclude

  • Impdp exclude some table grants

    Hi,
    I exported a schema containing tables. Each table has grants provided to other schemas.
    for example:
    the schema CSFDS_BAR grants SELECT, INSERT, UPDATE, DELETE on the table EXAMPLE to the schema CSFDS_FOO
    and SELECT on the same table to the schema QUX.
    I would like to import the datapump to another schema: ERHPQ_BAR; and remap the grants of the table EXAMPLE of CSFDS_FOO to ERHPQ_FOO but exclude the grant provided to QUX.
    I use the following parameters to remap the schemas.
    SCHEMAS=CSFDS_BAR
    EXCLUDE=USER,SYSTEM_GRANT,ROLE_GRANT,DEFAULT_ROLE,TABLESPACE_QUOTA
    REMAP_SCHEMA=CSFDS_BAR:ERHPQ_BAR
    REMAP_SCHEMA=CSFDS_FOO:ERHPQ_FOO
    Grants to CSFDS_FOO are correctly remap to ERHPQ_FOO. But I haven't a way to exclude the grants to QUX.
    I tried EXCLUDE=OBJECT_GRANT:"GRANTEE in ('QUX')" but failed.
    Please advice.
    Sebastien

    Hi,
    "The error I got is
    With the Partitioning, OLAP and Data Mining options
    ORA-39001: invalid argument value
    ORA-39071: Value for EXCLUDE is badly formed.
    ORA-00920: invalid relational operator"
    this Error you get because you can not use the wrong syntax for Exclude in your command
    I tried your suggestion but it only exclude the grants provided the grantor not the grantee.
    AFAIK , you can not do what you want.

  • Impdp exclude=schema

    hi all,
    i have written this
    EXCLUDE=SCHEMA:"='ORDERS'"
    but it is not working...
    i even tried like this
    EXCLUDE=SCHEMA:\"='ORDERS'\"
    but i am getting error like "ORDERS" is INVALID identifier.
    so can any body please tell me how to user schema name in exclude....

    user5368861 wrote:
    hi all,
    i have written this
    EXCLUDE=SCHEMA:"='ORDERS'"
    but it is not working...
    i even tried like this
    EXCLUDE=SCHEMA:\"='ORDERS'\"
    but i am getting error like "ORDERS" is INVALID identifier.
    so can any body please tell me how to user schema name in exclude....if you place everything in a "control file",
    then you won't have to battle with command line interpreter

  • EXPDP/IMPDP EXCLUDING ROLES

    Hi All,
    I can't call myself new to this forums since I have more than 10 post here but I can call myself new to Oracle databases so please bear with me.
    I have a scenario where I need to datapump fron source to target but the issue here is I should not export any connect,resource,dba roles associated with the users.
    Can anyone help me what needs to be excluded during the initial export to avoid them being imported on the target.
    Thanks in advance for your help,
    -N

    Hi 705159 ,
    Thank you for your reply.
    I m familiar with the EXCLUDE option. I need everything(tables,objects,synonyms and all that is there) except the roles and that too only certain roles.
    Initially I figured out that I would do content=data_only and then apply all the metadata But found out that it is leads to same point.
    I have to manually go revoke all the CONNECT,RESOURCE and DBA roles for certain users.
    EXCLUDE option comes with role_grants, default_roles and grants.
    I am sure role_grants and grants would not solve my problem. I haven't tried default roles.
    So, it would be helpful if some had faced similar situation can guide me.
    Thanks,
    -N

  • How to ignore index during impdp...

    Hi All,
    I have Oracle 11g database, I want to import one schmea;s tables into 11g database. Table is having 2 millons records and table size is 54G.
    During impdp this will definately take long time. As we had ignore=y and create index file option with IMP, do we have similar kind of thing with impdp?
    If you have any idea then please suggest me.
    Thanks in advance.

    Hi ,
    your suggested link and exclude option helps me.
    I have one query , in my impdp if I mentioned exclude parameter like exclude=INDEX:IN('TESTEMP') , then will it exlude only TESTEMP table's index or entire schema's index?
    my entire impdp command like below:
    impdp system/********@testqa remap_schema=SCOTT:SCOTT dumpfile=SCOTT.dmp TABLE_EXISTS_ACTION=SKIP
    exclude=INDEX:IN('TESTEMP') logfile=SCOTT_!.log directory=DATA_PUMP_DIR
    when this dump is running I observed that it was taking too much time on this line "SCHEMA_EXPORT/TABLE/INDEX/INDEX"...so I though it create indexes for all the tables except which I exclude in command.
    Please suggest me.
    Thanks...

  • Impdp index

    Hello guys,
    i will do expdp of the whole 10gR2 database and impdp it to 11gR2 database.
    Indexes of the userA in the source database are created in the tablespace indexA,
    and i would like to impdp that user in the target 11g db so when his indexes are created they are created not in indexA tablespaces but in
    indexB tablespace.
    Is there some remap command for that ?

    Dean Gagne wrote:
    Hi,
    The 2 replies that stated:
    remap_tablespace=USERA:IndexA,USERA:IndexBand
    impdp userA/passA REMAP_TABLESPACE='tblA':'tblB'are incorrect. There is no such parameters in Data Pump. The remap_tablespace takes only an old tablespace name and a new tablespace name. It is not further qualified by an object type, object schema ,or object name.
    The only thing you can do is:
    remap_tablespace=old_tablespace:new_tablespace
    If you really need indexes to be remapped to a different tablepace then the only think you can do "with data pump" is to use sql file and then edit the file. Here is what you can do:
    impdp user/password exclude=indexes -- this will import everything but indexes.
    impdp user/password include=index sqlfile=index.sql -- this will create a file called index.sql that will contain all of the create statements for the indexes
    Then you can use your favorite editor and alter the tablespace names until you are happy, You also need to look for "-- connect" and add any passwords that are missing. Then from sqlplus just run the index.sql file.
    Thanks
    DeanDean,
    Please read the Oracle document:
    REMAP_TABLESPACE
    Default: none
    Purpose
    Remaps all objects selected for import with persistent data in the source tablespace to be created in the target tablespace.
    Syntax and Description
    REMAP_TABLESPACE=source_tablespace:target_tablespace
    Multiple REMAP_TABLESPACE parameters can be specified, but no two can have the same source tablespace. The target schema must have sufficient quota in the target tablespace.
    Note that use of the REMAP_TABLESPACE parameter is the only way to remap a tablespace in Data Pump Import. This is a simpler and cleaner method than the one provided in the original Import utility. In original Import, if you wanted to change the default tablespace for a user, you had to perform several steps, including exporting and dropping the user, creating the user in the new tablespace, and importing the user from the dump file. That method was subject to many restrictions (including the number of tablespace subclauses) which sometimes resulted in the failure of some DDL commands.
    By contrast, the Data Pump Import method of using the REMAP_TABLESPACE parameter works for all objects, including the user, and it works regardless of how many tablespace subclauses are in the DDL statement.
    You say that my " impdp userA/passA REMAP_TABLESPACE='tblA':'tblB'" is wrong, then you say "There's no such parameters in Data Pump! The only thing you can do is: remap_tablespace=old_tablespace:new_tablespace" - What is the difference? Is there a syntax error or something?
    Please clarify
    Thanks
    Gokhan

  • Exporting index with partition export using expdp

    Hi,
    I am using EXPDP export In 11.1.0.7, is there a way i can export indexes along with the partition export of a table. With full table export, indexes are exported, but i don't see this with only a single partition export because i don't see indexes creation in following scenario.
    1. Export a partition from the production table.
    2. In development environment, drop all indexes on this table.
    3. Drop same partition in development before importing it afresh from the export file created at first step.
    4. Import the partition exported n first step (this does not automatically create indexes dropped in step 2.
    5. Manually recrease indexes again.
    Thanks

    when you do a table mode export, indexes are included, unless you said exclude=index. Please list your expdp and impdp command and the log files to show that indexes are not included.
    Thanks
    Dean

  • Impdp Performing a Schema-Mode Import Example

    The Oracle docs ( http://docs.oracle.com/cd/B12037_01/server.101/b10825/dp_import.htm#i1006564) has an example of performing a schema-mode import as follows:
    impdp hr/hr SCHEMAS=hr DIRECTORY=dpump_dir1 DUMPFILE=expschema.dmp
    EXCLUDE=CONSTRAINT, REF_CONSTRAINT, INDEX TABLE_EXISTS_ACTION=REPLACE
    Looking carefully at this example what does " INDEX TABLE_EXISTS_ACTION=REPLACE" mean, specifically with respect to "INDEX"?
    Does it mean it will drop the table and associated index if it already exists and then re-create and load it using the dump file contents?

    Index is an argument to "EXCLUDE" and Table_Exists_Action is separate option. In this example, It is excluding Indexes during import. It has nothing to do with "TABLE_EXISTS_ACTION=REPLACE"
    Thanks

  • Expdp impdp - redo generation?

    Friends...
    Oracle 11gr2 SE
    OS: Linux
    I did tried to search in documentation but couldn't find answer.
    I'm dropping some tables but before that exporting them for backup, db is in archivelog mode.
    Before dropping tables, trying to find whether expdp job generates lots of redo or not since file system only have 20 GB of free space.
    Question.
    1. If I'm performing expdp of some tables with the size of 80 GB (table size.. index not included), does expdp will generate similar amount of redo or will it generate lots of redo?
    2. Does impdp job also generate lots of redo or only during index creation in impdp?
    thanks,
    Mike

    Export do NOT generate any redo. It's just dumping data into files in binary format. Very minimal redo just to maintain data export dump table but very very minimal. IF I have to guess no more than 1 MB.
    Import does generate redo logs. Imports run 'Insert' statement behind the scenes and it does generate lot of redo logs. You can use sqlfile to create index definition and than run it manually with NOLOGGING which will reduce some redo. something like
    impdp user/password exclude=indexes -- this will import everything but indexes.
    impdp user/password include=index sqlfile=index.sql -- this will create a file called index.sql that will contain all of the create statements for the indexes

  • Impdp

    Hi,
    I am importing partitions separately in a new schema and using this command
    impdp sh2/xxx directory=dp_dir dumpfile=export_sh1.dmp logfile=exportsh1.log tables=sh1.costs1_part:p4 table_exists_action=append content=all remap_schema=sh1:sh2
    It gives an error ORA-39151: Table "SH2"."COSTS1_PART" exists. All dependent metadata and data will be skipped due to table_exists_action of append
    Although it imports that partition and I can verify the records as well. How to fix this error, I have to import the indexes as well which it skipped. How can i do that?
    Any suggestions?
    Thanks

    Check
    ORA-39151 in impdp
    use
    CONTENT=DATA_ONLY TABLE_EXISTS_ACTION=APPEND EXCLUDE=INDEX,CONSTRAINT
    Edited by: Osama_mustafa on Oct 24, 2012 9:13 AM

  • INDEX failed to create while  Import using datapump

    Hi DBA's
    database 11.2.01
    OS : Solaris 10
    I am trying to Import the data using the following command.
    impdp system/******* SCHEMAS=EIMS DIRECTORY=expdp_dir DUMPFILE=eimsexp.dmp*
    but it fails import index and error out, but the tables and data imported.
    I checked in the metalink and followed the Note id (During Data Pump Import Index Creation Fails With: ORA-39083 and ORA-14102 errors OR ORA-39083 ORA-02158 and ORA-39112 errors [ID 1066635.1]) , but no luck.
    Kindly advice me.
    ERROR
    ORA-39083: Object type INDEX failed to create with error:
    ORA-14102: only one LOGGING or NOLOGGING clause may be specified
    Failing sql is:
    CREATE UNIQUE INDEX "EIMS"."PK_MDS_PSTN_LEVEL" ON "EIMS"."MDS_PSTN_LEVEL" ("REGION_CODE", "AREA_CODE", "LEVEL_NO", "EXCHANGE_CODE") PCTFREE 10 INITRANS 2 MAXTRANS 255 NOLOGGING NOCOMPRESS LOGGING STORAGE( INITIAL 65536 FREELISTS 1 FREELIST GROUPS 1) TABLESPACE "EIMS_DATA" PARALLEL 1
    ORA-39083: Object type INDEX failed to create with error:
    ORA-14102: only one LOGGING or NOLOGGING clause may be specified
    Best Regards,
    SG

    Dear Hussein,
    Yes i applied the patch, still i am getting the same error and again i followed one more note (Impdp Failed With Error Ora-39083, 0ra-01403 On Index_statistics (Doc ID 755253.1))
    in that note i given option "exclude=index", then i got in different error.
    We are in the process of doing testing on Tablespace Encryption.
    We are having two instances one is dev and uat instance.
    we are creating Encryption tablespace on uat instance and trying to import the data from dev instance only from particular user.
    We completed the followings.
    1. Created tablespace Encryption.
    2. Created user and assigned the tablespace to the user EIMS1.
    3. Took export from the dev instance using the following command.
    expdp system/******** SCHEMAS=EIMS DIRECTORY=expdp_dir DUMPFILE=eimsexp.dmp
    4. Importing data from
    impdp system/******** REMAP_SCHEMA=EIMS:EIMS1 DIRECTORY=expdp_dir exclude=index DUMPFILE=eimsexp.dmp
    Error
    ====
    ORA-39083: Object type CONSTRAINT failed to create with error:
    ORA-14102: only one LOGGING or NOLOGGING clause may be specified
    Failing sql is:
    ALTER TABLE "EIMS1"."DOCS" ADD PRIMARY KEY ("ID") USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 NOLOGGING NOCOMPRESS LOGGING STORAGE( INITIAL 65536 FREELISTS 1 FREELIST GROUPS 1) TABLESPACE "EIMS_DATA" ENABLE
    ORA-39083: Object type CONSTRAINT failed to create with error:
    ORA-14102: only one LOGGING or NOLOGGING clause may be specified
    before i used to get the bellow errors
    ==========================
    ALTER TABLE "EIMS1"."TST1" ADD CONSTRAINT "ADMACHINEDEPLOYMENTSTATUS_PK" PRIMARY KEY ("MID") USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 NOLOGGING NOCOMPRESS LOGGING STORAGE( INITIAL 65536 FREELISTS 1 FREELIST GROUPS 1) TABLESPACE "EIMS_DATA" ENABLE
    Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
    ORA-39083: Object type INDEX_STATISTICS failed to create with error:
    ORA-01403: no data found
    ORA-01403: no data found
    Failing sql is:
    DECLARE I_N VARCHAR2(60); I_O VARCHAR2(60); c DBMS_METADATA.T_VAR_COLL; df varchar2(21) := 'YYYY-MM-DD:HH24:MI:SS'; BEGIN DELETE FROM "SYS"."IMPDP_STATS"; c(1) := 'ID'; DBMS_METADATA.GET_STAT_INDNAME('EIMS1','DOCS',c,1,i_o,i_n); INSERT INTO "SYS"."IMPDP_STATS" (type,version,flags,c1,c2,c3,c5,n1,n2,n3,n4,n5,n6,n7,n8,n9,n10,n11,n12,d1,cl1) VALUES ('I',5,0,I_N,NUL
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"EIMS1"."PK_MDS_PSTN_LEVEL" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"EIMS1"."PK_MD_AMT_REQUEST_PRIORITY" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"EIMS1"."PK_MD_AMT_REQUEST_QUEUE" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"EIMS1"."PK_MD_BH02_REQUEST_PRIORITY" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"EIMS1"."PK_MD_BH03_REQUEST_PRIORITY" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"EIMS1"."PK_MD_BH03_REQUEST_QUEUE" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"EIMS1"."PK_MD_BH04_REQUEST_PRIORITY" creation failed
    Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
    Job "SYSTEM"."SYS_IMPORT_FULL_01" completed with 1049 error(s) at 20:43:02
    Thanks
    SG

  • Impdp/expdp ignoring logfile path.

    Greetings All, hopefully this is a no brainer for one of you. Whenever I use impdp/expdp and i specify: logfile=direcotry:filename, or directory=path, logfile=filename they are ignored and the logfile is always written to ORACLE_HOME\database.
    I am on the Windows platform and I am running 11g R1 SP19
    Thanks.

    impdp system/sys@DP1 LOGFILE=DATADUMP_DIR:ACCOUNT_IMP.log DUMPFILE=DATADUMP_DIR:ACCOUNT.DMP job_name=ACCOUNTImport metrics=y trace=4a0300 exclude=index,ref_constraint tables=TESTUSER.ACCOUNT

  • How to view index details of another user

    I can't view index detail of another schema in sql developer release 5.
    I'm doing this steps :
    1) I'm connecting with user lopes
    2) Open folder of user mrt
    3) Open table folder
    4) select a table xpto. At this point is openeda a frame details of table xpto. In this frame several information are displayed, when I select Indexes nothing is showed, but this table has a lot of indexes.
    How should I make this indexes information visible ? I think this form is using user_indexes.
    Thanks in advance.
    Danilo

    Who owns the indexes?
    I have cases where I am logged on as a user who has access to a table owned by another user, but indexes created and owned by the connected user (so would obviously be able to see them) are not displayed on the indexes tab for the table.
    I get the same problem with triggers owned by the connected user and dependencies to objects owned by the connected user not displaying on the table tab for tables owned by a different user.
    Presumably, rather than excluding indexes, triggers or dependencies owned by the current user, the details are being restricted to objects owned by the table owner.

Maybe you are looking for