Re: Problem with impdp

simpsonjohnj_at_gmail.com wrote:
> Hi everyone,
>
> I am setting up a new server and attempting to use the oracle import
> data pump to import a schema to a new tablespace. The orinal
> tablespace is a read-only tablespace, and the new one is not. When I
> try to do this on the new server, I get the error displayed below. If
> I change the original tablespace to read, write, then the import works
> fine. However, I should not have to do this, as I am able to use the
> import dp utility to import a schema to a new read-write tablespace
> from a read-only tablespace on two other identical servers. Does
> anyone have any idea as to what is causing this problem or how I should
> go about fixing it. The impd call form the command line and the error
> are shown below. Thanks in advance.
>
> IMPDP admin_username/password_at_instance DIRECTORY=oradumps
> DUMPFILE=Warehouse_par_exp%u.dmp REMAP_SCHEMA=orig_schema:new_schema
> REMAP_TABLESPACE=orig_tbs:new_tbs parallel=2
>
> Import: Release 10.2.0.1.0 - 64bit Production on Tuesday, 10 October,
> 2006 10:52:07
>
> Copyright (c) 2003, 2005, Oracle. All rights reserved.
>
> Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0
> - 64bit Production
> With the Partitioning, OLAP and Data Mining options
> ORA-31626: job does not exist
> ORA-31633: unable to create master table "ADMIN.SYS_IMPORT_FULL_05"
> ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
> ORA-06512: at "SYS.KUPV$FT", line 863
> ORA-01647: tablespace 'ORIG_TBS' is read only, cannot allocate space in
> it

Error:	  ORA-31633  (ORA-31633)
Text:	  unable to create master table %s.%s
---------------------------------------------------------------------------
Cause:	Job creation failed because a Master Table and its indexes could

	not be created, most commonly due to the pre-existance of a table
	with the same name (job name) in the user schema. Refer to any
	following error messages for clarification.
Action:	Select a different job name, DROP the existing table, or
	eliminate any problems indicated by the following error messages.

Definitely a call to support for this one, unless, maybe on the servers that work you let the user have quota on the ts?

jg

--
@home.com is bogus.
http://www.newsoftheweird.com/special/special.html