\n
![\"Capture1\"](\"https://www.dbi-services.com/blog/wp-content/uploads/sites/2/2022/04/Capture1.png\")
\nbut you will not find the AUX_COUNT there:
\n
![\"CaptureMTFU2\"](\"https://www.dbi-services.com/blog/wp-content/uploads/sites/2/2022/04/CaptureMTFU2.png\")
\nSo unfortunatly you have no clue about the need to licence the option from there.
.
\nMatching the Feature Usage Statistics to licensed options is not always easy. And once a feature usage is recorded, it is usually stored definitively. Let’s see how the multitenant option is recorded there.
\n
I have a single-tenant database with only one user pluggable database:
\n\n16:19:20 SQL> show pdbs\n \n CON_ID CON_NAME OPEN MODE RESTRICTED\n---------- ------------------------------ ---------- ----------\n 2 PDB$SEED READ ONLY NO\n 3 PDB READ WRITE NO\nTwo pluggable databases are displayed. The forst one is the seed (CON_ID=2) and user pluggable databases have CON_ID>2.
\nand I run the Database Feature Usage Sampling:
\n16:19:20 SQL> exec sys.dbms_feature_usage_internal.exec_db_usage_sampling(sysdate); commit;\n \nPL/SQL procedure successfully completed.\n \nUsually this is run automatically on weekly basis, but we can run it manually as I did above.
\nLet’s check the result from DBA_FEATURE_USAGE_STATISTICS:
\n\n16:19:34 SQL> select name, version, detected_usages, aux_count, feature_info,last_usage_date from dba_feature_usage_statistics where name = 'Oracle Pluggable Databases';\n \nNAME VERSION DETECTED_USAGES AUX_COUNT FEAT LAST_USAGE_DATE\n-------------------------- ----------- --------------- ---------- ---- ---------------\nOracle Pluggable Databases 12.1.0.2.0 11 1 27-MAR 16:19:20\nHere is the first conclusion: ‘Oracle Pluggable Database’ is the initial name of ‘Oracle Multitenant’ feature and is used as long as we are in CDB.
\nYou don’t need the Multitenant Option for that as long as AUX_COUNT is 1 because AUX_COUNT is the number of user pluggable databases.
I’ll create an additional pluggable database. I Standard Edition, I can’t (ORA-65010: maximum number of pluggable databases created) but in Enterprise Edition there is no supported way to prevent it:
\n\n16:19:34 SQL> create pluggable database PDB2 from PDB file_name_convert=('/PDB/','/PDB2/');\n \nPluggable database created.\n \n16:20:54 SQL> show pdbs\n \n CON_ID CON_NAME OPEN MODE RESTRICTED\n---------- ------------------------------ ---------- ----------\n 2 PDB$SEED READ ONLY NO\n 3 PDB READ WRITE NO\n 4 PDB2 MOUNTED\nAnd I run again the sampling:
\n\n16:20:54 SQL> exec sys.dbms_feature_usage_internal.exec_db_usage_sampling(sysdate); commit;\n \nPL/SQL procedure successfully completed.\n \n16:21:15 SQL> select name, version, detected_usages, aux_count, feature_info,last_usage_date from dba_feature_usage_statistics where name = 'Oracle Pluggable Databases';\n \nNAME VERSION DETECTED_USAGES AUX_COUNT FEAT LAST_USAGE_DATE\n-------------------------- ----------- --------------- ---------- ---- ---------------\nOracle Pluggable Databases 12.1.0.2.0 12 2 27-MAR 16:20:54\nThe difference here is the AUX_COUNT. When higher than 1 you need to buy the Multitenant Option.
\nThe DBA_FEATURE_USAGE_STATISTICS is displayed in Enterprise Manager:
\n
\nbut you will not find the AUX_COUNT there:
\n
\nSo unfortunatly you have no clue about the need to licence the option from there.
When you don’t have the Multitenant Option, as you don’t have a way to prevent licence violation, you need to monitor that AUX_COUNT and raise an alert. Then what to do? Here, because the difference between single-tenant and multitenant is only in AUX_COUNT, and only the latest AUX_COUNT value is stored you can easily repair your error.
\nFirst, you drop the additional pluggable database (plug it into another CDB if you still need it):
\n\n16:21:15 SQL> drop pluggable database PDB2 including datafiles;\n \nPluggable database dropped.\n \n16:21:16 SQL> show pdbs\n \n CON_ID CON_NAME OPEN MODE RESTRICTED\n---------- ------------------------------ ---------- ----------\n 2 PDB$SEED READ ONLY NO\n 3 PDB READ WRITE NO\nThen run sampling again:
\n\n16:21:16 SQL> exec sys.dbms_feature_usage_internal.exec_db_usage_sampling(sysdate); commit;\n \nPL/SQL procedure successfully completed.\nand the temporary violation of single-tenant disappeared:
\n\n16:21:30 SQL> select name, version, detected_usages, aux_count, feature_info,last_usage_date from dba_feature_usage_statistics where name = 'Oracle Pluggable Databases';\n \nNAME VERSION DETECTED_USAGES AUX_COUNT FEAT LAST_USAGE_DATE\n-------------------------- ----------- --------------- ---------- ---- ---------------\nOracle Pluggable Databases 12.1.0.2.0 13 1 27-MAR 16:21:16\nYou don’t need to run the full sampling in order to check the number of pluggable databases. You can call the DBMS_PDB_NUM:
\n\n16:21:30 SQL> variable feature_boolean number\n16:21:30 SQL> variable aux_count number\n16:21:30 SQL> variable feature_info clob\n16:21:30 SQL> exec dbms_pdb_num(:feature_boolean,:aux_count,:feature_info);\n \nPL/SQL procedure successfully completed.\n \n16:21:30 SQL> print\n \nFEATURE_BOOLEAN\n---------------\n 1\n \n AUX_COUNT\n----------\n 1\n \nFEATURE_INFO\n--------------------------------------------------------------------------------\n \nIf you check catfusrg.sql in rdbms/admin you know how it is collected: the usage consider that V$DATABASE.CDB=’YES’ and the AUX_COUNT counts V$PDBS where CON_ID > 2
\nWhile we are there, let’s show another way to report from DBA_FEATURE_USAGE_STATISTICS:
\n\n16:21:30 SQL> SELECT output FROM TABLE(dbms_feature_usage_report.display_text);\n \nOUTPUT\n--------------------------------------------------------------------------------\nDB FEATURE USAGE report for\n \nDB Name DB Id Release Total Samples Last Sample Time\n------------ ----------- ----------- ------------- ------------------\nCDB 2021614852 12.1.0.2.0 1 24-Mar-16 10:02:09\n \n -------------------------------------------------------------\n \nDB Feature Usage Summary DB/Release: CDB/12.1.0.2.0\n-> This section displays the summary of Usage for Database Features.\n-> The Currently Used column is TRUE if usage was detected for\n-> the feature at the last sample time.\n \n Curr-\n ently Detected Total Last Usage\nFeature Name Used Usages Samples Time\n----------------------------------------- ----- -------- -------- --------------\nResource Manager TRUE 1 1 03/24/16 10:02\n...\nOracle Pluggable Databases FALSE 13 1 03/27/16 16:21\n...\nDB Feature Usage Details DB/Release: CDB/12.1.0.2.0\n-> This section displays the detailed usage data for the features\n-> that have at least one detected usage\n \nFeature Name\n------------------------------------------------------------\nDetected Usages Total Samples First Usage Date Last Usage Date Aux Count\n--------------- -------------- ----------------- ----------------- ----------\nFeature Info\n--------------------------------------------------------------------------------\n...\nOracle Pluggable Databases\n 13 1 03/24/16 10:02 03/27/16 16:21 1\nThere are currently (in 12.1) no way to limit to single-tenant when you are in Enterprise Edition, but there is an Evolution Request filled about it and we can expect to be able to set something like a ‘max pdbs’ parameters in future release. Anyway, it’s easy to monitor usage and get back to single-tenant.
\n", "protected": false } }