resource manager used with SE2 [message #687774] |
Tue, 30 May 2023 08:58 |
|
Mulhmma
Messages: 9 Registered: May 2023
|
Junior Member |
|
|
Hi,
When I create a database with Oracle SE2, even empty, I can see in dba_feature_usage-statistics that RESOURCE MANAGER (which seems to be an EE feature) is used.
I tried many things as add the following lines in the init.ora before to create the database :
resource_limit=FALSE or TRUE
resource_manager_plan=''
and at the end of the creation, I immediatly ran theses queries :
execute dbms_scheduler.set_attribute('MONDAY_WINDOW','RESOURCE_PLAN','');
execute dbms_scheduler.set_attribute('TUESDAY_WINDOW','RESOURCE_PLAN','');
execute dbms_scheduler.set_attribute('WEDNESDAY_WINDOW','RESOURCE_PLAN','');
execute dbms_scheduler.set_attribute('THURSDAY_WINDOW','RESOURCE_PLAN','');
execute dbms_scheduler.set_attribute('FRIDAY_WINDOW','RESOURCE_PLAN','');
execute dbms_scheduler.set_attribute('SATURDAY_WINDOW','RESOURCE_PLAN','');
execute dbms_scheduler.set_attribute('SUNDAY_WINDOW','RESOURCE_PLAN','');
execute dbms_scheduler.set_attribute('WEEKNIGHT_WINDOW','RESOURCE_PLAN','');
execute dbms_scheduler.set_attribute('WEEKEND_WINDOW','RESOURCE_PLAN','');
but this does not change anything.
If anybody has an idea about disable "Resource Manager".
thank you
Regards
Den
|
|
|
|
|
|
Re: resource manager used with SE2 [message #687779 is a reply to message #687778] |
Tue, 30 May 2023 11:29 |
John Watson
Messages: 8960 Registered: January 2010 Location: Global Village
|
Senior Member |
|
|
It is documented (somewhere....) that instance caging is implemented with the RM. That must be how the 16 thread limit is imposed. Also documented is that instance caging is available in all editions. I would think this is an example of Uncle Oracle breaking his own rules. There are several such. The weirdest one, for me, is Transparent Data Encryption. That is Enterprise Edition plus the Adv Security pack. Oh no it isn't! On OCI, TDE is not only available in SE2, but if you don't use it you get a shed load of warnings. Parallel query is another: you can't use it in SE2. But on an SE2 RAC (which is no longer possible, of course) PQ was used to query the GV$ views.
|
|
|
|
|
|
|
Re: resource manager used with SE2 [message #687785 is a reply to message #687782] |
Thu, 01 June 2023 06:23 |
John Watson
Messages: 8960 Registered: January 2010 Location: Global Village
|
Senior Member |
|
|
Quote:- SQL Plan Directive : I had to put several parameters in init.ora to disable it
I am not aware that Directives are not permitted in SE2. They certainly get created - automatically - just as in EE.
Whether you want to use them is a different matter. When they appeared in 12.1 I thought they were an excellent facility and they were enabled by default. However, it seems that at a minority of sites (0.1% ? 49.9% ? No idea) they caused problems, so from 12.2 they are still created automatically but by default not used.
|
|
|
Re: resource manager used with SE2 [message #687786 is a reply to message #687785] |
Fri, 02 June 2023 03:46 |
|
Mulhmma
Messages: 9 Registered: May 2023
|
Junior Member |
|
|
Hi John,
Indeed we can use it in a reduced way with the SE2 but as we find a use in dba_feature_statistics_usage (mcoptions also reports this information), we prefer better to deactivate the functionality.
Once again I don't find this to be very clear in terms of Oracle licensing and as I'm not an expert ... :?
But, you are probably right.
Den
|
|
|