{"id":371,"date":"2013-07-03T16:55:27","date_gmt":"2013-07-03T14:55:27","guid":{"rendered":"http:\/\/www.ludovicocaldara.net\/dba\/?p=371"},"modified":"2020-08-18T16:56:20","modified_gmt":"2020-08-18T14:56:20","slug":"oracle-database-12c-an-overview-of-the-standard-edition-rac","status":"publish","type":"post","link":"https:\/\/www.ludovicocaldara.net\/dba\/oracle-database-12c-an-overview-of-the-standard-edition-rac\/","title":{"rendered":"Oracle Database 12c: Multitenant, Services and Standard Edition RAC"},"content":{"rendered":"

The installation process of a typical Standard Edition RAC does not differ from the Enterprise Edition. To achieve a successful installation refer to the nice quick guide made by Yury Velikanov<\/a>\u00a0and change accordingly the Edition when installing the DB software.<\/p>\n

Standard Edition and Feature availability<\/strong><\/p>\n

The first thing that impressed me, is that you’re still able to choose to enable pluggable databases in DBCA even if Multitenant option is not available for the SE.<\/p>\n

So I decided to create a container database CDB01 using template files, so all options of EE are normally cabled into the new DB. The Pluggable Database name is PDB01.<\/p>\n

[oracle@se12c01 ~]$ sqlplus\r\n\r\nSQL*Plus: Release 12.1.0.1.0 Production on Wed Jul 3 14:21:47 2013\r\n\r\nCopyright (c) 1982, 2013, Oracle. All rights reserved.\r\n\r\nEnter user-name: \/ as sysdba\r\n\r\nConnected to:\r\nOracle Database 12c Release 12.1.0.1.0 - 64bit Production\r\nWith the Real Application Clusters and Automatic Storage Management options<\/pre>\n
As you can see, \u00a0the initial banner contains “Real Application Clusters and Automatic Storage Management options<\/strong>“.<\/p>\n
Multitenant option is not avilable. How SE reacts to its usage?<\/p>\n
First, on the ROOT db, dba_feature_usage_statistics is empty.<\/p>\n
SQL> alter session set container=CDB$ROOT;\r\n\r\nSession altered.\r\n\r\nSQL> select * from dba_feature_usage_statistics;\r\n\r\nno rows selected\r\n\r\nSQL><\/pre>\n
This is interesting, because all features are in (remember it’s created from the generic template) , so the feature check is moved from the ROOT to the pluggable databases.<\/p>\n
On the local PDB I have:<\/p>\n
SQL> alter session set container=PDB01;\r\n\r\nSession altered.\r\n\r\nSQL> select * from dba_feature_usage_statistics where lower(name) like '%multitenant%';\r\n\r\nNAME               VERSION    DETECTED_USAGES   TOTAL_SAMPLES   CURRE\r\n----------------------------- ----------------- --------------- -----\r\nOracle Multitenant 12.1.0.1.0                 0               0 FALSE<\/pre>\n
Having ONE PDB is not triggering the usage of Multitenant (as I was expecting).<\/p>\n
How if I try to create a new pluggable database?<\/p>\n
SQL> alter session set container=CDB$ROOT;\r\n\r\nSession altered.\r\n\r\nSQL> create pluggable database PDB02 admin user pdb02admin identified by pdb02admin;\r\ncreate pluggable database PDB02 admin user pdb02admin identified by pdb02admin\r\n*\r\nERROR at line 1:\r\nORA-65010: maximum number of pluggable databases created\r\n\r\nSQL><\/pre>\n
A-AH!! Correctly, I can have a maximum of ONE pluggable database in my container.<\/p>\n
This allows however:<\/p>\n