Transportable tablespaces requirment

Hello All,
This is what I am running on.
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
CORE 10.2.0.4.0 Production
TNS for IBM/AIX RISC System/6000: Version 10.2.0.4.0 - Productio
NLSRTL Version 10.2.0.4.0 - Production
We have datawarehouse env. and we are thinking of doing transportable tablespace. From what I understand when you do transportable tablespace the block size have to be the same and NLS_chracater? I am sure there are more requirments that I am not aware of. Please if you have a helpful link please let me know. My question is what are the requirments for transportable tablespace?
Thanks in advance

http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/tspaces.htm#sthref1288
OR
http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/tspaces.htm#i1007169

Similar Messages

Transportable tablespaces for migration and upgrade

Hello All,
I'm trying to find out some theory about transportable tablespace and upgrade in a single step. I've to move a DB from a Windows server to a Linux server. Win is running 10.1 and Linux 10.2 . It's possible to use RMAN to migrate the whole database and then on new node run startup upgrade and catupgrd.sql to upgrade catalog ?
Should work?
Thanks
Raj

The following doc for TDB says :-
"Note: TDB requires the same Oracle Database software version on the source and target systems; hence, a database upgrade cannot be accomplished simultaneous with the platform migration. However, best practices for a database upgrade, as documented in the Oracle Upgrade Companion, also apply to any planned database maintenance activity, including platform migration."
http://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10gR2_PlatformMigrationTDB.pdf
There is also an Oracle Whitepaper called "Database Upgrade Using Transportable Tablespaces: Oracle Database 11g Release 1" but I am still trying to find a copy.

Transportable tablespace feature

iam trying to use transportable tablespace feature on tablespace size 20gb on my prod.
so i thought i would try it on my dev serever first..i created the database on the dev server ..with a standard block size of 8k..
SQL> EXEC DBMS_TTS.TRANSPORT_SET_CHECK(ts_list => 'EXAMPLE', incl_constraints =>
true)
PL/SQL procedure successfully completed.
SQL> SELECT * FROM transport_set_violations;
VIOLATIONS
Index PM.ONLINEMEDIA_PK in tablespace INDEX_DATA enforces primary constriants o
f table PM.ONLINE_MEDIA in tablespace EXAMPLE
this is wat i got..so how do i resolve this..my require ment would be just to add the example TS..i want the constraints to be with it too...
secondly my standard block size is 16k where as in the production box the the actual tablespace size is 8k..
so wat should i do to successfuly make us of TTS feature
ur ideas would be definitely helpful..
Thanks
we r using oracle10gR2

agreed on moving the the index to the example tablespace..
well how about the block size....infact in the real senario iam trying to move the 8k tablespace size into 16k DEV env..
will it affect or not??
if it affects wat should i do in order to resolve??
Thanks

Why transportable tablespace for platform migration of same endian format?

RDBMS Version : 10.2.0.4
We are planning to migrate our DB to a different platform. Both platforms are of BIG endian format. From googling , I came across the following link
http://levipereira.files.wordpress.com/2011/01/oracle_generic_migration_version_1.pdf
In this IBM document, they are migrating from Solaris 5.9 (SPARC) to AIX 6 . Both are of BIG endian format.Since they both are of same endian format can't they use TRANSPORTABLE DATABASE ? Why are they using RMAN COVERT DATAFILE (Transportable tablespace ) ?

In this IBM document, they are migrating from Solaris 5.9 (SPARC) to AIX 6 . Both are of BIG endian format.Since they both are of same endian format can't they use TRANSPORTABLE DATABASE ? Why are they using RMAN COVERT DATAFILE (Transportable tablespace ) ?they are using transportable database - they are not importing data to dictionary, not creating users... - instead of using convert database, they used convert datafile to avoid of converting all datafiles (you need to convert only undo + system tablespace) - there's MOS note: Avoid Datafile Conversion during Transportable Database [ID 732053.1].
Basic steps for convert database:
1. Verify the prerequisites
2. Identify any external files and directories with DBMS_TDB.CHECK_EXTERNAL.
3. Shutdown (consistent) and restart the source database in READ ONLY mode.
4. Use DBMS_TDB.CHECK_DB to make sure the database is ready to be transported.
5. Run the RMAN convert database command.
6. Copy the converted files to the target database. Note that this implies that you will need 2x the storage on the source database for the converted files.
7. Copy the parameter file to the target database.
8. Adjust configuration files as required (parameter, listener.ora, tnsnames, etc).
9. Fire up the new database!
All other details are in:
http://docs.oracle.com/cd/B19306_01/backup.102/b14191/dbxptrn.htm#CHDFHBFI
Lukas

Error while using Transport Tablespace

