Common Consistency Check Messages

Use this topic to help you understand and fix some of the most common consistency check warnings and errors.

This topic provides a partial list of check consistency messages, and doesn't describe all possible warnings and errors.

If the standard consistency checks don't meet your model's unique validation requirements, you can create custom consistency check rules specific to your model. See About Custom Consistency Check Rules.

Error or Warning Example	Error or Warning	More Information
[14031] The content filter of a source for logical table: FACT_TABLE_NAME references multiple dimensions.	Error	Indicates that the 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. Leading 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	Indicates that logical columns aren't mapped to any logical table source. These mappings are invalid and cause queries to fail. Both of the validation rules relate 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 used for both queries and for initialization blocks. This configuration isn't recommended. To fix this issue, create a dedicated connection pool for initialization blocks. Otherwise, query performance may suffer, or user logins can 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	Indicates that some database feature defaults were changed in this release of Oracle Analytics. 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	Indicates that the given column is only mapped to logical table sources that are disabled. This warning prompts you to decide if you want to use the default behavior.
[39059] Logical dimension table MY_DIM has a source MY_DIM_DAILY at level Daily that joins to a higher level fact source MY_FACT_SUM.MTHLY_SUM	Warning	Indicates that the fact logical table source has an aggregate grain set in this dimension, but either no join was found that connects to any logical table source in this dimension or an invalid join was found. This means that either no join exists at all, or it does exist but is potentially invalid because it connects a higher-level fact source to a lower-level dimensional source. Such joins are potentially invalid because if followed, they might lead to double counting in query results. For example, consider Select year, yearlySales. Even if a join exists between monthTable and yearlySales table on yearId, it shouldn't be used because such a join would overstate the results by a factor of 12 (the number of months in each year). If you get a 39059 warning after upgrading, verify that the join is as intended and doesn't result in incorrect double counting. If the join is as intended, then ignore the 39059 warning.
[39055] Fact table "HR"."FACT - HC Budget" isn't joined to tables in logical dimension "HR"."DIM - HR EmployeeDim". This can cause problems when extracting project(s).	Warning	Indicates that there's a physical join between the given fact and dimension sources, but there isn't a corresponding logical join between the fact table and the dimension table.
[39057] There are physical tables mapped in Logical Table Source ""HR"."Dim - Schedule"."SCH_DEFN"" that aren't used in any column mappings or expressions.	Warning	Indicates that the given logical table source contains tables that aren't used in any mapping. This situation shouldn't cause any errors.