Thank you.

We already have the connections pools separated by database.

Thanks for all the replies. My use case is we currently have a single environment for 15 groups. Now the 2 groups are split into separate groups and for the new group we are looking for faster code release process for 1 group and normal restrictive process for other group. So in order to achieve this we are looking for…

I agree with you and that is the default behavior of the tool. Normally when I am issuing an analysis against dimensions and a metric from each fact table, the Bi server is issuing 2 queries one to each fact and then doing a stitch join to both the result sets. What I am failing to understand is when I am trying to run an…

Finally we got the solution from oracle, the variable NQSCHED_IBOT_BALANCE Environment Variable set for the BI Scheduler (obisch) in the DOMAIN_HOME/config/fmwconfig/bienv/OBISCH/obisch.properties file should be set as NQSCHED_IBOT_BALANCE=false

Alright sorry for the confusion. 1) "when I introduce a filter say Fact.ColA='ABC'" When I say Fact.ColA='ABC'" its actually the physical column thats coming from the fact table, but in Presentation layer and BMM layer its DegenreateDim.ColA To summarize I have taken an alias of the fact table say Fact_A, created all the…

In the physical layer its just one single alias table, the split to dimension and fact is done only in the BMM layer. The reason I am doing this is I do not have a primary key on the fact table and all I have is a couple of business keys, so if I have to do this in Physical layer, it creates the burden of a fact to fact…

Fact.ColA is an attribute so I have split up the degenerate dimension columns from physical fact table in the logical layer, leaving only the metrics in the logical fact and all attributes into logical dimension.

I finally got it to working by setting all the metrics from Fact A to total level for the attributes from Degenerate dimension Fact B which resolved the issue. But the downside I see from this is, every time I try running such a scenario the other metric is aggregated fully which might throw some performance issues and…

Yes, I did create hierarchies for all the other dimensions. so I created 2 degenearte logical dimensions with attributes from fact A to Degen Dim A and attributes from fact B to Degen Dim B, created the businness keys for the dims and also the basic total and detail hiererachy. Created the logical join in BMM with the new…

So adding all the attribute columns to a logical dimension without having a hierarchy set, will that work? as it has no key to define.In my case I dont have a business key from single column that uniquely identifies, can I use multiple columns for business key?

Thanks for the replies Gianni and Christian, so as I said these attributes are actually coming from the physical fact table itself, so based on what you are suggesting, in the BMM layer shall I bring these attribute columns from the fact table and create a new logical table just for these attributes? In my case I do not…