After implementing full Oracle Data Redaction, you change the default value for the NUMBER data type as follows:
After changing the value, you notice that FULL redaction continues to redact numeric data with a zero.
What must you do to activate the new default value for numeric full redaction?
About Altering the Default Full Data Redaction Value
You can alter the default displayed values for full Data Redaction polices. By default, 0 is the redacted value when Oracle Database performs full redaction (DBMS_REDACT.FULL) on a column of the NUMBER data type. If you want to change it to another value (for example, 7), then you can run the DBMS_REDACT.UPDATE_FULL_REDACTION_VALUES procedure to modify this value. The modification applies to all of the Data Redaction policies in the current database instance. After you modify a value, you must restart the database for it to take effect.
Note:
* The DBMS_REDACT package provides an interface to Oracle Data Redaction, which enables you to mask (redact) data that is returned from queries issued by low-privileged users or an application.
* UPDATE_FULL_REDACTION_VALUES Procedure
This procedure modifies the default displayed values for a Data Redaction policy for full redaction.
* After you create the Data Redaction policy, it is automatically enabled and ready to redact data.
* Oracle Data Redaction enables you to mask (redact) data that is returned from queries issued by low-privileged users or applications. You can redact column data by using one of the following methods:
/ Full redaction.
/ Partial redaction.
/ Regular expressions.
/ Random redaction.
/ No redaction.
Your multitenant container database (CDB) contains several pluggable databases (PDBs). Users c# #A admin and B_ADMIN have only connect privileges.
You create a common role c##_role1 with common privileges create table and select any table.
You then execute these commands to grant the role to users In the root container:
SQL> GRANT c##_role1 TO c##_a_admin CONTAINER=ALL;
Then,
SQL> CONN sys/oraclHR_PDB as sysdba
SQL> GRANT C# #_role1 TO b_admin CONTAINER=CURRENT;
Which two statements are true?
Examine the current values for the following parameters in your database instance:
SGA_MAX_SIZE = 1024M
SGA_TARGET = 700M
DB_8K_CACHE_SIZE = 124M
LOG_BUFFER = 200M
You issue the following command to increase the value of DB_8K_CACHE_SIZE:
SQL> ALTER SYSTEM SET DB_8K_CACHE_SIZE=140M;
Which statement is true?
Which three features work together, to allow a SQL statement to have different cursors for the same statement based on different selectivity ranges? (Choose three.)
* In bind variable peeking (also known as bind peeking), the optimizer looks at the value in a bind variable when the database performs a hard parse of a statement.
When a query uses literals, the optimizer can use the literal values to find the best plan. However, when a query uses bind variables, the optimizer must select the best plan without the presence of literals in the SQL text. This task can be extremely difficult. By peeking at bind values the optimizer can determine the selectivity of a WHERE clause condition as if literals had been used, thereby improving the plan.
C: Oracle 11g/12g uses Adaptive Cursor Sharing to solve this problem by allowing the server to compare the effectiveness of execution plans between executions with different bind variable values. If it notices suboptimal plans, it allows certain bind variable values, or ranges of values, to use alternate execution plans for the same statement. This functionality requires no additional configuration.
Your multitenant container database (CDB) contains two pluggable databases (PDBs). Which three tools can be used to add a new PDB to the CDB?
