Skip to content

Validation Rules

Catalog

Mandatory

  1. name
  2. default_connection The specified connection must be available.

Optional

  1. objectID Points to the repository ID of the Semantic Catalog content.

Business Rules

  1. Must have a connection.
  2. Must have a model.
  3. Must have a table.
  4. All models in a catalog must have unique names.

  5. All connections in a catalog must have unique names.

  6. All tables in a catalog must have unique names.

Connection

Mandatory

  1. name The connection name and file name must match.
  2. default_connection The specified connection must be available.

Optional

  1. synonyms. If specified, all synonyms must have unique names.

Model

Mandatory

  1. name The model name and file name must match.
  2. fact The specified fact semantic table must be available.

Optional

  1. connection If specified, the connection must be available. When missing, the catalog default_connection must be specified. TBD: Should it be mandatory?

  2. joins

  3. The to_semantic_table must be available.

  4. The from_fk_columns must be specified.

  5. objectID

Points to the repository ID of the Semantic Model object.

Business Rules

  1. All visible (hide=false) semantic columns in a model must have unique names to enable the model relationship database view to list them.

  2. All hierarchies in a model must have unique names to enable Oracle Analytic View to define them.

Table

Mandatory

  1. name The table name and file name must match.
  2. unique_keys Must be present for tables that play the FK role in joins that the model uses. The fact table in a model does not have to have the unique_keys.

Optional

  1. columns

  2. All columns and metrics must have unique names.

  3. Column expressions can reference database columns and other semantic columns.

  4. metrics

  5. Metric expressions can reference columns and other metrics, but not database columns.

  6. joins

  7. The to_semantic_table must be available.

  8. The from_fk_columns must be specified.

  9. A join adds all semantic columns defined in the FROM semantic table to the TO semantic table. When the FROM semantic table has joins, the same applies. All these columns must have unique names.

  10. levels

Oracle Analytic Views require each ATTRIBUTE DIMENSION to have at least one level. When a semantic table does not define levels, the export bridge creates a level named after the table, with key_columns pointing to its default unique_keys columns, and creates a hierarchy named after the table plus 'hierarchy' with the level.