Reg:-nQSError: 1005(metadata consistency warnings)

Hi all,
I tried to modify one report by adding a new column Supplier Account Number. But when I added this column to the report,I am getting this error.Same is the case if I add any column from Dim - Supplier Account to the report.
*State: HY000. Code: 11494. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: Dim - Supplier Account.Supplier Account Number. Please fix the metadata consistency warnings. (HY000)*
Need help
Thanx in advance

RPD issue. Make sure your dim is linked to fact in BMM using complex join

Similar Messages

Metadata Consistency warnings error.....need help

I'm getting this error when i run my reports. I checked in all my files and I'm not seeing any consistency warnings. Can someone tell me why and how i can fix this error?
Odbc driver returned an error (SQLExecDirectW).
Error Details
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: count(HPQC_DEFECT.BG_BUG_ID by [ HPQC_DEFECT.BG_BUG_ID, HPQC_DEFECT.BG_SEVERITY, HPQC_DEFECT.BG_PRIORITY, HPQC_DEFECT.BG_DETECTION_DATE, HPQC_DEFECT.BG_DETECTION_VERSION, HPQC_DEFECT.BG_USER_03, HPQC_DEFECT.BG_USER_05, HPQC_DEFECT.BG_USER_15, HPQC_DEFECT.Closing Date, Project_Dim.DOMAIN, HPQC_DEFECT.Week of Defect Closed Date, hpqc_audit_log_prop_EIT.AU_TIME, hpqc_audit_log_prop_EIT.AP_NEW_VALUE, case when Project_Dim.PROJECT = 'PRODUCT_13_2' then 'Stores' when Project_Dim.PROJECT = 'System_Test_13_2' then 'MOM' when Project_Dim.PROJECT = 'Enterprise_13_2' then 'EIT' else Project_Dim.PROJECT end ] ). Please fix the metadata consistency warnings. (HY000)
SQL Issued: SELECT "Projec Dim".Domain saw_0, case WHEN "Projec Dim".Project = 'PRODUCT_13_2' then 'Stores' WHEN "Projec Dim".Project = 'System_Test_13_2' then 'MOM' WHEN "Projec Dim".Project = 'Enterprise_13_2' then 'EIT' else "Projec Dim".Project end saw_1, COUNT("Defect Facts"."Defect ID") saw_2, "Defect Facts"."Defect ID" saw_3, "Defect Facts".Severity saw_4, "Defect Facts".Priority saw_5, "Defect Facts"."Reported Release (Base)" saw_6, "Defect Facts"."Closing Date" saw_7, "Defect Facts".Status saw_8, "Defect Facts".Type saw_9, RSUM(COUNT("Defect Facts"."Defect ID")) saw_10, "Defect Facts"."Week of Defect Closed Date" saw_11, "Defect Facts"."Testing Type" saw_12, "Defect Facts"."Detected on Date" saw_13, hpqc_audit_log_prop_EIT.AP_NEW_VALUE saw_14, hpqc_audit_log_prop_EIT.AU_TIME saw_15 FROM Defect WHERE ("Defect Facts"."Closing Date" IS NOT NULL) AND ("Projec Dim".Project IN ('System_Test_13_2', 'PRODUCT_13_2', 'Enterprise_13_2')) AND ("Defect Facts"."Reported Release (Base)" IN ('13.2', '13.2 Euphrates')) AND ("Defect Facts"."Testing Type" IN ('System', 'System Test', 'Integration', 'Regression', 'EIT')) AND ("Defect Facts"."Detected on Date" > timestamp '2010-04-01 00:00:00') AND (Audit_Log_Dim.AU_ENTITY_TYPE = 'BUG') AND (hpqc_audit_log_prop_EIT.AP_NEW_VALUE IN ('Cancelled', 'Closed', 'Completed', 'Resolved')) AND (hpqc_audit_log_prop_EIT.AU_TIME = date '2010-04-01') ORDER BY saw_11, saw_4