Hi,
I am running into the below errors when I do the transport tablespace in 11g using the OEM --> Data Movement --> Transport Tablespace.
RMAN-03009: failure of conversion at source command on ORA_DISK_1 channel at 04/22/2008 08:28:32
RMAN-20038: must specify FORMAT for CONVERT command
When I search for the RMAN-03009 in OTN,Metalink,google , I get some unrelated hits with different message and not the "Failure of Conversion..." message.. for this message code.
Please advice if you have had the same issue and resolved the same.
Thanks
Sheik

From 11g Error Messages:
RMAN-20038: must specify FORMAT for CONVERT command
Cause: No FORMAT was specified when using CONVERT command.
Action: Resubmit the command using FORMAT clause.

Steps to create Cross-Platform Transportable Tablespaces

hi
what is the steps to do Cross-Platform Transportable Tablespaces.
i want to perform this in my pc, i have linux and windows in same PC, i want to migrate from linux to windows and vice versa.
so can i know complete steps and commands to perform Cross-Platform Transportable Tablespaces. to get complete knowledge i am doing this so i can implement this in my office when any migrate issues comes. so once i do this i will get confidence so that i can do the same in my office which saves my time.
veeresh s
oracle-dba
[email protected]

Hi, also you can review the Note:413586.1 into metalink site.
Good luck.
Regards.

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

Standby not in sync because test on primary of transportable tablespace etc

This environment is new build environment , have not in use yet.
db version is 11.2.0.3 in linux, both primary/standby are configured in RAC two nodes and storage are in ASM storage.
primary db had tested by migration data using transportable tablespace methods. So the datafiles imported were put in a local filesystem which I have to switch to ASM afterwards.
In such way, the standby db got the impression that datafiles should be in local filesystem and it got invalidated.
Here is the error from standby log:
ORA-01157: cannot identify/lock data file 4 - see DBWR trace file
ORA-01110: data file 4: '/stage/index.341.785186191'
and datafiles names are all in local filesystem in standby: /stage/...../
However in primary datafile names are all in ASM instance:
+DAT/prd/datafile/arindex.320.788067609
How to resolve such situation?
Thanks

My steps for transportable tablespaces after scp the datafiles to linux are import the transportable datafiles into the database. and then using rman to copy it to "+DATA' in asm. and then switch dababase to copy.
Those procedure all worked on primary.
The standby was built before the transportable tablespace when there are only system, users, tools etc basic tablespaces. it worked and in sync with primary. However everytime the primary tested data migration with the transportable tablespaces, it will not work.
so what is the right way to perform this migration? how can I made standby in sync with primary and to read the datafiles in ASM storage?
Is there a way before the RMAN command to transfer the filesystem datafile to ASM, can I copy those local filesystem datafiles to ASM storage ? then do a import transportable datafiles with those on ASM?If you added any datafiles manually then those will be created in standby also as per the settings,
But here you performing TTS, of course DML/DDLs can be transfered to standby by archive logs, but what about actual datafiles? Here in this case files exist in primary & those files not exist in standby
AFAIK, you have to perform couple of steps. Once after your complete migration done in primary do as follows. (Do test it)
1) Complete your migration on primary
-- Check all data file status and location.
2) Now Restore standby controlfile & newly migrated tablespaces in standby Database
-- here you can directly restore to ASM using RMAN, because you are taking backup in primary using RMAN. So RMAN can restore them directly in ASM file system.
3) Make sure you have all the datafiles where you want and take care no one data file is missing. Crosscheck all tablespace information in primary & standby databases.
4) Now start *MRP*
Here is my above plan, But I suggest to test it...
One question, After *successful migration* are you able to SYNC standby with primary earlier ?

Transportable tablespace Windows to Linux different character sets

Hi,
Is it absolutely necessary to have the same character set when doing a cross platform transport tablespace from Windows to Linux? We are trying to do it on Oracle10gR2 from Windows to Linux.
Thank you.

Hi, yes is necessary that your databases have the same chracter set, please review the limitations into the Note:291024.1.
Luck.
Have a good day.
Regards.

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;

Transport Tablespace via RMAN

Hii all
I configured control file autobackup on and take a backup whole database with "backup database;" command and
RMAN> transport tablespace users tablespace destination 'c:\Transport' auxiliary destination 'c:\Auxi';
I am receiving ;
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06024: no backup or copy of the control file found to restore
In begining lines of rman command I saw that "control_files=c:\Auxi/cntrl_tspitr_ST1_dFcB.f" looks like using unix path format in windows? Have you any idea ?
Best Regards
Oracle 10.2.0.3 on Vista Sp2

hi
Yes it is on besides I take backup with "backup database include current controlfile" nothing has changed
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\
NCFST1.ORA'; # default
also I have just tested same command on aix platform it works well I think this is related windows platform ?
Edited by: EB on Sep 25, 2009 4:56 PM

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

Oracle 10gR2 - Any way to speed up Transportable Tablespace Import?

