Peter promised that there would be more problems with tablespaces
and backup/restore. As usual he's right. But in this case, there
would be a problem even if every tablespace were a subset of a
database.
Suppose a database D includes a table T which is in a Falcon
tablespace called FTS stored in /myDBs/tableSpaces/FTS.fts.
Backup D.
Then drop tablespace FTS and create a second database called
DPrime, which includes a Falcon table called TPrime, stored in
a new tablespace called FTSPrime, in /myDBs/tableSpaces/FTS.fts.
Now restore D.
Falcon cares not a whit about the file names of tablespaces, but
objects strenuously if there is not a one to one match of tablespaces
and files.
...
Solutions?
Cheers,
Ann
