Transportable tablespace /imp problem

Dear all ,
please i need to correct me if i am wrong
transportable tablespace can you done of different version of oracle database
(means can do that task from lower to upper ex:10g.2 to 11g.2) take in your consideration the limitation of this taks.???
1. when i do this task in same platform unix to unix and same edians big to big
there is no way to convert datafile or tablespace
the take is done by take tablespace read only and then exp this tablespace and ftp the datafile and dmp file
to new server and switch tablespace read write thus imp the dmp ???
2. when this taks is done from win to unix from 10g.2 to 11g.2
check the self_contained this in the two and take tablespace read only and convert and exp and ftp the datafile and dmp file
to new server thus convert the datafile and then imp and the last one switch the tablespace in read write???
please i need your opinion obout this ?????
and i need your advice in import
imp USERID=\'sys/iti_ICON_sys as sysdba\' \ tablespaces=USERS transport_tablespace=y FROMUSER=sys@TABSTST as sysdba TOUSER=sys@PRODICON as sysdba file=/icon/appl/oracle/trans.dmp datafiles='/icon/appl/oracle/USERS01.dbf'oraicon@billdb03 $ imp USERID=\'sys/iti_ICON_sys as sysdba\' \ tablespaces=USERS transport_tablespace=y FROMUSER=sys@TABSTST as sysdba TOUSER=sys@PRODICON as sysdba file=/icon/appl/oracle/trans.dmp datafiles='/icon/appl/oracle/USERS01.dbf'
Import: Release 10.2.0.3.0 - Production on Tue Dec 20 12:11:34 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
Export file created by EXPORT:V10.02.01 via conventional path
About to import transportable tablespace(s) metadata...
import done in AL32UTF8 character set and AL16UTF16 NCHAR character set
export client uses US7ASCII character set (possible charset conversion)
IMP-00017: following statement failed with ORACLE error 29342:
"BEGIN sys.dbms_plugts.checkUser('ORAESB'); END;"
IMP-00003: ORACLE error 29342 encountered
ORA-29342: user ORAESB does not exist in the database
ORA-06512: at "SYS.DBMS_PLUGTS", line 1895
ORA-06512: at line 1
IMP-00000: Import terminated unsuccessfully
oraicon@billdb03 $ imp USERID=\'sys/iti_ICON_sys as sysdba\' \ tablespaces=USERS transport_tablespace=y file=trans.dmp datafiles='/icon/appl/oracle/USERS01.dbf'
Import: Release 10.2.0.3.0 - Production on Tue Dec 20 12:28:50 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
Export file created by EXPORT:V10.02.01 via conventional path
About to import transportable tablespace(s) metadata...
import done in AL32UTF8 character set and AL16UTF16 NCHAR character set
export client uses US7ASCII character set (possible charset conversion)
. importing SYS's objects into SYS
. importing SYS's objects into SYS
IMP-00017: following statement failed with ORACLE error 29342:
"BEGIN sys.dbms_plugts.checkUser('ORAESB'); END;"
IMP-00003: ORACLE error 29342 encountered
ORA-29342: user ORAESB does not exist in the database
ORA-06512: at "SYS.DBMS_PLUGTS", line 1895
ORA-06512: at line 1
IMP-00000: Import terminated unsuccessfully
oraicon@billdb03 $
MANY THANKS

1 read documentation. You can use rman to convert the files
2 read documentation. You can use rman to convert the files.
3 the error message is self explanatory
4 the error message is self explanatory
Please do your own research prior to posting.
Please include only 1 question per post.
Sybrand Bakker
Senior Oracle DBA

Similar Messages

Transport tablespace related problem

