A bit-for-bit copy that is similar to an operating system file copy of a database file like a datafile, archived redo log, or control file. This is generated by the BACKUP AS COPY command. This type of backup is quicker for recovery purposes because it is not stored in a Recovery Manager (RMAN) proprietary format.
See database incarnation.
A recovery that stops before the point of failure that forced recovery or a recovery that does not have available all committed transactions performed before the failure occurred. Incomplete recovery is sometimes called database point-in-time recovery (DBPITR) because this is recovery to a specific point-in-time.
A Recovery Manager (RMAN) backup that only backs up modified blocks. Incremental backups are performed by levels. A level 0 backup backs up all blocks much like a full backup. Level 1 backups back up only the blocks that have changed since the last incremental backup. See also differential incremental backup.
A cluster type that performs much like a b-tree index to ensure quick access to the rows in each cluster table. An index cluster is beneficial if the tables in the cluster are always queried together.
A type of table that is most effective when the access of the table is primarily by the primary key and the primary key columns constitute a large part of the table's columns. An IOT uses a single segment to store the data and the index information.
Database objects that provide referential integrity and performance benefits to tables. These non-critical database objects can be rebuilt based on the table's existence.
A program defined within the confines of a scheduler job object. An inline program is not stored as an independent program object and therefore cannot be referenced by any other jobs.
A schedule defined within the confines of a job object. An inline schedule is not stored as an independent program object and therefore cannot be referenced by any other jobs.
A local connection type that connects directly to the database not using networking connectivity.
See index-organized table.
A special type of table required when you create bitmap indexes on an IOT.
A segment used when the IOT's row data exceeds the threshold of available space in a block; the row's data is dynamically and automatically moved to the overflow area. When you create an IOT, you specify a tablespace to hold the IOT overflow segment.
See Inter Process Control.