We're trying out something unique over here (!!??) This is for a large read only
historical database (2 TB). The physical files will be on tape libraries using
ASM (SAM-FS) which shows as if the files are on the disk. We find that even
though the tablespaces are made read only, during startup of oracle, it tries to
touch all the physical files.
- What is Oracle trying to verify during startup on the physical files of read
only tablespaces? How much of the file should be available to complete this
verification? (In ASM, we can keep part of the file on disk and rest on tape)?
- For partitioned local indexes (8.0.5), does oracle touch all the partitions
to satisfy a query even if the query only refers to few partitions in the
table? Does Oracle optimizer check with its dictionary to find the partitions
before actually reading the index information from all partitions? Any help or
white papers is highly appreciated.
Thanks
Biju
--
Visit Biju's Oracle Page at
http://www.geocities.com/SiliconValley/Peaks/4535/oracle_main.htm
Received on Wed Nov 11 1998 - 10:03:34 CST
