1. Database Administrator's Guide for Oracle Essbase
  2. Design Rules for Data Load or Dimension Build
  3. Define Load Rules in Essbase Web Interface
  4. Validate Rules

Validate Rules

Essbase validates dimension build rules and data load rules, checking whether all members and dimensions in the rule are mapped to the associated cube outline. Learn what is required to ensure load rules are valid.

Validation cannot ensure that the source data loads properly.

To validate, click Verify in the rule editor.

If the rule is correct, you can perform a data load or dimension build.

If the rule is not valid, see the appropriate topic for each rule type:

Requirements for Valid Data Load Rule Files

For a data load rule file to validate, all of the following questions must be answered “yes.”

  • Is the rule file associated with the correct outline?

  • Does each record in the data source contain only one member from each dimension?

    See Items in a Source of Data.

  • Are all member and dimension names spelled correctly?

  • Are all members enclosed in quotation marks if they contain spaces, numbers, or file delimiters? Are there extra delimiters in the source?

    See Valid Member Fields.

  • Is the member that each data field maps to spelled correctly in the rules file?

    See Change Field Names.

  • Are the file delimiters correctly placed?

    See Valid Delimiters.

  • Is the member in the field name a valid member?

    See Map Fields.

  • Is the dimension name used in only one field (for example, not in a field name and the header)?

    You can map a single data value to only one set of members.

  • Is only one field defined as a data field?

    See Data Fields in the Load Rule.

  • Is the UDA used for sign flipping in the associated outline?

    See Flip Field Signs.

  • If a header is used in the rule, does it contain only valid members that are in the dimensions of the outline?

  • Do field names contain references only to valid members that are in the dimensions of the outline?

Requirements for Valid Dimension Build Rule Files

For a dimension build rule file to validate, all of the following questions must be answered “yes.”

  • Is the rule file associated with the correct outline?

  • Are all member and dimension names spelled correctly?

  • Are all members enclosed in quotation marks if they contain spaces, numbers, or file delimiters? Are there extra delimiters in the source?

    See Valid Member Fields.

  • Are the reference numbers sequential?

    See Set Dimension Build Field Type Information.

  • Are there no repeated generations? Are all generations set to a value of 1 or higher (0 is not not allowed)? Generations cannot be skipped (if there is a generation 2 and 4, there must be a 3). In Regular rules, they must also be in sequential order.

    See Set Dimension Build Field Type Information.

  • Is each field type valid for the build method?

    Set Dimension Build Field Type Information

  • Are all the fields in correct order?

    See Set Dimension Build Field Type Information.

  • Does each child field have a parent field?

  • Do all dimension names exist in the outline or the rule file?

  • Are any dimensions specified in both the header record in the rules file and the header record in the data source?

    Dimensions can be specified in either the header in the rule file or the header in the data source, but not in both.

    See Handle Header Records.