I have a nightly process that uses expdp/impdp with Transportable Tablespace option to copy a full schema from one database to another. This process was initially done with just expdp/impdp, however the creation of the indexes started to slow down the process at which time I switched to using Transportable Tablespace.
In the last 3 months, the number of objects in the schema has not changes however the amount of data has increased 15.73%. At the same time, the Transportable Tablespace impdp has increased 30.77% in time to process.
Is there any way to speed up a Transportable Tablespace impdp in Oracle 10gR2? The docs show that I cannot use parallel with TTS. I have excluded STATISTICS in the export.
Eventually I will be moving away from doing this TTS expdp/impdp, however for now I need to do what I can to contain the amount of time it takes to process.
Environment: Oracle 10.2.0.4 (source and destination) on Sun Solaris SPARC v10. We are not using ASM currently. Tablespace is 6 datafiles for a total of 87.5GB, 791 tables, 1924 indexes, 1773 triggers, and 10 LOBs.
Any help would be greatly appreciated.
Thanks!
-Vorpel

My reading of this thread was that there was a need to be able to do offline setups when the client had lost oracle lite (we get this on PDAs all the time when they go totally dead), so the CD install is something that can be sent out.
Any install (CD or otherwise) will be empty in terms of applications and data, not much you can do about that on a CD, but depending on the type of device and the storage possibilities you have you can secure the database and application files seperately. for example on a PDA using the external SD or flash for the data and file storage will keep them when the orace directory is lost from main storage and therefore all thet is needed after the oracle lite recovery is to recreate the odbc file (and possibly polite if you have special parameters). The setting of the crr flags for 'real' data on the server is a trick to bring the database up to date without a total rebuild.
NOTE if you use SD cards etc. on PDAs/small devices, beware of windows ce/mobile power up differential between main memory and external storage. If you power down in the middle of an update or query, you can get device read/write errors when the device powers up due to processing continuing before the storage media is active

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

TIP 03: Transportable Tablespaces in 10g by Joel Pèrez

Hi OTN Readers!
Everyday I get connection on Internet and one of the first issues that
I do is to open the OTN main page to look for any new article or any
new news about the Oracle Technology. After I open the main page of
OTN Forums and I check what answers I can write to help some people
to work with the Oracle Technology and I decided to begin to write some
threads to help DBAs and Developers to learn the new features of 10g.
I hope you can take advantage of them which will be published here in
this forum. For any comment you can write to me directly to : [email protected]
Please do not replay this thread, if you have any question related to
this I recommend you to open a new post. Thanks!
The tip of this thread is: Transportable Tablespaces
Joel Pérez
http://otn.oracle.com/experts

Step 9: Apply this command to see all the options of the export utility
C:\>
C:\>EXP HELP=Y
Export: Release 10.1.0.2.0 - Production on Fri Apr 23 19:48:30 2004
Copyright (c) 1982, 2004, Oracle. All rights reserved.
You can let Export prompt you for parameters by entering the EXP
command followed by your username/password:
     Example: EXP SCOTT/TIGER
Or, you can control how Export runs by entering the EXP command followed
by various arguments. To specify parameters, you use keywords:
     Format: EXP KEYWORD=value or KEYWORD=(value1,value2,...,valueN)
     Example: EXP SCOTT/TIGER GRANTS=Y TABLES=(EMP,DEPT,MGR)
               or TABLES=(T1:P1,T1:P2), if T1 is partitioned table
USERID must be the first parameter on the command line.
Keyword    Description (Default)      Keyword      Description (Default)
USERID     username/password          FULL         export entire file (N)
BUFFER     size of data buffer        OWNER        list of owner usernames
FILE       output files (EXPDAT.DMP) TABLES       list of table names
COMPRESS   import into one extent (Y) RECORDLENGTH length of IO record
GRANTS     export grants (Y)          INCTYPE      incremental export type
INDEXES    export indexes (Y)         RECORD       track incr. export (Y)
DIRECT     direct path (N)            TRIGGERS     export triggers (Y)
LOG        log file of screen output STATISTICS   analyze objects (ESTIMATE)
ROWS       export data rows (Y)       PARFILE      parameter filename
CONSISTENT cross-table consistency(N) CONSTRAINTS export constraints (Y)
OBJECT_CONSISTENT    transaction set to read only during object export (N)
FEEDBACK             display progress every x rows (0)
FILESIZE             maximum size of each dump file
FLASHBACK_SCN        SCN used to set session snapshot back to
FLASHBACK_TIME       time used to get the SCN closest to the specified time
QUERY                select clause used to export a subset of a table
RESUMABLE            suspend when a space related error is encountered(N)
RESUMABLE_NAME       text string used to identify resumable statement
RESUMABLE_TIMEOUT    wait time for RESUMABLE
TTS_FULL_CHECK       perform full or partial dependency check for TTS
TABLESPACES          list of tablespaces to export
TRANSPORT_TABLESPACE export transportable tablespace metadata (N)
TEMPLATE             template name which invokes iAS mode export
Export terminated successfully without warnings.Joel Pérez
http://otn.oracle.com/experts

Transportable tablespaces requirment

Similar Messages

Maybe you are looking for