Skip Headers
Oracle® Retail Predictive Application Server Administration Guide for the Classic Client
Release 14.1
E59120-01
  Go To Table Of Contents
Contents

Previous
Previous
 
Next
Next
 

A Appendix: Curve Administration Guide

This appendix provides details about the utilities used in Curve administration.

curvevalidate

The curvevalidate utility automatically executes during the domain installation, and it can also be run at any time against a master domain or one subdomain. If run against the master domain, it checks the master and all subdomains. If run against a subdomain, it checks the master domain and only the subdomain (not all other subdomains). This function verifies that:

  • Profile and Source intersections and source data are properly defined

  • Profile intersections respect the partition dimension

curvevalidate Usage

curvevalidate -d domainpath [-s]

Table A-1provides descriptions of the arguments used by the curvevalidate utility.

Table A-1 Arguments Used by the curvevalidate Utility

Argument Description

-d domainpath

Indicates the path to the domain.

-s

Sets defaults.

-debug

Causes temporary measures to be retained for debugging purposes.

-h

Displays information about curvebatch in the terminal screen.

-version

Displays version information.

-loglevel

Sets the logger verbosity level. Available verbosity levels are as follows:

  • all

  • profile

  • information

  • warning

  • error

  • none

-noheader

Disables the use of timestamp header.


  1. Each Profile must have at least one Source Level.

  2. For each Profile:

    1. For global domains, all intersections {Data Intersection, Profile Intersection, Stored Intersection, Aggregation Intersection, and Approval Intersection} must be below the partition (not HBI).

    2. Data Intersection (if a data source is specified) must conform to X in {Profile Intersection, Stored Intersection, Aggregation Intersection, and Approval Intersection}.

    3. Profile Intersection must conform to the Stored Intersection.

    4. Aggregation Intersection must conform to the Approval Intersection.

    5. Aggregation Intersection must not be below the Approval Intersection.

    6. Aggregation Intersection must be above the Data Intersection (if data source specified).

    7. If the Aggregation Intersection conforms to Profile Intersection:

      - The Profile Type must not be diff(8).

      - The Aggregation Intersection must be above the Profile Intersection.

      - The Aggregation Intersection must be above the Stored Intersection.

    8. If Aggregation Intersection does not conform to Profile Intersection:

      - The Profile Type must be diff (8).

      - At least one common hierarchy must exist between the Aggregation Intersection and X in {Profile Intersection, Stored Intersection}.

      - For each common non-PROD hierarchy H of Aggregation Intersection and X in {Profile Intersection, Stored Intersection}: Aggregation Intersection's H dimension must not be below X's H dimension.

  3. For each Source Level:

    1. For global domains, all intersections {Profile Intersection, Stored Intersection, and Aggregation Intersection} must be below the partition (not HBI).

    2. Parent Profile's Data Intersection (if data source specified) must conform to X in {Profile Intersection, Stored Intersection, and Aggregation Intersection}.

    3. Profile Intersection must conform to Stored Intersection.

    4. Aggregation Intersection must be above parent Profile's Data Intersection (if data source specified).

    5. If Aggregation Intersection conforms to Profile Intersection:

      - The Profile Type must not be diff(8).

      - The Aggregation Intersection must be above the Profile Intersection.

      - The Aggregation Intersection must be above the Stored Intersection.

    6. If Aggregation Intersection does not conform to Profile Intersection:

      - The Parent Profile Type must be diff (8).

      - There must be at least one common hierarchy between the Aggregation Intersection and X in {Profile Intersection and Stored Intersection}.

      - For each common non-PROD hierarchy H of Aggregation Intersection and X in {Profile Intersection and Stored Intersection}: Aggregation Intersection's H dimension must not be below X's H dimension.

curvebatch

This section provides details about the curvebatch utility.

curvebatch Usage

curvebatch -d domainpath [-level # ] [-debug] | -h | -version

Table A-2 provides descriptions of the arguments used by the curvebatch utility.

Table A-2 Arguments Used by the curvebatch Utility

Argument Description

-d domainpath

Indicates the path to the domain.

-level #

The # signifies the profile ID. When used, a valid profile ID must be provided.

-debug

Causes temporary measures to be retained for debugging purposes.

-h

Displays information about curvebatch in the terminal screen.

-version

Displays version information.

-loglevel

Sets the logger verbosity level. Available verbosity levels are as follows:

  • all

  • profile

  • information

  • warning

  • error

  • none