“Oracle Retail Data Model Implementation and Operations Guide Release 11.3.2-144 中文版”

oracle

需积分: 5 139 浏览量更新于2023-11-24 收藏 3.38MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

资源详情

资源推荐

Before You Begin Customizing the Oracle Retail Data Model

1-4 Oracle Retail Data Model Implementation and Operations Guide

Before You Begin Customizing the Oracle Retail Data Model

Before you begin customizing Oracle Retail Data Model, ensure the following teams

and committees exist:

■ Data warehouse governance steering committee. This steering committee has the

responsibilities outlined in "Responsibilities of a Data Warehouse Governance

Committee" on page 1-5.

■ Implementation team. This team consists of IT engineers who have the expertise

outlined in "Prerequisite Knowledge for Implementors" on page 1-4. This team has

the responsibilities outlined in "Steps for Implementing an Oracle Retail Data

Model Warehouse" on page 1-3.

■ Fit-gap analysis team. This team consists of business analysts who can identify the

business requirements and scope of the Oracle Retail Data Model and at least

some engineers in the Implementation team. Business members of this team must

understand logical data modeling so that they can evaluate what changes must be

made to the foundation and access layers of the physical model. This team has the

responsibilities outlined in "Performing Fit-Gap Analysis for Oracle Retail Data

Model" on page 1-10.

After these teams and committees are formed:

■ Discuss the approach and determine the involvement and roles of every party

involved in the customization (for example, business and IT).

■ Agree on the scope of the project (that is, agree on what new data must be in the

data warehouse and why it is needed).

■ Agree on the timing and the working arrangements.

Prerequisite Knowledge for Implementors

As outlined in "Oracle Products That Make Up Oracle Retail Data Model" on page 1-2,

the Oracle Retail Data Model uses much of the Oracle stack. Consequently, to

successfully implement the Oracle Retail Data Model, the implementation team needs:

■ Experience performing information and data analysis and data modeling.

(Experience using Oracle SQL Developer Data Modeler, is a plus.)

■ An understanding of the Oracle technology stack, especially data warehouse

(Database, Data Warehouse, OLAP, Data Mining, Warehouse Builder, Oracle

Business Intelligence Suite Enterprise Edition)

■ Hands-on experience using:

■ Oracle Database

■ PL/SQL

■ SQL DDL and DML syntax

■ Analytic Workspace Manager

■ Oracle SQL Developer Data Modeler

Note: Keep 'clean' copies of the components delivered with Oracle

Retail Data Model. This is important when upgrading to later versions

of Oracle Retail Data Model.

Before You Begin Customizing the Oracle Retail Data Model

Introduction to Oracle Retail Data Model Customization 1-5

■ Oracle Business Intelligence Suite Enterprise Edition Administrator, Answers,

and Dashboards

■ One implementation team member is familiar or has training with Oracle Retail

Data Model, or the team engages a partner with Oracle Retail Data Model

implementation experience.

Responsibilities of a Data Warehouse Governance Committee

Governance is of concern to any enterprise, executive team or individual with an

interest in the processes, standards, and compliance. It is even more important to

organizations that have invested in data warehousing.

Data warehouse governance occurs within the context of overall IT governance. It

provides the necessary policies, process and procedures, which must be clearly

communicated to the entire corporation, from the IT employees to the front-end

operational personnel.

Before you customize Oracle Retail Data Model, setup a data warehouse governance

steering committee if one does not exist. The role of this steering committed is to

oversee the data warehouse to provide an environment that reaches across the

enterprise and drives the best business value.

Data Warehouse Governance Committee: Overall Responsibilities

The data warehouse governance steering committee sets the direction and is

responsible for the governance framework, including the following areas:

■ The entire data warehouse life cycle

■ The data to process and the data to make available to end-users

■ The minimum quality criteria for the data that is available to end users and how to

measure and analyze these criteria against the quality of the data that is the source

data for the data warehouse.

■ The business goals of the organization to apply core information from the data

warehouse.

■ The policies, procedures, and standards for data resources and data access.

