Oracle Fachvokabular

A clause used with SQL statements to limit the number of rows retrieved.

A database backup that includes all data files and at least one control file.

The amount of work that an application or the database can perform in a specified amount of time. This is frequently used as a performance measure in systems.

The difference between the time zone and UTC (Coordinated Universal Time zone).

Datatype used to storage datetime data with a fraction of seconds, and optional time-zone information.

The name of the physical file that is used to resolve an Oracle Net service name when you are using the local naming resolution method.

An Oracle-supplied utility used to test basic connectivity from an Oracle client to an Oracle listener.

A configuration that records all events that occur on a network, even when an error does not occur. This facility can be established at the client, the middle tier, or the server location.

A unit of work within a series of SQL statements. A statement begins with the user’s first Data Manipulation Language (DML) statement and ends with a COMMIT or ROLLBACK command. See also Data Manipulation Language (DML).

A Procedural Language/SQL (PL/SQL) program that is invoked in response to a database event.

A network architecture that is characterized by a client computer and a back-end server that communicate using some type of network protocol, such as TCP/IP.

A tool within the Oracle advisory framework that uses past undo usage to recommend settings for the UNDO_RETENTION parameter as well as an optimal size for the undo tablespace.

The data blocks changed or updated, along with pointers to rows inserted that are stored in an undo tablespace to support read consistency, rolling back, and recovery from failed transactions or an instance crash. This is also referred to as rollback information.

The segment that stores the before image of modified data. This is used for rollback or transaction-recovery purposes.

A special type of tablespace that holds undo data. Only one undo tablespace can be active in the database at any given time.

Functions that operate on groups of rows, also known as group
functions. The exact number of inputs for aggregate functions is not determined until the
query is executed and all rows are fetched. This differs from single-row functions, in which
the number of inputs is known at parse time, before the query is executed.

A file where Oracle Database writes information about the database startups,
shutdown, check points, redo log switches, errors, and warning information.

An unnamed PL/SQL program.

A file that contains the contents of a previously used redo log file.
It’s created only when the database is operating in ARCHIVELOG mode.

A database configuration in which redo log files are copied to the
archive log destination, which ensures that they won’t be overwritten and lost. These
archived logs are used primarily for media recovery.

An Oracle background process that copies the online redo log files to an archived
log destination.

Operators used to manipulate information in the arithmetic expressions.
Addition (+), subtraction (–), multiplication (*), and division (/) are the arithmetic
operators.

The monitoring and recording of specific database activities.

The process that analyzes the data in the Automatic Workload Repository (AWR) to identify
sources of potential performance bottlenecks and that recommends solutions for correcting
the problem. See also Automatic Workload Repository (AWR).

Tasks performed by Oracle Database to gather database
statistics, run the segment-space advisor periodically, and so on.

A type of storage mechanism that is new in
Oracle 10g. Oracle manages the storage definitions of the database within a second database
used exclusively by ASM to keep track of the disk allocations for your databases.

A mechanism to manage the memory requirement automatically by allocating the total memory to Oracle. Oracle will manage the SGA and PGA based on demand.

mechanism to manage the shared memory requirement automatically by allocating the memory to Oracle. Oracle will manage
the individual pools in SGA based on demand.

The collection of tables, owned by the SYSMAN schema, that stores the performance statistics gathered from the system global area (SGA)
by the Memory Monitor (MMON) background process.