I was facing this problem for a long time, this came up
1) when there was no link between the columns shown in the report and the dimension against which it is shown. Sol: You need a physical join at the physical layer and also properly define logical joins at the BMM layer.
2) when you use facts for dimensions as well. Sol: you need to make sure all aliases are mapped(in the dimension) as well when you show the data.
3)when content level has not been set correctly.Content level is very important, you need to make sure that the content levels are set properly, make sure that content levels for all the dimensions used in the request that is throwing an error, are set in the Logical Table Source of the fact and are at the correct levels. If you are not sure of any content level then do not set any content level.
4)when I had a duplicate column under different presentation tables. Remove the duplicate.
Thanks
Manoj
Edited by: user13367543 on Jul 27, 2010 12:30 AM

Please fix the metadata consistency warnings error..

Hi Guys,
I am new to OBIEE, When i try to convert a chart view into Pivot table i get th ebelow error.How can i fix this issue?
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 3058399872. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: FILTER(Budget Amount:[DAggr(Fact - Fins - Budget.Budget Amount by [ ] )] USING Dim - GL Account.Group Account Number = 'MKTG PAYROLL'). Please fix the metadata consistency warnings. (HY000)
SQL Issued: SELECT "Time"."Fiscal Quarter" saw_0, "Time"."Fiscal Period" saw_1, "Facts - Budget"."Total Operating Expenses" saw_2, "Facts - Actuals"."Total Operating Expenses" saw_3, "Facts - Budget"."Total Operating Expenses"-"Facts - Actuals"."Total Operating Expenses" saw_4, "Facts - Budget"."Total Operating Expenses YTD" saw_5, "Facts - Actuals"."Total Operating Expenses YTD" saw_6, "Facts - Budget"."Total Operating Expenses YTD"-"Facts - Actuals"."Total Operating Expenses YTD" saw_7, AGGREGATE(saw_2 BY ), AGGREGATE(saw_3 BY ), AGGREGATE(saw_4 BY ), AGGREGATE(saw_7 BY ), AGGREGATE(saw_2 BY saw_0), AGGREGATE(saw_3 BY saw_0), AGGREGATE(saw_4 BY saw_0), AGGREGATE(saw_7 BY saw_0) FROM "Financials - GL Budget and Expenses" WHERE ((Time."Fiscal Quarter" <= VALUEOF(NQ_SESSION."CURRENT_FSCL_QUARTER")) AND (Time."Fiscal Quarter" > VALUEOF(NQ_SESSION."FSCL_QTR_YEAR_AGO"))) AND (("WFS Segments".SEGMENT_NAME IN ('Aviation', 'Corporate', 'Land', 'Marine')) AND ("WFS Segments".ORG_NUM = VALUEOF(NQ_SESSION."OU_ORG"))) AND ("GL Segment1"."Hierarchy ID" = 'TTTTT') AND (Time.Status = 'Closed') ORDER BY saw_0, saw_1

As of my knowledge, you shouldn't get results set for any of views because of this error..!!
I see you are using 2 facts in the report.
And, dimensions you are using in this reports are confirmed dimensions to these 2 facts?
Are you mentioned proper content levels for each Fact LTSs?
Basic funda is: If fact and dimensions are joined directly, then you should mention the the level of granularity in Fact LTS. If not, you should mention total level of the dimensional hierarchy for the Fact LTS

Fix the metadata consistency warnings issue ...

Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: AR.AR_TP_ID. Please fix the metadata consistency warnings. (HY000)
Please help me to find the solution.

Hi,
I've got the following problem :
HY000 CODE : 10058 [NQODBC][SQLSTATE : HY000][NQSERROR:10058] a general error occurred. [NQSERROR:14026] Unable to navigate requested expression : Dim - Werkgever.WGVR Nr[]. Please fix the metadata consistency warnings (HY000)
How can I fix this problem ???
When I do a Global consistency check via the administration tool, I get no errors and no warnings. Nothing is changed in the Dim - Werkgever.
Who can help me ?
Kind Regards,
Else

Unable to navigate requested Expression.Please fix the metadata consistency

Hello ,
I have created one criteria but when I m running the request i m geeting this error, State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: Dim - GL Account.Unit Code. Please fix the metadata consistency warnings. (HY000)
now when i checked the RPD for this and run the consistency check everything went fine.No warning MSG, No Error, No Best Best Practice.
now i checked the join condition in BMM for the dimension i m using in report and fact.
it's like Fact F is directly Joined with Dim A & Dim B.
now when i checked the Physical join it's like Fact F1 is joined with Dim Aand Dim C , Fact F2 is joined with Dim B and Dim C.
so there is no direct fact table join between Dim A and Dim B.
Fact F1 & Fact F2 goes as MTLS in BMM and creating Fact F, now when i got this error i went to Fact F in BMM and checked the LTS and level of granuality for DIM A and Dim B for Fact F1 and Fact F2 respectively. and it is also set as detail level. and in BMM LTS Fact F1 and Fact F2 is also join with inner join with Dim C. and Dim C's level of granuality is also set in Fact F1 and Fact F2 .
the Columns that i m taking criteria are coimng from Fact F, Dim A, Dim B.
can anyone suggest me what to do in this case????
Thanking you..

Hi Veer,
If I get you correctly,
In BMM
Fact F = (physical F1 + F2)
In Physical:
F1 -> Dim A, Dim C ; F2 -> Dim B,Dim C
So, in your BMM, please make sure that
1. Logical source for physical F1 has 'Detail for Dim A, Dim C' and 'Total for Dim B'
2. Logical source for physical F2 has 'Detail for Dim B , Dim C' and 'Total for Dim A'.
I think this should resolve the issue.
Hope this helps.
Thank you,
Dhar

Fix the metadata consistency

Hi
Could you pls find the error:
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: SCBT_MST.GROUP_CODE. Please fix the metadata consistency warnings. (HY000)
How can I fix this problem ???
When I do a Global consistency check via the administration tool, I getting 2 warnings.
How can i solve.
Thanks

State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: SCBT_MST.GROUP_CODE. Please fix the metadata consistency warnings. (HY000)check SCBT_MST.GROUP_CODE column.Check if it is properly mapped to somep physical column or not.
Can you close all your threads for which you are provided solution.you have not closed any of the thread.
Regards,
Sandeep
Edited by: 771488 on Dec 2, 2010 3:24 AM

Reg : nQSError:10058 in OBIEE

Hi Experts,
Am getting the following error in my dashboard.Can anyone provide inputs as what is the cause of this issue and how to resolve it.
nQSError: 10058] A general error has occurred. The backend MDX query did not generate correct output and could be parsed

Hi,
I googled this error and find this
The backend MDX query did not generate correct output and could be parsed.
Cause. The MDX query did not generate axis information.
Response. Modify the SQL query and try again.
So try removing coulmns one by one from report and check.
Thanks
Sandeep

Please fix the metadata consistency warning..

Hello Gurus,
I have come across the scenario where i have to add the Dummy Fact and dummy column for data densification between Fact and Dimension to see all possible result on answer set.
so I have created the Dummy Fact with Dummy column and done the Cartesian join between all dim with that Dummy fact with 1=1 in physical layer.
now in BMM I imported the Dummy fact and done same joins that I have with the other fact.
now when i create the criteria with dummy fact and orginal fact i m getting the consistency check error on report.
can some suggest me what to do in such case??
Thanking You....

Hey Veeravalli,
Dummy Fact is just created in physical layer with "select 1 as dummy from dual"....
and even the RPD is not showing any warning , error or best practise in consistancy check.
it's only when i pull the Dummy Column from Dummy Fact and any Fact column from regular fact , the error msg is showing in result.
Let me know if you need any further details..

Ediscovery Export : Metadata Consistency

Hello Everyone,
I am facing a peculiar challenge in one of our ediscovery project implementation.
Challenge description:
When legal users export the hold documents (Image-1), It’s showing the exported date/time as “Date Modified” not the actual modified
date of the documents (Image -2).
I have verified that none of the document properties hold the actual modified date.
Image -1 :
Image - 2:
Business users need the actual modified date as “Date Modified”, as failing to do so will be considered as "Tampering of Evidence
Please let me know if anyone has encountered this before and any solution/approach implemented.
I have checked the api to override the export functionality but there is little to none information available about this.
Regards,
Akash

The OWB Bridge metadata export will work with 10.1.0.4. So you should be able to deploy your OLAP schema to your target instance.
Hope this helps,
Keith
Oracle Business Intelligence Product Management
BI on Oracle: http://www.oracle.com/bi/
BI on OTN: http://www.oracle.com/technology/products/bi/
BI Beans http://www.oracle.com/technology/products/bib/index.html
Discoverer: http://www.oracle.com/technology/products/discoverer/
BI Software: http://www.oracle.com/technology/software/products/ias/devuse.html
Documentation: http://www.oracle.com/technology/documentation/appserver1012.html
BI Samples: http://www.oracle.com/technology/products/bi/samples/
Blog: http://oraclebi.blogspot.com/

Consistency Warning: [39008] Logical dimension table ... has a source ...

Hi and many thinks for reading,
I have a problem (which is quite common as I saw, though I could'nt find a solution which resolves my issue yet) with the consistency.
My physical layer looks like this:
Table_A
Table_B
Table_C
Table_D
Table_E
In the Business Model I have just the same tables and the following joins in the Logical Table Diagram:
Table_A -> Table_B
Table_C -> Table_A
Table_D -> Table_A
Table_E -> Table_A
The consistency check is delivering the following two warnings:
Warning
Logical Table Source
Table_A
[39008] Logical dimension table Table_A has a source Table_A that does not join to any fact source.
Warning
Logical Table Source
Table_B
[39008] Logical dimension table Table_B has a source Table_B that does not join to any fact source.
While working in BI answers I manage to retrieve all data from Tables C, D, E. But for tables A and B I can retrieve just the columns which are defined in the join Table_A->Table_B. All other columns deliver the following error:
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: Table_A.Column_X. Please fix the metadata consistency warnings. (HY000)
If i retrieve one Column from Table_A and one from Table_E, I have the following error:
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table Table_E) does not contain mapping for [Table_B.Column_X]. (HY000)
(yes its Table_B not a)
I would like to fix this errors but am not sure where the problem is hidden.
Any help is kindly appreciated.
Evgeny

Hi Goran,
thanks for you help.
I tried to create the BMM in the two way but, it doesn't work out neither way. The Administration tool is recognizing the repository as consistent, thought it has some warnings, but in BI Answers I cant retrieve even a single column from one table.
I am also not sure, how does it work, that you just add TableB to the logical TableA, who would the programm know which rows belong together? I assume one must establish a logical connection between TableA and TableB to make it compatible?
About my tables:
Actually TableA, TableB and TableC are recognized dimensions (white) and TableD and TableE are recognized as facts (yellow) in the Administration tool. Though I dont agree with this assignment. TableA is definitly a fact table (it is also the center of the star schema) while the other tables are the dimension tables. Not sure how the Administration tool is distinguishing between facts and dimensions...
Here are my warnings:
BUSINESS MODEL TAB: (with two logical tables)
[39008] Logical dimension table TableA has a source TableA that does not join to any fact source.
[39008] Logical dimension table TableA has a source TableB that does not join to any fact source.
BUSINESS MODEL TACDE: (with three logical table sources)
[39008] Logical dimension table LT2 has a source TableE that does not join to any fact source.
[39008] Logical dimension table LT2 has a source TableD that does not join to any fact source.
[39008] Logical dimension table LT2 has a source TableC that does not join to any fact source.
And the errors in Answers:
Retrieving ColumnX from TableA in the first model
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: TableA.ColumnX. Please fix the metadata consistency warnings. (HY000)
Retrieving ColumnX from TableA in the second model
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 17001] Oracle Error code: 12170, message: ORA-12170: TNS:Connect timeout occurred at OCI call OCIServerAttach. [nQSError: 17014] Could not connect to Oracle database. (HY000)
Thanks for further help!
Evgeny

