Is there a limitation on BMM modeling when we use complex join in physical layer. I have 1 Fact and 4 Dimension table having following relationship in physical table.
F.Col1=D1.Col1, D1.Col2=D2.Col2, D2.Col3=D3.Col3 and D3.Col4= case when D4.Col5 is null then D4.Col6 else D4.Col5 end)
I am using complex join for D3-D4. In the report I am getting the error [nQSError: 12002] Socket communication error at call=recv: (Number=10038) An operation was attempted on something that is not a socket
If I create the new calculated column CalCCol in D4 table in sql, containing the same logic (case when D4.Col5 is null then D4.Col6 else D4.Col5 end) and using this column for physical join D3-->D4 (D3.Col4=D4.CalcCol) in physical layer, the report works without any error.
Do we have to do modeling differently in bmm layer or just its a limitation with complex join in physical layer?
Fact table is joined with D1 dimension table which has four (D1,D2,D3,D4) Logical Table Source(LTS).
I dont think there are limitations for complex joins in both BMM and Physical layer. Correct me if I'm wrong...
Reg. nQSError: 12002 error--> Might be currupted cache reason might see when doing changes online mode...
Delete the cache and re-start the services might help you.
Assuming you mapped D2,D3,D4 tables to D1 by Add button, looks good to me.
Send me your rpd file if you have any issues..
If helps pls mark
Edited by: Srini VEERAVALLI on Jan 22, 2013 4:01 PM