Tagged: 11g

Oracle Database

HASH-PARTITIONED TABLES

The PARTITION BY HASH clause of the CREATE TABLE statement identifies that the table is to be hash- partitioned. The PARTITIONS clause can then be used to specify the number of partitions to create, and optionally, the tablespaces to store them in. Alternatively, you can use PARTITION clauses to name the individual partitions and their tablespaces. The only attribute you can specify for hash partitions is TABLESPACE. All of the hash partitions of a table must share the same segment attributes (except TABLESPACE), which are inherited from the table level. Using Reference Partitioning: Hash partitioning is useful when there is...

Oracle Database

DB_ULTRA_SAFE parameter

DB_ULTRA_SAFE is a new parameter introduced in 11g. It provides an integrated mechanism to offer protection from various possible data corruptions. and provides critical high availability benefits for Oracle Database. Setting DB_ULTRA_SAFE initialization parameter will configure the appropriate data protection block checking level in the database. It will control DB_BLOCK_CHECKING, DB_BLOCK_CHECKSUM, and DB_LOST_WRITE_PROTECT. DB_BLOCK_CHECKING controls whether or not Oracle performs block checking for database blocks. DB_BLOCK_CHECKSUM determines whether DBWn and the direct loader will calculate a checksum and store it in the cache header of every data block when writing it to disk. DB_LOST_WRITE_PROTECT enables or disables lost write detection....