RE: Transportable tablespace with missing datafile

Welll if you're really sure you're not going to use any blocks out of that file, you could patch the headers to make it look as if it is okay.

Then Oracle would swallow it and of course you might well have total crud relationally. But if you then carefully unload the good stuff -- I guess I'd verify no extents of a table being kept had anything in the file in question. From a standpoint of ever using that tablespace in production again I'd say you're toast, but if you unload or export the data and make a new tablespace to hold it you should be okay.

Good luck. It is totally on you to get it right.

mwf

-----Original Message-----

From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org]On Behalf Of scott.hutchinson_at_interact-analysis.com
Sent: Tuesday, March 01, 2005 1:15 PM
To: oracle-l_at_freelists.org
Subject: Transportable tablespace with missing datafile

All,

Does anyone know any tricks for forcing a transportable tablespace to "import"
when a datafile is missing? I don't mind loosing the data within this datafile, but there are many other valuable tables in other datafiles within this tablespace.

Due to an operational error, 1 file (out of 91) from a 2tb tablespace has been
deleted after the metadata was exported. We have a cold backup of the datafiles from this tablespace only (not full DB) but the tablespace was NOT readonly at the point of the backup, and the database was restarted for the metadata export. This means we can not simply restore the missing file.

The error we get on import is ORA-19722, and the oracle version is 9.2.0.5.

Thanks,
Scott.

::This message sent using the free Web Mail service from http://TheName.co.uk
--

http://www.freelists.org/webpage/oracle-l

--

http://www.freelists.org/webpage/oracle-l Received on Tue Mar 01 2005 - 13:51:39 CST