This content has been marked as final. Show 11 replies
Try to create the same on any of logical fact tables ie. F0 Revenue Base Measures
F1 Targets Base Measures
where ever the related to same BMM schema (Busines Model Diagram)
Edited by: Srini VEERAVALLI on Mar 20, 2013 12:03 PM
I've just tried to create the same logical column on the fact table, the error is the same.
But sorry I don't understant what you mean by : "where ever the related to same BMM schema (Busines Model Diagram)", I reproduce my problem with the sample RPD,there is just one Business model in the SampleAppLite Rpd
I would like to add that my RPD is working on our production environment (version 22.214.171.124.2 PB1).
May be I have to fill a SR ..
I mean to say that we can have multiple logical fact tables and its no mandatory that all dims in BMM are mapped to logical facts.
There is no relation between
"SampleApp Lite"."D3 Orders (Facts Attributes)"."Order Date"
"SampleApp Lite"."D0 Time"."Calendar Date"
Just in case if you want to the same way what you are trying, make sure implicit fact setting
I would see this is coding issue SR may not help you.
Edited by: Srini VEERAVALLI on Mar 20, 2013 12:25 PM
Edited by: Srini VEERAVALLI on Mar 20, 2013 12:27 PM
I know that there is no relation between "SampleApp Lite"."D3 Orders (Facts Attributes)"."Order Date", "SampleApp Lite"."D0 Time"."Calendar Date", it's also the same thing in my own RPD.
But as it's working with the 126.96.36.199.2 BP1 version I don't understand why it's not working with 188.8.131.52.9.
Implicit fact column is not set on my repository, but I don't have any request with only dimensional column, so if my understanding is correct I don't need to use it. Also, the problem appears during the check of the repository not in answers.
Hello, I'm facing the same problem. Have you found a solution or logged an SR regarding this issue?
Yes I created yesterday a SR and oracle support told me that is an internal bug which is planned to be corrected in 184.108.40.206.10.
This case is working with 220.127.116.11.7 version but not in 18.104.22.168.9 version.
This is the last information I have, I will update this thread if I have further informations.
Thank you for the feedback Benjamin.
In my case the repository was working on 22.214.171.124.8, these errors appeared after applying 126.96.36.199.9 patches. The workaround was to rollback to the 188.8.131.52.8 version.
I will be checking your updates on this thread.
Thanks again. Regards.
We are having the same problem but in a Windows Server 2003 (64-bit) environment. Is there a certain Opatch in the bundle patchset that can be rolled back or does anyone have any suggestions for how to roll back to 184.108.40.206.8? Thanks.
I've just tested the 220.127.116.11.10 version, and the problem was corrected.
Corrected in Version 18.104.22.168.10