NQSError: 10058 - Unable to Navigate Requested Expression Error in OBIEE

We are getting the below error when we try to generate report using a dimension column and a fact column.
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: FILTER(# of Responses:[DAggr(Fact - Leads & Interest .# of Responses by [ Dim - Contact.First Name, Dim - Contact.ROW_ID, Team & Opty Based Org.POSTN_WID, Team & Opty Based Org.Level 1 Employee Name, LN Leads & Interest.ROW_ID] SB Revenue Attributes Total,Sales Velocity Attributes Total)] USING Team & Opty Based Org.Level 1 Employee Name <> 'Test, USLMMarketing' and (LN Leads & Interest.Customer Supplied Email <> email@removed ' or LN Leads & Interest.Customer Supplied Email is null)). Please fix the metadata consistency warnings. (HY000)
We are using the below logical formula for the measure column.
FILTER(Core."Fact - Leads & Interest "."# Of Response Final" USING (Core."LN Leads & Interest"."Customer Supplied Email" <> email@removed ' OR Core."LN Leads & Interest"."Customer Supplied Email" IS NULL ) AND Core."Team & Opty Based Org"."Level 1 Employee Name" <> 'Test, USLMMarketing')
We have this measure in a logical fact table.
Please help me know why would this error occur.

Sorry i missed while pasting the formula. Below is the logical column formula.
FILTER(Core."Fact - Leads & Interest "."# Of Response Final" USING (Core."LN Leads & Interest"."Customer Supplied Email" <> '[email protected]' OR Core."LN Leads & Interest"."Customer Supplied Email" IS NULL ) AND Core."Team & Opty Based Org"."Level 1 Employee Name" <> 'Test, USLMMarketing')
This measure is working properly with other dimension attributes in the subject area.

OBI Enterprise Edition hierarchical levels definition - nQSError: 10058

Hi,
i'm trying, in the BI administration tool, to define a dimension hierarchy based on not star nor snowflake scheme. I've a physical fact-table RICETTA linked to the first level physical table DISTRETTO. the physical table DISTRETTO is then linked to the both upper levels: USL and REGIONE. The conceptual hierarchy is DISTRETTO -> USL -> REGIONE. how can I define the logical hierarchy if there's no physical link between REGIONE and USL tables?
The Answer front-end returns the seguent error: Stato: HY000. Codice: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: USL.NOM_REGIONE. Please fix the metadata consistency warnings. (HY000).
Thank for help

If you followed up the setup document (http://docs.oracle.com/cd/E21043_01/bi.1111/e10541/configscorecard.htm), make sure you Restart the Oracle BI Server, through the Enterprise Manager for your bi instance.
After that, make sure you give your 'BIsystem' role permissions for "Allowing or Disallowing Direct Database Requests".
(You can access that through your RPD->Manage->Identities. Select BIsystem, click on "Permissions", Select tab "Query Limits", and select "Allow" in the "Allow or Disallow Direct Database Requests").
And make sure you either Delete the configured database ("System DB (Update me)") that comes with the Samples, in the RPD, that already has a connection named "BSC", change the connection name in that database, or just use it as the BSC annotations schema.
If you still have problems after that, make sure the connection credentials in your BSC connections are good to go.
Hope it helps.
Best regards.

[nQSError: 14026] Unable to navigate requested expression

Hi,
My BMM diagram is like
D1 --- Fact 1 -- D 2 -- D3 -- Fact 2 -- D4
I am getting navigation error, When I selected the fields from Fact1 and D4.
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression:Fact1 .Flag. Please fix the metadata consistency warnings. (HY000)
SQL Issued: SELECT Fact1. Flag" saw_0, D4. Code saw_1 FROM "Temp" ORDER BY saw_0, saw_1
As there is no join between Fact 1 and D4. I have tried by setting Aggregation level of D4 to Total at Fact 1. But still I am getting same error.
Any suggestions to fix this error?
Thanks.

Hi
Have you resolved this issue? I am facing same issue can you let me know how did you resolve this issue
Thanks & Regards
Sameer

Fix Metadata Warning

Hi,
I had created a report and this is working fine in the my laptop and the local Presentation Services, but when i putting this in the Dev/Test Environment it is throwing an error
"State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: Procurement - Key Dates.Fiscal Year. Please fix the metadata consistency warnings. (HY000)"
I am not able to undertand the issue.
Regards,
Amit

Just a few things off the top of my head you can check:
1) Check your dimensional hierarchies and make sure that they are all in order (keys setup properly, number of distinct values setup properly)
2) Check any measures and look at their Content levels. Make sure those are in order.
3) Check that you included dimensions that were actually linked to your fact via a foreign key.
Best regards,
-Joe

Join two fact tables

Hi,
I have two fact tables F1 and F2 joined with few dimensions D1.....D9. D1,D2 and D3 are conformed dimensions.
In Physical:
F1>--D1,D2,D3,D4,D5,D6
F2>--D1,D2,D3,D7,D8,D9
In Logical:
F1>--D1,D2,D3,D4,D5,D6
F2>--D1,D2,D3,D7,D8,D9
there are some ports already using above star schemas. now I got new requirements and I need to use measures from both the fact tables and conformed and unconformed dimensions.
I did the following in logical
F1 LTS GENERAL TAB ADDED F2,D1,D2,D3,D7,D8,D9 and in content tab set logical level to unconformed dimensions at total level and for conformed dimensios at details level.
F2 LTS GENERAL TAB ADDED F1,D1,D2,D3,D7,D8,D9 and in content tab set logical level to unconformed dimensions at total level and for conformed dimensios at details level.
but I'm still getting
[nQSError: 14026] Unable to navigate requested expression:
Please fix the metadata consistency warnings. (HY000)
I cheked metadata global consistency and no errors found.
Appreciate your help
Thanks
Jay.
Edited by: Jay on Sep 27, 2011 10:14 AM
Edited by: Jay on Sep 27, 2011 10:15 AM

Let me explain my issue again
In Physical:
F1>--D1,D2,D3,D4,D5,D6
F2>--D1,D7
In Logical: Single logical fact Fact_FY_Ratio has two logical sources
LTS1: F1>--D1,D2,D3,D4,D5,D6
LTS2: F2>--D1,D7
Set the content level for each LTS in Fact_FY_Ratio:
F1 to Detail for D1,D2,D3,D4,D5,D6 and to Total for D7
F2 to Detail for D1,D7 and to Total for D2,D3,D4,D5,D6
In LTS 1 general tab added inner joins with all dimensions F1,D1,D2,D3,D4,D5,D6,D7and F2
In LTS 2 general tab added inner joins with all dimensions F2,D1,D7,D2,D3,D4,D5,D6 and F1
And I also did logical complex join for Fact_FY_Ratio with all logical dimensions D1,D2,D3,D4,D5,D6,D7
I'm able to run query using D1,D2,D3,D4,D5,D7,F1,F2 but when I include D6(time dimension) it is causing problem with F2(witth F1 it is working fine).
query success with:
F1,D1,D2,D3,D4,D5,D6
F2,D1,D7
D1,D2,D3,D4,D5,D7,F1,F2
Query failed with:
F2>--D1,D7 and D6
Please let me know anything wrong with above configuration.
Thanks
Jay...
Edited by: Jay on Oct 3, 2011 7:11 AM

Reg:-nQSError: 1005(metadata consistency warnings)

Similar Messages

Maybe you are looking for