■ The life cycle of data warehouse component management.

Data Warehouse Governance Committee: Data Governance Responsibilities

The more detailed focus in data warehouse governance is data governance. Data

governance tasks include:

■ Approving the data modeling standards, metadata standards and other related

standards. This includes determining a metadata strategy as discussed in

"Managing Metadata for Oracle Retail Data Model" on page 1-6' and identifying

the data modeling tools to use that support these standards.

■ Determining the data retention policy.

■ Designing a data access policy based on legal restrictions and data security rules.

■ Designing a data backup strategy that aligns with the impact analysis to the

business unit.

■ Monitoring and reporting on data usage, activity, and alerts.

Managing Metadata for Oracle Retail Data Model

1-6 Oracle Retail Data Model Implementation and Operations Guide

Managing Metadata for Oracle Retail Data Model

Metadata is any data about data and, as such, is an important aspect of the data

warehouse environment. Metadata allows the end user and the business analyst to

navigate through the possibilities without knowing the context of the data or what the

data represents.

Metadata management is a comprehensive, ongoing process of overseeing and

actively managing metadata in a central environment which helps an enterprise to

identify how data is constructed, what data exists, and what the data means. It is

particularly helpful to have good metadata management when customizing Oracle

Retail Data Model so that you can do impact analysis to ensure that changes do not

adversely impact data integrity anywhere in your data warehouse.

■ Metadata Categories and Standards

■ Working with a Metadata Repository

■ Browsing the Metadata Repository Supplied With Oracle Retail Data Model

■ Using the Metadata Generation Packages

■ Using Oracle Warehouse Builder with the Oracle Retail Data Model

Metadata Categories and Standards

Metadata is organized into three major categories:

■ Business metadata describes the meaning of data in a business sense. The

business interpretation of data elements in the data warehouse is based on the

actual table and column names in the database. Gather this mapping information

and business definition and rules information into business metadata.

■ Technical metadata represents the technical aspects of data, including attributes

such as data types, lengths, lineage, results from data profiling, and so on.

■ Process execution metadata presents statistics on the results of running the ETL

process itself, including measures such as rows loaded successfully, rows rejected,

amount of time to load, and so on.

Since metadata is so important in information management, many organizations

attempt to standardize metadata at various levels, such as:

■ Metadata Encoding and Transmission Standard (METS). A standard for encoding

descriptive, administrative, and structural metadata regarding objects within a

digital library.

■ American National Standards Institute (ANSI). The organization that coordinates

the U.S. voluntary standardization and conformity-assessment systems.

■ International Organization for Standardization (ISO). The body that establishes,

develops, and promotes standards for international exchange.

■ Common Warehouse Metamodel (CWM). A specification, released and owned by

the Object Management Group, for modeling metadata for relational,

non-relational, multi-dimensional, and most other objects found in a data

warehousing environment.

When you implement your metadata management solution, reference your data

warehouse infrastructure environment and make the decision which standard to

follow.

Managing Metadata for Oracle Retail Data Model

Introduction to Oracle Retail Data Model Customization 1-7

Working with a Metadata Repository

You manage metadata using a Metadata Repository. At the highest level, a Metadata

Repository includes three layers of information. The layers are defined in the

following order:

1. A Physical layer. This metadata layer identifies the source data.

2. A Business Model and Mapping layer. This metadata layer organizes the physical

layer into logical categories and records the appropriate metadata for access to the

source data.

3. The Presentation layer. This metadata layer exposes the business model entities for

end-user access.

The first step in creating a Metadata Repository is to scope your metadata

management needs by:

■ Identifying the metadata consumers. Typically, there are business consumers and

technical consumers.

■ Determine the business and technical metadata requirements.

■ Aligning metadata requirements to specific data elements and logical data flows.

Then:

■ Decide how important each part is.

■ Assign responsibility to someone for each piece.

■ Decide what constitutes a consistent and working set of metadata

■ Determine where to store, backup, and recover the metadata.

■ Ensure that each piece of metadata is available only to those people who need it.