Hi all,
I have a problem i want to export tablespaces as i have to migrate my db from oracle 9.2 to oracle 10.2 from win to RHEL4.......but i am getting an error ,pls suggest me for the same....
SQL> @G:\oracle\ora92\rdbms\admin\dbmsplts.sql;
Package created.
Package created.
Grant succeeded.
Package created.
Grant succeeded.
drop view sys.transport_set_violations
ERROR at line 1:
ORA-00942: table or view does not exist
PL/SQL procedure successfully completed.
drop table sys.transts_error$
ERROR at line 1:
ORA-00942: table or view does not exist
Package created.
SQL> exec sys.dbms_tts.transport_set_check('SRO',true);
BEGIN sys.dbms_tts.transport_set_check('SRO',true); END;
ERROR at line 1:
ORA-04068: existing state of packages has been discarded
ORA-04063: package body "SYS.DBMS_TTS" has errors
ORA-06508: PL/SQL: could not find program unit being called
ORA-06512: at line 1
SQL> desc dbms_tts
PROCEDURE DOWNGRADE
FUNCTION ISSELFCONTAINED RETURNS BOOLEAN
Argument Name                  Type                    In/Out Default?
TS_LIST                        CLOB                    IN
INCL_CONSTRAINTS               BOOLEAN                 IN
FULL_CHECK                     BOOLEAN                 IN
PROCEDURE KFP_CKCMP
PROCEDURE TRANSPORT_SET_CHECK
Argument Name                  Type                    In/Out Default?
TS_LIST                        CLOB                    IN
INCL_CONSTRAINTS               BOOLEAN                 IN     DEFAULT
FULL_CHECK                     BOOLEAN                 IN     DEFAULT
SQL> exec dbms_tts.transport_set_check('SRO',true);
BEGIN dbms_tts.transport_set_check('SRO',true); END;
ERROR at line 1:
ORA-04068: existing state of packages has been discarded
ORA-04063: package body "SYS.DBMS_TTS" has errors
ORA-06508: PL/SQL: could not find program unit being called
ORA-06512: at line 1

Are you,by any chance, running Oracle 9i installation code in an Oracle 10g database?
If so : why?
As far as I know you can only transport tablespaces to a database of an identical version, so it looks like this is not going to work.
Sybrand Bakker
Senior Oracle DBA

Character set problem with transportable tablespace

Hi,
I'm trying to import a transportable tablespace with data pump into a database with a different character set compared to the source database. I know this is by default not possible. But there's no violating data in the tablespace that could make it a problem when transfering the TS. So I issued 'ALTER SYSTEM SET "_tts_allow_nchar_mismatch"=true;' on the target to force the import. However; I still get the eror:
ORA-29345: can not plug a tablespace into a database using a different character set
How can I fix this?

Hi,
What're the character sets of the source and target database?
A general restriction of transportable tablespace is that the source and target databases must use the same database character set.
Regards
Nat

Expdp problem when executing from pl/sql transportable tablespaces

