Global consistency warning.

I created a SA with four tables involved.Everything looked fine and I ran the reports for that rpd. Now I added one more table in the physical layer to create another SA involving just two tables. First it was a star schema in physical layer but after I involved this table it became a snow flake schema. But in BMM since the second SA involved only two tables I did not encounter this snow flake in BMM. First SA has 4 tables which is a star schem and second SA involved only two tables. Now after I am dome with everything and pulled the new SA to presenation layer and did a global consistency check I am getting a warning which says "39011 key “Subject Area2”.table.table_key#2 in logical table “Subject Area2.”table” is a superset or subset of another key in this table. Any redundant table key should be removed. What do i do to overcome this.

hi,
Double click on the table source,Keys tab delete the extra key '#' then check the consistency.
thanks,
saichand.v

Similar Messages

  • Check Global Consistency Warning

    Hi,
    Greetings.
    I have exported an EUL from the discoverer and got the RPD. Using that RPD I have created a Repository and it is fine till here.
    But, when I try to check the global consistency after defining the Primary Keys and Foriegn Keys of the tables, it is showing a Warning as follows
    "WARNINGS:GLOBAL: [39028] The features in Database 'AG_TEST' do not match the defaults. This can cause query problems."
    So, Please someone help me resolve the issue.
    Thanks in advance.
    Regards,
    Bhaskar.

    Its not advisable to change DB features. Check whether the DB you are using is 10g or 11g.
    if its 10g you should get this warning.
    Most of the time you should not have a problem.
    To ensure this you can deploy and do a through testing checking whether the results are obtained as expected. Also check the back end sql issued by OBI server.
    wrongly changing the DB features will impact the server behavior and can bring erratic queries. ( yet you might not see issues in consistency check)
    If you know what to change in DB features and know the impact of it then its fine. If not, better use the RPD as is as what you received.
    Besides this is just a warning.

  • Not  Displaying Options tab while Checking Global Consistancy in OBIEE 11G

    Hi,
    We recently upgraded from 10G to 11 G . Here When I checked Global Consistency I got some Errors but they are negligible . I need to disable those errors but am not finding that option .
    Please give me the soln.
    Thanks in Advance.

    Hi,
    11g does not allow beginning or trailing spaces in logical names within the RPD. This causes errors in this release instead of warnings as in OBIEE 10g.I would suggest you to close the window.
    For more information go through this blog http://www.skurabigroup.com/blog/?p=759
    Hope it helps you,if answered award points.
    By,
    KK

  • Importance of Global Consistency check

    Hello,
    I have always checked my rpd for global consistency without knowing the actual meaning behind it. But last night I created a logical column with the following expression:
    max(VALUEOF(NQ_SESSION......))
    basically i created an aggregation over a logical column that obtains its value from session variable. I know that if we need to use a column as an aggregation column we should use the aggregation tab in the column properties. When we choose an aggregation it disables the editable column formula field.
    I put the above formula which violates the rule. The result is perfect so long as I don't check for global consistency. It throws an error that looks something like this:
    [38083] The Attribute 'Acceptance Rate Target' defines a measure using an obsolete method.
    The question is.. what is the significance of global consistency check.. and what is the consistency criteria.. and is it ok to save the rpd without checking for global consistency (yes this does not cause the BI server to crash when trying to start)
    Thanks

    First, forget about the variable approach.
    Now you need to do the following steps:
    1) Import the table to the physical layer
    2) Create logical table in existing Business Model in BMM layer with the imported table as logical table source
    3) Create another logical table in existing Business Model in BMM layer with the imported table as logical table source
    4) Create complex join between both table, now you will get one logical dimension table and one logical fact table
    5) In the logical fact table you need to select the column ("Target") and add an aggregation rule, like MAX or MIN
    6) Assuming you have a hierarchy for every dimension in your BMM layer, you need to set the logical levels of the new measure to the Grand Total Level of each dimension hierarchy.
    By doing this, you get a "level based measure", for more info: read this:
    http://oraclebizint.wordpress.com/2007/12/03/oracle-bi-ee-101332-level-based-measures-lbms/
    By setting all logical levels to the grand total level, the measure will be "immune" for all dimensions used in your report.
    So when you have a report like
    Month__Actual___Target
    The BI Server will create two queries:
    select month, sum(sales) from calendar, sales_table where calendar.id = sales_table.calendar_id
    and
    select max(value) from target_table
    The BI Server will then stitch both results together.
    Regards,
    Stijn

  • Error when Check global consistency: Physical tables have multiple Joins

    Hi
    I have a table that have multiple joins with a dimension in the physical layer, this is a fact table and the dimension is a geograhic dimension, and in the fact table I have three codes, customer geography, account geography and office geography. This is a simple model and is correct for my DWH. However when I want to check global consistency the consistency check manager display the next error (three times):
    ERRORS:
    GLOBAL:
    [38015] Physical tables "ODS".."ODS"."FT_INTERFAZ_CICLO_FACTURACION" and "ODS".."ODS"."DIM_GEOGRAFIA" have multiple joins. Delete new foreign key object if it is a duplicate of existing foreign key.
    [38015] Physical tables "ODS".."ODS"."FT_INTERFAZ_CICLO_FACTURACION" and "ODS".."ODS"."DIM_GEOGRAFIA" have multiple joins. Delete new foreign key object if it is a duplicate of existing foreign key.
    [38015] Physical tables "ODS".."ODS"."FT_INTERFAZ_CICLO_FACTURACION" and "ODS".."ODS"."DIM_GEOGRAFIA" have multiple joins. Delete new foreign key object if it is a duplicate of existing foreign key.
    How can I do to solve this error?
    Thanks
    Edwin

    I have one dim table name team.
    In the dim table there are two primary keys like Team key and Team Type key.
    In the Fact table there are 4 foriegnkey like
    a) Sales team key
    b) Sales team type key
    c) Trader team key
    d) Trader team type key
    For this purpose , i am going to create the alias table in the physical layer. Can any body explain to me the whole process

  • Automating global consistency check

    Hi,
    Could anyone please share knowledge on how to automate rpd global consistency check and creating output file containing errors and warnings of rpd.
    Regards,
    Varun

    Hi varun,
    to automate rpd global consistency checkNo,there is no automate for consistency check.Anyways why you want to automate.Its a one step process just clicking global consistency check.
    By,
    Kranthi.

  • Global Consistency Check Errors after RPD Merge: 38120 and 38015

    Dears
    Can anyone of you point me to a documentation explains Global Consistency Check error numbers in details ?
    After merging 2 RPDs, it gives me the following errors: 38120 and 38015
    Thanks

    38120: Dimension xyz is not associated with any table(s)
    Comments: I checked this Dim table and did find tables associated with it. Don't know how else to check ?
    38015: Physical tables "<ABC>"."Fact - abc" and "<ABC>"."Dim - lmn" have multiple joins. Delete new foreign key object if it is a duplicate of existing foreign key.
    Comments: I did check the joins between this Fact and Dim table and found only 1 join.

  • Consistency Warning - [39008] Dimension Table not joined to Fact Source

    I have a schema in which I have the following tables:
    A) Patient Transaction Fact Table (i.e. supplies used, procedures performed, etc.)
    B) Demographic Dimension table (houses info like patient location code)
    C) Location Dimension table (tells me what Hospital each unique Location maps to)
    So table A is the fact, and table B is a dimension table joined to table A based on Patient ID, so I can get general info on the patient. This would allow me to apply logic to just see patient transactions where the patient was FEMALE, or was in the Emergency Room, by applying conditions to these fields in table B.
    Table C is a simple lookup table joined to table B by Location Code, so I can identify which hospital's emergency room the patient was located in for instance.
    So the schema is: A<---B<---C, where B and C are both dimension tables.
    The query works as desired, but my consistency check gives me the following WARNING:
    *[39008] Logical dimension table LOCATION MASTER D has a source LOCATION MASTER D that does not join to any fact source.*
    How do I resolve this WARNING, or at least suppress it?

    Hi,
    What you need to do is to add the (physical) location dimension table to the logical table source of the demographic dimension, for example by dragging it from physical layer on top of logical table source of demographic logical dimension table in bmm layer
    Regards,
    Stijn

  • 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

  • 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..

  • Obiee 11g Global Consistency Check Error

    Hello all,
    I need guidance regarding an error which pops up after the consistency check. However Admin tool lets the rpd to be saved and uploaded to the server, inspite of this error.
    The error is as follows:
    "the initialization string in the repository initialization block "NAME" contains the use of USER: or Password:"
    Any input is appriciated.
    Thank you.

    Here, you shud use something like this:
    Say ur user column us LOGIN in W_DAY_D table.
    Then IB sql should be: SELECT DISTINCT LOGIN FROM W_DAY_D WHERE LOGIN = ':USER'
    OR
    SELECT DISTINCT LOGIN FROM W_DAY_D WHERE LOGIN = 'VALUEOF(NQ_SESSION.USER)'
    and also, for ur default initialized may be you can use ur name say 'xxx'
    Hope this helps..

  • "Missing most detailed table for dimension tables" eror when I run the Global Consistency check

    ERRORS:
    Business Model DAC Measures:
    [nQSError: 15003] Missing most detailed table for dimension tables: [D_DETAILS,D_EXECUTION_PLAN,D_TASK].
    [nQSError: 15001] Could not load navigation space for subject area DAC Measures.
    I am also attaching my Business Model layer for easy understanding. I have a fact table and several Dimension table. I got this error only after creating the following hierarchies:
    Execution Plan -> Tasks -> Details
    Start Date Time Hierarchy
    End Date Time Hierarchy
    Is there a solution for this problem? Thanks in advance!

    Yes ! My Task Hierarchy has 3 dimension tables that form a hierarchy :Execution Plan -> Tasks -> Detail
    All the 3 levels in the hierarchy are 3 different dimension tables.

  • I get this error : "content filter of a source for logical table" while I run the Global consistency check.

    ERRORS:
    Business Model DAC Measures:
    [nQSError: 14031] The content filter of a source for logical table: D_END_TIME references multiple dimensions.
    [nQSError: 15001] Could not load navigation space for subject area DAC Measures.
    Thank you!

    Yes ! My Task Hierarchy has 3 dimension tables that form a hierarchy :Execution Plan -> Tasks -> Detail
    All the 3 levels in the hierarchy are 3 different dimension tables.

  • Why is consistency check warning [39054] raised?

    Hi,
    Today I migrated a 10g repository to 11g. After the upgrade I was checking the global consistency and the following warning is occuring several times
    WARNINGS:
    BUSINESS MODEL Declaraties:
    [39054] Fact table "[fact table 1]" is not joined to logical dimension table "[dimension 1]". This will cause problems when extracting project(s).
    The warning is correct, fact table 1 is not joined to dimension 1. But this is because there is no relationship between those two tables. Dimension 1 is not used by fact table 1. However, dimension table 1 is used by another fact in the same business area.
    Why am I getting this warning, it seems to me that not every dimension should be joined with all fact tables in a business area. What is intended with 'This will cause problems when extracting project(s)'?
    Regards,
    Albert

    Hi Albert,
    I will suggest you to resolve all the warning its a best practice as u said having 500+ warnings is not good
    Refer : Source does not join to any fact source
    Thanks,
    Saichand.v

  • Warning in the RPD: Error No 38128

    Hi All,
    When i'm running global consistency checker, it throws the following warning.
    **Error no: 38128**
    Presentation level. "presentation subject area"."presentation table". "presentation hierarchy table"."hierarchy detail " has no display columns.
    Could anyone Plz help me to resolve this warning.
    Thanks in advance !!!

    Hello,
    Did you set any "Use for display" at any level in the hierarchy of the dimension in question.
    Go to hierarchy with the error in the BMM go to each of its levels to find a level that has no key marked "Use for display"
    Remove the hierarchy from the Presentation Layer which was already created, and again drag from the BMM Layer for your changes to come into effect.
    Hope this helps. Pls mark if it does.
    Thanks,
    SVS

Maybe you are looking for