Full database import hangs

System:
Windows 2000 SP4
Oracle 8.1.7
Hi,
I am importing a full backup ( export dump file ). It was taken from the
database having the same structure as the database to which I am importing.
It is taking too long in importing data in a particular table and seems to hang
for hours. It says 40542226 rows imported. It seems to hang from here.
I checked the v$session to identify the session serving the import and
v$session_wait to verify the wait events for that session. But I don't see
any wait events for this session. What I see is the session itself.
I did the import using:
imp username/password@sid file'D:\data\fullbkp.dmp' log=D:\log\fullbkpimp.log' full=y
My question is: what are other diagnosis I should perform to help find out the cause and
possibly the solution of this import hang?

Hi,
In addition, when I want to see what's is going on, I usually execute the SQL below in order to monitory the import operation activity...
select substr(sql_text,instr(sql_text,'INTO "'),30) table_name,
rows_processed,
round((sysdate-to_date(first_load_time,'yyyy-mm-dd hh24:mi:ss'))*24*60,1) minutes,
trunc(rows_processed/((sysdate-to_date(first_load_time,'yyyy-mm-dd hh24:mi:ss'))*24*60)) rows_per_min
from sys.v_$sqlarea
where sql_text like 'INSERT %INTO "%' and
command_type = 2 and open_versions > 0; Cheers
Legatti