Hello
i have a very strange problem for which your assistance is really appreciated. i am applying the transportable tablespaces approach and i have a problem when executing expdp from commandline in comparison to the procedure generated to make the exact same thing.
more precisely when running:
expdp etl/etl dumpfile=TBSP090609_DMP.dmp logfile=TBSP090609_DMP.log directory=EXPDP transport_tablespaces=TBSP090609 transport_full_check=y
the dmp file produced is over 200MB.
when runng the below pl/sql code the volume produced is around 50MB. any idea what i am missing?
job_handle :=
dbms_datapump.OPEN (operation => 'EXPORT',
job_mode => 'TRANSPORTABLE',
job_name => 'export_tablespace',
VERSION => 'COMPATIBLE'
dbms_datapump.add_file (handle => job_handle,
filename => dump_file_name,
DIRECTORY => export_dir_name
dbms_datapump.set_parameter (handle => job_handle,
NAME => 'TTS_FULL_CHECK',
VALUE => 1
dbms_datapump.metadata_filter (handle => job_handle,
NAME => 'TABLESPACE_LIST',
VALUE => '('''
|| tablespace_name
|| ''')'
dbms_datapump.start_job (job_handle);

thanx you for your response. the problem was eventually managed to be resolved as follows:
job_handle :=
dbms_datapump.OPEN (operation => 'EXPORT',
job_mode => 'TRANSPORTABLE',
job_name => 'export_tablespace',
VERSION => 'COMPATIBLE'
dbms_datapump.add_file (handle => job_handle,
filename => dump_file_name,
DIRECTORY => export_dir_name
dbms_datapump.set_parameter (handle => job_handle,
NAME => 'TTS_FULL_CHECK',
VALUE => 1
dbms_datapump.metadata_filter (handle => job_handle,
NAME => 'TABLESPACE_EXPR',
VALUE => 'IN('''
|| tablespace_name
|| ''')');
dbms_datapump.start_job (job_handle);

Transportable tablespace or what?

Sorry if I'm posting to a wrong forum, but I have a task to create a procedure that 'archives' some data.
It should do it in a way that user can start 'archiving' process wich should move some table partitions to an archive..
archive should be some kind of export (that should be easy to restore), transportable tablespace or anything similar..
what do you reccomend? DB is 11G R2
my current plan is to use partitioned tables, and to move partitions to a transportable tablespace that will be online-offline if it needs to, but I've never tried to solve a problem on this way...
Does somebody have experience with that?
tnx for any idea/help
edit:
what is with offline tablespace? As I read, it's still used just for backward compatibility
Edited by: 846417 on Apr 6, 2011 5:02 AM

I think this is an appropriate forum if you are using Data Pump or exp/imp to get your task complete.
I'm not sure how your database is set up, but if it was done using partitions and you want to take one or more partitions to a archive area, you can use transportable tablespace in the table mode to just get the information about 1 partition. Ideally, you would want one partition per tablespace. Here is how it would work.
Let's say your table is created like this:
create table foo (a number, b date)
partition by range (a)
(partition jan-2000 values less than 'feb-2000' tablespace jan_2000_tbs,
(partition feb-2000 values less than 'mar-2000' tablespace feb_2000_tbs,
(partition mar-2000 values less than 'apr-2000' tablespace mar_2000_tbs,
(partition apr-2000 values less than 'may-2000' tablespace apr_2000_tbs,
Now, you can export just 1 partition at a time:
expdp user/password table=foo:jan-2000 transportable=always ...
This will generate a dumpfile for the metadata. You would have to save both the dumpfile and any data files associated with tablespace jan_2000_tbs.
Hope this helps.
Dean

Error ORA-39125 and ORA-04063 during export for transportable tablespace

I'm using the Oracle Enterprise Manager (browser is IE) to create a tablespace transport file. Maintenance...Transport Tablespaces uses the wizard to walk me through each step. The job gets created and submitted.
The 'Prepare' and 'Convert Datafile(s)' job steps complete successfully. The Export step fails with the following error. Can anyone shed some light on this for me?
Thank you in advance!
=======================================================
Output Log
Export: Release 10.2.0.2.0 - Production on Sunday, 03 September, 2006 19:31:34
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Username:
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
Starting "SYS"."GENERATETTS000024": SYS/******** AS SYSDBA dumpfile=EXPDAT_GENERATETTS000024.DMP directory=EM_TTS_DIR_OBJECT transport_tablespaces=SIEBEL job_name=GENERATETTS000024 logfile=EXPDAT.LOG
Processing object type TRANSPORTABLE_EXPORT/PLUGTS_BLK
Processing object type TRANSPORTABLE_EXPORT/TABLE
Processing object type TRANSPORTABLE_EXPORT/TABLE_STATISTICS
ORA-39125: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA while calling DBMS_METADATA.FETCH_XML_CLOB [TABLE_STATISTICS]
ORA-04063: view "SYS.KU$_IOTABLE_VIEW" has errors
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
ORA-06512: at "SYS.KUPW$WORKER", line 6241
----- PL/SQL Call Stack -----
object line object
handle number name
2CF48130 14916 package body SYS.KUPW$WORKER
2CF48130 6300 package body SYS.KUPW$WORKER
2CF48130 2340 package body SYS.KUPW$WORKER
2CF48130 6861 package body SYS.KUPW$WORKER
2CF48130 1262 package body SYS.KUPW$WORKER
2CF0850C 2 anonymous block
Job "SYS"."GENERATETTS000024" stopped due to fatal error at 19:31:44

More information:
Using SQL Developer, I checked the view SYS.KU$_IOTABLE_VIEW referred to in the error message, and it does indeed report a problem with that view. The following code is the definition of that view. I have no idea what it's supposed to be doing, because it was part of the default installation. I certainly didn't write it. I did, however, execute the 'Test Syntax' button (on the Edit View screen), and the result was this error message:
=======================================================
The SQL syntax is valid, however the query is invalid or uses functionality that is not supported.
Unknown error(s) parsing SQL: oracle.javatools.parser.plsql.syntax.ParserException: Unexpected token
=======================================================
The SQL for the view looks like this:
REM SYS KU$_IOTABLE_VIEW
CREATE OR REPLACE FORCE VIEW "SYS"."KU$_IOTABLE_VIEW" OF "SYS"."KU$_IOTABLE_T"
WITH OBJECT IDENTIFIER (obj_num) AS
select '2','3',
t.obj#,
value(o),
-- if this is a secondary table, get base obj and ancestor obj
decode(bitand(o.flags, 16), 16,
(select value(oo) from ku$_schemaobj_view oo, secobj$ s
where o.obj_num=s.secobj#
and oo.obj_num=s.obj#),
null),
decode(bitand(o.flags, 16), 16,
(select value(oo) from ku$_schemaobj_view oo, ind$ i, secobj$ s
where o.obj_num=s.secobj#
and i.obj#=s.obj#
and oo.obj_num=i.bo#),
null),
(select value(s) from ku$_storage_view s
where i.file# = s.file_num
and i.block# = s.block_num
and i.ts# = s.ts_num),
ts.name, ts.blocksize,
i.dataobj#, t.bobj#, t.tab#, t.cols,
t.clucols, i.pctfree$, i.initrans, i.maxtrans,
mod(i.pctthres$,256), i.spare2, t.flags,
t.audit$, t.rowcnt, t.blkcnt, t.empcnt, t.avgspc, t.chncnt, t.avgrln,
t.avgspc_flb, t.flbcnt, t.analyzetime, t.samplesize, t.degree,
t.instances, t.intcols, t.kernelcols, t.property, 'N', t.trigflag,
t.spare1, t.spare2, t.spare3, t.spare4, t.spare5, t.spare6,
decode(bitand(t.trigflag, 65536), 65536,
(select e.encalg from sys.enc$ e where e.obj#=t.obj#),
null),
decode(bitand(t.trigflag, 65536), 65536,
(select e.intalg from sys.enc$ e where e.obj#=t.obj#),
null),
(select c.name from col$ c
where c.obj# = t.obj#
and c.col# = i.trunccnt and i.trunccnt != 0
and bitand(c.property,1)=0),
cast( multiset(select * from ku$_column_view c
where c.obj_num = t.obj#
order by c.col_num, c.intcol_num
) as ku$_column_list_t
(select value(nt) from ku$_nt_parent_view nt
where nt.obj_num = t.obj#),
cast( multiset(select * from ku$_constraint0_view con
where con.obj_num = t.obj#
and con.contype not in (7,11)
) as ku$_constraint0_list_t
cast( multiset(select * from ku$_constraint1_view con
where con.obj_num = t.obj#
) as ku$_constraint1_list_t
cast( multiset(select * from ku$_constraint2_view con
where con.obj_num = t.obj#
) as ku$_constraint2_list_t
cast( multiset(select * from ku$_pkref_constraint_view con
where con.obj_num = t.obj#
) as ku$_pkref_constraint_list_t
(select value(ov) from ku$_ov_table_view ov
where ov.bobj_num = t.obj#
and bitand(t.property, 128) = 128), -- IOT has overflow
(select value(etv) from ku$_exttab_view etv
where etv.obj_num = o.obj_num)
from ku$_schemaobj_view o, tab$ t, ind$ i, ts$ ts
where t.obj# = o.obj_num
and t.pctused$ = i.obj# -- For IOTs, pctused has index obj#
and bitand(t.property, 32+64+512) = 64 -- IOT but not overflow
-- or partitioned (32)
and i.ts# = ts.ts#
AND (SYS_CONTEXT('USERENV','CURRENT_USERID') IN (o.owner_num, 0) OR
EXISTS ( SELECT * FROM session_roles
WHERE role='SELECT_CATALOG_ROLE' ));
GRANT SELECT ON "SYS"."KU$_IOTABLE_VIEW" TO PUBLIC;

Oracle Upgrade V9 to V10 - Transportable Tablespaces

Hi,
I am upgrading a database from Oracle 9i v 9.2.0.6.0 to Oracle 10g 10.2.0.4.0. Both servers are running Windows 2003 Server 32Bit.
My plan is to upgrade using Transportable Tablespaces. This is what I have done.
1) exec DBMS_TTS.TRANSPORT_SET_CHECK('XXX,XXX,XXX,XXX,XXX,XXX,XXX,XXX,XXX,XXX,XXX',true); --> This checked out fine.
2) Set the above tablespaces as read only.
3) Copied all the datafiles to the new server (2TB)
4) Did the export: exp 'xxx@xxxx as sysdba' transport_tablespace=y tablespaces=(XXX,XXX,XXX,XXX,XXX ETC...) tts_full_check=y file=c:\EXP.dmp log=c:\exp.log
5) Here comes the problem: When I do the import it imports the tables with the data and forces me o create the Schemas manually. It does not import the users / packages / views / triggers etc...
I need to do an export that that will include everything (Creates Schemas, Packages, Views, Triggers, Tables, data).
I know there is a function FULL=y, this will not work as I do not have an additional 2TB for the export file.
Can someone please explain how to do this?
Kind Regards
Henk

Welcome to the forums !
Is there a reason you are using transportable tablespaces ? Would it not be easier to do an in-place upgrade on the current server, then copy/clone the instance to the new server ?
HTH
Srini

TRANSPORTABLE TABLESPACE IN 8.1

제품 : ORACLE SERVER
작성날짜 : 2004-08-16
Oracle8i에서는 tablespace단위로 그 구성 datafile들을 옮겨서 다른
database에 연결시켜 사용할 수 있는 기능이 제공된다.
SCOPE
8i~10g Standard Edition 에서는 Import transportable tablespaces 기능만이 지원이 됩니다.
유용성
1. 전사적 정보시스템내에서 대량의 data의 흐름이 필요할 경우, - 예를 들어,
OLTP database에서 data warehouse database로의 data이전 또는 data
warehouse에서 data mart로의 data이전 등 - 8.1이전까지는 SQL*Loader의
direct path나 parallel DML등의 방법을 이용하여 그 작업속도를
향상시키려고 시도 하였다. 8.1의 Transportable Tablespace기능을
이용한다면 datafile들을 새로운 system으로 copy하는 정도의 시간으로
작업을 완료할 수 있다.
2. 중앙에서 변경, 관리되고 지방(지사)에서 사용되는 data들을 CD-ROM에 담아서
배포하는 등에 이용가능하다.
예를 들어, 제품의 사양, 가격등에 대한 정보를 담는 tablespace를 중앙에서
변경, 저장하여 배포하고, 이 data를 지방의 database에 연결하여 주문
system등에 이용할 수 있다.
3. Contents 사업자들은 자신이 제공하는 contents들을 Transportable
Tablespace형태로 제공 하여 고객들의 database에 바로 연결하여 사용할 수
있도록 할 수 있다.
특성, 제한사항
1. 특정 tablespace내의 전체 data를 이동시킨다.
2. Media recovery를 지원한다.
3. Source database와 target database는
- 동일한 OS에서 구동되고 있어야 한다.
- Oracle8i(8.1)이상의 version이어야 한다.
- 동일한 block size를 이용해야 한다.
- 동일한 characterset을 이용해야 한다.
작업절차
1. 대상 tablespace를 read only 상태로 변경한다.
file을 copy하는 동안 해당 tablespace에 변경작업이 일어나지 않도록
보장한다.
2. Source database에서 metadata를 export한다.
해당 tablespace와 그 안의 object들에 대한 dictionary정보를 dump file에
받는 과정이다.
3. 대상 tablespace의 datafile들을 target system으로 이동시킨다.
4. Export dump file을 이동시킨다.
5. Metadata를 target database에 import한다.
6. 필요하다면 이후에 해당 tablespace를 read-write mode로 변경한다.
SAMPLE
Source database : dbA
Target database : dbB
이동 대상 tablespace : TRANS_TS(/u01/data/trans_ts01.dbf, /u01/data/trans_ts02.dbf 로 구성)
1. dbA에서 TRANS_TS를 read only로 변경
alter tablespace TRANS_TS read only ;
2. dbA에서 metadata를 export한다.
exp sys/manager file=trans.dmp transport_tablespace=y
tablespaces=trans_ts triggers=n constraints=n
version이 8.1.6이상이라면,
exp system/manager 대신에 exp \'sys/manager as sysdba\'와 같이
주여야 한다.
transport_tablespace(Y or N)는 Y로 설정한다.
tablespaces에는 transport의 대상이 되는 tablespace를 지정한다.
대상 tablespace의 table들에 걸려있는 trigger, constraint들도 대상으로
할 것인지를 지정한다.
3. TRANS_TS의 두개의 datafile들을 dbB가 존재하는 system으로 binary
copy한다.
4. 위의 2번 과정에서 export한 dump file을 dbB가 존재하는 system으로
binary copy한다.
5. dbB에 metadata를 import한다.
imp sys/manager file=trans.dmp transport_tablespace=y
datafiles=/disk1/trans_ts01.dbf,/disk2/trans_ts02.dbf
8.1.6이상이라면 이 부분도 sys/manager대신에 \'sys/manager as dba\'
와 같이 적는다.
transport_tablespace(Y or N)는 Y로 설정한다.
datafile의 name은 dbB system에 copy된 filename을 지칭한다.
6. 필요할 경우 tablespace를 read write mode로 변경한다.
alter tablespace TRANS_TS read write ;
TRANSPORT SET
Transport하고자 하는 tablespace set은 self-contained이어야만 한다.
대상이 되는 tablespace set 내에 partitioned table이 존재한다면 해당
table의 모든 partition들이 이들 tablespace 내에 존재해야 하며, 비슷하게
LOB column의 data들도 table의 data들과 함께 이들 tablespace 내에 존재해야
하는데, 이렇게 서로 관련된 object들이 tablespace set내에 모두 존재하는
것을 self-contained라고 지칭한다.
tablespace set이 self-contained하지 않다면 transport할 수 없다.
Transport tablespace set이 self-contained인지의 여부를 확인하기 위해서
DBMS_TTS.TRANSPORT_SET_CHECK procedure를 이용한다.
예를 들어,
DBMS_TTS.TRANSPORT_SET_CHECK(ts_list=>'A,B,C',incl_constraints=>TRUE)
을 수행하면 A, B, C 세개의 tablespace로 구성된 transport tablespace set이
self-contained인지에 대한 정보를 TRANSPORT_SET_VIOLATIONS view에 기록해
준다.
incl_constraints를 설정하면 referencial(foreign key) constraint에
대해서도 self-contained 여부를 check해준다.

you can do the following:
1. export all objects in your tablespace, by using option tables=(x,y,...)
2. drop your tablespace including contents
3. create new tablespace with a desired name using the same datafiles names (you can physically delete them first or use a REUSE option)
4. create objects you exported in the new tablespace.
5. perform your import
By creating objects first, you guarantee that export will populate tables in the tablespace you need.
This is just a general plan, you have to clarify and confirm all details.

Transportable tablespace

hi all
i am new to oracle
i want to export in oracle 10g. transportable tbs.
when i execute expdp cmd. it give me error
cmd>expdp scott@orcl/tiger directory=data_load dumpfile=emp.dmp transport_tablespace=users.
in documentation i read transport_datafile ?? clearify me what is mean of transport_datafile and we used this clause in expdp cmd then what happend.
thanx in advance.

why dont you use exp and imp instead of expdp and impdpbcoz. i thing according to doc. transport tbs in original exp and imp tools used in different ways.
and oracle 10g. data pump in expdp and impdp transport tbs used in different ways.
bcoz i search in doc and i found differenct command in original and data pump utitites export and import.
before that plz clearify what is mean and what is used to transport tablespace i read doc in doc. transport tbs is used to metadata but i not know much about metadata.
thanx for reply sir

Run transportable tablespace

Hi;
I have a file system database on linux which is 10g.I want to transport this database to new host asm on 11g.
I am unable to use transportable database since the endian formats are different. I want to use transportable tablespace feature with rman.
The database is pretty big. I dont have enough space to do the conversion on the source database.
If I ship the backup of the database to new host, can I do the conversion on new host ?
ie:
run {
allocate channel t1 type 'SBT_TAPE';
transport tablespace "USERS"
Tablespace destination '/ora_backup/tts'
Auxiliary destination '/ora_backup/tts'
Datapump directory data_pump_dir
dump file 'tts_test.dmp'
Import script 'tts_test.imp'
Export log 'exp_tts_test.log'

Ricardo,
I had given you a link in the other thread of yours. Did you see it? If not , please do. You can do the conversion either on the source or you can ship the files on the target host and can convert there as well. Please see the link since it covers it completely.
Aman....

Transportable tablespace error

Oracle version 9.2.0.8
OS - Windows XP
I am doing tablespace transport from one database to another database.
My export went good but while importing I am getting some errors
Not only that but I have to restart instance every time I try import
C:\>exp userid='sys/**** as sysdba' transport_tablespace=y tablespaces=xyz5 file='C:\u03\expor\xyz5.dmp' log='C:\u03\expor\xyz.log'
Export: Release 9.2.0.8.0 - Production on Sat Mar 22 22:50:20 2008
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to: Oracle9i Enterprise Edition Release 9.2.0.8.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.8.0 - Production
Export done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
Note: table data (rows) will not be exported
About to export transportable tablespace metadata...
For tablespace EXAMPLE3 ...
. exporting cluster definitions
. exporting table definitions
. . exporting table
. exporting referential integrity constraints
. exporting triggers
. end transportable tablespace metadata export
Export terminated successfully without warnings.
C:\>imp USERID='sys/** AS SYSDBA' TRANSPORT_TABLESPACE=y DATAFILES='C:\oracle\oradata\spri\xyz5.DBF' TABLESPACES=xyz5 FILE='C:\u03\expor\xyz5.dmp'
Import: Release 9.2.0.8.0 - Production on Sat Mar 22 23:21:58 2008
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to: Oracle9i Enterprise Edition Release 9.2.0.8.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.8.0 - Production
Export file created by EXPORT:V09.02.00 via conventional path
About to import transportable tablespace(s) metadata...
import done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
. importing SYS's objects into SYS
IMP-00017: following statement failed with ORACLE error 3113:
"BEGIN sys.dbms_plugts.beginImport ('9.2.0.8.0',178,'2000',NULL,'NULL',252"
"78,7151,1); END;"
IMP-00003: ORACLE error 3113 encountered
ORA-03113: end-of-file on communication channel
IMP-00000: Import terminated unsuccessfully

How the error of exp and imp will come in alert.log file?
It will come in the log file we specified in parameter. I already posted that information.

Transportable tablespace number of datafiles

We are using transportable tablespace to move tablespaces.
Our database one data tablespace contain 21 datafile and index tablespace contain 18 datafiles.
Tablespace Name:TEST_DATA Datafiles: /oradata/test_data001.dbf,/oradata/test_data002.dbf, .... /oradata/test_data021.dbf
Tablespace Name:INDEX_DATA Datafiles: /oradata/index_data001.dbf,/oradata/index_data002.dbf, .... /oradata/test_data018.dbf
I will take export Successfully bellow using command.
exp "'/ as sysdba'" file=exp_tts.dmp log=exp_tts.log transport_tablespace=y \
tablespaces=TEST_DATA,INDEX_DATA
For Example. (datafile sample i have given)
imp "'/ as sysdba'" file=exp_tts.dmp log=imp_tts.log fromuser=xxx \
touser=xxx transport_tablespace=y datafiles=/oradata/test_data001.dbf,/oradata/test_data002.dbf, .... /oradata/test_data021.dbf, \
/oradata/index_data001.dbf,/oradata/index_data002.dbf, .... /oradata/test_data018.dbf
Over all we are using 39 datafiles in transportable tablespace.
My question is import side i will give all datafiles name. it is very Complicated ( it's possiable to miss any datafile name)
1.Any other way to using import ?
2.It's possiable to given one location in all datafiles. (ex datafile=/oradata)
3.we are using source location and target location same.
Regds
Murali
Edited by: skrmurali on Oct 30, 2009 12:21 PM

hi,
you can give your desired location during import... but you should give the exact location of the datafiles that have been restored..
i.e,
if you copied all datafiles to /uo1/oradata/test_data001.dbf
then in the import you must mention the same,, datafiles='/uo1/oradata/test_data001.dbf'.....
import will done successfully...
orelse if you can do cloning do RMAN clone..
regards,
Deepak

Transportable Tablespace in No archive log

Can I use transportable tablespaces when both source and destination databases are in noarchive log mode?

Fahd Mirza wrote:
Can I use transportable tablespaces when both source and destination databases are in noarchive log mode?Yes... It is exp/imp utility so it has nothing to do with archivelog.
Regards
Rajesh

Transportable tablespace procedure in oracle 9i

Hi all,
We are using oracle 9.2.0.7 version in our production.In that one tablespace is having 160GB but objects size is 60Gb,am unable to get back the remaining space.So we are planning for either creating new tablespace and moving all the objects to that and dropping earlier one or transportable tablespace(not sure whether it is possible)
So please suggest me the better approch. help me out to transport a tablespace procedure
Thanks a lot

exp/imp is the other option.
Or you can use this query find out the object (table/index) on high water mark and just move them.
select a.tablespace_name
       ,a.file_name
       ,(b.maximum+c.blocks-1)*d.db_block_size highwater
from   dba_data_files a
       ,(select file_id,max(block_id) maximum
         from dba_extents
         group by file_id) b
       ,dba_extents c
       ,(select value db_block_size
         from v$parameter
         where name='db_block_size') d
where a.file_id = b.file_id
and   c.file_id = b.file_id
and   c.block_id = b.maximum
order by a.tablespace_name,a.file_name
/

Transport Tablespace Issues

hi.. i'm trying to use transport tablespace across the same platforms rather than performing export/import . i'm following the steps in Note:371556.1to exp/imp ASM files.
i have finished all the steps and successfully transport the tablespace. this process involved only 2 TBS, CC_DATA and CC_INDEXES and the schema is CC. i choose to check the full containment before the export done. but when i count the objects before export and after the import, the count is different. the question is how to make the count of objects is same before and after transport.
before export
SQL> select count(*), object_type from user_objects group by object_type;
COUNT(*) OBJECT_TYPE
33 SEQUENCE
3 DATABASE LINK
55 TABLE
82 INDEX
19 SYNONYM
39 VIEW
6 rows selected.
after import
SQL> select count(*), object_type from user_objects group by object_type;
COUNT(*) OBJECT_TYPE
82 INDEX
55 TABLE
thanks in advance.
-julie-
Edited by: gunit on Nov 17, 2008 7:35 PM

It's a limitation on transportable tablespace (http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/tspaces.htm#i1007233)
You cannot transport the SYSTEM tablespace or objects owned by the user SYS. Some examples of such objects are PL/SQL, Java classes, callouts, views, synonyms, users, privileges, dimensions, directories, and sequences.So you need to transfer the views, sequences,etc., one method is using exp/imp.
[source]$ exp cc/<pwd> file=cc.dmp rows=no
[target]$ imp cc/<pwd> file=cc.dmp ignore=yes HTH
Enrique

Transportable tablespace /imp problem

Similar Messages

Maybe you are looking for