Tables ... tables

We have an application which uses paradox tables and we are porting it to Oracle. Because of the limitations inherent to paradox, we create different sets of tables in different places.
Ex. table a & b reside in c:\here and table b & c reside in c:\there

     both sets of tables are exactly the same table structures (we could use either

     place to store the same info....
We do this because of the file size limitiation and potencial for table corruption.
Obvioulsy, file size and corruption is less of a problem is Oracle. Our app could keep 6 months of data on line which would mean that the biggest table could have 20,000,000 rows. I'm having a hard time convincing everybody that creating different sets of tables does not buy us anything as far reliability (assuming performance is not an issue). Can somebody give me some feedback to my questions?
Also, if all of your tables reside in the same tablespace, do you have table level corruption or is it at the tablespace level? Received on Wed Dec 16 1998 - 16:11:51 CST