It is always worth it to do the math and see what licensing model is the most cost-effective for you. In Oracle Cloud, you have standardization and simplicity. For EE, it becomes a bit tricky. At the end of the day, you are only allowed to use database options you have supported licenses for. The benefit here is that you have the flexibility to add database options as needed without migrating your database to a new VM DB System.
However, you have to make sure that your developers and DBAs only use those database options you are eligible for as you usually do on-premises. A: No! Similar to on-premises, you only need the EE supported license and you are allowed to use any database option that you have licenses for.
In ExaCS and ExaCC, you may use the following database options and features even if you do not have the corresponding licenses:.
A: Legally, No! Furthermore, all Cloud Automation provided patching, upgrade, automatic backups, one-click restore, etc. In short, it just does not make sense to me. If you are on 19c, what you should be, then you are allowed to use 3 PDBs without the Multitenant option license.
In the end, the question is, how many databases do you want to run in your Exadata environment? Oracle management packs cannot be used with Personal Edition. In addition to the Oracle Database offerings listed in the preceding table, this guide describes licensing policies for Authorized Cloud Environments. For more information about these environments, refer to the following document:.
The tables in this section list Oracle Database features, Oracle Database options, and Oracle management packs, and their availability for each Oracle Database offering. These tables can help you understand the difference between Oracle Database offerings to determine which one is right for you. Consolidation - Table Development Platform - Table High Availability - Table Integration - Table Manageability - Table Networking - Table Performance - Table Scalability - Table Security - Table Snapshots and Cloning - Table Spatial and Graph Data - Table Oracle Multitenant.
The number value in each column indicates the maximum number of pluggable databases PDBs that can be created for each offering. For all offerings, if you are not licensed for Oracle Multitenant, then the container database architecture is available in single-tenant mode, that is, with one user-created PDB, one user-created application root, and one user-created proxy PDB.
Microsoft Distributed Transaction Coordinator support. Oracle Fail Safe. Oracle Data Guard—Redo Apply. Oracle Active Data Guard. Online index rebuild. Block change tracking for fast incremental backup. Block-level media recovery. Automatic Block Repair. Parallel backup and recovery. Tablespace point-in-time recovery. Trial recovery. Fast-start fault recovery.
Optimization for Flashback Data Archive. Recovering tables and table partitions from RMAN backups. Oracle Streams. All other Database Gateway products are available for all offerings, but require a separate product license.
AQ Sharded Queues. Oracle Data Masking and Subsetting Pack. Oracle Diagnostics Pack. Oracle Tuning Pack. Oracle Real Application Testing. SQL Tuning Sets. Oracle Fleet Patching and Provisioning. Oracle Connection Manager.
Available via a custom install of the Oracle Database client, usually installed on a separate machine or compute instance. Client Side Query Cache. Database Smart Flash Cache. Oracle Database In-Memory. Automatic Workload Management.
Oracle Advanced Security. Oracle Database Vault. Oracle Label Security. Real Application Security. Oracle Spatial and Graph. Oracle Spatial and Graph no longer requires an extra cost license. See Oracle Database Insider blog post for more information. Partitioned spatial indexes.
Oracle Partitioning. Oracle Machine Learning formerly Advanced Analytics. Oracle Machine Learning no longer requires an extra cost license. Oracle Advanced Compression. Prefix Compression also called Key Compression. Basic Table Compression. Bitmapped index, bitmapped join index, and bitmap plan conversions. Parallel capture and apply via XStream. Transportable tablespaces, including cross-platform and full transportable export and import.
Summary management—Materialized View Query Rewrite. Table lists Oracle Database options, the Oracle Database offerings for which each option is available, and the features that are included with each option. You must be licensed for an option in order to use any of its features.
Fast Incremental Backup on Physical Standby. In an Oracle Data Guard configuration, Oracle Active Data Guard must be licensed on any standby databases with any of the above features in use, as well as the primary database. If there are additional standby databases in the Oracle Data Guard configuration that are not using any of the Oracle Active Data Guard features, those standby databases do not require an Oracle Active Data Guard license.
Oracle Active Data Guard must still be licensed on standby databases, if any other of the above features are in use. Exadata Flash Cache Compression This feature can be enabled only on Exadata storage servers, and all database processors that access the Exadata storage servers must be licensed for Oracle Advanced Compression.
Oracle Advanced Security includes a restricted use license for certain Oracle Enterprise Manager features. Oracle Database Vault includes a restricted use license for certain Oracle Enterprise Manager features. Oracle Label Security includes a restricted use license for certain Oracle Enterprise Manager features. For EE and PE , the ability to have up to pluggable databases per multitenant container database. A restricted use license for Oracle Multitenant is included with all Oracle Database offerings.
Oracle Real Application Testing includes the following features:. The Oracle Real Application Testing license is required on both capture and replay systems for Database Replay and is charged by the total number of CPUs on those systems. Database Migration Planner, introduced in Oracle Enterprise Manager Cloud Control 13c, provides a data-driven and systematic approach to consolidation by eliminating guess work and human errors. On the database target home page, select the Administration menu, then select Database Migration Planner.
All features, functions, links, buttons, and drill-downs on this page are licensed as part of the Database Migration Planner. Database Migration Workbench, introduced in Oracle Enterprise Manager Cloud Control 13c Release 4, is a single workbench that integrates all needs for migration sizing and performance comparison. All features, functions, links, buttons, and drill-downs on this page are licensed as part of the Database Migration Workbench. Table lists Oracle management packs, the Oracle Database offerings for which each pack is available, and the features that are included with each pack.
You must be licensed for a management pack in order to use any of its features. Database-as-a-Service comprising self-service database provisioning on physical or virtual infrastructure. Support shared server, shared cluster, and shared database Schema-as-a-Service deployment models. Virtual assembly provisioning. For example, if there is an assembly topology of three VMs two WebLogic Server-managed servers and one database , you will need both packs to cover the respective tiers.
Metering and chargeback based on fixed cost, utilization metrics and configuration parameters of the database. Starting on the Enterprise Summary home page, click the Enterprise menu. Cloud , then Infrastructure Home. Cloud , then Infrastructure Request Dashboard. Cloud , then Infrastructure Policies. Cloud , then Middleware and Database Home. Cloud , then Middleware and Database Request Dashboard. Cloud , then Self Service Portal.
Cloud , then Service Instances. Provisioning and Patching , then Database Provisioning. Starting on the Enterprise Summary home page, click the Setup menu. Provisioning and Patching , then Storage Registration. On the Multitenant container database's home page, from the Oracle Database menu, select Provisioning , then Provision Pluggable Database. These verbs operate on a database pool. The following objects within the repository schema are licensed under Oracle Cloud Management Pack for Oracle Database:.
Also, any report created using the "create-like" feature of BI publisher referring the preceding reports, falls under this license. This characteristic is valid across multiple databases or multiple runs assuming that the same substitution values are used in the two runs. That is, the actual rows and values in the substitution table do not change. For example, suppose the two values Joe and Tom were masked to Henry and Peter. When you repeat the same mask on another database using the same substitution table, if there were Bob and Tom, they might be replaced with Louise and Peter.
Notice that even though the two runs have different data, Tom is always replaced with Peter. Substring is similar to the database substr function. The start position can be either a positive or a negative integer. For example, if the original string is abcd , a substring with a start position of 2 and length of 3 generates a masked string of bcd. A substring with start position of -2 and length of 3 generates a masked string of cd. A table column enables you to select values from the chosen column as the replacement value or part thereof.
The data type and uniqueness must be compatible. Truncates all rows in a table. If one of the columns in a table is marked as truncated, the entire table is truncated, so no other mask formats can be specified for any of the other columns. If a table is being truncated, it cannot be referred to by a foreign key constraint or a dependent column.
You may occasionally need to consistently mask multiple, distinct databases. For instance, if you run HR, payroll, and benefits that have an employee ID concept on three separate databases, the concept may be consistent for all of these databases, in that an employee's ID can be selected to retrieve the employee's HR, payroll, or benefits information. Deterministic masking provides a solution for this problem. You can use the Substitute format to mask employee ID column s in all three databases.
The Substitute format uses a table of values from which to substitute the original value with a mask value. As long as this table of values does not change, the mask is deterministic or consistent across the three databases.
Ensure that you have the following minimum privileges for data masking:. Ensure the format you select does not violate check constraints and does not break any applications that use the data. Exercise caution when masking partitioned tables, especially if you are masking the partition key.
In this circumstance, the row may move to another partition. Data Masking does not support clustered tables, masking information in object tables, XML tables, and virtual columns.
Relational tables are supported for masking. If you plan to mask a test system intended for evaluating performance, the following practices are recommended:.
Try to preserve the production statistics and SQL profiles after masking by adding a pre-masking script to export the SQL profiles and statistics to a temporary table, then restoring after masking completes. Any performance changes other than what appears in the evaluation report are usually related to application-specific changes on the masked database. To create a masking definition:.
The Data Masking Definitions page appears, where you can create and schedule new masking definitions and manage existing masking definitions. A masking definition includes information regarding table columns and the format for each column. You can choose which columns to mask, leaving the remaining columns intact. When you click the search icon and select an Application Data Model ADM name from the list, the system automatically populates the Reference Database field. When you enable this check box, the masking definition is evaluated to determine if the SQL Expression format or conditional masking is being used.
If either is in use when you click OK, the option becomes unchecked and an error message appears asking you to remove these items before selecting this option. Either select one or more columns for later formatting on the Create Masking Definition page, or formatting now if the data types of the columns you have selected are identical. Optional : if you want to mask selected columns as a group, enable Mask selected columns as a group. The columns that you want to mask as a group must all be from the same table.
Enable this check box if you want to mask more than one column together, rather than separately. When you select two or more columns and then later define the format on the Define Group Mask page, the columns appear together, and any choices you make for format type or masking table apply collectively to all of the columns.
After you define the group and return to this page, the Column Group column in the table shows an identical number for each entry row in the table for all members of the group. For example, if you have defined your first group containing four columns, each of the four entries in this page will show a number 1 in the Column Group column. If you define another group, the entries in the page will show the number 2, and so forth.
This helps you to distinguish which columns belong to which column groups. Either click Add to add the column to the masking definition, return to the Create Masking Definition page and define the format of the column later, or click Define Format and Add to define the format for the column now. The Define Format and Add feature can save you significant time. When you select multiple columns to add that have the same data type, you do not need to define the format for each column as you would when you click Add.
You will eventually need to define the format of the column in the Create Masking Definition page before you can continue. When you are ready to do so, click the icon in the page Format column for the column you want to format. Depending on whether you decided to mask selected columns as a group on the Add Columns page, either the Define Column mask or Define Group mask appears. Read further in this step for instructions for both cases. If you clicked Define Format and Add in the previous step and did not check Mask selected columns as a group :.
The Define Column Mask page appears, where you can define the format for the column before adding the column to the Create Masking Definition page, as explained below:.
Provide a format entry for the required Default condition by either selecting a format entry from the list and clicking Add , or clicking Import Format , selecting a predefined format on the Import Format page, then clicking Import.
The Import Format page displays the formats that are marked with the same sensitive type as the masked column. For information about Oracle-supplied predefined masking format definitions, see "Using Oracle-supplied Predefined Masking Formats". Add another condition by clicking Add Condition to add a new condition row, then provide one or more format entries as described in the previous step.
When you have finished formatting the column, click OK to return to the Create Masking Definition page. If you clicked Define Format and Add in the previous step and checked Mask selected columns as a group :. The Define Group Mask page appears, where you can add format entries for group columns that appear in the Create Masking Definition page, as explained below:. Select one of the available format types. For complete information on the format types, see the online help for the Defining the Group Masking Format topic.
When you have finished formatting the group, click OK to return to the Create Masking Definition page. Your configuration appears in the Columns table. The sensitive columns you selected earlier now appear on this page. The selected columns are the primary key, and the foreign key columns are listed below.
These columns are masked as well. Expand Show Advanced Options and decide whether the selected default data masking options are satisfactory.
Select the definition and click Generate Script to view the script for the list of database commands used to mask the columns you selected earlier. This process checks whether sufficient disk space is available for the operation, and also determines the impact on other destination objects, such as users, after masking.
After the process completes, the Script Generation Results page appears, enabling you to do the following:. Clone and mask the database using the Clone Database wizard this requires a Database Lifecycle Management Pack license. If you are working with a production database, click Clone and Mask to clone and mask the database you are currently working with to ensure that you do not mask your production database.
If you are already working with a test database and want to directly mask the data in this database, click Schedule Job. Provide the requisite information and desired options. You can specify the database at execution time to any database.
The system assumes that the database you select is a clone of the source database. By default, the source database from the ADM is selected. The Data Masking Definitions page appears. The job has been submitted to Enterprise Manager and the masking process appears. The Status column on this page indicates the current stage of the process. Here are some guidelines for estimating space requirements for masking operations.
These estimates are based on a projected largest table size of GB. In making masking space estimates, assume a "worst-case scenario. Worse case is every column is to be masked. You can specify a tablespace for mapping tables during script generation. If you do not specify a tablespace, the tables are created in the tablespace of the executing user.
There are some situations, for example when using the shuffle format, that do not require a mapping table. In these cases, updates to the original table happen in-line. Dependent columns are defined by adding them to the Application Data Model. The following prerequisites apply for the column to be defined as dependent:. If the column does not meet these criteria, an "Invalid Dependent Columns" message appears when you attempt to add the dependent column.
The following procedure explains how to mask data across columns for packaged applications in which the relationships are not defined in the data dictionary.
To mask dependent columns for packaged applications:. Manually add a referential relationship:. When sensitive column discovery is complete, review the columns found by the discovery job and mark them sensitive or not sensitive as needed.
When marked as sensitive, any discovery sensitive column also marks its parent and the other child columns of the parent as sensitive. Consequently, it is advisable to first create the ADM with all relationships. ADM by default, or after running drivers, may not contain denormalized relationships. You need to manually add these. For more information about sensitive column discovery, see step 6. Enterprise Manager executes the generated script on the target database and masks all of your specified columns.
The following options on the Masking Definitions page are all checked by default, so you need to uncheck the options that you do not want to enable:. Masking disables redo logging and flashback logging to purge any original unmasked data from logs. However, in certain circumstances when you only want to test masking, roll back changes, and retry with more mask columns, it is easier to uncheck this box and use a flashback database to retrieve the old unmasked data after it has been masked.
You can use Enterprise Manager to flashback a database. If you have already enabled statistics collection and would like to use special options when collecting statistics, such as histograms or different sampling percentages, it is beneficial to turn off this option to disable default statistics collection and run your own statistics collection jobs.
Masking creates temporary tables that map the original sensitive data values to mask values. In some cases, you may want to preserve this information to track how masking changed your data. Note that doing so compromises security. These tables must be dropped before the database is available for unprivileged users. This option decrypts columns that were previously masked using Encrypt format. To decrypt a previously encrypted column, the seed value must be the same as the value used to encrypt.
Decrypt only recovers the original value if the original format used for the encryption matches the original value. If the originally encrypted value did not conform to the specified regular expression, when decrypted, the encrypted value cannot reproduce the original value. Oracle Database can make parallel various SQL operations that can significantly improve their performance. Data Masking uses this feature when you select this option.
You can enable Oracle Database to automatically determine the degree of parallelism, or you can specify a value. For more information about using parallel execution and the degree of parallelism, see Oracle Database Data Warehousing Guide. Additionally, if you use the Substitute format, a seed value is required when you schedule the masking job or database clone job.
When masking a test system to evaluate performance, it is beneficial to preserve the object statistics after masking. You can accomplish this by adding a pre-masking script to export the statistics to a temporary table, then restoring them with a post-masking script after masking concludes.
Since masking modifies data, you can also perform tasks, such as rebalancing books or calling roll-up or aggregation modules, to ensure that related or aggregate information is consistent. Example Pre-masking Script for Preserving Statistics. Example Post-masking Script for Preserving Statistics. When you clone and mask the database, a copy of the masking script is saved in the Enterprise Manager repository and then retrieved and executed after the clone process completes.
Therefore, it is important to regenerate the script after any schema changes or modifications to the production database. To clone and optionally mask the masking definition's target database:. From the Data Masking Definitions page, select the masking definition you want to clone, select Clone Database from the Actions list, then click Go. The Clone Database wizard appears, where you can create a test system to run the mask. You can also access this wizard by clicking the Clone and Mask button from the Script Generation Results page.
Specify the type of source database backup to be used for the cloning operation, then click Continue. Proceed through the wizard steps as you ordinarily would to clone a database. For assistance, refer to the online help for each step. In the Database Configuration step of the wizard, add a masking definition, then select the Run SQL Performance Analyzer option as well as other options as desired or necessary.
You can import and re-use a previously exported data masking definition template, including templates for Fusion Applications, saved as an XML file to the current Enterprise Manager repository. Verify that the name of the masking definition to be imported does not already exist in the repository. To import a data masking template:. The Data Masking Definitions Page reappears and displays the imported definition in the table list for subsequent viewing and masking.
After you have created a data masking definition, you may want to use it to analyze the performance impact from masking on a test system. The procedures in the following sections explain the process for this task for masking only, or cloning and masking. From the Data Masking Definitions page, select the masking definition to be analyzed, then click Schedule Job.
The script file location pertains to the masking script, which also contains the pre- and post-masking scripts you created in "Pre- and Post-mask Scripts". This section only appears for masking definitions that use the Substitute or Encrypt formats. If you use a SQL Tuning Set that has sensitive data to evaluate performance, it is beneficial to mask it for security, consistency of data with the database, and to generate correct evaluation results. Select the Capture Files option, if desired, then select a capture directory.
When you select this option, the contents of the directory is masked. The capture file masking is executed consistently with the database.
0コメント