tailieunhanh - G Miscellaneous Topics

Appendix Overview This appendix assists you to: • Use bigfile tablespaces for very large databases (VLDB) • Describe the row IDs for bigfile tablespaces • Use temporary tablespace groups (TTG) for VLDB BFT ROWI TTG | Miscellaneous Topics Appendix Overview This appendix assists you to: Use bigfile tablespaces for very large databases (VLDB) Describe the row IDs for bigfile tablespaces Use temporary tablespace groups (TTG) for VLDB BFT ROWID TTG Bigfile Tablespaces: Overview A bigfile tablespace contains a single file. The maximum file size ranges from 8 TB through 128 TB. Tablespaces are logically equivalent to data files. Database Tablespace SMALLFILE Data file BIGFILE Data file Bigfile Tablespaces: Overview A bigfile tablespace (BFT) is a tablespace containing a single file that has a very large size. The addressing scheme allows up to four billon blocks in a single data file, and the maximum file size can be 8 TB–128 TB depending on the Oracle block size. To distinguish a BFT from the traditional tablespace that can contain multiple, relatively small files, the traditional tablespace is referred to as a “smallfile” tablespace. An Oracle database can contain both bigfile and smallfile . | Miscellaneous Topics Appendix Overview This appendix assists you to: Use bigfile tablespaces for very large databases (VLDB) Describe the row IDs for bigfile tablespaces Use temporary tablespace groups (TTG) for VLDB BFT ROWID TTG Bigfile Tablespaces: Overview A bigfile tablespace contains a single file. The maximum file size ranges from 8 TB through 128 TB. Tablespaces are logically equivalent to data files. Database Tablespace SMALLFILE Data file BIGFILE Data file Bigfile Tablespaces: Overview A bigfile tablespace (BFT) is a tablespace containing a single file that has a very large size. The addressing scheme allows up to four billon blocks in a single data file, and the maximum file size can be 8 TB–128 TB depending on the Oracle block size. To distinguish a BFT from the traditional tablespace that can contain multiple, relatively small files, the traditional tablespace is referred to as a “smallfile” tablespace. An Oracle database can contain both bigfile and smallfile tablespaces. The BFT concept eliminates the need for adding new data files to a tablespace. This simplifies manual or automatic management of the disk space (using Oracle Managed Files (OMF) or Automated Storage Management (ASM)) and provides data file transparency. The graphic in the slide shows the entity-relationship diagram of the Oracle database space management architecture. The one-to-many relationship between tablespaces and data files complicates the architecture and can create difficulties in managing disk space utilization whenever one tablespace is associated with hundreds of data files. The BFT concept makes the notion of tablespaces logically equivalent to data files. All operations traditionally performed on data files can be performed on tablespaces. Benefits of Bigfile Tablespaces Significantly increase the storage capacity Simplify data file management for large databases by making tablespaces the main units of disk space administration BFT 1 8 EB 4 billion blocks One-to-one

TỪ KHÓA LIÊN QUAN
crossorigin="anonymous">
Đã phát hiện trình chặn quảng cáo AdBlock
Trang web này phụ thuộc vào doanh thu từ số lần hiển thị quảng cáo để tồn tại. Vui lòng tắt trình chặn quảng cáo của bạn hoặc tạm dừng tính năng chặn quảng cáo cho trang web này.