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

Similar Messages

Export / Import Mapping into Different Project in same repository

Hi,
Any one tell me, its this possible?
We have one repository ( OWB 10 R2 ) and two projects named dev_project and test_project.
We want to copy or (export /import) the mappings from dev_project to test_project, how to do this? It seems export and import can be done if the servers are different (also it is possible to recover from the back up to the same server and same project.)
Thanks in advance
-NB

I don't use 10gr2, but with 9.2 it is possible to do this, but you need to modify the MDL file before importing it.
** Before doing this, I'd recommend you export everything from your design repository to be safe **
Export the object(s) from DEV_PROJECT to an MDL file. Then open the MDL file in your favorite text editor and rename the project from DEV_PROJECT to TEST_PROJECT. Then import the MDL file back into the repository matching by name (NOT UOID).
I'd recommend you not do this, however. Why do you need a seperate project for test and dev? Why not create another runtime repository connection in your project so that you can deploy to both the development and test environment from the same project?

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.

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

How to export/import data with different nls_lang???

hello
now i try to run my forms by APPLICATION SERVER to view the forms as web forms i success but data appear unreadable that it is arabic and i use the nls WE8ISO8859P1 so i change the nls to arabic like AR8MSWIN1256 but i faild so i create new database with charset UTF8 and nls_lang is AR8MSWIN1256 and try to insert new data when i do query about data ......the new data appear readable but the old unreadable so what can i do???
i think that if i do export data and import it with new (charset and nls_lang) it will be success....but how can i do it??
thank u
regards

Hi did you already exported data from SQL SERVER? if not using SQL*LOADER you cannot export data. SQL*LOADER is only mean for importing data from flat files(usually text files) into ORACLE tables.
for importing data into oracle tables using sql*loader use below steps
1) create a sql*loader control file.
it looks like as follows
LOAD DATA
INFILE 'sample.dat'
BADFILE 'sample.bad'
DISCARDFILE 'sample.dsc'
APPEND
INTO TABLE emp
TRAILING NULLCOLS
or for sample script of control file search google.
2) at command prompt issue following
$ sqlldr test/test
enter control file=<give control file name which you create earlier>
debug any errors (if occured)

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.

Export-import in 9.7

Hello DB6 experts!
I've made an export-import in a 9.7 database.
The problem is that after this clean process, I can't use the statement:
db2 alter tablespace tbs_name reduce MAX
it gives me an error:
SQL1763N Invalid ALTER TABLESPACE statement for table space
It's an error expected if the tablespace was created in a db version previous that 9.7.
Although, sin I have made an export-import, I think that tablespace was created in 9.7 version.
Do you know how can I get rid of this error?
regards,
Filipe Vasconcelos

I was able to check the log sapinst_dev.log and there is the following statement:
function createTablespaceCreateStatement <done>, return <create tablespace PR8#BTABD
in nodegroup SAPNODEGRP_PR8 pagesize 16k extentsize 2 prefetchsize automatic
no file system caching
dropped table recovery off;
So these tablespaces were created in 9.7 during the import.
thanks.
regards,
Filipe

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

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

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 !

Export / import tablespace with all objects (datas, users, roles)

Hi, i have a problem or question to the topic export / import tablespace.
On the one hand, i have a database 10g (A) and on the other hand, a database 11g (B).
On A there is a tablespace called PRO.
Furthermore 3 Users:
PRO_Main - contains the datas - Tablespace PRO
PRO_Users1 with a role PRO_UROLE - Tablespace PRO
PRO_Users2 with a role PRO_UROLE - Tablespace PRO
Now, i want to transfer the whole tablespace PRO (included users PRO_MAIN, PRO_USER1, PRO_User2 and the role PRO_UROLE) from A to B.
On B, I 've created the user PRO_Main and the tablespace PRO.
On A , i execute following statement:
expdp PRO_Main/XXX TABLESPACES=PRO DIRECTORY=backup_datapump DUMPFILE=TSpro.dmp LOGFILE=TSpro.log
On B:
impdp PRO_Main/XXX TABLESPACES=PRO DIRECTORY=backup_datapump DUMPFILE=TSpro.dmp LOGFILE=TSpro.log
Result:
The User PRO_Main was imported with all the datas.
But i 'm missing PRO_USER1, PRO_User2 and the role PRO_UROLE...
I assume, i 've used wrong parameters in my expd and / or impdp.
It would be nice, if anybody can give me a hint.
Thanks in advance.
Best Regards,
Frank

