Which of the following are examples of global consistency check all that apply

Repository metadata must pass a consistency check before you can make the repository available for queries.

The Consistency Check Manager lets you enable and disable rules for consistency checks, find and fix inconsistent objects, and limit the consistency check to specific objects. You can also use the validaterpd utility to check the validity of all metadata objects.

Note:

The Model Check Manager identifies modeling problems that affect Oracle BI Summary Advisor and aggregate persistence performance and results. Run Model Check Manager before running Oracle BI Summary Advisor or the Aggregate Persistence Wizard. See .

This section contains the following topics:

About the Consistency Check Manager

The Consistency Check Manager checks the validity of your repository to ensure that it can load at run time, and to identify any syntax or semantic errors that may cause queries to fail.

Running a consistency check might result in updates to your repository metadata when you run the Global Consistency Check or the Check Consistency option against an object. You must save the repository when using those options. For example, invalid objects are deleted during Consistency Checks. This behavior might result in deleted expressions and filters on logical table sources and logical columns. Invalid references can occur when objects were deleted in the Physical layer without properly accounting for the references in the Business Model and Mapping layer objects.

The Show Consistency Check option is read-only and doesn't implement changes in the repository.

The Consistency Check Manager doesn't check the validity of objects outside the metadata using the connection. It only checks the consistency of the metadata and not the mapping to the physical objects outside the metadata. If the connection isn't working or objects were deleted in the database, the Consistency Check Manager doesn't report these errors.

The Consistency Check Manager identifies application roles that defined in the Administration Tool, but that weren't added to the policy store. Messages about placeholder application roles only appear when you perform a consistency check in online mode. The set of consistency check messages returned for your repository might contain different results depending on whether you've opened the repository in offline or online mode.

If you use lookup tables to store translated field names with multilingual schemas, the consistency checking rules are relaxed for the lookup tables. See Localize Oracle Analytics Server in Administering Oracle Analytics Server.

The consistency checker returns the following types of messages:

• Errors

  These messages describe errors that you must fix. Use the information in the message to correct the inconsistency, then run the consistency checker again. The following is an example of an error message:

  [38082] Type of Hierarchy '"0RT_C41"..."0RT_C41/MDF_BW_Q02"."Product Hierarchy for Material MARA"' in Cube Table '"0RT_C41"..."0RT_C41/MDF_BW_Q02"' needs to be set.
  

  If you disable an object and it's inconsistent, a message is displayed, asking if you want to make the object unavailable for queries.

• Warnings

  These messages indicate conditions that you might need to fix. For example, you might receive a warning message about a disabled join that was intentionally disabled to eliminate a circular join condition. Other messages may warn of inconsistent values, or feature table changes that don't match the defaults. The following is an example of a warning message:

  [39024] Dimension '"Paint"."MarketDim"' has defined inconsistent values in its levels' property 'Number of elements'.

Note:

After upgrading from a previous software version and checking the consistency of your repository, you might notice messages that you hadn't received in previous consistency checks. The inconsistencies are the result of issues that were undetected before the upgrade, not new errors.

Run the Consistency Check Manager

Use the Oracle BI Administration Tool to run the consistency checker on all of the repository objects, on a specific physical database or data source, physical database, business model, or subject area.

You can view the Consistency Check Manager’s results without performing a global consistency check, by selecting the Show Consistency Checker from Tools menu. If you've checked consistency in the current session, the messages from the last check appear in the Messages pane.

If a disabled object is inconsistent, you're prompted to make the object unavailable for queries. If an object isn't consistent, the Consistency Check Manager appears and displays a list of messages.

1. In the Administration Tool, open a repository.
2. Do one of the following:
   • From the File menu, select Check Global Consistency , then select Report Only. This option reviews all of the objects in the repository and generates a list of errors.
   • From the File menu, select Check Global Consistency , then select Auto-fix. This option reviews all of the objects in the repository and automatically fixes any errors where possible. When this option is chosen, a list of all fixes is logged to the following file: orainst\servers\obis1\logs\username_NQSAdminTool.log.
   • In the repository, select an object, right-click, and select Check Consistency. This option reviews all of the objects in the repository and automatically fixes any errors where possible. When this option is chosen, a list of all fixes is logged to the following file: orainst\servers\obis1\logs\username_NQSAdminTool.log

Review the output. If you've chosen to automatically fix problems in the repository, you must save the fixed repository. If your repository is read-only the auto-fix option is disabled and the right-click Check Consistency option generates a report without making fixes.

Use the validaterpd Utility to Check Repository Consistency

You can use the Oracle BI Server validaterpd utility to check the validity of all metadata objects in a repository.

Running this utility performs the same validation checks as the Consistency Check Manager in the Administration Tool.

The validaterpd utility is available on both Windows and Linux systems. You can run validaterpd against a binary Oracle BI repository file, against an XML file based on the Oracle BI Server XML API, or against a set of MDS XML documents.

You must provide the full path names to your repository files, both the input files and the output files, if they're located in a different directory.

The location of the validaterpd utility is:

[39024] Dimension '"Paint"."MarketDim"' has defined inconsistent values in its levels' property 'Number of elements'.

Using validaterpd with the

[39024] Dimension '"Paint"."MarketDim"' has defined inconsistent values in its levels' property 'Number of elements'.

[39024] Dimension '"Paint"."MarketDim"' has defined inconsistent values in its levels' property 'Number of elements'.

Syntax

The validaterpd utility takes the following parameters:

validaterpd {-R repository_name | -I input_file_pathname | 
-D MDS_XML_document_directory} [-P repository_password] {-O output_txt_file_name |
-C output_csv_file_name | -X output_xml_file_name} [-8] [-F fixed_rpd_name|-E] [-S] [-B]