Similar Messages

  • Full database import(impdp) error

    HI ppl,
    Plz help..
    My full database import is failing due to
    ORA-39126: Worker unexpected fatal error in KUPW$WORKER.LOAD_METADATA [TABLE_DATA:"SYS"."SYS_IMPORT_FULL_04"]
    SELECT process_order, flags, xml_clob, NVL(dump_fileid, :1), NVL(dump_position, :2), dump_length, dump_allocation, grantor, object_row, object_schema, object_long_name, processing_status, processing_state, base_object_type, base_object_schema, base_object_name, property, size_estimate, in_progress FROM "SYS"."SYS_IMPORT_FULL_04" WHERE process_order between :3 AND :4 AND processing_state <> :5 AND duplicate = 0 ORDER BY process_order
    ORA-25153: Temporary Tablespace is Empty
    ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
    ORA-06512: at "SYS.KUPW$WORKER", line 6272
    ----- PL/SQL Call Stack -----
    object line object
    handle number name
    c000000267348288 14916 package body SYS.KUPW$WORKER
    c000000267348288 6293 package body SYS.KUPW$WORKER
    c000000267348288 3511 package body SYS.KUPW$WORKER
    c000000267348288 6882 package body SYS.KUPW$WORKER
    c000000267348288 1259 package body SYS.KUPW$WORKER
    c00000026fb2de68 2 anonymous block
    Job "SYS"."SYS_IMPORT_FULL_04" stopped due to fatal error at 14:56:10
    regards

    Hi..
    ya temporary tablespace is present,and also contains 2gb freespace,with 2 datafiles.Are you sure its a datafile.It must be a tempfile. :)
    Secondly, have you checked the default temporary tablespace of the database.Is it the one that you have mentioned.
    SELECT PROPERTY_NAME,PROPERTY_VALUE FROM DATABASE_PROPERTIES where PROPERTY_NAME='DEFAULT_TEMP_TABLESPACE';
    Anand

  • [Q] ORA-30510 error while doing full database import

    We have ORACLE 9.2.0.6 on Redhat LINUX AS 3.4. while we doing "full database import" there has ORA-30510 come out. I searched Metalink and Google, but not found much information. The error messages on import are:
    . importing OUTLN's objects into OUTLN
    . importing SYSTEM's objects into SYSTEM
    . importing TKOWNER's objects into TKOWNER
    IMP-00017: following statement failed with ORACLE error 30510:
    "CREATE TRIGGER "TKOWNER".TRIG_DONOTANALYZE before analyze on schema decla"
    "re begin if sys.dictionary_obj_name = 'MYWTKEMPLOYEE' then raise_ap"
    "plication_error(-20101, 'Do Not ANALYZE MYWTKEMPLOYEE'); end if; end; "
    IMP-00003: ORACLE error 30510 encountered
    ORA-30510: system triggers cannot be defined on the schema of SYS user
    . importing SYS's objects into SYS
    . importing TKOWNER's objects into TKOWNER
    About to enable constraints...
    Import terminated successfully with warnings.

    877410 wrote:
    Hi I get the following ierrors while importing a schema from prod to dev database... can anyone help ,thanks!
    impdp system DIRECTORY=DATA_PUMP_DIR DUMPFILE=abcdprod.DMP LOGFILE=abcdprod.log REMAP_SCHEMA=abcdprod:abcddev
    ORA-39002: invalid operation
    ORA-31694: master table "SYSTEM"."SYS_IMPORT_FULL_01" failed to load/unload
    ORA-31644: unable to position to block number 170452 in dump file "/ots/oracle/echo/wxyz/datapump/abcdprod.DMPpost complete command line for the expdp that made the abcdprod.DMP file

  • Import all users and their objects without doing full database import

    Hi Guys,
    I have a task to that involves Importing all existing users and their objects in production to the test database without doing a full database import - Please how do i do this?
    Pls i need your help urgently.

    SQL> select * from v$version;
    BANNER
    Oracle Database 10g Express Edition Release 10.2.0.1.0 - Product
    PL/SQL Release 10.2.0.1.0 - Production
    CORE 10.2.0.1.0 Production
    TNS for Linux: Version 10.2.0.1.0 - Production
    NLSRTL Version 10.2.0.1.0 - Production
    I tried to import objects and data from a user from a FULL dump file. File was created with the following command:
    server is: SQL*Plus: Release 10.2.0.1.0 - Production on Wed May 26 15:34:05 2010
    exp full=y FILE="full.dmp" log=full.log
    Now I imported:
    imp file=full.dmp log=full.log INCTYPE=SYSTEM
    imp fromuser=user1 file=full.dmp
    Results: not all the user procedures have been imported:
    SQL> select count(*) from user_procedures;
    the Original
    COUNT(*)
    134
    the current:
    select count(*) from user_procedures;
    COUNT(*)
    18
    I also tried these alternatives:
    exp tablespaces="user1_data" FILE="user1.dmp" log=user1.log
    exp LOG=user1.log TABLESPACES=user1_data FILE=user1_data.dmp
    exp LOG=user1owner.log owner=user1 FILE=user1owner.dmp
    expdp DIRECTORY=dpump_dir1 dumpfile=servdata_pump version=compatible SCHEMAS=user1
    impdp directory=data_pump_dir dumpfile=servdata_pump.dmp :
    ORA-39213: Metadata processing is not available
    SQL> execute dbms_metadata_util.load_stylesheets
    BEGIN dbms_metadata_util.load_stylesheets; END;
    ERROR at line 1:
    ORA-31609: error loading file "kualter.xsl" from file system directory
    "/usr/lib/oracle/xe/app/oracle/product/10.2.0/server/rdbms/xml/xsl"
    ORA-06512: at "SYS.DBMS_METADATA_UTIL", line 1793
    ORA-06512: at line 1
    file kualter.xsl does not exist in XE !!
    imp owner=user1 rows=n ignore=y
    imp full=y file=user1_data.dmp
    imp full=y file=full.dmp tablespaces=user1_data,user1_index rows=n ignore=y
    So, I do not understand why user1 objects are not imported:
    see this part of the first import log:
    Export file created by EXPORT:V10.02.01 via conventional path
    import done in US7ASCII character set and AL16UTF16 NCHAR character set
    import server uses WE8ISO8859P1 character set (possible charset conversion)
    . importing SYS's objects into SYS
    . importing USER1's objects into USER1
    . . importing table .........................
    why only 18 rows?
    if you have an suggestion, you are welcome, as I do not have any other idea...
    ren
    Edited by: ronpetitpatapon on May 26, 2010 12:38 PM
    Edited by: ronpetitpatapon on May 26, 2010 12:41 PM
    Edited by: ronpetitpatapon on May 26, 2010 1:03 PM

  • Full database import issue

    Hi everybody,
    our database version is 9.2.0.6 running in solaris, our one of the database got fragmented. In order to avoid fragmentation i export the full database and try to import the dumpfile to the same database(which i exported).If i do so means, the recored in the table will get duplicate. can someone help me out in this issue.Yhanks in advance
    Regards
    Hamid

    Why do you import back on the same database (Where you feel the database is fragmented)?, Insted, prepare the new database with all the recommendation of the fragmented database i.e. Database Name, Character Set, Tablespaces (if the datafile locations are different), etc. Then, import your dump into the newly created database.
    By the way, is this your production database?
    Regards,
    Sabdar Syed.

  • Full database import

    Hi,
    I am trying to import a full database using the impdp method.
    impdp system/oracle dumpfile=datap:fulldb.dmp full=y logfile=datap:full.log
    I am getting fatal error message while importing.
    ===========================
    ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
    ORA-06512: at "SYS.KUPW$WORKER", line 6273
    ----- PL/SQL Call Stack -----
    object line object
    handle number name
    5e6414d4 14916 package body SYS.KUPW$WORKER
    5e6414d4 6300 package body SYS.KUPW$WORKER
    5e6414d4 12689 package body SYS.KUPW$WORKER
    5e6414d4 11968 package body SYS.KUPW$WORKER
    5e6414d4 3279 package body SYS.KUPW$WORKER
    5e6414d4 6889 package body SYS.KUPW$WORKER
    5e6414d4 1262 package body SYS.KUPW$WORKER
    6408cfd0 2 anonymous block
    Job "SYSTEM"."SYS_IMPORT_FULL_03" stopped due to fatal error at 13:19:32:
    ==================================
    My question is 'should we have to create all the tablespaces(other than system tablespaces) that was available in the primary database manually in the target machine before executing the import command?
    What are the prerequisites for importing a full export into a database? How do we make the target database ready to accept the import?
    my oracle version is 10.2.0 on solaris 10
    Thanks in advance....
    Edited by: user13364377 on 24-Jul-2010 14:33

    Hi,
    My db version is 10.2.0.0 and OS is solaris 10..
    I am pasitng the contents of the alert log file.
    ==================================
    kupprdp: master process DM00 started with pid=19, OS id=1328
    to execute - SYS.KUPM$MCP.MAIN('SYS_IMPORT_FULL_01', 'SYSTEM', 'KUPC$C_1_20100724100422', 'KUPC$S_1_20100724100422', 0);
    kupprdp: worker process DW01 started with worker id=1, pid=20, OS id=1330
    to execute - SYS.KUPW$WORKER.MAIN('SYS_IMPORT_FULL_01', 'SYSTEM');
    Sat Jul 24 10:04:28 2010
    CREATE UNDO TABLESPACE "UNDOTBS1" DATAFILE '/oracle/product/dbn/undotbs01.dbf' SIZE 26214400 AUTOEXTEND ON NEXT 5242880 MAXSIZE 32767M BLOCKSIZE 8192 EXTENT MANAGEMENT LOCAL AUTOALLOCATE
    ORA-1543 signalled during: CREATE UNDO TABLESPACE "UNDOTBS1" DATAFILE '/oracle/product/dbn/undotbs01.dbf' SIZE 26214400 AUTOEXTEND ON NEXT 5242880 MAXSIZE 32767M BLOCKSIZE 8192 EXTENT MANAGEMENT LOCAL AUTOALLOCATE...
    Sat Jul 24 10:04:28 2010
    CREATE TABLESPACE "SYSAUX" DATAFILE '/oracle/product/dbn/sysaux01.dbf' SIZE 125829120 AUTOEXTEND ON NEXT 10485760 MAXSIZE 32767M LOGGING ONLINE PERMANENT BLOCKSIZE 8192 EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO
    ORA-1543 signalled during: CREATE TABLESPACE "SYSAUX" DATAFILE '/oracle/product/dbn/sysaux01.dbf' SIZE 125829120 AUTOEXTEND ON NEXT 10485760 MAXSIZE 32767M LOGGING ONLINE PERMANENT BLOCKSIZE 8192 EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO...
    Sat Jul 24 10:04:28 2010
    CREATE TEMPORARY TABLESPACE "TEMP" TEMPFILE '/oracle/product/dbn/temp01.dbf' SIZE 31457280 AUTOEXTEND ON NEXT 655360 MAXSIZE 32767M EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1048576
    ORA-1543 signalled during: CREATE TEMPORARY TABLESPACE "TEMP" TEMPFILE '/oracle/product/dbn/temp01.dbf' SIZE 31457280 AUTOEXTEND ON NEXT 655360 MAXSIZE 32767M EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1048576
    Sat Jul 24 10:04:28 2010
    CREATE TABLESPACE "USERTB" DATAFILE '/oracle/product/dbn/users01.dbf' SIZE 5242880 AUTOEXTEND ON NEXT 1310720 MAXSIZE 32767M LOGGING ONLINE PERMANENT BLOCKSIZE 8192 EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO
    ORA-1119 signalled during: CREATE TABLESPACE "USERTB" DATAFILE '/oracle/product/dbn/users01.dbf' SIZE 5242880 AUTOEXTEND ON NEXT 1310720 MAXSIZE 32767M LOGGING ONLINE PERMANENT BLOCKSIZE 8192 EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO...
    Sat Jul 24 10:04:28 2010
    CREATE TABLESPACE "EXAMPLE" DATAFILE '/oracle/product/dbn/example01.dbf' SIZE 104857600 AUTOEXTEND ON NEXT 655360 MAXSIZE 32767M NOLOGGING ONLINE PERMANENT BLOCKSIZE 8192 EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO
    ORA-1119 signalled during: CREATE TABLESPACE "EXAMPLE" DATAFILE '/oracle/product/dbn/example01.dbf' SIZE 104857600 AUTOEXTEND ON NEXT 655360 MAXSIZE 32767M NOLOGGING ONLINE PERMANENT BLOCKSIZE 8192 EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO
    Sat Jul 24 10:04:28 2010
    CREATE TABLESPACE "NEWTABLESPACE" DATAFILE '/oracle/product/newtablespace.dbf' SIZE 10485760 LOGGING ONLINE PERMANENT BLOCKSIZE 8192 EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1048576 SEGMENT SPACE MANAGEMENT AUTO
    ORA-1119 signalled during: CREATE TABLESPACE "NEWTABLESPACE" DATAFILE '/oracle/product/newtablespace.dbf' SIZE 10485760 LOGGING ONLINE PERMANENT BLOCKSIZE 8192 EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1048576 SEGMENT SPACE MANAGEMENT AUTO
    Sat Jul 24 10:04:28 2010
    CREATE TABLESPACE "T16KTAB" DATAFILE '/oracle/16k.dbf' SIZE 3145728 LOGGING ONLINE PERMANENT BLOCKSIZE 16384 EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO
    ORA-29339 signalled during: CREATE TABLESPACE "T16KTAB" DATAFILE '/oracle/16k.dbf' SIZE 3145728 LOGGING ONLINE PERMANENT BLOCKSIZE 16384 EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO
    Sat Jul 24 10:04:28 2010
    CREATE TABLESPACE "INDX_TS" DATAFILE '/oracle/indxts.dbf' SIZE 26214400,'/oracle/secondf.dbf' SIZE 26214400 LOGGING ONLINE PERMANENT BLOCKSIZE 8192 EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO
    ORA-1119 signalled during: CREATE TABLESPACE "INDX_TS" DATAFILE '/oracle/indxts.dbf' SIZE 26214400,'/oracle/secondf.dbf' SIZE 26214400 LOGGING ONLINE PERMANENT BLOCKSIZE 8192 EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO
    Sat Jul 24 10:04:43 2010
    Replication pre-import: trying to disable constraint REPCAT$_TEMPLATE_OBJECTS_FK1 for "SYSTEM"."REPCAT$_TEMPLATE_OBJECTS"
    Replication pre-import: constraint REPCAT$_TEMPLATE_OBJECTS_FK1 for "SYSTEM"."REPCAT$_TEMPLATE_OBJECTS" is disabled successfully
    Replication pre-import: trying to disable constraint REPCAT$_TEMPLATE_PARMS_FK1 for "SYSTEM"."REPCAT$_TEMPLATE_PARMS"
    Replication pre-import: constraint REPCAT$_TEMPLATE_PARMS_FK1 for "SYSTEM"."REPCAT$_TEMPLATE_PARMS" is disabled successfully
    Replication pre-import: trying to disable constraint REPCAT$_OBJECT_PARMS_FK1 for "SYSTEM"."REPCAT$_OBJECT_PARMS"
    Replication pre-import: constraint REPCAT$_OBJECT_PARMS_FK1 for "SYSTEM"."REPCAT$_OBJECT_PARMS" is disabled successfully
    Replication pre-import: trying to disable constraint REPCAT$_OBJECT_PARMS_FK2 for "SYSTEM"."REPCAT$_OBJECT_PARMS"
    Replication pre-import: constraint REPCAT$_OBJECT_PARMS_FK2 for "SYSTEM"."REPCAT$_OBJECT_PARMS" is disabled successfully
    Replication pre-import: trying to disable constraint REPCAT$_USER_AUTHORIZATION_FK2 for "SYSTEM"."REPCAT$_USER_AUTHORIZATIONS"
    Replication pre-import: constraint REPCAT$_USER_AUTHORIZATION_FK2 for "SYSTEM"."REPCAT$_USER_AUTHORIZATIONS" is disabled successfully
    Replication pre-import: trying to disable constraint REPCAT$_USER_PARM_VALUES_FK1 for "SYSTEM"."REPCAT$_USER_PARM_VALUES"
    Replication pre-import: constraint REPCAT$_USER_PARM_VALUES_FK1 for "SYSTEM"."REPCAT$_USER_PARM_VALUES" is disabled successfully
    Replication pre-import: trying to disable constraint REPCAT$_FLAVOR_OBJECTS_FK2 for "SYSTEM"."REPCAT$_FLAVOR_OBJECTS"
    Replication pre-import: constraint REPCAT$_FLAVOR_OBJECTS_FK2 for "SYSTEM"."REPCAT$_FLAVOR_OBJECTS" is disabled successfully
    Replication pre-import: trying to disable constraint REPCAT$_FLAVOR_OBJECTS_FK1 for "SYSTEM"."REPCAT$_FLAVOR_OBJECTS"
    Replication pre-import: constraint REPCAT$_FLAVOR_OBJECTS_FK1 for "SYSTEM"."REPCAT$_FLAVOR_OBJECTS" is disabled successfully
    Replication pre-import: trying to disable constraint REPCAT$_FLAVORS_FK1 for "SYSTEM"."REPCAT$_FLAVORS"
    Replication pre-import: constraint REPCAT$_FLAVORS_FK1 for "SYSTEM"."REPCAT$_FLAVORS" is disabled successfully
    Replication pre-import: trying to disable constraint REPCAT$_REPSCHEMA_DEST for "SYSTEM"."REPCAT$_REPSCHEMA"
    Replication pre-import: constraint REPCAT$_REPSCHEMA_DEST for "SYSTEM"."REPCAT$_REPSCHEMA" is disabled successfully
    Replication pre-import: trying to disable constraint REPCAT$_REPOBJECT_PRNT for "SYSTEM"."REPCAT$_REPOBJECT"
    Replication pre-import: constraint REPCAT$_REPOBJECT_PRNT for "SYSTEM"."REPCAT$_REPOBJECT" is disabled successfully
    Replication pre-import: trying to disable constraint REPCAT$_REPGEN_PRNT2 for "SYSTEM"."REPCAT$_GENERATED"
    Replication pre-import: constraint REPCAT$_REPGEN_PRNT2 for "SYSTEM"."REPCAT$_GENERATED" is disabled successfully
    Replication pre-import: trying to disable constraint REPCAT$_REPGEN_PRNT for "SYSTEM"."REPCAT$_GENERATED"
    Replication pre-import: constraint REPCAT$_REPGEN_PRNT for "SYSTEM"."REPCAT$_GENERATED" is disabled successfully
    Replication pre-import: trying to disable constraint REPCAT$_PARAMETER_COLUMN_F1 for "SYSTEM"."REPCAT$_PARAMETER_COLUMN"
    Replication pre-import: constraint REPCAT$_PARAMETER_COLUMN_F1 for "SYSTEM"."REPCAT$_PARAMETER_COLUMN" is disabled successfully
    Replication pre-import: trying to disable constraint REPCAT$_PRIORITY_F1 for "SYSTEM"."REPCAT$_PRIORITY"
    Replication pre-import: constraint REPCAT$_PRIORITY_F1 for "SYSTEM"."REPCAT$_PRIORITY" is disabled successfully
    Replication pre-import: trying to disable constraint REPCAT$_REPSCHEMA_PRNT for "SYSTEM"."REPCAT$_REPSCHEMA"
    Replication pre-import: constraint REPCAT$_REPSCHEMA_PRNT for "SYSTEM"."REPCAT$_REPSCHEMA" is disabled successfully
    Replication pre-import: trying to disable constraint REPCAT$_REPCOLUMN_FK for "SYSTEM"."REPCAT$_REPCOLUMN"
    Replication pre-import: constraint REPCAT$_REPCOLUMN_FK for "SYSTEM"."REPCAT$_REPCOLUMN" is disabled successfully
    Replication pre-import: trying to disable constraint REPCAT$_KEY_COLUMNS_PRNT for "SYSTEM"."REPCAT$_KEY_COLUMNS"
    Replication pre-import: constraint REPCAT$_KEY_COLUMNS_PRNT for "SYSTEM"."REPCAT$_KEY_COLUMNS" is disabled successfully
    Replication pre-import: trying to disable constraint REPCAT$_REPPROP_PRNT for "SYSTEM"."REPCAT$_REPPROP"
    Replication pre-import: constraint REPCAT$_REPPROP_PRNT for "SYSTEM"."REPCAT$_REPPROP" is disabled successfully
    Replication pre-import: trying to disable constraint REPCAT$_DDL_PRNT for "SYSTEM"."REPCAT$_DDL"
    Replication pre-import: constraint REPCAT$_DDL_PRNT for "SYSTEM"."REPCAT$_DDL" is disabled successfully
    Replication pre-import: trying to disable constraint REPCAT$_GROUPED_COLUMN_F1 for "SYSTEM"."REPCAT$_GROUPED_COLUMN"
    Replication pre-import: constraint REPCAT$_GROUPED_COLUMN_F1 for "SYSTEM"."REPCAT$_GROUPED_COLUMN" is disabled successfully
    Replication pre-import: trying to disable constraint REPCAT$_RESOLUTION_F1 for "SYSTEM"."REPCAT$_RESOLUTION"
    Replication pre-import: constraint REPCAT$_RESOLUTION_F1 for "SYSTEM"."REPCAT$_RESOLUTION" is disabled successfully
    Replication pre-import: trying to disable constraint REPCAT$_RESOLUTION_F3 for "SYSTEM"."REPCAT$_RESOLUTION"
    Replication pre-import: constraint REPCAT$_RESOLUTION_F3 for "SYSTEM"."REPCAT$_RESOLUTION" is disabled successfully
    Replication pre-import: trying to disable constraint REPCAT$_AUDIT_COLUMN_F2 for "SYSTEM"."REPCAT$_AUDIT_COLUMN"
    Replication pre-import: constraint REPCAT$_AUDIT_COLUMN_F2 for "SYSTEM"."REPCAT$_AUDIT_COLUMN" is disabled successfully
    Replication pre-import: trying to disable constraint REPCAT$_AUDIT_COLUMN_F1 for "SYSTEM"."REPCAT$_AUDIT_COLUMN"
    Replication pre-import: constraint REPCAT$_AUDIT_COLUMN_F1 for "SYSTEM"."REPCAT$_AUDIT_COLUMN" is disabled successfully
    Replication pre-import: trying to disable constraint REPCAT$_REPGROUP_PRIVS_FK for "SYSTEM"."REPCAT$_REPGROUP_PRIVS"
    Replication pre-import: constraint REPCAT$_REPGROUP_PRIVS_FK for "SYSTEM"."REPCAT$_REPGROUP_PRIVS" is disabled successfully
    Replication pre-import: trying to disable constraint REPCAT$_PARAMETER_COLUMN_PK for "SYSTEM"."REPCAT$_PARAMETER_COLUMN"
    Replication pre-import: constraint REPCAT$_PARAMETER_COLUMN_PK for "SYSTEM"."REPCAT$_PARAMETER_COLUMN" is disabled successfully
    Replication pre-import: trying to disable constraint REPCAT$_GROUPED_COLUMN_PK for "SYSTEM"."REPCAT$_GROUPED_COLUMN"
    Replication pre-import: constraint REPCAT$_GROUPED_COLUMN_PK for "SYSTEM"."REPCAT$_GROUPED_COLUMN" is disabled successfully
    Replication pre-import: trying to disable constraint REPCAT$_SITES_NEW_FK1 for "SYSTEM"."REPCAT$_SITES_NEW"
    Replication pre-import: constraint REPCAT$_SITES_NEW_FK1 for "SYSTEM"."REPCAT$_SITES_NEW" is disabled successfully
    Replication pre-import: trying to disable constraint REPCAT$_SITES_NEW_FK2 for "SYSTEM"."REPCAT$_SITES_NEW"
    Replication pre-import: constraint REPCAT$_SITES_NEW_FK2 for "SYSTEM"."REPCAT$_SITES_NEW" is disabled successfully
    Sat Jul 24 10:14:19 2010
    The value (30) of MAXTRANS parameter ignored.
    kupprdp: master process DM00 started with pid=20, OS id=1354
    to execute - SYS.KUPM$MCP.MAIN('SYS_IMPORT_TABLESPACE_01', 'SYSTEM', 'KUPC$C_1_20100724101420', 'KUPC$S_1_20100724101420', 0);
    kupprdp: worker process DW01 started with worker id=1, pid=23, OS id=1356
    to execute - SYS.KUPW$WORKER.MAIN('SYS_IMPORT_TABLESPACE_01', 'SYSTEM');
    Sat Jul 24 10:15:27 2010
    create tablespace indx_ts datafile '/oracle/ts.dbf' size 10m
    Sat Jul 24 10:15:29 2010
    Completed: create tablespace indx_ts datafile '/oracle/ts.dbf' size 10m
    The value (30) of MAXTRANS parameter ignored.
    kupprdp: master process DM00 started with pid=23, OS id=1368
    to execute - SYS.KUPM$MCP.MAIN('SYS_IMPORT_TABLESPACE_01', 'SYSTEM', 'KUPC$C_1_20100724101548', 'KUPC$S_1_20100724101548', 0);
    kupprdp: worker process DW01 started with worker id=1, pid=24, OS id=1370
    to execute - SYS.KUPW$WORKER.MAIN('SYS_IMPORT_TABLESPACE_01', 'SYSTEM');
    statement in resumable session 'SYSTEM.SYS_IMPORT_TABLESPACE_01.1' was suspended due to
    ORA-01652: unable to extend temp segment by 128 in tablespace INDX_TS
    Sat Jul 24 10:46:04 2010
    The value (30) of MAXTRANS parameter ignored.
    kupprdp: master process DM02 started with pid=17, OS id=1426
    to execute - SYS.KUPM$MCP.MAIN('SYS_EXPORT_SCHEMA_01', 'SYSTEM', 'KUPC$C_1_20100724104604', 'KUPC$S_1_20100724104604', 0);
    Sat Jul 24 10:46:46 2010
    The value (30) of MAXTRANS parameter ignored.
    kupprdp: master process DM02 started with pid=17, OS id=1432
    to execute - SYS.KUPM$MCP.MAIN('SYS_EXPORT_SCHEMA_01', 'SYSTEM', 'KUPC$C_1_20100724104647', 'KUPC$S_1_20100724104647', 0);
    Sat Jul 24 10:48:16 2010
    The value (30) of MAXTRANS parameter ignored.
    kupprdp: master process DM02 started with pid=17, OS id=1463
    to execute - SYS.KUPM$MCP.MAIN('SYS_SQL_FILE_FULL_01', 'SYSTEM', 'KUPC$C_1_20100724104816', 'KUPC$S_1_20100724104816', 0);
    kupprdp: worker process DW03 started with worker id=1, pid=18, OS id=1465
    to execute - SYS.KUPW$WORKER.MAIN('SYS_SQL_FILE_FULL_01', 'SYSTEM');
    Sat Jul 24 12:00:40 2010
    Thread 1 advanced to log sequence 2
    Current log# 2 seq# 2 mem# 0: /rmandb/rmandata/redo02.log
    Sat Jul 24 12:15:52 2010
    statement in resumable session 'SYSTEM.SYS_IMPORT_TABLESPACE_01.1' was timed out
    Sat Jul 24 13:18:59 2010
    The value (30) of MAXTRANS parameter ignored.
    kupprdp: master process DM00 started with pid=18, OS id=1841
    to execute - SYS.KUPM$MCP.MAIN('SYS_IMPORT_FULL_03', 'SYSTEM', 'KUPC$C_1_20100724131859', 'KUPC$S_1_20100724131859', 0);
    kupprdp: worker process DW01 started with worker id=1, pid=19, OS id=1843
    to execute - SYS.KUPW$WORKER.MAIN('SYS_IMPORT_FULL_03', 'SYSTEM');
    Sat Jul 24 13:19:10 2010
    CREATE UNDO TABLESPACE "UNDOTBS1" DATAFILE '/oracle/product/dbn/undotbs01.dbf' SIZE 26214400 AUTOEXTEND ON NEXT 5242880 MAXSIZE 32767M BLOCKSIZE 8192 EXTENT MANAGEMENT LOCAL AUTOALLOCATE
    ORA-1543 signalled during: CREATE UNDO TABLESPACE "UNDOTBS1" DATAFILE '/oracle/product/dbn/undotbs01.dbf' SIZE 26214400 AUTOEXTEND ON NEXT 5242880 MAXSIZE 32767M BLOCKSIZE 8192 EXTENT MANAGEMENT LOCAL AUTOALLOCATE...
    Sat Jul 24 13:19:10 2010
    CREATE TABLESPACE "SYSAUX" DATAFILE '/oracle/product/dbn/sysaux01.dbf' SIZE 125829120 AUTOEXTEND ON NEXT 10485760 MAXSIZE 32767M LOGGING ONLINE PERMANENT BLOCKSIZE 8192 EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO
    ORA-1543 signalled during: CREATE TABLESPACE "SYSAUX" DATAFILE '/oracle/product/dbn/sysaux01.dbf' SIZE 125829120 AUTOEXTEND ON NEXT 10485760 MAXSIZE 32767M LOGGING ONLINE PERMANENT BLOCKSIZE 8192 EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO...
    Sat Jul 24 13:19:10 2010
    CREATE TEMPORARY TABLESPACE "TEMP" TEMPFILE '/oracle/product/dbn/temp01.dbf' SIZE 31457280 AUTOEXTEND ON NEXT 655360 MAXSIZE 32767M EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1048576
    ORA-1543 signalled during: CREATE TEMPORARY TABLESPACE "TEMP" TEMPFILE '/oracle/product/dbn/temp01.dbf' SIZE 31457280 AUTOEXTEND ON NEXT 655360 MAXSIZE 32767M EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1048576
    Sat Jul 24 13:19:10 2010
    CREATE TABLESPACE "USERTB" DATAFILE '/oracle/product/dbn/users01.dbf' SIZE 5242880 AUTOEXTEND ON NEXT 1310720 MAXSIZE 32767M LOGGING ONLINE PERMANENT BLOCKSIZE 8192 EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO
    ORA-1119 signalled during: CREATE TABLESPACE "USERTB" DATAFILE '/oracle/product/dbn/users01.dbf' SIZE 5242880 AUTOEXTEND ON NEXT 1310720 MAXSIZE 32767M LOGGING ONLINE PERMANENT BLOCKSIZE 8192 EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO...
    Sat Jul 24 13:19:10 2010
    CREATE TABLESPACE "EXAMPLE" DATAFILE '/oracle/product/dbn/example01.dbf' SIZE 104857600 AUTOEXTEND ON NEXT 655360 MAXSIZE 32767M NOLOGGING ONLINE PERMANENT BLOCKSIZE 8192 EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO
    ORA-1119 signalled during: CREATE TABLESPACE "EXAMPLE" DATAFILE '/oracle/product/dbn/example01.dbf' SIZE 104857600 AUTOEXTEND ON NEXT 655360 MAXSIZE 32767M NOLOGGING ONLINE PERMANENT BLOCKSIZE 8192 EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO
    Sat Jul 24 13:19:10 2010
    CREATE TABLESPACE "NEWTABLESPACE" DATAFILE '/oracle/product/newtablespace.dbf' SIZE 10485760 LOGGING ONLINE PERMANENT BLOCKSIZE 8192 EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1048576 SEGMENT SPACE MANAGEMENT AUTO
    ORA-1119 signalled during: CREATE TABLESPACE "NEWTABLESPACE" DATAFILE '/oracle/product/newtablespace.dbf' SIZE 10485760 LOGGING ONLINE PERMANENT BLOCKSIZE 8192 EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1048576 SEGMENT SPACE MANAGEMENT AUTO
    Sat Jul 24 13:19:10 2010
    CREATE TABLESPACE "T16KTAB" DATAFILE '/oracle/16k.dbf' SIZE 3145728 LOGGING ONLINE PERMANENT BLOCKSIZE 16384 EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO
    ORA-29339 signalled during: CREATE TABLESPACE "T16KTAB" DATAFILE '/oracle/16k.dbf' SIZE 3145728 LOGGING ONLINE PERMANENT BLOCKSIZE 16384 EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO
    Sat Jul 24 13:19:10 2010
    CREATE TABLESPACE "INDX_TS" DATAFILE '/oracle/indxts.dbf' SIZE 26214400,'/oracle/secondf.dbf' SIZE 26214400 LOGGING ONLINE PERMANENT BLOCKSIZE 8192 EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO
    ORA-1543 signalled during: CREATE TABLESPACE "INDX_TS" DATAFILE '/oracle/indxts.dbf' SIZE 26214400,'/oracle/secondf.dbf' SIZE 26214400 LOGGING ONLINE PERMANENT BLOCKSIZE 8192 EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO
    ...

  • Full database import and export

    Hi,
    i performed full database export and want to perform full import please suggest me how to perform full import..

    Oracle will change the data to the db characterset on import. This can be good or bad depending on what you have and what you want. So, what do you have and what do you want? Don't forget to check logs you should be keeping with these utilities. Edit: original exp/imp states the characterset in a log, expdp I guess you need to look at the 3rd line in the dump file. Don't edit dump files, if you are on unix you can use the strings command. It would help if you told us the exact version, patch set and platform you are on.
    Also, see the [url http://docs.oracle.com/cd/E11882_01/server.112/e10729/toc.htm]Globalization Guide.
    Edited by: jgarry on Apr 25, 2012 3:37 PM

  • Full database export hangs (Oracle9i rel2)

    I recently migrated successfully from oracle8i rel 8.0. to oracle9i release 2,But now am not able to do a full database export.has anyone experienced this and whats the remedy?.
    the text i get is listed below.
    Microsoft Windows [Version 5.2.3790]
    (C) Copyright 1985-2003 Microsoft Corp.
    C:\Documents and Settings\Administrator>exp system/manager@ORCL file=C:\orclbk\p
    oll.dmp full=y
    Export: Release 9.2.0.1.0 - Production on Tue Aug 9 18:36:13 2005
    Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
    Connected to: Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.1.0 - Production
    Export done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
    About to export the entire database ...
    . exporting tablespace definitions
    . exporting profiles
    . exporting user definitions
    . exporting roles
    . exporting resource costs
    . exporting rollback segment definitions
    . exporting database links
    . exporting sequence numbers
    . exporting directory aliases
    . exporting context namespaces
    . exporting foreign function library names
    . exporting PUBLIC type synonyms
    . exporting private type synonyms
    . exporting object type definitions
    EXP-00090: cannot pin type "OE"."CUSTOMER_TYP"
    EXP-00056: ORACLE error 22303 encountered
    OCI-22303: type "OE"."CUSTOMER_TYP" not found
    EXP-00056: ORACLE error 24323 encountered
    ORA-24323: value not allowed
    EXP-00000: Export terminated unsuccessfully
    C:\Documents and Settings\Administrator>

    You have to run the export with the SYS user. This error may arise on any plattform ranging form 9.0.1 to 10.2.0.
    C:\>exp "'sys/oracle as sysdba'" full=y

  • Import error while full database import

    Hi,
    I am getting below error while import from one server to other server.
    oracle version from 10.2.0.1.0 to 10.2.0.5.0.
    IMP-00015: following statement failed because the object already exists: on full import
    Export file created by EXPORT:V10.02.01 via conventional path
    import done in US7ASCII character set and AL16UTF16 NCHAR character set
    import server uses WE8ISO8859P1 character set (possible charset conversion)
    . importing SYSTEM's objects into SYSTEM
    IMP-00017: following statement failed with ORACLE error 1119:
    "CREATE TABLESPACE "JISPREPCORBILLINGPRD501" BLOCKSIZE 8192 DATAFILE '/opt/"
    "u01/app/oracle/oradata/ora10g/jisprepcorbillingprd501.dbf' SIZE 52428800 "
    " AUTOEXTEND ON NEXT 8192 MAXSIZE 32767M EXTENT MANAGEMENT LOCAL AUTOAL"
    "LOCATE ONLINE PERMANENT SEGMENT SPACE MANAGEMENT AUTO"
    IMP-00003: ORACLE error 1119 encountered
    ORA-01119: error in creating database file '/opt/u01/app/oracle/oradata/ora10g/jisprepcorbillingprd501.dbf'
    ORA-27040: file create error, unable to create file
    Linux-x86_64 Error: 2: No such file or directory
    IMP-00017: following statement failed with ORACLE error 1119:
    "CREATE TABLESPACE "CYBEROAM" BLOCKSIZE 8192 DATAFILE '/opt/u01/app/oracle/"
    "oradata/ora10g/cyberoam.dbf' SIZE 70057984 AUTOEXTEND ON NEXT 8192 M"
    "AXSIZE 32767M EXTENT MANAGEMENT LOCAL AUTOALLOCATE ONLINE PERMANENT SEGM"
    "ENT SPACE MANAGEMENT AUTO"
    IMP-00003: ORACLE error 1119 encountered
    ORA-01119: error in creating database file '/opt/u01/app/oracle/oradata/ora10g/cyberoam.dbf'
    ORA-27040: file create error, unable to create file
    Linux-x86_64 Error: 2: No such file or directory
    IMP-00017: following statement failed with ORACLE error 1119:
    "CREATE TABLESPACE "CAPTIVEPORTAL" BLOCKSIZE 8192 DATAFILE '/opt/u01/app/or"
    "acle/oradata/ora10g/captiveportal.dbf' SIZE 52428800 AUTOEXTEND ON NE"
    "XT 8192 MAXSIZE 32767M EXTENT MANAGEMENT LOCAL AUTOALLOCATE ONLINE PERMA"
    "NENT SEGMENT SPACE MANAGEMENT AUTO"
    IMP-00003: ORACLE error 1119 encountered
    how to resolve it?
    Thanks in advance.

    "CREATE TABLESPACE "JISPREPCORBILLINGPRD501" BLOCKSIZE 8192 DATAFILE '/opt/"
    "u01/app/oracle/oradata/ora10g/jisprepcorbillingprd501.dbf' SIZE 52428800 "
    " AUTOEXTEND ON NEXT 8192 MAXSIZE 32767M EXTENT MANAGEMENT LOCAL AUTOAL"
    "LOCATE ONLINE PERMANENT SEGMENT SPACE MANAGEMENT AUTO"
    "CREATE TABLESPACE "CYBEROAM" BLOCKSIZE 8192 DATAFILE '/opt/u01/app/oracle/"
    "oradata/ora10g/cyberoam.dbf' SIZE 70057984 AUTOEXTEND ON NEXT 8192 M"
    "AXSIZE 32767M EXTENT MANAGEMENT LOCAL AUTOALLOCATE ONLINE PERMANENT SEGM"
    "ENT SPACE MANAGEMENT AUTO"
    "CREATE TABLESPACE "CAPTIVEPORTAL" BLOCKSIZE 8192 DATAFILE '/opt/u01/app/or"
    "acle/oradata/ora10g/captiveportal.dbf' SIZE 52428800 AUTOEXTEND ON NE"
    "XT 8192 MAXSIZE 32767M EXTENT MANAGEMENT LOCAL AUTOALLOCATE ONLINE PERMA"
    "NENT SEGMENT SPACE MANAGEMENT AUTO"
    IMP-00003: ORACLE error 1119 encounteredThree tablespaces.
    how to resolve it?Create those tablesspaces manually and then try to improt it.
    to take the DDL, you can use either SQLFILE option in impdp or use dbms_metadata.get_ddl

  • Some objects in sys schema not imported usinf full database import/export.

    Hello All,
    We need to migrate database from one server to new server using same database version 11g Release 2 (11.2.0.1.0). We have some production objects in sys schema. We took full export using full=y and then import on new server using full=y. Other objects belonging to different tablespaces and users has successfully imported but production objects i.e table in sys schema not import.
    We used following commands for export and import:
    # exp system file=/u01/backup/orcl_full_exp.dmp log=/u01/backup/orcl_full_exp.log full=y statistics=none
    # imp system file=/u01/backup/orcl_full_exp.dmp log=/u01/backup/orcl_full_imp.log full=y ignore=y
    Kind Regards,
    Sharjeel

    Hi,
    First of all it is not good practice to keep user object in the sys schema
    second you are useing version 11gr2 what not you go for datapump export/import method.
    third, did you get any error in import, what is the error

  • Importing full database and SYSTEM password

    Hi,
    I have a export dump of a database (full database dump). Want to import on my existing database.
    I have create a database, with tablespaces matching names with source database (i.e. got a list of tablespaces from the dba of source database and created them). Now, I am ready to import with imp command (with FULL=Y option).
    Will the full database import change my SYSTEM's password to the system's password on the source database ?
    Reason for this question is, If you try to read the export of full database (using wordpad !!), you will find all commands creating tablespaces, users, roles etc etc etc. Also, you will see commands which alter the users SYS and SYSTEM to change the password !!!
    Any past experiences ??
    Thanks in advance.

    Hi,
    >>Will the full database import change my SYSTEM's password to the system's password on the source database ?
    Yes, take a look at demonstration below:
    C:\>exp system/pass file=test.dmp full=y statistics=none
    Export: Release 10.2.0.1.0 - Production on Mon Apr 21 13:59:51 2008
    Copyright (c) 1982, 2005, Oracle.  All rights reserved.
    Connected to: Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
    Export done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
    About to export the entire database ...
    . exporting tablespace definitions
    . exporting profiles
    . exporting user definitions
    . exporting roles
    . exporting resource costs
    . exporting rollback segment definitions
    . exporting database links
    . exporting sequence numbers
    . exporting directory aliases^C
    C:\>findstr /C:"ALTER USER SYS" TESTE.DMP
    ALTER USER SYS IDENTIFIED BY VALUES '5638228DAF52805F' TEMPORARY TABLESPACE "TEMP"
    ALTER USER SYSTEM IDENTIFIED BY VALUES 'D4DF7931AB130E37' TEMPORARY TABLESPACE "TEMP"
    Cheers
    Legatti

  • Full Database Export/Import

    I was attempting to export a full database from one server (DB files on the N: drive) and import it into a freshly created new database with the same instance name on a new server (DB files on the D: drive).
    I was told to:
    1) Export the full database as sys using full=y
    2) Pre-create all of the tablespaces on the target database that do not exist on the target database
    3) Import the full database as sys using full=y
    =========================================================
    Here are the steps I had to follow:
    1) Export the full database as sys using full=y
    2) Pre-create all of the tablespaces on the target database
    3) Import the full database as sys using full=y - Result: over 1900 invalid objects and thousands of errors
    4) Run Utlrp.sql - Result: 8 to 10 invalid objects
    5) Manually attempt to compile or rebuild objects. Several grants were required to get most of these to work. - Result: After quite a bit of hand crafting, two objects are still invalid.
    6) After spending almost two hours in a Collaborative Conference with an analyst who is working very hard to sold this, there are still two objects that are invalid.
    Note: From my perspective this is not a straight forward process
    =========================================================
    Questions:
    1) Has anyone successfully moved a database as described without all of these annoying steps?
    2) Is there a document that details the full database export/import?
    Thanks, RJZ

    Hello RJZ,
    There is not sufficient information to reply accurately to your queries,
    1. Could you post the error message that you're getting when you compile these two programs? Do they compile okay on the old server?
    2. What was the reason you choose exp and imp, to move your db to the new server and different disk? Were you migrating to a different version, or was it because of the db-reorg? It would have been possible to simple copy the db-files to the new location, and then rename the datafiles in mount-state. It would be more simpler I believe unless as stated above
    Did you check the import logs? While importing were there any errors? Actually it should have been pretty straight forward (no reason why you need documentation for exp / imp). Grants should have automatically come, unless you have select grants=n option
    I think because of the changes you have done for step-5, you might have changed some stuff somewhere. Please post the error message, and tell us if you have migrated the db to a higher version
    Regards
    Sudhanshu

  • Importing full database in 8i

    I have a full database export of a database.
    I will have to import that into an oracle 8i database.
    May I know what are the considerations to be made/ precautions to be taken care of in precise?
    Shd I create all the tablespaces and users forehand? Or the full=y statement during import creates it all ?

    imp will attempt to run CREATE TABLESPACE statement with the DATAFILE names and sizes being the same as in the source database.
    If your filesystem structure / filesystem sizes are different at the target you should manually precreate each Tablespace.
    Also, manually precreating Tablespaces gives you the option to change DEFAULT STORAGE parameters.
    Hemant K Chitale

  • Export/Import full database dump fails to recreate the workspaces

    Hi,
    We are studying the possibility of using Oracle Workspace to maintain multiple versions of our business data. I recently did some tests with the import/export of a dump that contains multiple workspaces. I'm not able to import the dump successfully because it doesn't recreate the workspaces on the target database instance, which is an empty Oracle database freshly created. Before to launch the import with the Oracle Data Pump utility, I have the "LIVE" workspace that exists in the WMSYS.WM$WORKSPACES_TABLE table. After the import is done, there is nothing in that table...
    The versions of the Oracle database and Oracle Workspace Manager are the same on source and target database:
    Database version (from the V$VERSION view):
    Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
    PL/SQL Release 10.2.0.4.0 - Production
    CORE     10.2.0.4.0     Production
    TNS for 64-bit Windows: Version 10.2.0.4.0 - Production
    NLSRTL Version 10.2.0.4.0 - Production
    Workspace Manager version (from the WM_INSTALLATION view):
    OWM_VERSION: 10.2.0.4.3
    In order to recreate the tablespaces successfully during the full import of the dump, the directory structure for the tablespaces is the same on the target database's computer. I used the instructions given in this document, section "1.6 Import and Export Considerations" at page 1-19:
    http://www.wyswert.com/documentation/oracle/database/11.2/appdev.112/e11826.pdf
    Considering that the release of Oracle database used is version 10.2.0.4, I use the following command to import the dump since it doesn't contain the WMSYS schema:
    impdp system/<password>@<database> DIRECTORY=data_pump_dir DUMPFILE=expfull.dmp FULL=y TABLE_EXISTS_ACTION=append LOGFILE=impfull.log
    The only hints I have in the import log file are the following block of lines:
    1st one:
    ==============================
    Traitement du type d'objet DATABASE_EXPORT/SYSTEM_PROCOBJACT/PRE_SYSTEM_ACTIONS/PROCACT_SYSTEM
    ORA-39083: Echec de la création du type d'objet PROCACT_SYSTEM avec erreur :
    ORA-01843: ce n'est pas un mois valide
    SQL en échec :
    BEGIN
    if (system.wm$_check_install) then
    return ;
    end if ;
    begin execute immediate 'insert into wmsys.wm$workspaces_table
    values(''LIVE'',
    ''194'',
    ''-1'',
    2nd one at the end of the import process:
    ==============================
    Traitement du type d'objet DATABASE_EXPORT/SCHEMA/POST_SCHEMA/PROCACT_SCHEMA
    ORA-39083: Echec de la création du type d'objet PROCACT_SCHEMA avec erreur :
    ORA-20000: Workspace Manager Not Properly Installed
    SQL en échec :
    BEGIN
    declare
    compile_exception EXCEPTION;
    PRAGMA EXCEPTION_INIT(compile_exception, -24344);
    begin
    if (system.wm$_check_install) then
    return ;
    end if ;
    execute immediate 'alter package wmsys.ltadm compile';
    execute immediate 'alter packag
    The target operating system is in french... here is a raw translation:
    1st one:
    ==============================
    Treatment of object type DATABASE_EXPORT/SYSTEM_PROCOBJACT/PRE_SYSTEM_ACTIONS/PROCACT_SYSTEM
    ORA-39083: Object type creation failed PROCACT_SYSTEM with error :
    ORA-01843: invalid month
    failed SQL :
    BEGIN
    if (system.wm$_check_install) then
    return ;
    end if ;
    begin execute immediate 'insert into wmsys.wm$workspaces_table
    values(''LIVE'',
    ''194'',
    ''-1'',
    2nd one at the end of the import process:
    ==============================
    Treatment of object type DATABASE_EXPORT/SCHEMA/POST_SCHEMA/PROCACT_SCHEMA
    ORA-39083: Object type creation failed PROCACT_SCHEMA with error :
    ORA-20000: Workspace Manager Not Properly Installed
    failed SQL :
    BEGIN
    declare
    compile_exception EXCEPTION;
    PRAGMA EXCEPTION_INIT(compile_exception, -24344);
    begin
    if (system.wm$_check_install) then
    return ;
    end if ;
    execute immediate 'alter package wmsys.ltadm compile';
    execute immediate 'alter packag
    By the way, the computer of the source database is Vista 64 in english and the destination computer is Vista 64 in french, do you think this has anything to do with these error messages? The parameters of the NLS_SESSION_PARAMETERS view are the same in the source and target database...
    Thanks in advance for your help!
    Joel Autotte
    Lead Developer
    Edited by: 871007 on Jul 13, 2011 7:31 AM

    I tried to import the full database dump with the "imp" command and I had the same error message with more detail:
    . Import d'objets SYSTEM dans SYSTEM
    IMP-00017: Echec de l'instruction suivante avec erreur ORACLE 1843 :
    "BEGIN "
    "if (system.wm$_check_install) then"
    " return ;"
    " end if ;"
    " begin execute immediate 'insert into wmsys.wm$workspaces_ta"
    "ble"
    " values(''LIVE'',"
    " ''194'',"
    " ''-1'',"
    " ''SYS'',"
    " *to_date(''09-DEC-2009 00:00:00'', ''DD-MON-YYYY HH"*
    *"24:MI:SS''),"*
    " ''0'',"
    " ''UNLOCKED'',"
    " ''0'',"
    " ''0'',"
    " ''37'',"
    " ''CRS_ALLNONCR'',"
    " to_date(''06-APR-2011 14:24:57'', ''DD-MON-YYYY HH"
    "24:MI:SS''),"
    " ''0'',"
    " '''')'; end;"
    "COMMIT; END;"
    IMP-00003: Erreur ORACLE 1843 rencontrée
    ORA-01843: ce n'est pas un mois valide
    ORA-06512: à ligne 5
    The call to the TO_DATE function with the string of the date format is incompatible with the format and language set in the NLS parameters of my database. Since I know that the "imp" and "exp" commands work client side (unlike "impdp" and "expdp"), I did a full export of the source database from the computer on which I try to import the dump to have the same language exported in the dump and I was able to import the dump successfully.
    But, I would like to use the Data Pump tool instead of the old import and export tools. How would it be possible to set the NLS parameters that "impdp" must use before to launch the import of the dump?
    The NLS parameters are set to the "AMERICAN" settings in both source and destination database when I validate that with the "NLS_DATABASE_PARAMETERS" view. The dump I did with "expdp" on the source database exported the data with the "AMERICAN" settings as well...
    On the destination database, the computer language is in french and I guess it is considered by the Data Pump import tool since it outputs the log in the language of the computer and it tries to do a TO_DATE with the wrong date format because it works with the "CANADIAN FRENCH" settings...
    Any suggestions? I'll continue to read on my side and re-post if I find the solution.
    Thanks!
    Edited by: 871007 on Jul 19, 2011 8:42 AM
    Edited by: 871007 on Jul 19, 2011 8:43 AM
    Edited by: 871007 on Jul 19, 2011 8:43 AM

  • Import from a full database export having  5 .dmp files

    i have a full database export having 5 .dmp files of 2g each, its having a user agvlc and which contains some partitioned tables,i imported the data for the user agvlc in a tablespace agvlc al the tables gets imported but the partitions are not getting imported what can i do to import the partitions as well
    thanx in advance

    Hello,
    al the tables gets imported but the partitions are not getting imported what can i do to import the partitions as wellHow do you see that the Partitions are not imported ? Do you have any error message ?
    Which options did you use for the Import ?
    Please, as previously said, post all the informations so that we can help you efficiently.
    Best regards,
    Jean-Valentin

Maybe you are looking for