IMPORT INTO A DIFFERENT TABLESPACE

Hi All,
When attempting to import a .dmp file into a user with different default tablespace errors IMP-00003 and ORA-00922 was raised, some objects were imported but the problem seems to arise when importing tables. Help will be greatly appreciated.

Quote: apart from that you have to realize if the definition of your tables are poiting to a specific tablespace because if that is your case. You have to create that tablespace with quota for the new user and after move your tables from that tablespace.
Not true, Import first attempts to create an object in it's specified tablespace. If it is unable to then it will create the object in the owners default tablespace.
So buy changing a users default tablespace (with a quota) and removing the users quota from the old tablespace, you can actually change tablespaces on import.

Similar Messages

Importing data into a different tablespace

How do we import an user level export file into another user and a different tablespace from the tablespace clause specified in the export file ?
Thanx in advance
Abhijit

>
I can say that anybody with
no experience could easily do an export/import in
MSSQLServer 2000.
Anybody with no experience should not mess up my Oracle Databases !

How to move partitions/sub-partitions into a different tablespace?

Hi Uisng oracle 1..20.3 and have a range-hash partitioned table using interval partitioning - code below.
Works fine just one problem.
we wish to move the system geneerated partitions to different tablespaces later and also rename th epartitions.
When try assign partition to a different tablespace get the folloiwng message
alter table por_rt move partition SYS_P2283 tablespace bi_dw_data
get message ora-14257 - cannot move partition other than range,list, system or hash partition.
How can we avoid this.
We we need to move all the subpartitions first?
Tried this
alter table move subpartition SYS_SUBP2269 tablespace bi_dw_data;
but get message ora-01735 message invalid statement
-- Create table
create table POR_RT
plant_issue_id    NUMBER not null,
pf_run_num        NUMBER,
partitioning_date DATE
partition by range (PARTITIONING_DATE)
subpartition by hash (PLANT_ISSUE_ID)
partition PART_200912 values less than (TO_DATE(' 2010-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace BI_SUPPORT_DATA
    pctfree 10
    initrans 1
    maxtrans 255
    subpartition SYS_SUBP2261 tablespace BI_SUPPORT_DATA,
    subpartition SYS_SUBP2262 tablespace BI_SUPPORT_DATA,
    subpartition SYS_SUBP2263 tablespace BI_SUPPORT_DATA,
    subpartition SYS_SUBP2264 tablespace BI_SUPPORT_DATA
partition PART_201001 values less than (TO_DATE(' 2010-02-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace BI_SUPPORT_DATA
    pctfree 10
    initrans 1
    maxtrans 255
    subpartition SYS_SUBP2265 tablespace BI_SUPPORT_DATA,
    subpartition SYS_SUBP2266 tablespace BI_SUPPORT_DATA,
    subpartition SYS_SUBP2267 tablespace BI_SUPPORT_DATA,
    subpartition SYS_SUBP2268 tablespace BI_SUPPORT_DATA
partition SYS_P2273 values less than (TO_DATE(' 2010-03-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace BI_SUPPORT_DATA
    pctfree 10
    initrans 1
    maxtrans 255
    subpartition SYS_SUBP2269 tablespace BI_SUPPORT_DATA,
    subpartition SYS_SUBP2270 tablespace BI_SUPPORT_DATA,
    subpartition SYS_SUBP2271 tablespace BI_SUPPORT_DATA,
    subpartition SYS_SUBP2272 tablespace BI_SUPPORT_DATA
partition SYS_P2283 values less than (TO_DATE(' 2010-07-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace BI_SUPPORT_DATA
    pctfree 10
    initrans 1
    maxtrans 255
    subpartition SYS_SUBP2279 tablespace BI_SUPPORT_DATA,
    subpartition SYS_SUBP2280 tablespace BI_SUPPORT_DATA,
    subpartition SYS_SUBP2281 tablespace BI_SUPPORT_DATA,
    subpartition SYS_SUBP2282 tablespace BI_SUPPORT_DATA
partition SYS_P2278 values less than (TO_DATE(' 2010-08-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    tablespace BI_SUPPORT_DATA
    pctfree 10
    initrans 1
    maxtrans 255
    subpartition SYS_SUBP2274 tablespace BI_SUPPORT_DATA,
    subpartition SYS_SUBP2275 tablespace BI_SUPPORT_DATA,
    subpartition SYS_SUBP2276 tablespace BI_SUPPORT_DATA,
    subpartition SYS_SUBP2277 tablespace BI_SUPPORT_DATA
);Edited by: user5716448 on 22-Mar-2013 04:49

you can not move composite parition directly you need to move subpartition using this statments
alter table <tablename> move subpartition <sub partition name > tablespace <tablespace name>;
than change partition tablespace using
ALTER TABLE <table name> MODIFY DEFAULT ATTRIBUTES FOR PARTITION      <partition name> TABLESPACE <tablespace name>;

Export - import to a different tablespace ??

I have exported a schema from 8174 from production as the user itself.
exp user/user ........
I am trying to import it into development.
Only one table i am importing it from the dump.But this table structure is already existing in a tablespace different from production.....
say if t1 is in tbs1 -- Prrod.
t1 is in tbs2 -- dev.
so while import the data is going into this tbs2... and not tbs1 of dev.
The default tablespace of user is tbs1.
So how can i import it intot tbs2?
Please help me ...

Is t1 in development (the target database) already in the appropriate tablespace?
If not, correct that by doing:
alter table t1 move tablespace tablespace_where_t1_should_live;
Then do the import with "ignore=y".
That ought to take care of it.
-Mark

Impdp import schema to different tablespace

Hi,
I have PRTDB1 schema in PRTDTS tablespace, I need encrypt this tablespace.
and I have done this steps:
1. I created new encrypted PRTDTS_ENC tablespace.
2. I take export PRTDB1 schema. (expdp system/system schema=PRTDB1 directory=datapump dumpfile=data.dmp logfile=log1.log)
and I want import this dump to new PRTDTS_ENC tablespace.
can you give me impdp command, which I need?

Hello,
ORA-14223: Deferred segment creation is not supported for this table
Failing sql is:
CREATE TABLE "PRTDB1"."DATRE_CONT" ("BRON" NUMBER NOT NULL ENABLE, "PCDID" NUMBER(9,0) NOT NULL ENABLE, "OWNERSID" NUMBER NOT NULL ENABLE, "VALUESTR" VARCHAR2(4000 CHAR), "VALNUM" NUMBER, "VALDATE" DATE, "VALXML" "XMLTYPE") SEGMENT CREATION DEFERRED PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING So it means that these Tables "need" a Segment but, they are created with the option SEGMENT CREATION DEFERRED.
A workaround is to create a Segment for these Tables on the Source Database before exporting them. Then, at the Import you won't have the option SEGMENT CREATION DEFERRED. The following Note of MOS detail this Solution:
- *Error Ora-14223 Deferred Segment Creation Is Not Supported For This Table During Datapump Import [ID 1293326.1]*
The link below gives more informations about the DEFERRED SEGMENT CREATION:
http://docs.oracle.com/cd/E14072_01/server.112/e10595/tables002.htm#CHDGJAGB
With the DEFERRED SEGMENT CREATION feature, a Segment is created automatically at the first insert on the Table. So the Tables for which the error ORA-14223 occurs are empty.
You may also create them separately by using a script generated by the SQLFILE parameter in which you change the option SEGMENT CREATION DEFERRED by SEGMENT CREATION IMMEDIATE.
Hope this help.
Best regards,
Jean-Valentin

Import to different tablespace

Hi all..
I created dump file in one database with tablespace1 in Oracle 10g XE using expdp
and
now i want to import that dump file in another database with different tablespace2 name.
What is the option for this...?
Thanks in advance
Pal

Change the default tablespace of the user, under which the dump is to be imported, to a different tablespace.
Once importing is done, you can restore the tablespace.

Importing into a new schema with new logical structures

Hi,
I need to export an existing schema from a 9.2.0.3 database into a new schema ( all the objects into a different tablespace - tables & indexes ; from the original config ) within the same DB.
I am thinking of the following approach :
1. Export the original schema.
2. Create new tablespaces for the "new schema" tables and indexes.
3. Create an indexfile ; renaming the older tablespaces / usernames.
4. Create the new user and grant appropriate privileges.
5. Login as the new user and run the indexfile
Am I missing out any vital points ? Would the pl/sql structures associated with the schema be imported in ok ? Any associated complications that I should be prepared for ?
Unfortunately there isnt a test server in place to test it out before hand.
Please advice.

You missed a step. After you created the indexfile.sql and changed the tablespace names. You are supposed to run the indexfile.sql. That will pre-create the objects. You also have to remove at the comment block indicators: "REM", else it just tries to create indexes. You will also have to ad the "ignore=y" to your imp command, else it will try the create the objects and fail.
Unlimited tablespace shouldn't be an issue.

Export then Import to a different Hyper-V server

In http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/85dc7d36-491f-4b02-88ac-63c1ed0d94db I described a problem when exporting from a Hyper-V server and trying to import into a different Hyper-V server in a different domain. The import failed and the event log contained:
Failed to import the virtual machine from import directory 'D:\HV\Test\Test4GB-3\'. Error: One or more arguments are invalid(0x80070057)Well I've now identified the source of the problem. In the .exp file is:
<INSTANCE
CLASSNAME="Msvm_VirtualSystemGlobalSettingData">
<PROPERTY NAME="ScopeOfResidence" TYPE="string">
    <VALUE>
      e7668fbc-216e-4ed1-8ce3-3b932b42e22b
    </VALUE>
</PROPERTY>
If I edit the .exp file and delete the <value>..</value> then the virtual machine imports with no errors.
Looks like a Hyper-V bug to me!
JR

We are not planning to fix this for Windows 2008 at the moment - as SCVMM work around the problem when they move virtual machines (they remove the scope section just like you have done here). But here is a handy VBScript that you can run on a Hyper-V server that will go through and nuke all the scopes (do not use this if you are still using SCVMM) so you can export and import happily (note that you need to run this before exporting):
Option Explicit
Dim WMIService
Dim VMList
Dim VM
Dim VMSystemGlobalSettingData
Dim VMManagementService
Dim Result
'Get instance of 'virtualization' WMI service on the local computer
Set WMIService = GetObject("winmgmts:\\.\root\virtualization")
'Get a VMManagementService object
Set VMManagementService = WMIService.ExecQuery("SELECT * FROM Msvm_VirtualSystemManagementService").ItemIndex(0)
'Get all the MSVM_ComputerSystem object
Set VMList = WMIService.ExecQuery("SELECT * FROM Msvm_ComputerSystem")
For Each VM In VMList
   if VM.Caption = "Virtual Machine" then
       Set VMSystemGlobalSettingData = (VM.Associators_("MSVM_ElementSettingData", "Msvm_VirtualSystemGlobalSettingData")).ItemIndex(0)
       VMSystemGlobalSettingData.ScopeOfResidence = ""
       Result = VMManagementService.ModifyVirtualSystem(VM.Path_.Path, VMSystemGlobalSettingData.GetText_(1))
    end if
Next
Cheers,
Benjamin Armstrong
============================
Windows Virtualization
Senior Lead Program Manager
This posting is provided AS IS with no warranties, and confers no rights. You assume all risk for your use.

Importing objects in default tablespace

Dear all,
We have our UAT and PRODUCTION environment having the same structure (same tablespaces, same amount of users) ..our application mainly runs with only one user called APPSDT. we have the
same user in our UAT also..
user APPSDT have objects created in all the tablespaces of the PROD environment. When we are
refreshing the schema APPSDT with that of the schema in UAT , IMP imports the objects the
objects in all the tablespace (since the tablespace name is the same in UAT as well in PROD)
I've allocated a big file tablespace as the default tablespace to the user APPSDT in UAT.
When am doing the import , all the objects have to be imported into the default tablespace
and not to user anyother tablespace ?
Any idea ?
Kai

KaiS,
If you have allocated quota only one tablespace which is default tablespace of the schema user, then all the objects pertaining to that user will be created in default tablespace. And if you have allocated quota on other tablespace then objects will spread over the other tablespaces (same tablespace as in your production server).
Regards

Export Import with different tablespaces

Does anyone know if there is a way to export from one database (creating a dmp file) and then importing into another database with different tablespaces? I have tried this and get this error:
ORA 959. It complained that the tablespace doesnt exist (which it doesnt). Is there a way I can change the export or import parameters to avoid this and just use the default tablespaces?
I may well be missing the point here so please feel free to tell me I am being a fool.
Thanks
Johan

Example. All these tables are from the same schema with the same tablespace specified in the dmp file. There are many more and 90 % fail but not all.
importing SCHEMA1 objects into SCHEMA2
IMP-00017: following statement failed with ORACLE error 959:
"CREATE TABLE "ACCOUNT_RPRT_NOT_TOBE_PUBLISH" ("O__NUM" CHAR(13) NOT NULL EN"
"ABLE, "O__ST" NUMBER(4, 0) NOT NULL ENABLE, "STEP_COUNTER" NUMBER(7, 0), "S"
"TATUS" NUMBER(1, 0), "RETRY_COUNTER" NUMBER(5, 0), "RESTART_COUNTER" NUMBER"
"(5, 0), "PID" NUMBER(3, 0), "OBJ_LOCK" VARCHAR2(10), "MYFILE" VARCHAR2(200)"
", "LONG_FIELD" CLOB, "LAST_SELECT_B_S" VARCHAR2(250), "LAST_SELECTION" VARC"
"HAR2(250), "L_EXECUTION_CTRL" CHAR(13), "ID" NUMBER(6, 0), "ERROR_COUNTER" "
"NUMBER(7, 0), "CREATION_TIME" NUMBER(5, 0), "CREATION_DATE" NUMBER(6, 0), ""
"COMPLETION_TIME" NUMBER(5, 0), "COMPLETION_DATE" NUMBER(6, 0), "COMMIT_COUN"
"TER" NUMBER(5, 0)) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 STORAGE(I"
"NITIAL 65536 FREELISTS 1 FREELIST GROUPS 1) TABLESPACE "AIA_DATA_T_256K" LO"
"GGING NOCOMPRESS LOB ("LONG_FIELD") STORE AS (TABLESPACE "AIA_DATA_T_256K""
" ENABLE STORAGE IN ROW CHUNK 8192 PCTVERSION 10 NOCACHE STORAGE(INITIAL 65"
"536 FREELISTS 1 FREELIST GROUPS 1))"
IMP-00003: ORACLE error 959 encountered
ORA-00959: tablespace 'AIA_DATA_T_256K' does not exist
. . importing table "ACTUARIAL_RPT_CNTR" 0 rows imported
. . importing table "ACTUARIAL_RPT_CVRG" 0 rows imported
. . importing table "ALIS_CANCEL_BILLING" 2799 rows imported

I have an old Frank Sinatra CD called duets which I have imported but it has separated into several different albums one per track?How can I merge into the one album?s

Can somebody advise how to remerge what has been imported as several different tracks into the original Album format?

If you select the tracks all together in iTunes/ Songs then go to File/Get info you will be asked "Are you sure you want to edit information for multiple items?" Go ahead and you can make them into an album, putting in the artist name, etc.

Import schema to a different tablespace

hi,
I've exported my instance:
EXP SYSTEM/MANAGER@OLDINSTANCE FULL=Y FILE=C:\EXP_FILE.DMP LOG=C:\ERROR_EXP.LOG
after I've created new tablespace and new user:
CREATE TABLESPACE MAX DATAFILE 'c:\MAX01.dbf' SIZE 3800M REUSE DEFAULT STORAGE
(INITIAL 10240 NEXT 10240 MINEXTENTS 1 MAXEXTENTS 256 PCTINCREASE 0) ONLINE;
CREATE USER MAX IDENTIFIED BY MAX DEFAULT TABLESPACE MAX TEMPORARY TABLESPACE TEMP;
finally I've imported tom's objects in MAX:
IMP SYSTEM/MANAGER@NEWINSTANCE FROMUSER=TOM TOUSER=MAX FILE=C:\EXP_FILE.DMP LOG=C:\ERROR_IMP.log
but in some tables I get these errors:
IMP-00017: following statement failed with ORACLE error 1658:
"CREATE TABLE "AREA" ("OFL" VARCHAR2(4), "OBL" VARCHAR2(32), "OSITE" V"
"ARCHAR2(32), "OLS" VARCHAR2(32), "OAREA" NUMBER, "DV_ID" VARCHAR2(32), "DP_"
"ID" VARCHAR2(32), "ODISMESSO" VARCHAR2(2), "OTYPE" VARCHAR2(64), "OCAT" VAR"
"CHAR2(64), "OOCCUP" NUMBER, "SFL" VARCHAR2(32), "SBL" VARCHAR2(32), "SSITE""
" VARCHAR2(32), "PRORATE" VARCHAR2(8), "STYPE" VARCHAR2(64), "SCAT" VARCHAR2"
"(64), "SAREA" NUMBER, "SOCCUP" NUMBER, "AREA_SERV" NUMBER) PCTFREE 10 PCTU"
"SED 40 INITRANS 1 MAXTRANS 255 LOGGING STORAGE(INITIAL 314572800 NEXT 52428"
"800 MINEXTENTS 1 MAXEXTENTS 1000 PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS "
"1 BUFFER_POOL DEFAULT) TABLESPACE "TOM""
IMP-00003: ORACLE error 1658 encountered
ORA-01658: unable to create INITIAL extent for segment in tablespace TOM
In new instance there are 2 tablespaces (TOM, MAX)
I tried 2 solution:
1) I've taken the tablespace TOM offline in the new instance, but when I import fromuser=TOM touser=MAX.............
I get error because not exist tablespace TOM
2)I removed MAX's quota on the TOM tablespace in the new instance.
ALTER USER MAX QUOTA unlimited ON TOM;
but when I import I get alway the same error:
ORA-01658: unable to create INITIAL extent for segment in tablespace TOM
I know That I must encrease tablespace TOM for avoid this error, but I must create 6 new users in 6 different tablespaces and I'd to increase tablespace TOM too much (how many GB?).
how can I import schema to a different tablespace?
Thanks
Raf

I don't understand why you cannot import TOM's scheme
to new instance, because you say that you' ve TOM
tablespace in the database.
Check size of it, may be you need to increase size or
you can TOM tablespace set autoextended.
Also, you can set MAX tablespace is default in new database and set TOM tablespace is readonly.
Then import cannot create object in TOM tablespace
and create this in MAX tablespace.
Best regards, Victor

How to import partitioned tables in different tablespace

Hi everyone,
I try to import the partitioned tables in different tablespace.
Consider the following situation:
I have a dump file which is created by using "Export" utility. Some data are in partitioned tables, some of them are in non-partitioned tables. Also, all tables are located in "MYTBS" tablesapce. I try to import all data from this dump file to another database. I didn't get error messages when importing the data from non-partitioned tables. However, I got error message when importing the data from partitioned tables. The error message is: tablespace 'MYTBS' does not exist.
I just want to how I can solve this problem other than create 'MYTBS' tablespace for my new database.
Thanks in advance.
Angel

Hi,
I got the following error message:
IMP-00017: following statement failed with ORACLE error 959:
"CREATE TABLE "FACILITYCONNECTION",....., "CONNECTIONTYPE" "
"NUMBER(1, 0) NOT NULL ENABLE) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 25"
"5 PARALLEL ( DEGREE DEFAULT INSTANCES 1) NOLOGGING STORAGE( PCTINCREASE 0) "
"TABLESPACE "MYTBS" PARTITION BY RANGE ("CONNECTIONTYPE" ) (PARTITION "
""EXT" VALUES LESS THAN (1) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 S"
"TORAGE(INITIAL 65536) TABLESPACE "MYTBS" NOLOGGING, PARTITION "FAC" VA"
"LUES LESS THAN (2) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 STORAGE(I"
"NITIAL 65536) TABLESPACE "MYTBS" NOLOGGING )"
IMP-00003: ORACLE error 959 encountered
ORA-00959: tablespace 'MYTBS' does not exist
Thanks.
Angel

How can I import schema to a different tablespace in a new database?

Hi,
I want to transport a schema "abc", which is on 'USERS" tablespace in the old database, to a new database using Data Pump. But on the new server, I want it on a different tablespace, say "TEST". How can I do that? I tried the following but it does not work:
1. Create a user "abc" on new database, assign "TEST" as its default tablespace;
2. use impdp to import the dmp file;
I found that on the new server, the imported tables are still on the "USERS" tablespace.
Can anyone tell me how to do it? thanks a lot.

Use the REMAP_TABLESPACE option:
REMAP_TABLESPACE = source_tablespace:target_tablespace
Rick

Moving objects into different tablespaces

Hi Gurus,
Here is my query .
I have 40gb space to have dataset from production database.
Test enviornment will be refreshed with production database.
From testing enviornment development will be refreshed to aviod any connections to production.
As part of data copying to dev env is depending on the conditions given by business.
So my question comes here
Initially I will be dumpring all the data to one tablespace in one tablespace of development environment.
It could take 39 to 40GB.
Now i want to move objects into different tablespaces accoring to storage clause and no of records .
New tablespaces will be created in development enviornment and will be created in same 40GB.
Space is constraint in dev env and cann't be extended.
How can i create tablespaces into the dev env and move objects into them?
I hope you understood my queries ...
In simple
TESTING ENV - - - -- - - - > DEV ENV(Initially one tablespace for all tables/objects) - - -- -- ---- >DEV ENV(Objects in diiferent tablespaces )

You say:
While creating scripts of tables we are removing all tablespace names as we will be having 3 tablespaces at target that is also after loading the data into them.Don't remove the TS clause, but replace the TS so-and-so with TS that-and-that.
Or replace tablespaces a, b and c with x+, and d* and e with y*+.
This can be automated, but you will have to write some logic for that.
Because ... we will be having only 3 tablespaces in DEV. ex NEWYORK tablespace is in production but it won't be created in DEv , istead all the objects into that tablespace will be moved to large table space.
As I said: You will need a code which greps for TS NEWYORK* and replaces it with +<your_big_TS>+.
So once again: Where is the problem?
It's just a question of coding.

IMPORT INTO A DIFFERENT TABLESPACE

Similar Messages

Maybe you are looking for