■ Quality-assure the metadata and ensure that it is complete and up to date.

■ Identify the Metadata Repository to use and how to control that repository from

one place

After creating the metadata definitions, review your data architecture to ensure you

can acquire, integrate, and maintain the metadata.

As the data is updated in your data warehouse day by day, you need to update the

Metadata Repository. To change business rules, definitions, formulas or process

especially when customizing the Oracle Retail Data Model, your first step is to survey

the metadata and do an impact analysis to list all of the attributes in the data

warehouse environment that would be affected by a proposed change.

Browsing the Metadata Repository Supplied With Oracle Retail Data Model

To customize the Oracle Retail Data Model model, you must understand the

dependencies among Oracle Retail Data Model components, especially how the report

KPIs are mapped to the physical tables and columns and how that data has been

transformed through the intra-ETL.

Oracle Retail Data Model provides a tool called the "Oracle Retail Data Model

Metadata" browser that helps you discover these dependencies. When you install

Oracle Retail Data Model with and the sample reports, the metadata browser is

delivered as a Dashboard.

Managing Metadata for Oracle Retail Data Model

1-8 Oracle Retail Data Model Implementation and Operations Guide

There are four tabs (reports) in the Oracle Retail Data Model Metadata browser:

■ Measure-Entity tab: Business Areas and Measures Attributes and Entities

■ Entity-Measure tab: Entity to Attribute Measures

■ Program-Table tab

■ Table-Program tab

Measure-Entity tab: Business Areas and Measures Attributes and Entities

On the Measure-Entity tab the measure descriptions, computational formulas with

physical columns, physical tables, and corresponding entities can be viewed by

Business Area.

To browse the data, select the business area and measure description that you are

interested in.

Entity-Measure tab: Entity to Attribute Measures

The Entity-Measure tab displays the measures supported by the entities and how they

are calculated. You can discover information about particular entities and attributes.

For example, take the following steps to learn more about an entity:

1. Select the entity.

2. Click GO.

Program-Table tab

The Program-Table tab displays the input and output tables used in the selected

programs. For example, take the following steps to learn more about intra-ETL

mappings:

1. Select the program type (that is, intra-ETL or report) and program name for

showing particular report or intra-ETL information.

2. Select GO.

Table-Program tab

The Table-Program tab lists the Programs used by a given table and whether that table

is an input or output, or both, of that program.

To discover what reports use a particular table, you must move a particular table from

the right pane to the left (Selected) pane.

For example, to see the reports that use a particular table, take the following steps:

1. In the right pane of the Table-Program tab, select the table.

2. Move the table to the Selected list on the left by clicking on < (left arrow), and click

OK.

3. Select GO.

The reports for the selected table are displayed.

See: Oracle Retail Data Model Installation Guide for more information

on installing the sample reports and deploying the Oracle Retail Data

Model RPD and webcat on the Business Intelligence Suite Enterprise

Edition instance.

剩余143页未读，继续阅读

weixin_40191861_zj

粉丝: 69
资源: 1万+

会员权益专享

“Oracle Retail Data Model Implementation and Operations Guide Re...

会员权益专享

最新资源

“Oracle Retail Data Model Implementation and Operations Guide Re...

Oracle Airlines Data Model Implementation and Operations Guide 1

Oracle Communications Data Model Implementation and Operations G

Oracle Retail Data Model Reference Release 11.3.2-726

外部表oracle_loader和oracle_datadump区别

oracle.dataaccess.dll oracle 10g 下载

oracle.dataaccess.dll x64 下载

oracle imp data only

Oracle rename datafile

Oracle 19c Data Guard物理备库搭建

oracle.dataaccess.dll

oracle data modeling and relational database design

oracle data access components for oracle server

Navicat 15for Oracle

oracle xmltype

oracle data source

oracle.manageddataaccess 19 下载

oracle DBMS_DATAPUMP

Oracle Data Guard

oracle data provider for .net下载,Oracle Data Provider for .NET

sqlsugar oracleclob类型批量插入到数据库

会员权益专享

最新资源