I've just installed the last version 184.108.40.206.9 in my test environment and I already have a problem with the RPD.
I've some logical column derived from existing columns using an expression. (so far, so good)
With Adminsitration Tool (Last Version 220.127.116.11.9), when I launch the Consistency Check Manager I have the following error (I use the SampleAppLite RPD in order to reproduce the problem)
SampleApp Lite :
[nQSError: 46008] Internal error: File server\objectmodel\Src\SOSecureRpGateway.cpp, line 479.
[nQSError: 23013] An error occurred when extracting the metadata definition for the Attribute '"SampleApp Lite"."D3 Orders (Facts Attributes)"."test"'.
The logical column test on "D3 Orders (Facts Attributes)" : CASE WHEN "SampleApp Lite"."D3 Orders (Facts Attributes)"."Order Date" > "SampleApp Lite"."D0 Time"."Calendar Date" THEN 1 ELSE 0 END
The problem appears only when I use multiple source table in column expression.
Does anyone has the same problem ? I think it's easy to reproduce (I searched on OracleSupport but I didn't find anything yet)
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 18.104.22.168.2 PB1).
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 22.214.171.124.2 BP1 version I don't understand why it's not working with 126.96.36.199.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.
Yes I created yesterday a SR and oracle support told me that is an internal bug which is planned to be corrected in 188.8.131.52.10.
This case is working with 184.108.40.206.7 version but not in 220.127.116.11.9 version.
This is the last information I have, I will update this thread if I have further informations.
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 18.104.22.168.8? Thanks.