Oracle Database Discussions

Hello,

I'm moving a tablespace from an Oracle 10g instance on Solaris 10 to an Oracle 11g instance created on RedHat Linux. I'm following the procedure described in the White Paper (Platform Migration Using Transportable Tablespaces: [http://www.oracle.com/technology/deploy/availability/pdf/maa_wp_11g_platformmigrationtts.pdf]) and I have a few types of errors during the tablespace import.

Basically, what I'm doing is this:
- shut down all applications that user Oracle on the source DB
- mark the tablespace read-only
- export the tablespace with DataPump;
- move the datafile and the datapump dump on the target machine;
- drop the tablespace on the target machine;
- convert the tablespace with RMAN;
- import the tablespace with DataPump.

During the "Processing object type TRANSPORTABLE_EXPORT/TABLE" step, this error is displayed:

ORA-39083: Object type TABLE failed to create with error:
ORA-01647: tablespace 'TBS' is read only, cannot allocate space in it
Failing sql is:
CREATE TABLE "TBS"."TABLE_NAME" (....)

These errors (215 of them) are probably the cause of the following errors:

ORA-39112: Dependent object type INDEX:"TBS"."I_INDEX_NAME" skipped, base object type TABLE:"TBS"."TABLE_NAME" creation failed (229 errors)

ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"TBS"."I_INDEX_NAME" creation failed (16 errors)

ORA-39112: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"TBS"."TABLE_NAME" creation failed (another 16 errors)

And lastly, two of these:

Processing object type TRANSPORTABLE_EXPORT/DOMAIN_INDEX/INDEX
ORA-39083: Object type INDEX failed to create with error:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-13249: internal error in Spatial index: [mdidxrbd]
ORA-13249: Error in Spatial index: index build failed
ORA-13249: Error in R-tree: [mdrcrtscrt]
ORA-13231: failed to create index table [MDRT_22D654$] during R-tree creation
ORA-13249: Stmt-Execute Failure: CREATE TABLE "TBS".TBLNAME$ (NODE_ID NUMBER, NODE_LEVEL NUMBER, INFO BLOB) LOB (INFO) STORE AS (NOCACHE NOLOGGING)


Now, the creation of tables failing because the tablespace is read-only is fairly obvious, but the procedure states that the source tablespace should be marked read-only on the source DB, exported, the tablespace transferred on the target machine, converted with RMAN, imported, and only then marked as read-write on the target machine.

To me, this seems a bit contradictory - the import is trying to create tables on a read-only tablespace (on the other hand, I can't run DataPump on a read-write tablespace in the first place).

Can anyone enlighten me? Should I just disregard all these errors?

Thank you for your time,

Adrian