Logically Linking database files

>...Reply-To: bediger@teal.csn.org (Bruce Ediger) writes... >Given a requirement for a *large* database, beyond the reaches of >32-bit file sizes, what mechanisms are available from the various >vendors for logically linking different database files? In other words, >assuming I'm required for one reason or another to split a large >database into different files (And not just large databases; >maybe just for administrative reasons), can I perform operations on >that database as a whole, or do I have to treat each file as a separate >database? I'm not using raw partitions; the database files are regular >Unix files. Oracle 6 and 7 databases are composed of one or more tablespaces which are in turn composed of one or more unix files (they can also be composed of raw partitions). Tables can be directed to tablespaces, but not files. That is, if one has a tablespace made up of two files, any data in the tablespace may be stored in one, the other, or both of the files. Databases can only be linked via SQL*Net, but this is not required to handle large DB sizes due to the hierarchical breakdown described above (it may be required for other reasons, of course). Regards, Marv SHL Systemhouse Inc. >Also, would it be possible to construct some sort of a hierarchical >database with DB package "X" that would allow different servers to >access pieces (thos separate files referred to above), but also >let them span the entire database? >Yours truly, >Bruce Ediger