| Oracle® Database Concepts 11g Release 1 (11.1) Part Number B28318-01 |
|
|
View PDF |
| Oracle® Database Concepts 11g Release 1 (11.1) Part Number B28318-01 |
|
|
View PDF |
ADRCI
A command-line tool that is part of the fault diagnosability infrastructure introduced in Oracle Database 11g.
AFTER trigger
When defining a trigger, you can specify the trigger timing—whether the trigger action is to be executed before or after the triggering statement.
AFTER triggers execute the trigger action after the triggering statement is run.
BEFORE and AFTER apply to both statement and row triggers.
See also: trigger
ARCHIVELOG mode
The mode of the database in which Oracle Database copies filled online redo logs to disk. Specify the mode at database creation or by using the ALTER DATABASE statement. You can enable automatic archiving either dynamically using the ALTER SYSTEM statement or by setting the initialization parameter LOG_ARCHIVE_START to TRUE.
Running the database in ARCHIVELOG mode has several advantages over NOARCHIVELOG mode. You can:
Back up the database while it is open and being accessed by users.
Recover the database to any desired point in time.
To protect the ARCHIVELOG mode database in case of failure, back up the archived logs.
Automatic Database Diagnostic Monitor (ADDM)
This lets Oracle Database diagnose its own performance and determine how identified problems could be resolved. It runs automatically after each AWR statistics capture, making the performance diagnostic data readily available.
Automatic Diagnostic Repository
The Automatic Diagnostic Repository (ADR) is a system-wide tracing and logging central repository. The repository is a file-based hierarchical datastore for depositing diagnostic information, including network tracing and logging information.
Automatic Storage Management (ASM)
A vertical integration of both the file system and the volume manager built specifically for Oracle Database files. It extends the concept of stripe and mirror everything to optimize performance, while removing the need for manual I/O tuning.
Automatic Storage Management disk
Storage is added and removed from Automatic Storage Management disk groups in units of Automatic Storage Management disks.
Automatic Storage Management file
Oracle Database file stored in an Automatic Storage Management disk group. When a file is created, certain file attributes are permanently set. Among these are its redundancy level (MIRROR, HIGH, or UNPROTECTED) and its striping policy. Automatic Storage Management files are not visible from the operating system or its utilities, but they are visible to database instances, RMAN, and other Oracle-supplied tools such as ASMCMD.
Automatic Storage Management instance
An Oracle database instance that mounts Automatic Storage Management disk groups and performs management functions necessary to make Automatic Storage Management files available to database instances. Automatic Storage Management instances do not mount databases.
See also: instance
Automatic Storage Management template
Collections of attributes used by Automatic Storage Management during file creation. Templates simplify file creation by mapping complex file attribute specifications into a single name. A default template exists for each Oracle Database file type. Users can modify the attributes of the default templates or create new templates.
automatic undo management mode
A mode of the database in which it automatically manages undo space in a dedicated undo tablespace. In this mode, the database also automatically tunes the undo retention period. This is the default mode for new database installations for Oracle Database 11g and later.
See also: manual undo management mode
Automatic Workload Repository (AWR)
A built-in repository in every Oracle Database. At regular intervals, the Oracle Database makes a snapshot of all its vital statistics and workload information and stores them here.
background process
Background processes consolidate functions that would otherwise be handled by multiple Oracle programs running for each user process. The background processes asynchronously perform I/O and monitor other Oracle processes to provide increased parallelism for better performance and reliability.
Oracle Database creates a set of background processes for each instance.
See also: instance, process, Oracle process, user process
BEFORE trigger
When defining a trigger, you can specify the trigger timing—whether the trigger action is to be executed before or after the triggering statement.
BEFORE triggers execute the trigger action before the triggering statement is run.
BEFORE and AFTER apply to both statement and row triggers.
See also: trigger
buffer cache
The portion of the SGA that holds copies of Oracle Database data blocks. All user processes concurrently connected to the instance share access to the buffer cache.
The buffers in the cache are organized in two lists: the dirty list and the least recently used (LRU) list. The dirty list holds dirty buffers, which contain data that has been modified but has not yet been written to disk. The least recently used (LRU) list holds free buffers (unmodified and available), pinned buffers (currently being accessed), and dirty buffers that have not yet been moved to the dirty list.
See also: system global area (SGA)
cache recovery
The part of instance recovery where Oracle Database applies all committed and uncommitted changes in the redo log files to the affected data blocks. Also known as the rolling forward phase of instance recovery.
CHECK constraint
A CHECK integrity constraint on a column or set of columns requires that a specified condition be true or unknown for every row of the table. If a DML statement results in the condition of the CHECK constraint evaluating to false, then the statement is rolled back.
checkpoint
A data structure that defines an SCN in the redo thread of a database. Checkpoints are recorded in the control file and each datafile header, and are a crucial element of recovery.
client
In client/server architecture, the front-end database application, which interacts with a user through the keyboard, display, and pointing device such as a mouse. The client portion has no data access responsibilities. It concentrates on requesting, processing, and presenting data managed by the server portion.
See also: client/server architecture, server
client/server architecture
Software architecture based on a separation of processing between two CPUs, one acting as the client in the transaction, requesting and receiving services, and the other as the server that provides services in a transaction.
cluster
Optional structure for storing table data. Clusters are groups of one or more tables physically stored together because they share common columns and are often used together. Because related rows are physically stored together, disk access time improves.
column
Vertical space in a database table that represents a particular domain of data. A column has a column name and a specific datatype. For example, in a table of employee information, all of the employees' dates of hire would constitute one column.
commit
Make permanent changes to data (inserts, updates, deletes) in the database. Before changes are committed, both the old and new data exist so that changes can be stored or the data can be restored to its prior state.
See also: rolling back
concurrency
Simultaneous access of the same data by many users. A multiuser database management system must provide adequate concurrency controls, so that data cannot be updated or changed improperly, compromising data integrity.
See also: data consistency
connection
Communication pathway between a user process and an Oracle database instance.
See also: session, user process
consistent backup
A whole database backup that you can open with the RESETLOGS option without performing media recovery. In other words, you do not need to apply redo to datafiles in this backup for it to be consistent. All datafiles in a consistent backup must:
Have the same checkpoint system change number (SCN) in their headers, unless they are datafiles in tablespaces that are read only or offline normal (in which case they will have a clean SCN that is earlier than the checkpoint SCN)
Contain no changes past the checkpoint SCN, that is, are not fuzzy
Match the datafile checkpoint information stored in the control file
You can only take consistent backups after you have made a clean shutdown of the database. The database must not be opened until the backup has completed.
See also: inconsistent backup
control file
A file that records the physical structure of a database and contains the database name, the names and locations of associated databases and redo log files, the time stamp of the database creation, the current log sequence number, and checkpoint information.
See also: physical structures, redo log
Data Recovery Advisor
An Oracle Database infrastructure that automatically diagnoses persistent data failures, presents repair options to the user, and executes repairs at the user's request. The purpose of Data Recovery Advisor is to reduce the mean time to recover (MTTR) and improve manageability and reliability of Oracle Database by providing a centralized tool for automated data repair.
database
Collection of data that is treated as a unit. The purpose of a database is to store and retrieve related information. Each Oracle database instance accesses only one database.
database buffer
One of several types of memory structures that stores information within the system global area. Database buffers store the most recently used blocks of data.
See also: system global area (SGA)
database buffer cache
Memory structure in the system global area that stores the most recently used blocks of data.
See also: system global area (SGA)
database link
A named schema object that describes a path from one database to another. Database links are implicitly used when a reference is made to a global object name in a distributed database.
database writer process (DBWn)
An Oracle background process that writes the contents of buffers to datafiles. The DBWn processes are responsible for writing modified (dirty) buffers in the database buffer cache to disk.
See also: buffer cache
datafile
A physical file on disk that was created by Oracle Database and contains data structures such as tables and indexes. A datafile can belong to only one database, and is located either in an operating system file system or in an Automatic Storage Management disk group.
See also: index, physical structures
datafile copy
A copy of a datafile on disk produced by either:
The Recovery Manager COPY command
An operating system utility
data block
Smallest logical unit of data storage in Oracle Database. Also called logical blocks, Oracle blocks, or pages. One data block corresponds to a specific number of bytes of physical database space on disk.
data consistency
In a multiuser environment, where many users can access data at the same time (concurrency), data consistency means that each user sees a consistent view of the data, including visible changes made by the user's own transactions and transactions of other users.
See also: concurrency
data dictionary
The central set of tables and views that are used as a read-only reference about a particular database. A data dictionary stores such information as:
The logical and physical structure of the database
Valid users of the database
Information about integrity constraints
How much space is allocated for a schema object and how much of it is in use
A data dictionary is created when a database is created and is automatically updated when the structure of the database is updated.
data integrity
Business rules that dictate the standards for acceptable data. These rules are applied to a database by using integrity constraints and triggers to prevent the entry of invalid information into tables.
See also: integrity constraint, trigger
data segment
Each nonclustered table has a data segment. All of the table's data is stored in the extents of its data segment. For a partitioned table, each partition has a data segment.
Each cluster has a data segment. The data of every table in the cluster is stored in the cluster's data segment.
dedicated server
A database server configuration in which a server process handles requests for a single user process.
See also: shared server
disk group
One or more Automatic Storage Management disks managed as a logical unit. Automatic Storage Management disks can be added or dropped from a disk group while preserving the contents of the files in the group, and with only a minimal amount of automatically initiated I/O required to redistribute the data evenly. All I/O to a disk group is automatically spread across all the disks in the group.
dispatcher processes (Dnnn)
Optional background processes, present only when a shared server configuration is used. At least one dispatcher process is created for every communication protocol in use (D000, . . ., Dnnn). Each dispatcher process is responsible for routing requests from connected user processes to available shared server processes and returning the responses back to the appropriate user processes.
See also: shared server
distributed processing
Software architecture that uses more than one computer to divide the processing for a set of related jobs. Distributed processing reduces the processing load on a single computer.
DDL
Data definition language. Includes statements like CREATE/ALTER TABLE/INDEX, which define or change data structure.
DML
Data manipulation language. Includes statements like INSERT, UPDATE, and DELETE, which change data in tables.
extent
Second level of logical database storage. An extent is a specific number of contiguous data blocks allocated for storing a specific type of information.
See also: data block, segment
failure group
A subset of disks within an Automatic Storage Management (ASM) disk group that share a common resource whose failure must be tolerated. Failure groups are used to determine which ASM disks to use for storing redundant copies of data. For example, if, in a particular disk group, disks 1 through 4 are on disk controller A and disks 5 through 8 are on disk controller B, disks 1 through 4 can be assigned to failure group A, and disks 4 through 8 can be assigned to failure group B. For file extents on disks in failure group A, ASM always stores redundant copies of the extents on disks in failure group B. This way, if disk controller A fails, there is always at least one copy of every file extent available. It is up to the storage administrator to define failure groups based on current storage hardware configuration. If no specific failure group assignments are made, each disk in a disk group is automatically placed in its own failure group.
flash recovery area
An optional disk location that you can use to store recovery-related files such as control file and online redo log copies, archived logs, flashback logs, and RMAN backups. Oracle Database manages the files in the flash recovery area automatically. You can specify the disk quota, which is the maximum size of the flash recovery area.
foreign key
Integrity constraint that requires each value in a column or set of columns to match a value in a related table's UNIQUE or PRIMARY KEY.
FOREIGN KEY integrity constraints also define referential integrity actions that dictate what Oracle Database should do with dependent data if the data it references is altered.
See also: integrity constraint, primary key
inconsistent backup
A backup in which some of the files in the backup contain changes that were made after the files were checkpointed. This type of backup needs recovery before it can be made consistent. Inconsistent backups are usually created by taking online database backups; that is, the database is open while the files are being backed up. You can also make an inconsistent backup by backing up datafiles while a database is closed, either:
Immediately after an Oracle database instance failed (or all instances in an Oracle Real Application Clusters configuration)
After shutting down the database using SHUTDOWN ABORT
Note that inconsistent backups are only useful if the database is in ARCHIVELOG mode.
See also: consistent backup, online backup, system change number (SCN), whole database backup
index
Optional structure associated with tables and clusters. You can create indexes on one or more columns of a table to speed access to data on that table.
See also: cluster
indextype
An object that registers a new indexing scheme by specifying the set of supported operators and routines that manage a domain index.
index segment
Each index has an index segment that stores all of its data. For a partitioned index, each partition has an index segment.
initialization parameter file
A text file that contains initialization parameter settings. In contrast to the server parameter file, this parameter file is not binary and does not need to be located on the database host. The text-based initialization parameter file can be read by the database server, but it is not written to by the server. You can use a text editor to alter the file.
instance
A system global area (SGA) and the Oracle Database background processes constitute an Oracle database instance. Every time a database is started, a system global area is allocated and Oracle Database background processes are started. The SGA is deallocated when the instance shuts down.
See also: background process, system global area (SGA), Automatic Storage Management instance
integrity constraint
Declarative method of defining a rule for a column of a table. Integrity constraints enforce the business rules associated with a database and prevent the entry of invalid information into tables.
key
Column or set of columns included in the definition of certain types of integrity constraints. Keys describe the relationships between the different tables and columns of a relational database.
See also: integrity constraint, foreign key, primary key
large pool
Optional area in the system global area that provides large memory allocations for Oracle Database backup and restore operations, I/O server processes, and session memory for the shared server and Oracle XA.
See also: system global area (SGA), process, shared server, Oracle XA
logical backups
Backups in which an Oracle export utility uses SQL to read database data and export it into a binary file at the operating system level. You can then import the data back into a database using Oracle utilities. Backups taken with Oracle export utilities differ in the following ways from RMAN backups:
Database logical objects are exported independently of the files that contain those objects.
Logical backups can be imported into a different database, even on a different platform. RMAN backups are not portable between databases or platforms.
See also: physical backups
logical structures
Logical structures of Oracle Database include tablespaces, schema objects, data blocks, extents, and segments. Because the physical and logical structures are separate, the physical storage of data can be managed without affecting the access to logical storage structures.
See also: physical structures
LogMiner
A utility that lets administrators use SQL to read, analyze, and interpret log files. It can view any redo log file, online or archived. The Oracle Enterprise Manager application Oracle LogMiner Viewer adds a GUI-based interface.
log writer process (LGWR)
The log writer process (LGWR) is responsible for redo log buffer management—writing the redo log buffer to a redo log file on disk. LGWR writes all redo entries that have been copied into the buffer since the last time it wrote.
See also: redo log
manual undo management mode
A mode of the database in which undo blocks are stored in user-managed rollback segments. In automatic undo management mode, undo blocks are stored in a system-managed, dedicated undo tablespaces.
See also: automatic undo management mode
materialized view
A materialized view provides access to table data by storing the results of a query in a separate schema object.
See also: view
mean time to recover (MTTR)
The desired time required to perform instance or media recovery on the database. For example, you may set 10 minutes as the goal for media recovery from a disk failure. A variety of factors influence MTTR for media recovery, including the speed of detection, the type of method used to perform media recovery, and the size of the database.
mounted database
An instance that is started and has the control file associated with the database open. You can mount a database without opening it; typically, you put the database in this state for maintenance or for restore and recovery operations.
NOT NULL constraint
Data integrity constraint that requires a column of a table contain no null values.
See also: NULL value
NULL value
Absence of a value in a column of a row. Nulls indicate missing, unknown, or inapplicable data. A null should not be used to imply any other value, such as zero.
object type
An object type consists of two parts: a spec and a body. The type body always depends on its type spec.
online backup
A backup of one or more datafiles taken while a database is open and the datafiles are online. When you make a user-managed backup while the database is open, you must put the tablespaces in backup mode by issuing an ALTER TABLESPACE BEGIN BACKUP command. When you make an RMAN backup while the database is open, however, you do not need to put the tablespaces in backup mode.
online redo log
The online redo log is a set of two or more files that record all changes made to Oracle Database datafiles and control files. Whenever a change is made to the database, Oracle Database generates a redo record in the redo buffer. The LGWR process flushes the contents of the redo buffer into the redo log.
See also: redo log
operator
In memory management, the term operator refers to a data flow operator, such as a sort, hash join, or bitmap merge.
Oracle Clusterware
A portable cluster management solution that is integrated with Oracle Real Application Clusters 10g to monitor and restart Oracle components. Oracle Clusterware can be programmed to manage and monitor any application running in the cluster. Within a cluster managed by Oracle Clusterware, you can run both single instance and Oracle Real Application Clusters databases.
Oracle Enterprise Manager
An Oracle system management tool that provides an integrated solution for centrally managing your heterogeneous environment. It combines a graphical console, Oracle Management Servers, Oracle Intelligent Agents, common services, and administrative tools for managing Oracle products.
Oracle process
Oracle processes run Oracle Database code. They include server processes and background processes.
See also: process, server process, background process, user process
Oracle Real Application Clusters
Option that allows multiple concurrent instances to share a single physical database.
See also: instance
Oracle XA
The Oracle XA library is an external interface that allows global transactions to be coordinated by a transaction manager other than Oracle Database.
partition
A smaller and more manageable piece of a table or index. Tables are partitioned based on a partitioning key. For example, a sales history table may be partitioned by sales date, and there could be one partition for every calendar quarter. For large tables, partitions improve query performance and make table administration easier.
physical backups
Physical database files that have been copied from one place to another. The files can be datafiles, archived redo logs, or control files. You can make physical backups using Recovery Manager or with operating system commands such as the UNIX cp.
See also: logical backups
physical structures
Physical database structures of Oracle Database include datafiles, redo log files, and control files.
See also: logical structures
PL/SQL
Oracle's procedural language extension to SQL. PL/SQL enables you to mix SQL statements with procedural constructs. With PL/SQL, you can define and execute PL/SQL program units such as procedures, functions, and packages.
See also: SQL
primary key
The column or set of columns included in the definition of a table's PRIMARY KEY constraint. A primary key's values uniquely identify the rows in a table. Only one primary key can be defined for each table.
See also: PRIMARY KEY constraint
PRIMARY KEY constraint
Integrity constraint that disallows duplicate values and nulls in a column or set of columns.
See also: integrity constraint, key
priority inversion
Priority inversion occurs when a high priority job is run with lower amount of resources than a low priority job. Thus the expected priority is "inverted."
process
Each process in an Oracle database instance performs a specific job. By dividing the work of Oracle Database and database applications into several processes, multiple users and applications can connect to a single database instance simultaneously.
See also: Oracle process, user process
program global area (PGA)
A memory buffer that contains data and control information for a server process. A PGA is created by Oracle Database when a server process is started. The information in a PGA depends on the Oracle Database configuration.
query block
A self-contained DML against a table. A query block can be a top-level DML or a subquery.
See also: DML
read consistency
In a multiuser environment, the Oracle Database read consistency ensures that
The set of data seen by a statement remains constant throughout statement execution (statement-level read consistency).
Readers and writers of database data do not wait for other writers or other readers of the same data. Writers of database data wait only for other writers who are updating identical rows in concurrent transactions.
See also: concurrency, data consistency
read-only database
A database opened with the ALTER DATABASE OPEN READ ONLY command. As their name suggests, read-only databases are for queries only and cannot be modified. Oracle Database allows a standby database to be run in read-only mode, which means that it can be queried while still serving as an up-to-date emergency replacement for the primary database.
Recovery Manager (RMAN)
A utility that backs up, restores, and recovers Oracle Databases. You can use it with or without the central information repository called a recovery catalog. If you do not use a recovery catalog, RMAN uses the database's control file to store information necessary for backup and recovery operations. You can use RMAN in conjunction with a media manager to back up files to tertiary storage.
recovery point objective (RPO)
The maximum amount of data an IT-based organization is willing to lose as a result of a system failure. RPO is a balance point between the costs of more complete recovery and the harm done to the organization by loss of data. It indicates the data-loss tolerance of a business process or an organization in general. It is often measured in terms of time, such as five hours or two days worth of data loss.
recovery time objective (RTO)
The maximum amount of time that an IT-based organization is willing to be down after a system failure. RTO is the balance point between the costs of faster recovery and the costs of downtime to the organization. RTO indicates the downtime tolerance of a business process or an organization in general.
redo log
A set of files that protect altered database data in memory that has not been written to the datafiles. The redo log can consist of two parts: the online redo log and the archived redo log.
See also: online redo log
redo log buffer
Memory structure in the system global area that stores redo entries—a log of changes made to the database. The redo entries stored in the redo log buffers are written to an online redo log file, which is used if database recovery is necessary.
See also: system global area (SGA)
redo thread
The redo generated by an instance. If the database runs in a single instance configuration, then the database has only one thread of redo. If you run in an Oracle Real Application Clusters configuration, then you have multiple redo threads, one for each instance.
referential integrity
A rule defined on a key (a column or set of columns) in one table that guarantees that the values in that key match the values in a key in a related table (the referenced value). Referential integrity includes the rules that dictate what types of data manipulation are allowed on referenced values and how these actions affect dependent values.
See also: key
rollback segment
Logical database structure created by the database administrator to temporarily store undo information. Rollback segments store old data changed by SQL statements in a transaction until it is committed. Oracle has now deprecated this method of storing undo.
See also: commit, logical structures, segment, automatic undo management mode
rolling back
The use of rollback segments to undo uncommitted transactions applied to the database during the rolling forward stage of recovery.
See also: commit, rolling forward
rolling forward
The application of redo records or incremental backups to datafiles and control files in order to recover changes to those files.
See also: rolling back
row
Set of attributes or values pertaining to one entity or record in a table. A row is a collection of column information corresponding to a single record.
ROWID
A globally unique identifier for a row in a database. It is created at the time the row is inserted into a table, and destroyed when it is removed from a table.
schema
Collection of database objects, including logical structures such as tables, views, sequences, stored procedures, synonyms, indexes, clusters, and database links. A schema has the name of the user who controls it.
See also: logical structures
segment
Third level of logical database storage. A segment is a set of extents, each of which has been allocated for a specific data structure, and all of which are stored in the same tablespace.
See also: extent, data block
sequence
A sequence generates a serial list of unique numbers for numeric columns of a database's tables.
server
In a client/server architecture, the computer that runs Oracle software and handles the functions required for concurrent, shared data access. The server receives and processes the SQL and PL/SQL statements that originate from client applications.
See also: client, client/server architecture
server parameter file
A binary file containing initialization parameter settings that is maintained on the Oracle Database host. You cannot manually edit this file with a text editor. A server parameter file is initially built from a text initialization parameter file by means of the CREATE SPFILE statement or created directly with the Database Configuration Assistant.
server process
Server processes handle requests from connected user processes. A server process is in charge of communicating with the user process and interacting with Oracle Database to carry out requests of the associated user process.
See also: process, user process
service level agreement (SLA)
An agreement between a service provider and a service consumer, usually specifying what service is provided, maximum allowable interruptions in service, who will measure service delivery, and what happens if the provider fails to meet the terms of the agreement.
session
Specific connection of a user to an Oracle database instance through a user process. A session lasts from the time the user connects until the time the user disconnects or exits the database application.
See also: connection, instance, user process
shared pool
Portion of the system global area that contains shared memory constructs such as shared SQL areas. A shared SQL area is required to process every unique SQL statement submitted to a database.
See also: system global area (SGA), SQL
shared server
A database server configuration that allows many user processes to share a small number of server processes, minimizing the number of server processes and maximizing the use of available system resources.
See also: dedicated server
SQL
Structured Query Language, a nonprocedural language to access data. Users describe in SQL what they want done, and the SQL language compiler automatically generates a procedure to navigate the database and perform the task. Oracle SQL includes many extensions to the ANSI/ISO standard SQL language.
standby database
A copy of a production database that you can use for disaster protection. You can update the standby database with archived redo logs from the production database in order to keep it current. If a disaster destroys the production database, you can activate the standby database and make it the new production database.
subtype
In the hierarchy of user-defined datatypes, a subtype is always a dependent on its supertype.
synonym
An alias for a table, view, materialized view, sequence, procedure, function, package, type, Java class schema object, user-defined object type, or another synonym.
system change number (SCN)
A stamp that defines a committed version of a database at a point in time. Oracle Database assigns every committed transaction a unique SCN.
system global area (SGA)
A group of shared memory structures that contain data and control information for one Oracle database instance. If multiple users are concurrently connected to the same instance, then the data in the instance's SGA is shared among the users. Consequently, the SGA is sometimes referred to as the shared global area.
See also: instance
tablespace
A database storage unit that groups related logical structures together.
See also: logical structures
tempfile
A file that belongs to a temporary tablespace, and is created with the TEMPFILE option. Temporary tablespaces cannot contain permanent database objects such as tables, and are typically used for sorting.
temporary segment
Temporary segments are created by Oracle Database when a SQL statement needs a temporary database area to complete execution. When the statement finishes execution, the temporary segment's extents are returned to the system for future use.
transaction
Logical unit of work that contains one or more SQL statements. All statements in a transaction are committed or rolled back together.
See also: commit, rolling back
transaction recovery
Transaction recovery involves rolling back all uncommitted transactions of a failed instance. These are "in-progress" transactions that did not commit and that Oracle Database needs to undo. It is possible for uncommitted transactions to get saved to disk. In this case, Oracle Database uses undo data to reverse the effects of any changes that were written to the datafiles but not yet committed.
trigger
Stored database procedure automatically invoked whenever a table or view is modified, for example by INSERT, UPDATE, or DELETE operations.
Unicode
A way of representing all the characters in all the languages in the world. Characters are defined as a sequence of codepoints, a base codepoint followed by any number of surrogates. There are 64K codepoints.
UNIQUE KEY constraint
A data integrity constraint requiring that every value in a column or set of columns (key) be unique—that is, no two rows of a table have duplicate values in a specified column or set of columns.
See also: integrity constraint, key
user name
The name by which a user is known to Oracle Database and to other users. Every user name is associated with a password, and both must be entered to connect to Oracle Database.
user process
User processes execute the application or Oracle tool code.
See also: process, Oracle process
view
A view is a custom-tailored presentation of the data in one or more tables. A view can also be thought of as a "stored query." Views do not actually contain or store data; they derive their data from the tables on which they are based.
Like tables, views can be queried, updated, inserted into, and deleted from, with some restrictions. All operations performed on a view affect it's base tables.
