Installation tasks, Establish data warehouse partitioning strategy – Oracle Audio Technologies Retail Data Warehouse 13 User Manual

Page 15

Advertising
background image

Database Installation Guide 7

2

Installation Tasks

It is assumed that Oracle 10g release 2, with appropriate patches, has already been
installed. If not, refer to “Check Database Server Software Requirements” in Chapter 1,
“Preinstallation Tasks” before proceeding.

Note:

Become familiar with the RDW application in a

development environment before setting up a production
system. The following instructions are recommended for
development and test environments only. When
implementing RDW for a production environment, refer to
capacity planning information to determine size
requirements for tablespaces, tables, and indexes. The
installation scripts provided need to be modified
accordingly.

If a database has already been created, it is necessary to review the contents of this
section to determine if all database components have been installed and configured
properly. Also refer to Appendices C and D.

Note

: When running the scripts in this section, the following

errors may be encountered “ORA-04043 object XXXX does
not exist”, “ORA-01432 public synonym to be dropped does
not exist”, “ORA-00942 table or view does not exist”, “ORA-
29833 indextype does not exist”, “ORA-29807 specified
operator does not exist”, “ORA-29931 specified association
does not exist”, and “ORA-29816 object being disassociated
is not present”. These errors can be ignored. The ORA errors
are caused by dropping the objects the script is about to
create.

Establish Data Warehouse Partitioning Strategy

Establish a partitioning strategy before creating compressed datamart and historical
tables in a production environment. In doing so, consider the database size and business
requirements. For example, the amount of history to be held at various levels, and the
various functional areas that might be used should be referenced when determining a
partitioning strategy. Additionally, large non-compressed fact tables should be
partitioned for ease of rolling off history. Refer to the RDW Operations Guide for more
detailed information regarding the partitioning strategy for both compressed and non-
compressed fact tables. Refer to “Oracle® Database Concepts 10g Release 2 (10.2)
Chapter 18 “Partition Tables and Indexes” for further details regarding partitioning
concepts.

Advertising