Skip to Main Content
  • Questions
  • impdp is failing with below errors with full database import.

Breadcrumb

May 4th

Question and Answer

Connor McDonald

Thanks for the question, Immaniyelu.

Asked: September 22, 2015 - 3:31 pm UTC

Last updated: September 24, 2015 - 6:10 am UTC

Version: 11g

Viewed 10K+ times! This question is

You Asked

Hi Tom,

I am doing EBS migration from 32 bit linx to 64 bit.i am using EXPDP/IMPDP.

Expdp is done sucessfully.after that i installed dummy database on 64 bit server.and i am running impdp,with below parameters.But it was failing due to below errors.

parfile:

DUMPFILE=fullmig.dmp
DIRECTORY=migration
PARALLEL=3
FULL=y
LOGFILE=fullmigimp.log
JOB_NAME=fulldbimport
#ESTIMATE=y
userid=system/manager

logfile:

Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
;;;
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Master table "SYSTEM"."FULLDBIMPORT" successfully loaded/unloaded
Starting "SYSTEM"."FULLDBIMPORT": system/******** parfile=parfile.par
Processing object type DATABASE_EXPORT/TABLESPACE
ORA-39083: Object type TABLESPACE failed to create with error:
ORA-01119: error in creating database file '/slot/ems12460/oracle/mig/data/undo01.dbf'
ORA-27040: file create error, unable to create file
Linux-x86_64 Error: 2: No such file or directory
Additional information: 1
Failing sql is:
CREATE UNDO TABLESPACE "APPS_UNDOTS1" DATAFILE '/slot/ems12460/oracle/mig/data/undo01.dbf' SIZE 1048576000 AUTOEXTEND ON NEXT 8192 MAXSIZE 2097152000,'/slot/ems12460/oracle/mig/data/undo02.dbf' SIZE 1048576000 AUTOEXTEN
ORA-31684: Object type TABLESPACE:"TEMP" already exists
ORA-39083: Object type TABLESPACE failed to create with error:
ORA-01119: error in creating database file '/slot/ems12460/oracle/mig/data/archive1.dbf'
ORA-27040: file create error, unable to create file
Linux-x86_64 Error: 2: No such file or directory
Additional information: 1
Failing sql is:
CREATE TABLESPACE "APPS_TS_ARCHIVE" DATAFILE '/slot/ems12460/oracle/mig/data/archive1.dbf' SIZE 1048576000 AUTOEXTEND ON NEXT 8192 MAXSIZE 2097152000,'/slot/ems12460/oracle/mig/data/archive2.dbf' SIZE 1048576000 AUTOE
ORA-39083: Object type TABLESPACE failed to create with error:
ORA-01119: error in creating database file '/slot/ems12460/oracle/mig/data/media1.dbf'
ORA-27040: file create error, unable to create file
Linux-x86_64 Error: 2: No such file or directory

Failing sql is:
CREATE TABLESPACE "ORABPEL" DATAFILE '/slot/ems12460/oracle/mig/data/orabpel.dbf' SIZE 104857600 AUTOEXTEND ON NEXT 31457280 MAXSIZE 2097152000 LOGGING ONLINE PERMANENT BLOCKSIZE 8192 EXTENT MANAGEMENT LOCAL AUTOALLOCA
Processing object type DATABASE_EXPORT/PROFILE
ORA-31684: Object type PROFILE:"AD_PATCH_MONITOR_PROFILE" already exists
ORA-31684: Object type PROFILE:"EM_OAM_MONITOR_PROFILE" already exists
Processing object type DATABASE_EXPORT/SYS_USER/USER
Processing object type DATABASE_EXPORT/SCHEMA/USER
ORA-31684: Object type USER:"OUTLN" already exists
ORA-39083: Object type USER failed to create with error:
ORA-00959: tablespace 'APPS_TS_TX_DATA' does not exist
Failing sql is:
CREATE USER "ABM" IDENTIFIED BY VALUES 'D0F2982F121C7840' DEFAULT TABLESPACE "APPS_TS_TX_DATA" TEMPORARY TABLESPACE "TEMP"
ORA-39083: Object type USER failed to create with error:
ORA-00959: tablespace 'APPS_TS_TX_DATA' does not exist
Failing sql is:
CREATE USER "ADS" IDENTIFIED BY VALUES 'D23F0F5D871EB69F' DEFAULT TABLESPACE "APPS_TS_TX_DATA" TEMPORARY TABLESPACE "TEMP"
ORA-39083: Object type USER failed to create with error:
ORA-00959: tablespace 'APPS_TS_TX_DATA' does not exist
Failing sql is:
CREATE USER "ADSEUL_US" IDENTIFIED BY VALUES '4953B2EB6FCB4339' DEFAULT TABLESPACE "APPS_TS_TX_DATA" TEMPORARY TABLESPACE "TEMP"
ORA-39083: Object type USER failed to create with error:
ORA-00959: tablespace 'APPS_TS_TX_DATA' does not exist
Failing sql is:
CREATE USER "AHL" IDENTIFIED BY VALUES '7910AE63C9F7EEEE' DEFAULT TABLESPACE "APPS_TS_TX_DATA" TEMPORARY TABLESPACE "TEMP"
ORA-39083: Object type USER failed to create with error:
ORA-00959: tablespace 'APPS_TS_TX_DATA' does not exist
Failing sql is:
CREATE USER "AHM" IDENTIFIED BY VALUES '33C2E27CF5E401A4' DEFAULT TABLESPACE "APPS_TS_TX_DATA" TEMPORARY TABLESPACE "TEMP"
ORA-39083: Object type USER failed to create with error:
ORA-00959: tablespace 'APPS_TS_TX_DATA' does not exist
Failing sql is:
CREATE USER "AK" IDENTIFIED BY VALUES '8FCB78BBA8A59515'



and Connor said...

There was a problem trying to create a datafile:

ORA-01119: error in creating database file '/slot/ems12460/oracle/mig/data/undo01.dbf'

So possible causes are

- the directory might not exist,
- the permissions might not be correct for the oracle user to write to it
etc

Its no different then if you did:

echo Hello > /slot/ems12460/oracle/mig/data/undo01.dbf

The subsequent errors are because when we came to create a user, we wanted to assign a default tablespace, which did not exist because of datafile issues we had earlier in the import.

Hope this helps.

Rating

  (3 ratings)

Is this answer out of date? If it is, please let us know via a Comment

Comments

full database impdp is not working.

Immaniyelu Battula, September 23, 2015 - 5:46 am UTC

Hi Tom,

this is the source database datafile /slot/ems12460/oracle/mig/data/undo01.dbf.

I am importing the target.it should be convert that data file as per our requirement right.

Connor McDonald
September 24, 2015 - 1:34 am UTC

In a normal full import, the data *files* are not "converted", they are simply created. As the *data* is imported, it will be converted across charactersets (if necessary and if possible).

So you need to make sure that directories exist when you want the datafiles to be created.

do you have any metalink note id

Immaniyelu Battula, September 23, 2015 - 5:49 am UTC

Hi Tom,

do you have any meta link note id from cross plat form migration or document?

need to import EBS full database Linux 32 bit o 64 bit.

Connor McDonald
September 24, 2015 - 1:36 am UTC

If you are only going from 32 to 64bit on the *same* platform, you do not need to *convert* platform, you need to convert the word size.

See MOS Doc ID 341880.1

Hope this helps

need expdp and impdp metalink(not transportable tablespace)

Immaniyelu Battula, September 24, 2015 - 2:27 am UTC

Hi,

Do you have note id for expdp/impdp?.I want to learn cross platform migration.if you have pleae provide that moteid?

More to Explore

VLDB

If you are new to partitioning, check out Connor McDonald's introduction series here.

VLDB

Documentation set on VLDB and Partitioning.