Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 14 Oracle Analytics Lounge
- 211 Oracle Analytics News
- 41 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 77 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
Scaling out or disabling specific OBIEE component permanently
Hi,
Is there any way to scale out or disable permanently a specific component in OBIEE 11g and 12c ? So that, every time when we start OBIEE services, that specific component should not be considered.
Answers
-
-
Hi Gianni,
Thanks for your reply. I really appreciate your inputs. As you mentioned, this post is almost similar to my previous post. Yeah, it looks, but it is not. Let take an example :
I have started all OBIEE services using start command. But, since we are not going to use any feature of scheduler, so we planned to stop this component. But, next time when we want to restart our OBIEE for some reason. We don't want repeat same step (starting all OBIEE services and then stopping scheduler or any specific component) instead we wanted to remove or disable this component completely. So that, next if anyone starts OBIEE services, it will only start which we wanted to start (by default).
You would probably say, we could pass component name as parameter to start specific component. Yes, true we can do this. But, we wanted to know, if we could get some option by which we could skip specific component to start even when we execute startall command (kind of changing value in configuration file or related file).
Thanks.
0 -
Ok, and OBIEE 11g or 12c ?
Because in 11g it's OPMN managing the components, but in 12c OPMN doesn't exist anymore.
So it's simpler knowing if you are on 11g or already on 12c.
0 -
Why? Why do something that's going to leave you with a non-standard deployment? Leaving scheduler running makes no difference if you're not using it.
If you disable it, neatly or not, you're almost certainly always going to have a "component down" big red cross in EM - so each time you mentally need to check is that an expected error, or not? Or, you come to ignore "component down" and then it turns out one of the others really is down. Plus, when you come up upgrade/patch/migrate your deployment, you now have any additional change to bear in mind.
Keep it simple, Keep it vanilla, would be my advice.
0 -
Actually, we are doing all are our investigation for OBIEE 11g as well OBIEE 12c. Since, there is no direct upgrade path from OBIEE 10g (please correct, if I'm wrong).
So, it would better for us, if you could include you suggestion for both version OBIEE 11g and 12c as well.
Thanks again.
0 -
To be very frank, it isn't my thought to do this. Even I'm totally agree with your points as investigation itself taking lot of time. But, it's been asked and reason which I know is to "reduce resource consumption". I'm very sure, when it was asked, they might have considered everything, which I don't know or can not think of.
0 -
If the memory footprint of the Scheduler component is an issue then it's time to upgrade from a GameBoy to sth a bit more powerful.
Also: if you know you can script it why do you want an option to disable things when you "startall" - it wouldn't be "startall" anymore wouldn't it? the "all" is in there for a reason and you can script things for a reason. Noth thave their usage so use each one when it's appropriate and stop trying to make the one do less than what it's supposed to do.
0
