avoid impdp ORA-31684

Hello

on 11.2.0.3 on Win 2008

How to avoid the ORA-31684... Already exists

When you use impdp?

original imp, we used to IGNORE = Y

Thank you.

.


remove object before impdp

Tags: Database

Similar Questions

  • Import IMPDB problem. ORA-31684

    Hi Experts.

    When I try to import using impdb, I get the following error.
    impdp test_050211/test_050211@gemsdb DIRECTORY=expdpdir table_exists_action=replace DUMPFILE=test_030211.dmp exclude=USER:\"=\'test_030211\'\"
    Error:
    Import: Release 11.1.0.6.0 - Production on Friday, 18 February, 2011 17:24:59
    Error 
    Copyright (c) 2003, 2007, Oracle.  All rights reserved.
    
    Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    Master table "test_050211"."SYS_IMPORT_FULL_01" successfully loaded/unloaded
    Starting "test_050211"."SYS_IMPORT_FULL_01":  test_050211/********@gemsdb DI
    DIRECTORY=expdpdir table_exists_action=replace DUMPFILE=test_030211.dmp
    Processing object type SCHEMA_EXPORT/USER
    ORA-31684: Object type USER:"test_030211" already exists
    Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
    Processing object type SCHEMA_EXPORT/ROLE_GRANT
    Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
    Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
    Processing object type SCHEMA_EXPORT/SEQUENCE/SEQUENCE
    ORA-31684: Object type SEQUENCE:"test_030211"."AD_ERROR_SEQ" already exists
    ORA-31684: Object type SEQUENCE:"test_030211"."AD_PINSTANCE_SEQ" already exists
    ORA-31684: Object type SEQUENCE:"test_030211"."DBA_ERRORLOG_SEQ" already exists
    ORA-31684: Object type SEQUENCE:"test_030211"."LINENO_SEQ" already exists
    ORA-31684: Object type SEQUENCE:"test_030211"."MICROSOFTSEQDTPROPERTIES" already exists
    ORA-31684: Object type SEQUENCE:"test_030211"."SEQ_DEPTID" already exists
    ORA-31684: Object type SEQUENCE:"test_030211"."STMT_AC_HDR_SEQ" already exists
    Thanks in advance.

    Published by: Senthil_kumar on February 18, 2011 17:38

    Published by: Senthil_kumar on February 18, 2011 17:39

    1. try to use parfile
    2. give the user name that you want to exclude uppercase (assuming it was not created in lowercase with the quotation marks)

    Nicolas.

  • IMPDP ORA-39083: ORA-06564

    Hi all

    Redo EXPDP and IMPDP.

    How to avoid this error term impdp? When do the expdp treat?
    ORA-39083: Object type TABLE:"SPRODADM"."ET$0A9D022D0001" failed to create with error:
    ORA-06564: object CCB_MIG_DIR does not exist
    Failing sql is:
    CREATE TABLE "SPRODADM"."ET$0A9D022D0001" ("ADJ_ID" CHAR(12 BYTE), "SEQNO" NUMBER(5,0), "TOU_CD" CHAR(8 BYTE), "UOM_CD" CHAR(4 BYTE), 
    "SQI_CD" CHAR(8 BYTE), "RS_CD" CHAR(8 BYTE), "EFFDT" DATE, "RC_SEQ" NUMBER(4,0), "DST_ID" CHAR(10 BYTE), "CURRENCY_CD" CHAR(3 BYTE), 
    "CHAR_TYPE_CD" CHAR(8 BYTE), "CHAR_VAL" CHAR(16 BYTE), "PRT_SW" CHAR(1 BYTE), "APP_IN_SUMM_SW" 
    ORA-39083: Object type TABLE:"SPRODADM"."ET$099803190001" failed to create with error:
    ORA-06564: object CCB_MIG_DIR does not exist
    The client give us just this dump and when I impdp there I encountered this error. What I will tell them to include things in the expdp so that
    I will not meet it?

    Thank you very much
    Kinz
    ORA-06564: object CCB_MIG_DIR does not exist
    

    It's pretty simple, the directory object does not exist

    (a) create the directory object and copy the files from external table before running impdp

    or

    (b) ignore the error if the external table is not required on the site where you have imported, as a Data Pump dump contains only the metadata of the external tables with no data of the line

  • How to avoid the ORA-01722 in Collection queries?

    I'm in the middle of 11 g migration of 12 c and reproduciple face ORA-01722: virheellinen (invalid number) errors with selects for existing collections.

    Never paid any attention to it, but good to know that this can happen.

    So it's potentially get ORA-01722 invalid number

    select to_number(coll.c007) c007
      from my,apex_collections coll
     where 
          my.id                 =  coll.n002  -- my_id
      and coll.collection_name = 'TUNE_COLL'
      and to_number(coll.c007) = 1  -- first level 
    
    

    While this isn't:

    select to_number(c007) FROM (
    select c007
    from my,apex_collections coll
    where 
          my.id                 =  coll.n002  -- my_id
      and coll.collection_name = 'TUNE_COLL'
    --  and to_number(coll.c007) = 1  -- first level
    ) where  to_number(c007) = 1  -- first level
    

    What is nasty, it's that the responsibe 25 pages of theme with parts of report gets berzerk when error messages between and so on.

    I read the following articles, and it really seems that it comes and goes...

    Robert Schaefer's blog: Spooky "ORA-01722: invalid number" errors when using the collections of the Apex

    http://deneskubicek.blogspot.fi/2013/03/Apex-collections-and-joins.html

    But did not find any quick way to resolve all queries on collections. Somehow, this seems to be because I exceeds the number of columns n001-005 and start using vc c001... columns for numbers.

    So what is the best alternative to doing things?

    1.) divide collections a number c001... so that the numbers will always n001 numbers...   (it is a time consuming task)

    2.) extra make selects select collection... is it enough to convert vc/characters to numbers.

    3.) or in any another cool tip - are there for example views on collections?

    Paavo /rgrds

    Paavo wrote:

    The error comes randomly, and maybe it has something to do with the existing 'temporary' collections already.

    They may have something extraordinary in c007 which cannot be to_numbered with different collection_name.

    It has developed before, and this is indeed the cause. The optimizer apply predicates in a different order than that was used earlier. That is, instead of limiting the lines of the collection by the name of the collection to the collection of TUNE_COLL first, then filtering by the value converted C007, she asks C007 firstly, clause that straightens to lines of collections where C007 value can not be converted to a number. This tends to occur during or after the SUMMIT or base data at level, as in this case.

    The fix is beef - cross selects all collections and difficulty where the conditions so that they appear only at specific collection_name?

    Surely it is necessary on all access collection still? And as explained above, it will not necessarily solve the problem, because the optimizer can change the execution plan and apply predicates in any order.

    Why you have exceeded the n001-n005 number of columns? What values are held in these? Preferably, I would suggest using these columns to store digital keys that are used in joins, values put numerical values only referenced in query projections in the columns of characters c001-c050 (and of course to do the same for date values). Then, you can create a view of the collection which explicitly converts values of the column returned to numbers or dates. Using views on top of collections, it is good practice in any case because it allows explicit column names to use in queries rather than a lot of impenetrable n00x and c0xx, which avoids thinking sitting developers "which column is now the postal code?

  • Impdp ORA-39083 error: INDEX could not create with object type error:

    Hi Experts,

    I get the following error when importing schema HR after a fall it. The DB is r12.1.3 11.2.0.3 & ebs


    I did export with this command.

    patterns of HR/hr = hr = TEST_DIR dumpfile = HR.dmp logfile directory expdp = expdpHR.log statistics = none

    that the user HR with the option drop waterfall.


    And try to import it HR schemas in the database by the following.

    Impdp System/Manager schemas = hr = TEST_DIR dumpfile = HR.dmp logfile directory = expdpHR.log statistics = none

    Here is the error

    imported 'HR '. "" PQH_SS_PRINT_DATA "0 KB 0 rows

    ... imdoor 'HR '. "" PQH_TJR_SHADOW "0 KB 0 rows

    . . imported 'HR '. "" PQH_TXN_JOB_REQUIREMENTS "0 KB 0 rows

    . . imported 'HR '. "" PQH_WORKSHEET_BUDGET_SETS_EFC "0 KB 0 rows

    . . imported 'HR '. "" PQH_WORKSHEET_DETAILS_EFC "0 KB 0 rows

    . . imported 'HR '. "" PQH_WORKSHEET_PERIODS_EFC "0 KB 0 rows

    . . imported 'HR '. "" PQP_ALIEN_TRANSACTION_DATA "0 KB 0 rows

    . . imported 'HR '. "" PQP_ANALYZED_ALIEN_DATA "0 KB 0 rows

    . . imported 'HR '. "" PQP_ANALYZED_ALIEN_DETAILS "0 KB 0 rows

    . . imported 'HR '. "" PQP_EXCEPTION_REPORTS_EFC "0 KB 0 rows

    . . imported 'HR '. "" PQP_EXT_CROSS_PERSON_RECORDS "0 KB 0 rows

    . . imported 'HR '. "" PQP_FLXDU_FUNC_ATTRIBUTES "0 KB 0 rows

    . . imported 'HR '. "" PQP_FLXDU_XML_TAGS "0 KB 0 rows

    . . imported 'HR '. "" PQP_GAP_DURATION_SUMMARY "0 KB 0 rows

    . . imported 'HR '. "" PQP_PENSION_TYPES_F_EFC "0 KB 0 rows

    . . imported 'HR '. "" PQP_SERVICE_HISTORY_PERIODS "0 KB 0 rows

    . . imported 'HR '. "" PQP_VEHICLE_ALLOCATIONS_F_EFC "0 KB 0 rows

    . . imported 'HR '. "" PQP_VEHICLE_DETAILS_EFC "0 KB 0 rows

    . . imported 'HR '. "" PQP_VEHICLE_REPOSITORY_F_EFC "0 KB 0 rows

    . . imported 'HR '. "" PQP_VEH_ALLOC_EXTRA_INFO "0 KB 0 rows

    . . imported 'HR '. "" PQP_VEH_REPOS_EXTRA_INFO "0 KB 0 rows

    Processing object type SCHEMA_EXPORT/TABLE/SCHOLARSHIP/OWNER_GRANT/OBJECT_GRANT

    Processing object type SCHEMA_EXPORT/TABLE/SCHOLARSHIP/CROSS_SCHEMA/OBJECT_GRANT

    Object type SCHEMA_EXPORT/TABLE/COMMENT of treatment

    Object type SCHEMA_EXPORT/PACKAGE/PACKAGE_SPEC of treatment

    Processing object type SCHEMA_EXPORT/PACKAGE/COMPILE_PACKAGE/PACKAGE_SPEC/ALTER_PACKAGE_SPEC

    Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX

    Processing object type SCHEMA_EXPORT/TABLE/INDEX/FUNCTIONAL_INDEX/INDEX

    Object type SCHEMA_EXPORT/TABLE/CONSTRAINT/treatment

    Object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS of treatment

    Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/FUNCTIONAL_INDEX/INDEX_STATISTICS

    Object type SCHEMA_EXPORT/PACKAGE/PACKAGE_BODY of treatment

    Object type SCHEMA_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT of treatment

    Object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS treatment

    Processing object type SCHEMA_EXPORT/TABLE/INDEX/DOMAIN_INDEX/INDEX

    ORA-39083: Type what INDEX failed to create object error:

    ORA-29855: an error has occurred in the execution of routine ODCIINDEXCREATE

    ORA-20000: Oracle text error:

    DRG-50857: error oracle in drvxtab.create_index_tables

    ORA-00959: tablespace "APPS_TS_TX_IDX_NEW" does not exist

    Because sql is:

    CREATE INDEXES ' HR'.»» IRC_POSTING_CON_TL_CTX' ON 'HR '. "" INDEXTYPE IRC_POSTING_CONTENTS_TL "("NAME") IS"CTXSYS. "' CONTEXT ' PARALLEL 1

    Processing object type SCHEMA_EXPORT/POST_SCHEMA/PROCACT_SCHEMA

    Work 'SYSTEM '. "" SYS_IMPORT_SCHEMA_01 "completed with error (s 1) at 11:16:07

    SQL > select count (parameter), object_type from dba_objects where owner = 'HR' group by object_type.

    OBJECT_TYPE COUNT (OBJECT_NAME)

    ------------------ -------------------

    INDEX 37 PARTITION

    SEQUENCE OF 799

    TABLE 12 PARTITION

    LOB 70

    4 BODY PACKAGE

    PACKAGE OF 4

    3 RELAXATION

    2936 INDEX

    TABLE OF 1306

    Could you please suggest.

    Thank you

    MZ

    MZ,

    I get the following error when importing schema HR after a fall it. The DB is r12.1.3 11.2.0.3 & ebs


    Export and import of individual patterns of Oracle E-Business Suite stocked are not supported as this will violate referential integrity (except for custom schemas provided, you have no dependencies).

    Thank you

    Hussein

  • How to avoid the ORA-25188

    Hi all

    I am importing of tables using impdp.
    I truncated the existing tables so don't not to remove existing constraints.
    I want to say-able all constraints so that the children tables will not get a FK constraint error.
    But I came across this ORA 25188:
    SQL> ALTER TABLE OFFCYC_BGEN_K disable constraint XT367P0;
    ALTER TABLE OFFCYC_BGEN_K disable constraint XT367P0
    *
    ERROR at line 1:
    ORA-25188: cannot drop/disable/defer the primary key constraint for 
    index-organized tables or sorted hash cluster 
    Or I just ignore it because it will not affect the loading? for the FK errors.

    Help, please...

    Thank you very much

    Primary key is necessary for the ITO so to do, the answer would be that it will not be removable IMO.

    Aman...

  • spend AMM SAMS to avoid the ORA-04031?

    Database is 11 GR 2 on 64-bit Server 2008, currently allocated 400 MB for target PGA and 500 MB for the total size of SGA with SAMS on and off of MSA.

    Last a few days I get of "ORA-04031: unable to allocate 3896 bytes of shared memory" when a job trying to insert into a table. The error is intermittent and it happens a few times a day. This database has been used for months with these settings without error memory and nothing has changed.

    I usually run with active AMM, but for some reason when the database was installed it was set active SAMS and disabled AMM. Right now the shared pool takes up to 92% of the current envelope of the SGA. PGA target 402 MB with 190 MB currently allocated.

    I'd be better of allowing the AMM and give just the database of 900MB to use? If I do this should I set the same maximum memory size to the size of total memory (or slightly more than) for AMM? If I change the MMS then I need the DB, that is doable, but earlier I would not if I can avoid bouncing.


    Thank you
    500 MB for the total SGA

    It is not much in terms of a fingerprint memory decent 11 g, try to clear the pga_target and memory_target value = 1000 M or an appropriate value according to the amount of physical memory on the host, let the engine decide how to distribute the shared pool, PGA, etc. just based on the value of the memory_target.

    If the box has just 2G physical memory, a memory target 1 G will be tight.

  • Import/Export, impdp ORA-39083 on creation of the important role

    Version of DB 10204 on Windows 2003

    I clean a couple of databases by moving DB_OLD to DB_NEW database schemas and while doing so, I want to clean the unnecessary privileges and roles granted to the users/schema.

    I exported the schema of DB_OLD using expdp username@dbname parfile = D:\exp.par, inside her parfile I have:
    JOBNAME = EXP01JOB
    DIRECTORY = DUMP_DIR
    DUMPFILE=EXP01DUMP%U.DMP
    SCHEMAS = SCHEMA1, SCHEMA2, SCHEMA3
    PARALLEL = 4

    Everthing works well, the export is successful.

    When you import into DB_NEW, I use the impdp. I import using a file by as well and it works too, all objects belonging to the imported schemas, as well as all privileges for users and schemas.

    Issues related to the:

    (a) I tried to use EXCLUDE = of the export SUBSIDIES parfile, but it did not work. I want to export all the objects, but I want to clean what gets granted (sys privs and privs and role object) to the owner of the schema DB_NEW. So before exporting it, I tried to create the username and privileges in DB_NEW and then performs the import schema, but after importation that especially original DB_OLD privileges have been granted to the user in DB_NEW.
    Any other way around this? Here's what I ran into DB_OLD to see what had privileges SCHEMA1.

    SELECT DBMS_METADATA. GET_GRANTED_DDL('ROLE_GRANT','SCHEMA1') FROM DUAL;
    SELECT DBMS_METADATA. GET_GRANTED_DDL('SYSTEM_GRANT','SCHEMA1') FROM DUAL;
    SELECT DBMS_METADATA. GET_GRANTED_DDL('OBJECT_GRANT','SCHEMA1') FROM DUAL;

    Say that there is no workaround for the issue a solution) that is just the way would be to export schema and I revoke and to grant privileges.

    (b) I can not understand how to know what roles objects belong to? In the import.log, I see that I see this error:

    Processing object type SCHEMA_EXPORT/TABLE/SCHOLARSHIP/OWNER_GRANT/OBJECT_GRANT
    ORA-39083: Type than object_grant cannot create with eror of object:
    ORA-01917: user or role 'SCHEMA1_READONLY' does not exist
    Because SQL is:
    GRANT SELECT ON "SCHEMA1". "' TABLE_NAME ' TO 'SCHEMA1_READONLY '.

    I see that it is due to a role missing in DB_NEW, if I first create the role that I'm guessing that the error would not be there. However, I can't find a view of $ v that has this role. This role is created to allow certain users READ_ONLY access SCHEMA1 tables. What view should I be query to get the data? I looked at all the views that are listed under the dba_views which are like '% ROLE %' and I couldn't find the role "SCHEMA1_READONLY" listed in any of them.


    Thanks and let me know any suggestions.

    Hello

    Did you views dba_tab_privs and dba_roles that would help you to know what are the tables has the roles.

    Concerning
    Anurag Tibrewal.

  • Clear cache page after deletion to avoid errors ora-1403 Apex 5.01

    Hi all

    Always 'new' at Apex!

    I'm getting ORA-01403: no data available error after deleting a line in a 5.01 Apex form created from the interactive report + model form.

    After searching the forum, I found a direct reference to this situation:

    ORA-01403: no data available on the deletion of a record

    --------------------------------------------------------------------------------

    After deleting a record, you must clear the page cache. If you do not have the primary key item session state can keep the old value of the deleted record. The page loading process will try to retrieve this value from the table and meet no data found.

    ---------------------------------------------------------------------------------

    Unfortunately, I do not know where or how to " " " clear the cache of the page ' after deleting a record.

    I saw the reverence to APEX_UTIL. CLEAR_PAGE_CACHE but I don't know where to use

    Others say still set the value of the key null column.

    The documentation of the Apex is said to use the URL:

    2.9.3.2.2 example: clear cache on a Page and passing an element value

    This example shows how to implement a form of update. It erases the existing information and sets the value of the element (usually a primary key).

    f?p=6000:6003:&APP_SESSION.::NO:6003:MY_ITEM:1234 

    This example:

    • Runs the application 6003 6000 page and uses the ID of the current session

    • Specifies to not show debug information ( NO )

    • Clears all values maintained by the current session for the items on page 6003 cache

    • Sets the State of an element called session MY_ITEM value1234

    But I do not know where or how to do that in the context of the key Suppr.

    Can someone point me in the right direction? I'm learning the Apex using as many integrates native as possible features.

    If clearing the cache of the page, that's what needs to be done after the removal of a line, would not these features have been integrated to the Delete key?

    Thank you

    Mason

    OK, after wandering in the desert for a while, I tried this approach to clear the cache once you press the button Delete and it doesn't seem to work.

    I created a new process called "Clear the cache" after the process of "line process of...» »

    The process to clear the cache was of type PL/SQL Code with the section of Code PL/SQL, the value 'APEX_UTIL. CLEAR_PAGE_CACHE (2); »

    I don't know if it's a good way to do this, or if the accepted practices, or what side effects will rain down on me that they are, but at least I got a result that has solved my immediate problem.

    So nice to click on delete and not greeted with an ORA-01403 error!

    Thanks to everyone who helped me in on it!

    Mason

  • How to set permissions for drives avoid the ORA-15063 start-up ASM?

    Hello

    When I try to reboot the DSO after a reboot of the server, I get

    ERROR: diskgroup DATA was not mounted

    ORA-15032: not all changes made

    ORA-15017: diskgroup 'DATA' cannot be mounted

    ORA-15063: ASM discovered an insufficient number of drives for diskgroup "DATA".

    It seems the permission of disks have changed after the reboot. I guess the spfile is inside the DATA diskgroup because it can not even start ASM. When I create a file with values asm_diskgroup and asm_diskstring pfile and 777 on the drive, I managed to start the ASM.

    * .asm_diskgroups = "INDX", "DATA".

    * .asm_diskstring = "/ dev / *'"

    $ oracleasm querydisk p - DATA

    Disk 'DATA' is a valid ASM disk

    / dev/sdb4: LABEL = 'DATA' TYPE = 'oracleasm.

    $ ls-la/dev/sdb *.

    ...

    BRW - rw - 1 root disk 8, 19, 29 mai 10:42 / dev/sdb3 it

    brwxrwxrwx 1 root disk 8, 20, 29 mai 15:17 / dev/sdb4

    ...

    And when I read the documentation I see this ' that the owner of the ORACLE binary file has permissions to read/write on the discs"(so do not run required) but the problem is that this test server should have the same parameters as in production. And the production server has brw - r - for the corresponding disk. So my questions are

    Can it be handled somehow in a different way? How can this have been reached production without the same settings I put in test? Is there an other way around for me in test to achieve?

    The network user (who owns the infrastructue grid) belongs to the same group of test and production. Test and production have ASM version 11.2.0.3, but the different operating system.

    production: 2.6.18 - 274.12.1.el5

    test: 2.6.32 - 504.16.2.el6.x86_64

    As this is my first ASM/grid infrastructure, I don't even know where to begin this review except the support.oracle.com search but I've not found anything except the Action for the error code (which is perhaps the only way around it)

    Any help is appreciated

    Thank you

    / Jenny

    Remember that the permissions of the device must be configured so that the owner of the Oracle database or the process has full access to the appropriate device files. It is not enough to only give ASM full authorization for devices files. ASM provides management for volume, but the database has direct access to device files and ASM does not interfere with inputs and outputs. You can set up groups and owner accordingly. If you have a different owner for ASM, you must assign appropriate groups to give full access ASM configuring oracleasm.

  • Partial IMPDP Ora 11g Windows

    I ran an IMPDP from a full export file. I don't have two tablespaces than necessary import configuration.
    Question:
    If I place the tbsp missing can I just restart the complete installation without damaging the paintings already loaded from my first run?
    If not can I can a partial impdp and import only two storage spaces I'm missing?
    I've read through and I don't know clearly enough on Oracle to know what will happen if I try to restart.

    Thanks for any input.
    Carter

    Thanks - pl to re-run the import and it will skip the existing tables and create the lack

    HTH
    Srini

  • migration by expdp/impdp db to AIX and Linux. Impdp errors, help.

    Hi, I did complete expdp (11 GR 1 material) and complete impdp (11 GR 2) migrate db from aix to linux.

    I have the following questions in mind:
    (1) I checked the imp papers and found a lot of mistakes. I think that most can be ignored, but I just want to be double sure before that I release the new db migrated for use. Is there a better way to avoid these mistakes?


    ORA-31684: SEQUENCE object type: 'SYSTEM '. "" MVIEW$ _ADVSEQ_GENERIC ' already exists
    ORA-31684: SEQUENCE object type: 'SYSTEM '. "" MVIEW$ _ADVSEQ_ID ' already exists
    ORA-31684: SEQUENCE object type: 'SYSTEM '. "" REPCAT$ _EXCEPTIONS_S ' already exists
    ORA-31684: SEQUENCE object type: 'SYSTEM '. "" REPCAT$ _FLAVORS_S ' already exists
    ORA-31684: SEQUENCE object type: 'SYSTEM '. "" REPCAT$ _FLAVOR_NAME_S ' already exists
    ORA-31684: SEQUENCE object type: 'SYSTEM '. "" REPCAT$ _REFRESH_TEMPLATES_S ' already exists
    ......
    Table 'SYSTEM '. "" REPCAT$ _AUDIT_COLUMN "exists. Data will be added to the existing
    table but all dependent metadata will be ignored because the table_exists_action a
    ppend
    Table 'SYSTEM '. "" REPCAT$ _FLAVOR_OBJECTS "exists. Data will be added to the existin
    Table g but all dependent metadata will be ignored due to table_exists_action of
    Add
    Table 'SYSTEM '. "" REPCAT$ _TEMPLATE_STATUS "exists. Data will be added to existi
    ng table but all dependent metadata will be ignored due to table_exists_action o
    f add
    .......
    Treatment of type of object DATABASE_EXPORT/SCHEMA/VIEW/SCHOLARSHIP/OWNER_GRANT/OBJECT_GRAN
    T
    ORA-39111: Object Type dependent OBJECT_GRANT: 'SYSTEM' ignored, base object type
    VIEW: 'SYSTEM '. "' MVIEW_WORKLOAD ' already exists
    ORA-39111: Object Type dependent OBJECT_GRANT: 'SYSTEM' ignored, base object type
    VIEW: 'SYSTEM '. "' MVIEW_FILTER ' already exists
    ORA-39111: Object Type dependent OBJECT_GRANT: 'SYSTEM' ignored, base object type
    VIEW: 'SYSTEM '. "' MVIEW_LOG ' already exists
    ORA-39111: Object Type dependent OBJECT_GRANT: 'SYSTEM' ignored, base object type
    VIEW: 'SYSTEM '. "' MVIEW_FILTERINSTANCE ' already exists
    ORA-39111: Object Type dependent OBJECT_GRANT: 'SYSTEM' ignored, base object type
    VIEW: 'SYSTEM '. "' MVIEW_RECOMMENDATIONS ' already exists
    ORA-39111: Object Type dependent OBJECT_GRANT: 'SYSTEM' ignored, base object type
    VIEW: 'SYSTEM '. "' MVIEW_EVALUATIONS ' already exists
    ...............

    . . imported 'SYSTEM '. "" REPCAT$ _TEMPLATE_REFGROUPS ' 5,015 KB 0 rows
    . . imported 'SYSTEM '. "" REPCAT$ _TEMPLATE_SITES ' 5,359 KB 0 rows
    ORA-31693: Data Table object 'SYSTEM '. "" REPCAT$ _TEMPLATE_STATUS ' failed to load/u
    nLoad and being ignored because of the error:
    ORA-00001: unique constraint (SYSTEM. REPCAT$ _TEMPLATE_STATUS_PK) violated
    . . imported 'SYSTEM '. "" REPCAT$ _TEMPLATE_TARGETS ' 4,937 KB 0 rows
    ORA-31693: Data Table object 'SYSTEM '. "" REPCAT$ _TEMPLATE_TYPES ' failed to load/United Nations
    load and being ignored because of the error:
    ORA-00001: unique constraint (SYSTEM. REPCAT$ _TEMPLATE_TYPES_PK) violated
    . . imported 'SYSTEM '. "" REPCAT$ _USER_AUTHORIZATIONS ' 4,773 KB 0 rows
    . . imported 'SYSTEM '. "' SQLPLUS_PRODUCT_PROFILE ' 5,140 KB 0 rows
    . . imported 'SYSTEM '. "' TOAD_PLAN_SQL ' 4,859 KB 0 rows


    (2) in addition, I've seen a few new users 11 GR 2 is not in 11R1, I should not worry update these users, right?

    Thank you in advance.

    You receive the ORA-31684: SEQUENCE object type: 'SYSTEM '. "" MVIEW$ _ADVSEQ_GENERIC "already exists, because the SYSTEM object already exists. You can ignore this error.

    You can also view links below

    Cross platform Transportable Tablespace with RMAN
    http://www.oracleracexpert.com/2009/08/transportable-tablespace-export-import.html

    Import/export transportable tablespace on the same endian platforms
    http://www.oracleracexpert.com/2009/10/cross-platform-transportable-tablespace.html

    Hope this helps,

    Concerning
    http://www.oracleracexpert.com
    Block of Corruption and recovery
    http://www.oracleracexpert.com/2009/08/block-corruption-and-recovery.html]
    Redo log corruption and recovery
    http://www.oracleracexpert.com/2009/08/redo-log-corruption-and-recovery.html]

  • User header imported successfully, Impdp import the same user has: b getting object exists error

    Hello

    My scenario

    In our database of prod, we have user A that I recently imported A user in the Test database

    Now I need to import user A user B in the same Test database but get error object exists

    ORA-39151: Table "A.Table_Name" exists

    ORA-31684: Procedure 'A.Proc_Name' exists

    My impdp syntax is the following:

    Impdp USERID =------"/ ACE sysdba\ ' DIRECTORY = DATA_PUMP_DIR DUMPFILE = A.dmp EXCLUDE = USER LOGFILE = A_TO_B_imp.log

    REMAP_SCHEMA = A: B

    REMAP_TABLESPACE = USERS: B

    I thought that this was caused by the fact that the two user B in the database Test with same Tablespace by default, so I created a different tablespace for user B and provided remap tablespace parameter but still getting the same error.

    Please notify.

    Hello

    Seems for some reason any your part of remap_schema is not recognized.

    In the beginning of the impdp log, you should see the command it uses,

    Can you confirm the exact order impdp journal tries to run.

    Also run the impdp since the user of the system.

  • Replace all "already exists them" object when you perform an import complete (impdp)

    Hello

    I'm doing a full import from a database to a different database.

    "I already exported (expdp) all subject to a database with no problems, but when I tried to import (impdp) to a different database, an error appeared, as ' ORA-31684:... by object type already exists.

    My question is how to replace already not exist (old to new) objects, so that it shows no error?

    If I use TABLE_EXISTS_ACTION = REPLACE, is not it has replaced only tables and no other objects? I tried already and there was always a mistake.

    Advice will be appreciated. Thanks in advance.

    Kind regards

    Jerry Antonius

    If I use TABLE_EXISTS_ACTION = REPLACE, is not it has replaced only tables and no other objects?

    Yes, it won't replace tables, there is no function to replace all items

    You may need to delete all the objects before import or get the DDL of user, drop user cascade and re-create the user and import again.

  • ORA-00959: NSN_2 tablespace does not exist... But the tablespace is defined in the user temp script

    WHEN I SPEAR IMPDP I GET AN ERROR ABOUT "THE TABLESPACE DOES NOT EXIST.

    THIS space of STORAGE IS in FACT is MORE PRESENT on THE SYSTEM, BUT IT IS DEFINED IN the User1 SCRIPT

    IS there ANYWAY THAT I CAN ASK HIM don't GET THIS TEMP TABLESPACE

    or

    is there anyway I can remove the definition of the user (User1) NSN_2

    OR

    should I just re-create the NSN_2 tablescape

    HELP NEEDED PLS...

    DROP USER CASCADE USER1;

    CREATE THE USER1 USER

    IDENTIFIED BY < password >

    NSN_1 DEFAULT TABLESPACE

    TEMPORARY TEMP TABLESPACE

    -2 Tablespace quotas for User1

    ALTER USER USER1 QUOTA UNLIMITED ON NSN_1;

    ALTER USER USER1 QUOTA UNLIMITED ON NSN_2;                -point in contention

    Directory of Impdp User1/password = dump_dir dumpfile = logfile = LOG.log remap_schema user2.dmp = USER2:USER1 remap_tablespace = NSN_4:NSN_1

    Table main "USER1". "' SYS_IMPORT_FULL_01 ' properly load/unloaded

    Departure "USER1". "' SYS_IMPORT_FULL_01 ': User1 / * directory = dump_dir = setup_02102012.dmp = logfile dumpfile tries .log remap_schema = remap_tablespace of installation: USER1 = NSN_4:NSN_1

    Processing object type SCHEMA_EXPORT/USER

    ORA-31684: USER object Type: 'USER1' already exists

    Processing object type SCHEMA_EXPORT/SYSTEM_GRANT

    Processing object type SCHEMA_EXPORT/ROLE_GRANT

    Processing object type SCHEMA_EXPORT/DEFAULT_ROLE

    Processing object type SCHEMA_EXPORT/TABLESPACE_QUOTA

    ORA-39083: Type as tablespace_quota cannot be created with the object error:

    ORA-00959: tablespace "NSN_2" does not exist

    Because sql is:

    REPORT THE NUMBER OF TEMP_COUNT;   SQLSTR VARCHAR2 (200); BÉGIN SQLSTR: = ' ALTER USER 'USER1' QUOTA UNLIMITED ON 'NSN_2 ';  RUN IMMEDIATELY SQLSTR; EXCEPTION, THEN THAN OTHERS SO IF SQLCODE =-30041 THEN SQLSTR: = ' SELECT COUNT (*) OF USER_TABLESPACES WHERE NOM_TABLESPACE = "NSN_2" AND CONTENT = "TEMPORARY"';      RUN IMMEDIATELY SQLSTR IN TEMP_CO

    Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA

    Object type SCHEMA_EXPORT/SEQUENCE/SEQUENCE of treatment

    Object type SCHEMA_EXPORT/TABLE/TABLE processing

    ORA-39083: TABLE object type: "USER1". "" AVAIL_BY_OPTION_REF "impossible to create with the error:

    ORA-00959: tablespace "NSN_2" does not exist

    Impdp transform = segment_attributes

    Smit

Maybe you are looking for