Where:

repository_name is the name and path of the binary Oracle BI repository file that you want to validate.

input_file_pathname is the name and path of the XML input file that you want to validate.

MDS_XML_document_directory is the location of the input MDS XML documents.

repository_password is the password for the repository that you want to validate.

The repository_password argument is optional. If you don't provide the password argument, you're prompted to enter the password when you run the command. To minimize the risk of security breaches, Oracle recommends that you don't provide password arguments either on the command line or in scripts. The password argument is supported for backward compatibility only, and is removed in a future release. For scripting purposes, you can pass the password through standard input.

output_txt_file_name is the name and path of a text file where the validation results are recorded.

output_csv_file_name is the name and path of a csv file where the validation results are recorded.

output_xml_file_name is the name and path of an XML file where the validation results are recorded.

Specify

[39024] Dimension '"Paint"."MarketDim"' has defined inconsistent values in its levels' property 'Number of elements'.

[39024] Dimension '"Paint"."MarketDim"' has defined inconsistent values in its levels' property 'Number of elements'.

[39024] Dimension '"Paint"."MarketDim"' has defined inconsistent values in its levels' property 'Number of elements'.

[39024] Dimension '"Paint"."MarketDim"' has defined inconsistent values in its levels' property 'Number of elements'.

validaterpd {-R repository_name | -I input_file_pathname | 
-D MDS_XML_document_directory} [-P repository_password] {-O output_txt_file_name |
-C output_csv_file_name | -X output_xml_file_name} [-8] [-F fixed_rpd_name|-E] [-S] [-B]

Specify

validaterpd {-R repository_name | -I input_file_pathname | 
-D MDS_XML_document_directory} [-P repository_password] {-O output_txt_file_name |
-C output_csv_file_name | -X output_xml_file_name} [-8] [-F fixed_rpd_name|-E] [-S] [-B]

Specify

validaterpd {-R repository_name | -I input_file_pathname | 
-D MDS_XML_document_directory} [-P repository_password] {-O output_txt_file_name |
-C output_csv_file_name | -X output_xml_file_name} [-8] [-F fixed_rpd_name|-E] [-S] [-B]

validaterpd {-R repository_name | -I input_file_pathname | 
-D MDS_XML_document_directory} [-P repository_password] {-O output_txt_file_name |
-C output_csv_file_name | -X output_xml_file_name} [-8] [-F fixed_rpd_name|-E] [-S] [-B]

Specify

validaterpd {-R repository_name | -I input_file_pathname | 
-D MDS_XML_document_directory} [-P repository_password] {-O output_txt_file_name |
-C output_csv_file_name | -X output_xml_file_name} [-8] [-F fixed_rpd_name|-E] [-S] [-B]

Specify

validaterpd {-R repository_name | -I input_file_pathname | 
-D MDS_XML_document_directory} [-P repository_password] {-O output_txt_file_name |
-C output_csv_file_name | -X output_xml_file_name} [-8] [-F fixed_rpd_name|-E] [-S] [-B]

Examples

The following example generates an output file called results.txt that contains validation information for the repository called repository.rpd, and saves a fixed version to fixed_repository.rpd:

validaterpd -R repository.rpd -O results.txt -F fixed_repository.rpd
Give password: my_rpd_password

The following example generates an output file called results.csv that contains validation information for the repository contained in the MDS XML documents located at C:\MDS_dir:

validaterpd -D C:\MDS_dir -C results.csv
Give password: my_rpd_password

Common Consistency Check Messages

Review the table to get information about some commonly seen consistency check warnings and errors.

The table provides a partial list only and doesn't show all possible warnings and errors.

Validation Rule ExampleTypeDescription

[14031] The content filter of a source for logical table: FACT_TABLE_NAME references multiple dimensions.

Error

The given logical table has a logical table source with a WHERE clause filter that references multiple dimensions. A WHERE clause with multiple dimensions is invalid.

[38126] 'Logical Table' '"Technology - WFA"."Fact WFA WO "' has name with leading or trailing space(s).

Error

Identifies an object with leading or trailing spaces in the object name.

Repository objects can no longer have leading or trailing spaces in their names. Leading and trailing spaces in object names can cause query and reporting issues.

[38012] Logical column DIM_Start_Date.YEAR_QUARTER_NBR doesn't have a physical data type mapping, nor is it a derived column.

[38001] Logical column DIM_Start_Date.YEAR_QUARTER_NBR has no physical data source mapping.

Error

Logical columns that aren't mapped to any logical table source are reported as consistency errors, because the logical table source mappings are invalid and would cause queries to fail.

Both of the given validation rules are related to the same issue.

[39062] Initialization Block 'Authorization' uses Connection Pool '"My_DB".

"My_CP"' which is used for report queries. This may impact query performance.

Warning

Indicates that the same connection pool is being used for both queries and for initialization blocks. This configuration isn't recommended. Instead, create a dedicated connection pool for initialization blocks. Otherwise, query performance might suffer, or user logins might stop responding if authorization initialization blocks can't run.

[39028] The features in Database 'MyDB' don't match the defaults. This can cause query problems.

Warning

Some database feature defaults were changed in this release of Oracle Analytics Server. Unless you've specific customizations to your feature set, it's recommended that you reset your database features to the new defaults.

[39003] Missing functional dependency association for column: DIM_Offer_End_Date.CREATE_DT.

Warning

This warning indicates that the given logical table source has irrelevant tables added that aren't used in any mapping. This situation shouldn't cause any errors.