transportable tablespace with IOT [message #331533] |
Thu, 03 July 2008 18:01 |
cromagnon
Messages: 3 Registered: June 2008
|
Junior Member |
|
|
Can you do RMAN transportable tablespaces with IOT tables with constraints?
Below I create a simple table with FK, then an IOT table with FK and the subsequent ts_pitr_check fails. Is there any way to do this? Disabling constraints? How would you do that with an RMAN generated "recover tablespace"?
#
# create test table, not IOT
#
chris.BKUP_TEST> create table test (id number,constraint pkid primary key (id)) tablespace bkup_test;
Table created.
chris.BKUP_TEST> create table test2 (id number,constraint t2pk primary key (id),constraint fk2 foreign key (id) references test(id)) tablespace bkup_test;
Table created.
#
# Check that transportable okay
#
chris.SYS> select obj1_name,obj2_name,ts1_name,ts2_name,obj1_type,obj2_type,reason from sys.ts_pitr_check where ts1_name='BKUP_TEST' or ts2_name='BKUP_TEST';
no rows selected
#
# Now make table 2 IOT, and it fails
#
chris.BKUP_TEST> drop table test2;
Table dropped.
chris.BKUP_TEST> create table test2 (id number,constraint t2pk primary key (id),constraint fk2 foreign key (id) references test(id)) organization index tablespace bkup_test;
Table created.
chris.SYS> select obj1_name,obj2_name,ts1_name,ts2_name,obj1_type,obj2_type,reason from sys.ts_pitr_check where ts1_name='BKUP_TEST' or ts2_name='BKUP_TEST';
OBJ1_NAME OBJ2_NAME TS1_NAME TS2_NAME OBJ1_TYPE OBJ2_TYPE REASON
---------- ---------- ---------- ---------- ---------------- --------------- ---------------------------------------------------------------------------------
TEST TEST2 BKUP_TEST SYSTEM TABLE TABLE constraint between tables not contained in recovery set
TEST TEST2 BKUP_TEST SYSTEM TABLE TABLE constraint between tables not contained in recovery set
|
|
|
|
|