| Oracle® Warehouse Builder User's Guide 10g Release 1 (10.1) Part Number B12146-02 |
|
|
View PDF |
| Oracle® Warehouse Builder User's Guide 10g Release 1 (10.1) Part Number B12146-02 |
|
|
View PDF |
ABAP is a programming language for developing applications for the SAP R/3 system, a business application subsystem.
activity
In a process flow, activities represent units of work to be performed by the workflow engine. These units of work can involve components internal and external to Oracle Warehouse Builder. An example of an external activity is the Files Exists activity which checks for the existence of a file on a local or remote machine before continuing the process flow. An example of an internal activity is the FORK activity which specifies logic for launching concurrent activities.
Describes a fact/measure that can be summarized through addition. An additive fact is the most common type of fact. Examples include Sales, Cost, and Profit. (Contrast with: nonadditive, semi-additive.)
A database-integrated system containing message queues. AQs play a central role in enterprise data integration. Advanced Queues enable message management and communication required for application integration. Oracle Warehouse Builder supports Advanced Queues as data sources and targets for your warehouse design. In Warehouse Builder architecture, an AQ is a First Class Object (FCO). (See also: source, target.)
A software routine that runs on a remote computer and communicates with a central server. The server can delegate the execution of software that runs locally to an agent. An agent allows Warehouse Builder to call software on different machines.
Summarized data. For example, unit sales of a particular product could be aggregated by day, month, quarter and yearly sales. (See also: aggregation.)
The process of consolidating data values into a single value. For example, sales data could be collected on a daily basis and then be aggregated to the week level, the week data could be aggregated to the month level, and so on. The data can then be referred to as aggregate data. Aggregation is synonymous with summarization, and aggregate data is synonymous with summary data.
A single file containing objects that organize and store data in a form that OLAP Services can use. You determine the structure and contents of an analytic workspace by defining objects, examples of which are dimensions, variables, and programs. Once these definitions are in the analytic workspace dictionary, you can enter, change, or use the data with OLAP Services.
A value at any level higher than a given value in a hierarchy. For example, in a Time dimension, the value 1999 might be the ancestor of the values Q1-99 and Jan-99.
application program interface (API)
A set of public programmatic interfaces that consist of a language and message format to communicate with an operating system or other programmatic environment, such as databases, Web servers, JVMs, and so forth. These messages typically call functions and methods available for application development. You can access the Oracle Warehouse Builder Java API Reference through Oracle MetaBase Plus (OMB Plus).
To backup metadata in Oracle Warehouse Builder by exporting it with version information using the Metadata Loader (MDL). (See also: export metadata, restore metadata.)
Defined item of data that an object can store; a field represented by a column within an object (entity). In Oracle Warehouse Builder the term is used in two contexts:
For tables and views in Warehouse Builder, an attribute set contains a chosen set of columns in the order you specify. Warehouse Builder generates a predefined attribute sets for tables and defined constraints. You can create the your own attribute sets when designing mappings. For exporting an attribute set to Oracle Discoverer, you can create a bridge-type attribute set.
The language assigned to the Design Repository. All metadata is stored in this language. The display language must be set to this language in order to create new objects in the repository. Currently the only supported base language is American English.
The action that connects an operator in the Mapping Editor with an object in the Design Repository.
The purpose of an index is to provide pointers to the rows in a table that contain a given key value. A regular index achieves this by storing a list of ROWIDs for each key corresponding to the rows with that key value. A bitmap index uses a bitmap instead of a list of ROWIDs for each key value. Each bit in the bitmap corresponds to a possible ROWID, and if the bit is set, it means that the row with the corresponding ROWID contains the key value. A mapping function converts the bit position to an actual ROWID. Bitmap indexes are most effective for queries that contain multiple conditions in the WHERE clause.
A mapping object operator in Oracle Warehouse Builder that is connected to an object defined in the Design Repository. (Contrast with: unbound object.)
breakpoint
A point of discontinuity, change, or cessation. In Oracle Warehouse Builder, this term is used to describe a point in a data flow that can be interrupted in order to ensure that the operator is functioning as expected.
A component in Oracle Warehouse Builder that enables you to import metadata from and export metadata to various tools, such as CWM compliant applications, Oracle Discoverer, Oracle Express, and Oracle9i OLAP server.
The name of the Oracle Warehouse Builder object that is used in business applications. In previous releases of Warehouse Builder, this was known as the logical name. (Contrast with: physical name.)
A metadata snapshot in Oracle Warehouse Builder of a parent object (such as a project, folder, or mapping) that contains information about not only the parent object, but all its child objects as well. For example, if you take a cascade snapshot of a database module, Module A, which contains two tables, Table1 and Table2, and then change one of the tables in the repository, a comparison report will show Module A to have changed because one of its child objects has changed. (Contrast with: no cascade snapshot.)
In reference to dimensional hierarchies: A value at the level under a given value in a hierarchy. For example, in a Time dimension, the value Jan-99 might be the child of the value Q1-99. A value can be a child for more than one parent if the child value belongs to multiple hierarchies.
In reference to Oracle Warehouse Builder metadata objects: An object on the navigation tree that belongs to a higher-level object. For instance, a table is a child object of a database module; a database module, in turn, is a child object of a project.
The process of resolving inconsistencies and fixing the anomalies in source data, typically as part of the ETL process. (See also: extraction, transformation, and loading (ETL).)
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.
The area in Oracle Warehouse Builder client where cut or copied objects are stored. Only one object can be stored at a time.
The Oracle Warehouse Builder process of taking metadata stored in the Design Repository and generating code that will create the designed model in the target system.
A collection is a grouping mechanism you can use to group objects within a project in Oracle Warehouse Builder. Collections contain shortcuts to objects from the same project. If you want to export metadata to tools such as Oracle Discoverer, group the desired metadata in a collection. In Warehouse Builder architecture, a collection is a First Class Object (FCO).
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. (See also: row.)
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: rollback.)
Common Warehouse Metamodel (CWM)
A repository standard used by Oracle data warehousing, decision support, and OLAP tools including Oracle Warehouse Builder. The CWM repository schema is an open standard repository that other products can share.
A generic connectivity agent is included with the Oracle Database database server. This agent can be used for low-end data integration solutions when the transfer of data is subject to the rules of specific ODBC or OLE DB drivers installed on the client system.
An object on the Oracle Warehouse Builder navigation tree that is used to define connection information between locations. Only Oracle database module locations can have connectors defined. In Warehouse Builder architecture, a connector is a First Class Object (FCO). (See also: location.)
The main window of the Oracle Warehouse Builder application. It contains a menu bar, launcher, and navigation tree.
Constraints provide a mechanism for ensuring that data conforms to guidelines specified by the database administrator. The most common types of constraints include unique constraints (ensuring that every value for a given column is unique), not null constraints, and foreign key constraints (which ensure that two keys in different tables share a primary key:foreign key relationship).
conventional view
See: view.
crosstab
A crosstab is a display layout that arranges items in a matrix of rows and columns. Items can appear on the row, column page edges. A crosstab can be used to display summary information and show how data varies across dimensions, such as sales by region by month. A crosstab is sometimes called a matrix.
Fundamental structure for data in a multidimensional schema. A cube contains dimensions, hierarchies, levels and measures. In Warehouse Builder architecture, a cube is a First Class Object (FCO). (See also: dimension, hierarchy, level, measure.)
Data Definition Language (DDL)
Includes statements like CREATE/ALTER TABLE/INDEX, which define or change data structure.
In mappings, data flow operators alter or transform data as it flows from sources to targets. The Joiner operator is an example of a data flow operator because it joins multiple row sets from different sources with different cardinalities and produces a single output row set. (See also: mapping, operator, source operator, target operator.)
Data Manipulation Language (DML)
Includes statements like INSERT, UPDATE, and DELETE, which change data in tables.
A simple form of a data warehouse that is designed for a particular line of business, such as sales, marketing, or finance. Data marts are often built and controlled by a single department in an organization. Given their single-subject focus, data marts typically draw data from only a few sources. In a dependent data mart, the data can be derived from an enterprise-wide data warehouse. In an independent data mart, data can be collected directly from internal operational systems or external data.
A relational database that is designed for query and analysis rather than transaction processing. A data warehouse usually contains historical data that is derived from transaction data, but it can include data from other sources. It separates analysis workload from transaction workload and enables a business to consolidate data from several sources.
In addition to a relational database, a data warehouse environment often consists of an ETL solution, an OLAP engine, client analysis tools, and other applications that manage the process of gathering data and delivering it to business users. (See also: extraction, transformation, and loading (ETL), Online Analytical Processing (OLAP).)
Collection of data that is treated as a unit. The purpose of a database is to store and retrieve related information.
An Oracle database is a set of operating system files, treated as a unit, in which an Oracle database server stores a set of data dictionary tables and user tables. A database requires three types of files: database files, redo log files, and control files. (See also: table, relational database, relational database management system (RDBMS).)
An object stored in the local database that identifies a remote database, a communication path to the remote database, and optionally, a username and password for it. Once defined, a database link can be used to perform queries on tables in the remote database. Also called DBlink. In SQL*Plus, you can reference a database link in a DESCRIBE or COPY command.
Something created and stored in a database. Tables, views, synonyms, indexes, sequences, clusters, and columns are all examples of database objects. (See also: table, view, index, sequence, column.)
A standard form of data. The Oracle datatypes are CHAR, NCHAR, VARCHAR2, NVARCHAR2, DATE, NUMBER, LONG, CLOB, NCLOB, RAW, and LONG RAW; however, the Oracle database server recognizes and converts other standard datatypes.
A named set of fixed attributes that can be associated with an item as a property. Data typing provides a way to define the behavior of data. (See also: attribute.)
debug
To locate and correct malfunctioning elements or errors in a computer program code. In Oracle Warehouse Builder, this term is used to describe the process of looking for errors or problems in a data flow.
A flat file whose fields are separated by delimiters. Contrast with a fixed-length flat file. (See also: record, delimiter.)
A character or combination of characters used to separate one item or set of data from another. For example, in comma delimited records, a comma is used to separate each field of data. There are also fixed-length records, where each field's beginning and end is specified by position rather than any character acting as a delimiter. (See also: flat file, record.)
The process of allowing redundancy in a table so that it can remain flat. (Contrast with: normalize.)
Oracle Warehouse Builder's comprehensive deployment console that enables you to view and manage all aspects of deployment including configuration and validation. It also enables you to view the deployment history of an object to determine how you want to deploy the object.
A fact/measure that is generated from existing data using a mathematical operation or a data transformation. Examples include averages, totals, percentages, and differences.
Installed in an Oracle database, the Design Repository stores the metadata definitions for all of the objects used in Oracle Warehouse Builder. This is where all of the design information is stored for the target systems you are creating. You can access metadata stored here using the client user interface, or through Oracle MetaBase Plus (OMB Plus). This repository is created using the Repository Assistant. (Contrast with: Runtime Repository.)
A structure, often composed of one or more hierarchies, that categorizes data. Several distinct dimensions, combined with measures, enable end users to answer business questions. Commonly used dimensions are Customer, Product, and Time. In Oracle9i, a dimension is a database object that defines hierarchical (parent/child) relationships between pairs of column sets. In Warehouse Builder architecture, a dimension is a First Class Object (FCO).
One element in the list that makes up a dimension. For example, a computer company might have dimension values in the Product dimension called LAPPC and DESKPC. Values in the Geography dimension might include Boston and Paris. Values in the Time dimension might include MAY96 and JAN97.
dimensional object
Dimensional objects are similar to relational objects, but contain additional metadata to identify and categorize your data. When you define dimensional objects, you describe the logical relationships that help store the data in a more structured format. Dimensional objects include dimensions and cubes. (Contrast with: relational object.)
display set
In mappings, a display set is a graphical representation of a subset of operator attributes. Use display sets to limit the number of attributes visible in an operator and therefore simplify the display of complex mappings.
drill
To navigate from one item to a set of related items. Drilling typically involves navigating up and down through the levels in a hierarchy. When selecting data, you can expand or collapse a hierarchy by drilling down or up in it, respectively. (See also: level, drill down, drill up.)
drill down
To expand the view to include child values that are associated with parent values in the hierarchy. (See also: drill, drill up, level.)
drill up
To collapse the list of descendant values that are associated with a parent value in the hierarchy. (See also: drill, drill down, level.)
editor
A window in Oracle Warehouse Builder used to define or edit objects and their relationships to each other.
element
An object or process. For example, a dimension is an object, a mapping is a process, and both are elements.
endian
Refers to byte order, the numeric arrangement of bytes in a word, which is the basic unit of storage in a computer (words are 8, 16, 32 and 64 bits long). Big-endian is the normal order and the way humans deal with arithmetic: the most significant byte or digits are placed leftmost in the structure. Some CPUs deal with words in little-endian order, which is the reverse and places the least significant digits on the left. Since numbers are calculated by the CPU starting with the least significant digits, little-endian numbers are already set up in the required processing order.
enqueue
Enqueues are shared memory structures that serialize access to database resources and are associated with a session or transaction. (See also: lock.)
execution
The process of running deployed mappings and process flows in Oracle Warehouse Builder. (See also: deployment.)
export metadata
The extraction of a copy of metadata (that is, not physical files) from a repository using the Export utility. You can then use the Import utility to import the data into a repository. (See also: Metadata Loader (MDL), archive metadata.)
expression
A formula, such as SALARY + COMMISSION, used to calculate a new value from existing values. An expression can be made up of column names, functions, operators, and constants. Formulas are found in commands or SQL statements.
eXtensible Markup Language (XML)
An open standard for describing data developed by the W3C using a subset of the SGML syntax and designed for Internet use. Version 1.0 is the current standard, having been published as a W3C Recommendation in February 1998.
external table
An external table is a read-only table associated with a single record type in external data such as a flat file. External tables represent data from non-relational source in a relational table format. In Warehouse Builder architecture, an external table is a First Class Object (FCO).
extraction
The process of taking data out of a source as part of an initial phase of ETL. (See also: extraction, transformation, and loading (ETL).)
extraction, transformation, and loading (ETL)
ETL refers to the methods involved in accessing and manipulating source data and loading it into a data warehouse or other type of target. The order in which these processes are performed varies. ETT (extraction, transformation, transportation) and ETM (extraction, transformation, move) are sometimes used instead of ETL.
fact table
A table in a star schema that contains fact/measures. A fact table typically has two types of columns: those that contain facts and those that are foreign keys to dimension tables. The primary key of a fact table is usually a composite key that is made up of all of its foreign keys.
A fact table can contain either detail level facts or facts that have been aggregated (fact tables that contain aggregated facts are often instead called aggregate tables). A fact table usually contains facts with the same level of aggregation.
In Oracle Warehouse Builder, facts and fact tables are referred to as cubes. (See: cube.)
fact/measure
Data, usually numeric and additive, that can be examined and analyzed. Values for facts or measures are usually not known in advance; they are observed and stored. Examples include Sales, Cost, and Profit. Fact and measure are synonymous; fact is more commonly used with relational environments; measure is more commonly used with multi-dimensional environments. (See also: dimension, attribute.)
In Oracle Warehouse Builder, facts and fact tables are referred to as cubes. (See also: derived fact (or measure), cube.)
file
A collection of data treated as a unit, such as a list, document, index, note, set of procedures, and so on. Generally used to refer to data stored on magnetic tapes or disks. In Warehouse Builder architecture, a file is a First Class Object (FCO).
file-to-table mapping
Maps data from flat files to tables in the data warehouse. (See also: flat file, table.)
filter
To select data. Filters use patterns (masks) against which all data are compared and only matching data are "passed through," hence the concept of a filter. For example, e-mail clients and servers can filter out important messages and alert the user or look for text patterns that appear to be spam and delete it. In SQL, the WHERE clause contains the filter conditions on the data that is being queried.
In Oracle Warehouse Builder architecture, a First Class Object (FCO) represents a component in the metadata repository that can be manipulated through the Warehouse Builder interface. First Class Objects often, but not always, own other objects. For example, a TABLE is a First Class Object that may own the following second class objects: TABLE_COLUMN, UNIQUE_KEY, FOREIGN_KEY, and CHECK_CONSTRAINT. Other examples of FCOs include EXTERNAL_TABLE, CONNECTOR, and MAPPING.
As a rule of thumb for those accessing Warehouse Builder through the graphic user interface, first class objects generally appear on the navigation tree. Similarly, users who access Warehouse Builder through Oracle MetaBase Plus (OMB Plus) can generalize FCOs as objects of OMBCREATE, OMBALTER, OMBRETRIEVE, and OMBDELETE commands.
(See also: Second Class Object (SCO), Third Class Object.)
fixed-length field
A field whose beginning and end is specified by position rather than any character acting as a delimiter. Fixed-length fields conform to specified field sizes; for example, a 25-byte name field takes up 25 bytes in each record. (See also: fixed-length flat file, flat file.)
fixed-length flat file
A flat file whose records have fixed-length fields. Contrast with a delimited flat file, whose records contain variable-length fields separated by a delimiter. (See also: record, fixed-length field.)
flat file
A relatively simple database system in which each database is contained in a single table. A flat file is not related to, or does not contain any linkages to, another file. It is generally used for standalone lists. Flat files can be related, but only if the applications are programmed to do so. In contrast, relational database systems can use multiple tables to store information, and each table can have a different record format. When files must be related (such as customers to orders, vendors to purchases), a relational database manager is used, not a flat file manager. (See also: delimited flat file, fixed-length flat file, logical record.)
foreign key
An integrity constraint that requires each value in a column or set of columns to match a value in a the unique or primary key of a related table. Foreign key integrity constraints also define referential integrity actions that dictate what Oracle should do with dependent data if the data it references is altered.
Fourth Class Object
In Oracle Warehouse Builder architecture, Third and Fourth Class objects are relative rankings of objects owned by other objects. These refer only to objects whose ownership spans several layers. For example, INDEX_COLUMN is a Second Class Object in the scenario where a DIMENSTION_TABLE (which is a First Class Object) owns INDEX_COLUMN. However, INDEX_COLUMN becomes a Third Class Object in the scenario where the First Class Object CUBE_TABLE owns the Second Class Object INDEX, which in turn owns INDEX_COLUMN.
(See also: First Class Object (FCO), Second Class Object (SCO).)
full snapshot
A metadata snapshot that contains enough information about the object to use not only for comparison purposes, but for restore purposes as well. A Full snapshot consumes more space than a signature snapshot, but you can only restore metadata from full snapshots. Full snapshots can be converted to signature snapshots, but the reverse is not true.
group
In mappings, attributes in each operator are designated into groups. Groups indicate the directional nature of the attributes. Therefore, an input group contains attributes that are input into the operator. An output group contains operator output attributes. (See also: attribute.)
Hierarchies are logical structures that use ordered levels as a means of organizing data. A hierarchy can be used to define data aggregation. For example, in a Time dimension, a hierarchy might be used to aggregate data from the Month level to the Quarter level to the Year level. A hierarchy can also be used to define a navigational drill path, regardless of whether the levels in the hierarchy represent aggregated totals.
Hypertext Markup Language (HTML)
The markup language used to create the files sent to Web browsers and that serves as the basis of the World Wide Web. The next version of HTML is called xHTML and is an XML application.
import metadata
To bring previously exported metadata into an Oracle Warehouse Builder Design Repository using the Metadata Loader (MDL) utility. Imported metadata can be merged with or can overwrite existing objects. MDL has its own file format; only .MDL files can be exported and imported using the MDL utility. (See also: restore metadata, export metadata.)
index
Indexes are optional structures associated with tables and clusters. You can create indexes on one or more columns of a table to speed SQL statement execution on that table. (See also: bitmap index.)
inner join
This is the default type of join. It produces a resulting row if there is a matching condition. For example, matching shipments with receipts would produce only those shipments that have been received. (Contrast with: outer join.)
input role
In the Name and Address operator, input roles indicate what kind of name or address information resides in a line of data being extracted from the source. Input roles can be non-discrete (line oriented) for free-form data, or discrete (such as first name, primary address, or city) for specific input attributes. Whenever possible, choose discrete input roles (such as 'Person'), rather than non-discrete roles (such as 'Line1'). Discrete roles give the Name and Address operator more information about the content of the source attribute. (See also: output component.)
instance
A system global area (SGA) and the Oracle background processes constitute an Oracle instance. Every time a database is started, a system global area is allocated and Oracle background processes are started. The SGA is de-allocated when the instance shuts down.
Software that works with Oracle Warehouse Builder to facilitate definition, design, and extraction of source data. Examples of integrators include the Oracle Applications Integrator and the SAP Integrator.
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.
IP address
Used to identify a node on a network. Each computer on the network is assigned a unique IP address, which is made up of the network ID, and a unique host ID. This address is typically represented in dotted-decimal notation, with the decimal value of each octet separated by a period, for example 144.45.9.22.
join
In relational database management, a query that selects data from more than one table. A join matches one table (file) against another based on some condition, creating a third table with data from the matching tables. For example, a customer table can be joined with an order table creating a table for all customers who purchased a particular product. A join is characterized by multiple tables in the FROM clause. Oracle pairs the rows from these tables using the condition specified in the WHERE clause and returns the resulting rows. This condition is called the join condition and usually compares columns of all the joined tables. (See also: inner join, outer join.)
key
A 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.)
launcher
The panel in the Oracle Warehouse Builder console window that contains buttons to control the active environment. These environments include the Project environment, Administration environment, and Transformation Library environment.
level
A position in a hierarchy. For example, a Time dimension might have a hierarchy that represents data at the Month, Quarter, and Year levels.
level value table
A database table that stores the values or data for the levels you created as part of your dimensions and hierarchy definitions. (See also: dimension, level.)
local enqueues
Local enqueues are synchronization mechanisms utilized to coordinate concurrent access to shared data structures in cluster databases. Local enqueues are called local locks in single instance Oracle. (See also: enqueue.)
local locks
In single instance Oracle, local locks are synchronization mechanisms utilized to coordinate concurrent access to shared data structures. In a cluster database, local locks are called local enqueues.
locale
A collection of information regarding the linguistic and cultural preferences from a particular region. Typically, a locale consists of language, territory, character set, linguistic, and calendar information defined in National Language Support or Globalization Support data files.
location
An object on the Oracle Warehouse Builder navigation tree that represents the physical locations to which target systems will be deployed. In Warehouse Builder architecture, a location is a First Class Object (FCO). (See also: connector, deployment.)
lock
Locks are used in a multiuser environment where one user is given control to modify an object while the others have read only access. Maintains integrity of objects while sharing projects. A lock is kept by a user until the user commits or rolls back, and closes any open editors and property sheets. (See also: project, commit, rollback.)
logical record
In flat files, records can be organized logically with one logical record corresponding to multiple physical records.
logical structures
Logical structures of an 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. (Contrast with: physical structures.)
lookup
A data search performed within a predefined table of values (such as an array or matrix) or within a data file.
The definition of the relationship and data flow between source and target objects. In Warehouse Builder architecture, a mapping is a First Class Object (FCO).
master-detail
A multiple-record-type flat file where the master records have corresponding detail records. For example, a simple master-detail flat file can have two record types: master records with Department information, and detail records for each master record, containing Employee information for each employee in that department.
materialized view
A pre-computed table comprising aggregate data and/or joined data from cubes and possibly dimension tables. Also known as a summary or aggregate table. A materialized view provides indirect access to table data by storing the results of a query in a separate schema object. Like an index, a materialized view consumes storage space, must be refreshed when the data in its master tables changes, improves performance of SQL execution, and is transparent to SQL applications and users. Unlike an index, a materialized view can be accessed directly, using SELECT, INSERT, UPDATE, and DELETE statements. In Warehouse Builder architecture, a materialized view is a First Class Object (FCO). (Contrast with: conventional view.)
measure
Data, usually numeric and additive, that can be examined and analyzed. Values for facts or measures are usually not known in advance; they are observed and stored. Examples include Sales, Cost, and Profit. Fact and measure are synonymous; fact is more commonly used with relational environments; measure is more commonly used with multi-dimensional environments.
Data that describes data and other structures, such as objects, business rules, and processes. For example, the schema design of a data warehouse is typically stored in a repository as metadata, which is used to generate scripts that build and populate the data warehouse. A repository contains metadata.
Examples include: for data, the definition of a source to target transformation that is used to generate and populate the data warehouse; for information, definitions of tables, columns, and associations that are stored inside a relational modeling tool; for business rules, discount by 10 percent after selling 1,000 items.
Metadata Loader (MDL)
The Oracle Warehouse Builder utility that enables you to backup your Design Repository. You can export metadata from a Design Repository into an .MDL text file, and you can import metadata from an .MDL file into a repository. If desired, you can export metadata with version information. When importing, you can overwrite existing metadata objects, or merge using other options.
metadata snapshot
A method of capturing the state of your Design Repository (or selected objects in the repository) for metadata history management. Comparison reports can be generated between a metadata snapshot and the current repository, or between two metadata snapshots.
A full snapshot enables you to not only generate comparison reports, but to restore objects from the snapshot into the current repository, whereas a signature snapshot can only be used for comparison purposes. A cascade snapshot captures information about a selected object and all of its child objects (if any), where as a no cascade snapshot only captures information about the selected object. In Warehouse Builder architecture, a snapshot is a First Class Object (FCO).
model
An object that represents something to be made. A representative style, plan, or design. Metadata that defines the structure of the data warehouse. (See also: metadata.)
Modules are storage objects within projects that help to organize source and target objects. Visible on the Oracle Warehouse Builder main project navigation tree, modules are used as metadata containers for databases, files, applications, and process flows. Source modules contain the metadata from existing source systems from which you are pulling. Target modules contain the metadata you are designing.
natural key
A key that is native to the data and is used to identify each row. For example, the state codes of CA and DC can be used as natural keys.
navigation tree
The main console workspace where Oracle Warehouse Builder objects are organized into projects. This is similar to a file system with all of the objects organized into expandable folders. (See also: project, First Class Object (FCO).)
no cascade snapshot
A metadata snapshot that only captures information about the selected object, and not about its child objects. For example, if you take a no cascade snapshot of a database module, Module A, which owns two tables, Table1 and Table2, and then change one of the tables in the repository, a comparison report does not show Module A to have changed. (Contrast with: cascade snapshot.)
nonadditive
Describes a fact/measure that cannot be summarized through addition. An example is average. (Contrast with additive, semi-additive.)
normalize
In a relational database, the process of removing redundancy in data by separating the data into multiple tables. (Contrast with denormalize.)
OLAP
See: Online Analytical Processing (OLAP). Contrast with: Online Transactional Processing (OLTP).
OLTP
See: Online Transactional Processing (OLTP). Contrast with Online Analytical Processing (OLAP).
Online Analytical Processing (OLAP)
OLAP functionality is characterized by dynamic, multi-dimensional analysis of historical data, which supports activities such as the following:
Calculating across dimensions and through hierarchies
Analyzing trends
Drilling up and down through hierarchies
Rotating to change the dimensional orientation
OLAP tools can run against a multidimensional database or interact directly with a relational database. Contrast with Online Transactional Processing (OLTP). (See also: drill, hierarchy.)
Online Transactional Processing (OLTP)
OLTP systems are application systems that are characterized by updates to the database. Examples of OLTP systems include e-business systems and ERP applications (such as Oracle Applications and SAP R/3). More specialized examples include telephone call and billing systems, credit card transactions, and airline reservation systems. OLTP systems are also known as transaction systems. Contrast with Online Analytical Processing (OLAP). (See also: transaction.)
Open Database Connectivity (ODBC)
Oracle ODBC Driver provides a standard interface that allows one application to access many different data sources. The application's source code does not have to be recompiled for each data source. A database driver links the application to a specific data source. A database driver is a dynamic link library that an application can invoke on demand to gain access to a particular data source. Therefore, the application can access any data source for which a database driver exists.
operating system
The system software that manages a computer's resources, performing basic tasks such as allocating memory and allowing computer components to communicate. Oracle Warehouse Builder is available on these operating systems:
Windows: NT, 2000, and XP
UNIX: Solaris, Linux, and HP-UX
operator
The operator is the basic design element for a mapping. (See also: data flow operator, source operator, target operator.)
Oracle Enterprise Manager (OEM)
A separate Oracle product that combines a graphical console, agents, common services, and tools to provide an integrated and comprehensive systems management platform for managing Oracle products.
Oracle MetaBase (OMB)
The Oracle Warehouse Builder repository, including its services, such as version control, extensibility, multiuser locking, copy/paste.
Oracle MetaBase Plus (OMB Plus)
A tool that provides access to Oracle Warehouse Builder scripting capabilities.
Oracle Warehouse Builder Name and Address
Licensed separately from Oracle Warehouse Builder , this product consists of third-party data files that provide the name and address data to be used with the Oracle Warehouse Builder Name and Address operator to cleanse user data. These files are updated quarterly and updates are available on MetaLink.
Oracle Server
The relational database management system (RDBMS) sold by Oracle Corporation. Components of Oracle Server include the kernel and various utilities for use by DBAs and database users.
Oracle Universal Installer (OUI)
A graphical user interface (UI) that facilitates the installation of the Oracle database software and its related components.
Oracle Warehouse Builder
Oracle Warehouse Builder is a business intelligence tool that provides an integrated solution for designing and deploying enterprise data warehouses, data marts, and business intelligence applications. It solves the complex problem of data integration between various dispersed data sources and targets. In addition, Warehouse Builder provides all the necessary functionality to maintain the life cycle of the system you develop. (See also: data warehouse, data mart, source, target.)
It is a comprehensive toolset designed for practitioners who move and transform data, develop and implement data warehouses, perform metadata management, or create and manage Oracle databases and metadata. In addition to its graphical user interface (UI), Warehouse Builder provides an API in the form of Oracle MetaBase Plus (OMB Plus), where all the Warehouse Builder functionality can be accessed using the OMB Scripting Language.
ORACLE_HOME
Corresponds to the environment in which Oracle products run. This environment includes the location of installed product files, the PATH variable pointing to the products' binary files, registry entries, net service names, and program groups.
If you install an OFA-compliant database, using Oracle Universal Installer defaults, Oracle home (known as \ORACLE_HOME in this guide) is located beneath X:\ORACLE_BASE. It contains subdirectories for Oracle software executables and network files. (See also: service name.)
outer join
A join condition using the outer join operator (+) with one or more columns of one of the tables. Oracle returns all rows that meet the join condition. Oracle also returns all rows from the table without the outer join operator for which there are no matching rows in the table with the outer join operator. For example, matching shipments with receipts would produce not only those shipments that have been received, but would create a record for every shipment whether or not it was received. The data for received items would be attached to the shipments, and empty, or null, fields would be attached to shipments without receipts. (Contrast with: inner join.)
output component
In the Name and Address operator, the output component indicates which component of a name or address an attribute constitutes. Each output component represents a discrete name or address entity, such as a title, a standardized first name, a street number, a street name, or a street type. Every output attribute from the Name and Address operator must have an output component that identifies its role in the name or address. (See also: input role.)
dual address
In the Name and Address operator, a dual address contains both a Post Office (PO) box and a street address for the same address record. For records that have dual addresses, one address line becomes the normal address and one becomes the dual address. A sample dual address is:
PO Box 2589 4439 Mormon Coulee Rd La Crosse WI 54601-8231
package
A method of encapsulating and storing related procedures, functions, and other package constructs together as a unit in the database. While packages provide the database administrator or application developer organizational benefits, they also offer increased functionality and database performance. (See also: PL/SQL.)
A value at the level higher than a given value in a hierarchy. For example, in a Time dimension, the value Q1-99 might be the parent of the value Jan-99. (See also: child.)
In reference to Oracle Warehouse Builder metadata objects: An object on the navigation tree that owns to a lower-level objects. For instance, a project is a parent object of the modules it owns; a database module is, in turn, a parent object of the table objects it owns.
partition
A unique, non-overlapping directory naming context that is stored on one directory server.
partition exchange loading (PEL)
A runtime performance feature in Oracle Warehouse Builder where data partitioning is used improve performance when loading or purging data in a target system. (See also: partition.)
payload
A protocol structure encapsulating a set of logical ICE operations delivered at discrete intervals. A payload is a single instance of an XML document formatted according to the protocol definitions contained in this specification.
physical instance
A collection of related database objects that, when deployed, becomes a schema. Objects include tables, views, and other objects.
physical name
Unique name of a repository object. Conforms to the basic syntax rules for schema objects, as defined in the Oracle Database SQL Reference. Used in the generation of DDL scripts. Users can create a physical name of a new object or modify the physical name of an existing object.
physical structures
Physical database structures of an Oracle database include data files, redo log files, and control files. (See also: logical structures.)
pivot
In a mapping, the pivot operator enables you to transform a single row of attributes into multiple rows. Use this operator in a mapping when you want to transform data that is contained across attributes instead of rows. (See also: unpivot.)
PL/SQL
The 3GL Oracle procedural language extension of SQL. PL/SQL enables you to mix SQL statements with procedural constructs. PL/SQL combines the ease and flexibility of SQL with the procedural functionality of a structured programming language, such as IF...THEN, WHILE, and LOOP. Even when PL/SQL is not stored in the database, applications can send blocks of PL/SQL to the database rather than individual SQL statements, thereby reducing network traffic. With PL/SQL, you can define and execute PL/SQL program units such as procedures, functions, and packages. PL/SQL is interpreted and parsed at runtime; it does not need to be compiled. (See also: package, Structured Query Language (SQL), SQL*Plus.)
portlet
A portlet are components of information from other web sites or applications that you can use to build a customized web page. Warehouse Builder Browser, for example, consists of portlets that you can add to customize a web page for navigate and report on metadata in Warehouse Builder.
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: foreign key.)
privilege
A right to execute a particular type of Structured Query Language (SQL) statement or to access another user's object.
process flow
A process flow describes dependencies between Warehouse Builder mappings and external activities such as email, FTP, and operating system commands. It provides a visual representation of a sequence of actions in a flow. Basic design elements for a process flow include the activity and the transition. In Warehouse Builder architecture, a process flow is a First Class Object (FCO).
Oracle Warehouse Builder projects are the largest storage objects within the Warehouse Builder Design Repository and help users organize their work. Projects store and organize metadata definitions required to perform extraction, transformation, and loading (ETL) for a specific set of sources and targets. These definitions include data sources, target warehouse objects, mappings from source to targets, transformation operations, and configuration parameters. These definitions are organized into folders within the project. Typically a project contains related metadata. Creating multiple projects enables you to create your design in an organized manner.
query
A Structured Query Language (SQL) SELECT statement that retrieves data, in any combination, expression, or order. Queries are read-only operations; they do not change any data; they only retrieve data. Queries are often considered to be DML statements.
reconcile
In mappings, every operator you define can have a corresponding definition in the Oracle Warehouse Builder repository. When you reconcile operators, you ensure that the operator matches the repository object it represents. You can reconcile inbound (into the mapping) or outbound (out from the mapping). Inbound reconciliation updates the operator with the definition of a specified repository object. Outbound reconciliation updates a selected repository object to reflect changes you made to the operator in a mapping.
record
In flat file database management systems, a record is a complete set of information. Records are composed of fields, each of which contains one item of information. A set of records constitutes a file. For example, a personnel file might contain records that have three fields: a name field, an address field, and a phone number field.
relational database
A structured collection of data that stores data in the form of related tables consisting of one or more rows, each containing the same set of columns. Data in multiple tables is linked because the relationships between the tables are defined. The link is based on one or more fields common to both tables. Relational databases are powerful because they require few assumptions about how data is related or how it will be extracted from the database. As a result, the same database can be viewed in many different ways. An important feature of relational systems is that a single database can be spread across several tables. This differs from flat file databases, in which each database is self-contained in a single table.
relational database management system (RDBMS)
A computer program designed to store and retrieve shared data. In a relational system, data is stored in tables consisting of one or more rows, each containing the same set of columns. Oracle is a relational database management system. Other types of database systems are called hierarchical or network database systems.
relational object
A relational object, like a relational database, relies on tables and table-derived objects to store and link all of its data. The relational objects you define in Oracle Warehouse Builder are physical containers in the database that are used to store data. It is from these relational objects that you run queries after the warehouse has been created. Relational objects include tables, views, materialized views, and sequences. (Contrast with: dimensional object.)
remote database
A database other than your default database, which may reside on a remote computer; in particular, one that you reference in the CONNECT, COPY, and SQL*Plus commands.
repository
A metadata store; the repository environment contains the complete set of a business's metadata.
restore metadata
The act of importing archived metadata into the current Design Repository using the Metadata Loader (MDL) utility. Restoring metadata creates an additional project on the navigation tree and will not overwrite existing objects. (See also: archive metadata, import metadata.)
rollback
To discard pending changes made to the data in the current transaction using the SQL ROLLBACK command. (See also: commit.)
The basic unit for the processing of data in any mapping. A row is a set of attributes or values pertaining to one entity or record in a table. It is a collection of column information corresponding to a single record. A row has a structure and is defined by attributes, where each attribute is given a name and datatype, and length, scale, and precision.
row based
Operating mode option. Row based mode allows for the maximum amount of runtime auditing. A mapping that runs in row-based mode will process data from a source record by record. (Contrast with: set based.)
A row set consists of zero or more rows of structured data brought into or emerging from an operator in a mapping. A mapping defines how row sets are extracted from a source, transformed, and loaded into a target using operators. The number of rows in a row set is called the cardinality of that row set.
runtime environment
Refers to post-deployment environments. This is the location where objects are deployed. The Runtime Repository stores all data about deployments and runtime environments.
Runtime Platform Service (RTPS)
The server-side component of Oracle Warehouse Builder software that provides execution and deployment services. In order for you to be able to run these services, the Runtime Platform Service must be active. The Runtime Platform Service manages the execution of mappings and process flows from within Warehouse Builder and ensures that all execution and deployment audit data is stored in a Runtime Repository. For remote executions, it connects to the Oracle Enterprise Manager (OEM) Management Server. The Runtime Platform Service is invoked through a database job that is automatically started when the database is started and shut down when the database is shut down.
Runtime Repository
The Oracle Warehouse Builder repository that stores all of the deployment and execution data. This repository is created using the Runtime Assistant. (Contrast with: Design Repository.)
Collection of related database objects, including logical structures such as tables, views, sequences, stored procedures, synonyms, indexes, clusters, and database links. A schema is owned by a database user and has the same name as that user; relational schemas are grouped by database user ID. (See also: snowflake schema, star schema.)
In Oracle Warehouse Builder architecture, a Second Class Object (SCO) represents a dependent object component. An SCO is always owned by another object, and can, in turn, own objects itself. For example, the First Class Object MAPPING contains Second Class Object MAPPING_OPERATOR, which contains ATTRIBUTES. Other examples of SCOs include COLUMN, FOREIGN_KEY, and all the mapping operators.
As a rule of thumb for those accessing Warehouse Builder through the graphic user interface, Second Class Objects can only be manipulated through a First Class Object. Similarly, users who access Warehouse Builder through OMB Plus can only manipulate Second Class Object definitions through a command against a First Class Object.
(See also: First Class Object (FCO), Third Class Object).
semi-additive
Describes a fact/measure that can be summarized through addition along some, but not all, dimensions. Examples include Headcount and On Hand Stock. (Contrast with: additive, nonadditive.)
A database schema object that is a series of sequential, generated numbers. Oracle stores sequences as rows in a single data dictionary table in the SYSTEM tablespace. A sequence definition indicates general information: the name of the sequence, whether it ascends or descends, the interval between numbers, and other information. In Warehouse Builder architecture, a sequence is a First Class Object (FCO).
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.
service name
A service name is a short, convenient name mapped to a network address contained in a TNS connect descriptor. Users need only know the appropriate service name to make a TNS connection. (See also: tnsnames.ora.)
set based
Operating mode option. Enables Warehouse Builder to insert all data in a single SQL command. Using set based mode increases the speed of DML operations when the data is clean and does not require extensive auditing. (Contrast with: row based.)
The short name is a unique identifier that is used as the root name for all related objects created in Oracle Warehouse Builder.
signature
A compact definition of a Warehouse Builder metadata object that contains just enough information about the object to perform a difference analysis. (See also: signature snapshot.)
signature snapshot
A metadata snapshot that captures signature information only. A signature snapshot can be used to generate comparison reports between the snapshot and the current repository object or another snapshot. (Contrast with: full snapshot.)
slowly changing dimension (SCD)
This is a dimension created to manage both current and historical data over time in a data warehouse. It is considered and implemented as one of the most critical ETL tasks in respect to keeping history of dimension records.
A type of star schema in which the dimension tables are partly or fully normalized. (See also: normalize.)
Contains the integrators currently installed for Oracle Warehouse Builder. Accessed through the Administration environment.
A database, application, file, or other storage facility from which the data in a mapping is derived.
source operator
An operator that serves as a data source in a mapping. A mapping depicts data extraction from a source operator, transformation using one data flow operator or more, and loading to a target operator. Examples of source operators include the Table operator, the Flat File operator, and the External Table operator.
SQL*Loader
An Oracle tool used to load data from operating system files into Oracle database tables. It is the most efficient way to load large amounts of data. (See also: Structured Query Language (SQL).)
SQL*Plus
Oracle tool used to execute Structured Query Language (SQL) statements against an Oracle database. Oracle SQL includes many extensions to the ANSI/ISO standard SQL language. (See also: PL/SQL.)
A relational schema whose design represents a multidimensional data model. The star schema consists of at least one fact table and at least one dimension table. The tables are related through foreign keys. (See also: snowflake schema.)
Structured Query Language (SQL)
Structured Query Language, or SQL, is an industry-standard programming language developed specifically to support access to a relational database. Users describe in SQL what they want done, and the SQL language compiler automatically generates a procedure to navigate the database and perform the desired task. The general characteristics of the SQL language are:
It supports operations on sets of data, as opposed to row-by-row processing.
It can access data independently of the data's physical location
It is non-procedural. In other words, it only describes the data to be retrieved, not the method by which the data is to be retrieved.
Oracle Database database supports SQL and PL/SQL. (See also: SQL*Plus.)
subject area
A classification system that represents and distinguishes parts of an organization or areas of knowledge. A data mart is often developed to support a subject area such as sales, marketing, or geography.
surrogate key
A unique primary key that is generated by an RDBMS. This key is not derived from any data in the database and its only significance is to act as the primary key. In Oracle Warehouse Builder, the Sequence mapping operator can be used to generate this type of key. (See also: sequence.)
synchronization
A method used to update object definitions with the changes committed by other users in a multiuser environment. The objects displayed in the navigation tree are synchronized with the object definitions in the repository. (See also: commit.)
SYS username
One of two standard DBA usernames automatically created with each database (the other is the SYSTEM username). The Oracle user SYS is created with the password MANAGER.
SYSDBA
A special database administration role that contains all system privileges with the ADMIN OPTION, and the SYSOPER system privilege. SYSDBA also permits CREATE DATABASE actions and time-based recovery. (See also: SYSOPER.)
SYSOPER
A special database administration role that permits a database administrator to perform STARTUP, SHUTDOWN, ALTER DATABASE OPEN/MOUNT, ALTER DATABASE BACKUP, ARCHIVE LOG, and RECOVER, and includes the RESTRICTED SESSION privilege. (See also: SYSDBA.)
system identifier (SID)
A unique name for an Oracle instance. To switch between Oracle databases, users must specify the desired system identifier. The system identifier is included in the CONNECT DATA parts of the connect descriptors in a tnsnames.ora file, and in the definition of the network listener in the alistener.ora file.
SYSTEM tablespace
The SYSTEM tablespace differs from other tablespaces in that all data files contained in the tablespace must be online for Oracle to function. If a media failure affects one of the datafiles in SYSTEM, then you must mount the database and recover.
SYSTEM username
One of two standard database administrator usernames automatically created with each database. (The other username is the SYS username.) The Oracle user SYSTEM is created with the password MANAGER. The SYSTEM username is the preferred username for database administrators to use for database maintenance.
The basic unit of storage in a relational database management system (RDBMS). A table represents entities and relationships, and consists of one or more units of information (rows), each of which contains the same kinds of values (columns). Each column is given a column name, a datatype (such as CHAR, NCHAR, VARCHAR2, NVARCHAR2, DATE, or NUMBER), and a width (the width may be predetermined by the datatype, as in DATE). Once a table is created, valid rows of data can be inserted into it. Table information can then be queried, deleted, or updated. To enforce defined business rules on a table's data, integrity constraints and triggers can also be defined for a table. In Warehouse Builder architecture, a table is a First Class Object (FCO). (See also: row, column.)
tablespace
A database storage unit that groups related logical structures together. A database is divided into one or more logical storage units called tablespaces. Tablespaces are divided into logical units of storage called segments, which are further divided into extents.
Holds the intermediate or final results of any part of the extraction, transformation, and loading (ETL) process. The target of the entire ETL process is often the data warehouse.
target operator
An operator that serves as a data target in a mapping. A mapping depicts data extraction from a source operator, transformation using one data flow operator or more, and loading to a target operator. Examples of target operators include the Table operator and the Flat File operator.
temporary (TEMP) tablespace
The tablespace of temporary tables or indexes created during the processing of a SQL statement.
Third Class Object
In Oracle Warehouse Builder architecture, Third and Fourth Class objects are relative rankings of objects owned by other objects. These refer only to objects whose ownership spans several layers. For example, INDEX_COLUMN is a Second Class Object in the scenario where a DIMENSTION_TABLE (which is a First Class Object) owns INDEX_COLUMN. However, INDEX_COLUMN becomes a Third Class Object in the scenario where the First Class Object CUBE_TABLE owns the Second Class Object INDEX, which in turn owns INDEX_COLUMN.
(See also: First Class Object (FCO), Second Class Object (SCO).)
tnsnames.ora
A file that contains connect descriptors mapped to net service names. The file may be maintained centrally or locally, for use by all or individual clients. (See also: service name, client.)
Transfer Wizard
The Oracle Warehouse Builder utility for synchronizing, integrating, and using metadata that is stored in the Design Repository in a variety of business intelligence tools. Metadata can be imported and exported using a bridge. Metadata can also be exchanged with OMG files, Oracle Discoverer, Oracle Express, ERwin, Predesignate, and Oracle Database OLAP Server.
transaction
In the context of databases: A logical unit of work that comprises one or more SQL statements executed by a single user. All statements in a transaction are committed or rolled back together. According to the ANSI/ISO SQL standard, with which Oracle is compatible, a transaction begins with the user's first executable SQL statement. A transaction ends when it is explicitly committed or rolled back by the user. (See also: Online Transactional Processing (OLTP), commit, rollback.)
In the context of data warehousing concepts: The lowest grain of a business activity. Examples include: a bank deposit, an inventory movement of a single item, and a retail sale. OLTP systems are used to process transactions, whereas OLAP systems are used to analyze transactional data at a higher level. (See also: Online Transactional Processing (OLTP), Online Analytical Processing (OLAP).)
The process of manipulating data. Any manipulation beyond copying is a transformation. Examples include cleansing, aggregating, and integrating data from multiple source objects. In Warehouse Builder architecture, a transformation is a First Class Object (FCO).
Stores the reusable formulas for the transformation of data as it moves between source and target objects.
transition
In a process flow, transitions indicate the sequence and conditions in which activities occur in the process flow. You can use transitions to execute an activity based on the completion state of the preceding activity.
transparent gateway
Software product that allows SQL-based applications to access relational and non-relational data sources as if they were an Oracle database.
unbound object
A mapping object operator that is not connected to an object defined in the Design Repository. (Contrast with: bound object.)
unpivot
In a mapping, the Unpivot operator converts multiple input rows into one output row. It enables you to extract from a source once and produce one row from a set of source rows that are grouped by attributes in the source data. (See also: pivot.)
user-defined properties (UDP)
To enhance the metadata for your unique needs, Oracle Warehouse Builder enables you to create additional properties for objects. You can create user-defined properties for any object type on the navigation tree. User-defined properties typically store additional business, design, or versioning information for objects. Any user-defined properties must be prefixed with UDP_.
user interface (UI)
The combination of menus, screens, keyboard commands, mouse clicks, and command language that defines how a user interacts with a software application. Oracle Warehouse Builder offers a graphic user interface, as well as a scripting interface in Oracle MetaBase Plus (OMB Plus), and some command-line and SQL extensions.
username
The name by which a user is known to the Oracle server and to other users. Every username is associated with a password, and both must be entered to connect to an Oracle database.
view
A view can be thought of as a "stored query" with a custom-tailored presentation of data from one or many tables. A view does not actually contain or store data, but derives data from the base tables on which it is based. Like tables, views can be queried, updated, inserted into, and deleted from, with some restrictions. All operations performed on a view affect the base tables of the view. In Warehouse Builder architecture, a view is a First Class Object (FCO). (See also: materialized view.)
warehouse administrator
The warehouse administrator is the information specialist who manages the warehouse database and warehouse management applications. For example, the warehouse administrator would be responsible for managing and monitoring periodic updates of the warehouse database. (See also: data warehouse.)
watch
A point in a data flow that is used during a debug session to monitor the data that is passing through or has already passed through a particular operator.