When you do a TABLESPACE mode export by specifying just the tablespaces, then all that gets exported are the tables and their dependent objects. The users, roles, and the tablespace definitions themselves don't get exported.
When you do a SCHEMA mode export by specifying the schemas, you will get the schema definitions (if the schema running the export is privied) and all of the objects that the schema owns. The schema does not own roles or tablespace definitions.
In your case, you want to move
1. schemas - which you already created 1 on your target database
2. roles
3. everything in the tablespaces owned by multiple schemas.
There is no 1 export/import command that will do this. This is how i would do this:
1 - move the schema definitions
a. you can either create these manually or
b1. expdp schemas=<your list of schemas> include=user
b2 impdp the results from b1.
2. move the roles
expdp full=y include=role ...
remember, this will include all roles. If you want to limit what gets exported, then use:
include=role:"in ('ROLE1', 'ROLE2', ETC.)
impdo the roles just exported
3. move the user information
a. If you want to move all of the schema's objects like functions, packages, etc, then you need to use a schema mode
export
expdp user/password schemas=a,b,c ...
b. If you want to move only the objects in those tablespaces, then use the tablespace export
expdp user/password tablespaces=tbs1, tbs2, ...
c. import the dumpfile generated in step 3
impdp user/password ...
Hope this helps.
Dean

Portal Export Import with DB on different OS

Hi All,
I have a quick question about exporting the OracleAS Portal Metadata Repository database. Our source DB is on a different OS to our target DB.
We are going to apply the 10.1.2.3 patch and associated portal export/import patches to both nodes (from note 263995.1).
Our understanding was that we would use the method described in Chapter 10 of the Portal 10.1.4 Admin Guide (http://download.oracle.com/docs/cd/B14099_18/portal.1014/b19305/cg_imex.htm).
However, according to metalink note#276620.1, because our source and target OS are different, we should use the database export/import methodology that is described in Chapter 11 of the Application Server 10.1.2 Admin Guide (http://download.oracle.com/docs/cd/B14099_18/core.1012/b13995/prodtest.htm).
Could anyone tell me which way is better, we would prefer to use the database export/import method, has anyone tried this and what are their experiences.
Regards,
Tim.

kirwantd wrote:
We are going to apply the 10.1.2.3 patch and associated portal export/import patches to both nodes (from note 263995.1).
Our understanding was that we would use the method described in Chapter 10 of the Portal 10.1.4 Admin Guide (http://download.oracle.com/docs/cd/B14099_18/portal.1014/b19305/cg_imex.htm).
However, according to metalink note #276620.1, because our source and target OS are different, we should use the database export/import methodology that is described in Chapter 11 of the Application Server 10.1.2 Admin Guide (http://download.oracle.com/docs/cd/B14099_18/core.1012/b13995/prodtest.htm).
Could anyone tell me which way is better, we would prefer to use the database export/import method, has anyone tried this and what are their experiences.
Regards,
Tim.As far as your referred Metalink note is concerned, it gives you three options to move your repository with if you are working with 10.1.4 Portal.
It's a difference of can, should and must.
- It only shows ability to use three options ( can );
- on the whole, it does not give preferences for any method ( should );
- nor does it put a requirement for any single option ( must ).
( the only requirement/prohibition is for the option 2 which is not supported ).
we have used the first three methods given on the note (yes, we also tried 2; this note came later). 1 is what we use regularly for transports between environments; and 3 we use for environment staging (as given in chap 11 of pt. 3). both can be messy with a large repository (we do so for about ~400 GB) repository. but following that supportability guide (Metalink Note 333867.1), method 1 works too.
hope that helps!
AMN

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

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.

Export - import to a different tablespace ??

Similar Messages

Maybe you are looking for