Re: prob with export, transport_tablespace

"mammoth.usenet-access.com" wrote:
>
> I have been trying to use the transport tablespace feature of export to move
> some tablespaces a round an ran across a problem. I'm running 8.1.7 on
> Win2k. I took the tablespaces offline, then attempted to export 8
> tablespaces. Seven of them exported fine but the 8th hung up I tried doing
> it by itself and got the same result as shown below: Any Ideas???????
>
> C:\>exp 'sys/xxxxxx as sysdba' transport_tablespace=y tablespaces=
> ny_m_data_small
>
> Export: Release 8.1.7.0.0 - Production on Tue Feb 19 07:42:42 2002
>
> (c) Copyright 2000 Oracle Corporation. All rights reserved.
>
> Connected to: Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
> With the Partitioning option
> JServer Release 8.1.7.0.0 - Production
> Export done in WE8ISO8859P1 character set and WE8ISO8859P1 NCHAR character
> set
> Note: table data (rows) will not be exported
> About to export transportable tablespace metadata...
> EXP-00008: ORACLE error 29341 encountered
> ORA-29341: The transportable set is not self-contained
> ORA-06512: at "SYS.DBMS_PLUGTS", line 1031
> ORA-06512: at line 1
> EXP-00000: Export terminated unsuccessfully
>
> ______________________________________________________________________________
> Posted Via Binaries.net = SPEED+RETENTION+COMPLETION = http://www.binaries.net

Hello mammoth,
the procedure is fully described in:
http://otn.oracle.com/docs/products/oracle8i/doc_library/817_doc/server.817/a76956/tspaces.htm#5813

Basically, the error message indicates that your TS is not self-contained (has references outside the TS you are trying to export). Check if with the package dbms_tts.transport_set_check, eg:

set serveroutput on size 1000000
begin
dbms_tts.transport_set_check('YOUT_TS_NAME', TRUE); end;
/  

prompt query view transport_set_violations.... prompt Note the view is only populated if your TS is not self-contained! select * from transport_set_violations;

make all the TS listed in the view transport_set_violations read only and include them all in the export command, eg: EXP TRANSPORT_TABLESPACE=y TABLESPACES=(your_ts_name1,second_ts)

        TRIGGERS=y/n CONSTRAINTS=y/n GRANTS=y/n FILE=expdat.dmp

Take a look at the URL above for limitations, object behaviors depending in the datatypes you are exporting.
Hope that helps, additions, corrections or further info is always welcome
Manuela Mueller Received on Tue Feb 19 2002 - 11:28:46 CST