Post reply

Analysis Server Error: Detected two sibling members with the same name:

  • October 22, 2004 at 2:53 am

    #108736

    This error is triggered when processing a hierarchy dimension.

    Can somebody explain me when this error is triggered ?

    If you need more information don't hesitate to reply.

    Thanks in advance.

    Regards

     

  • October 23, 2004 at 5:38 pm

    #527738

    Can u post the entire error message.

     

    Thanks.

     

  • October 24, 2004 at 5:19 pm

    #527760

    This is two siblings with either the same name or key.  The uniqueness on your levels and on the dimension itself needs to be modified if you want to allow this, alternatively, it's a message that indicates that your data in the datawarehouse may need more cleansing (well, mapping really) as are two key values that have the same description/name.  If this is based on say Customers, then you may well want to map the two customers to one.

    Steve.

  • June 3, 2005 at 1:22 am

    #562789

    Hi steve,

    i encountered this error recently. i've checked the data but there's no key which has the same name.

    For the member key column, the cube uses the ID in the fact table

    while the member name column uses the name in dimension table.

    What else can i check?

    Level 1 and level 2 for that dimension joins well.

    Please help. Thanks!

  • June 7, 2005 at 1:14 am

    #563400

    Can't really think of what could cause this *other* than the error message be correct and that there are two sibling members with the same name.  Can you post the exact error message that you're receiving?

     

    Steve.

  • June 7, 2005 at 1:51 am

    #563409

    the error is

    Analysis Server Error: Detected two sibling members with the same name: - (Customer Type L0).

    the cube is processed using incremental update but the dimension is not a shared dimension.

    any way to solve this problem?

    thanks!

  • June 9, 2005 at 4:31 pm

    #564430

    I would suggest dropping and recreating the private dim. good luck

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply