We are the best inside introducing one of the most useful 1Z0-062 equipment for the clients that may undoubtedly help make these people reach your goals in the real Oracle 1Z0-062 examination. A great Oracle manual includes a wonderful and finest basic materials which prepares a person totally and offers the actual guarantee of the achievement which isnt just a little factor. Merely download the Actualtests 1Z0-062 Oracle Database 12c: Installation and Administration totally free trial features to see the options and degree of Actualtests products. Youll be inspired from your 1Z0-062 study manual pdf defiantly. In the event you title any 100% success, using Actualtests 1Z0-062 for your Oracle Database 12c: Installation and Administration qualified preparing is the best choice.
2016 Jul exam 1z0-062:
Q1. Identify three benefits of Unified Auditing.
A. Decreased use of storage to store audit trail rows in the database.
B. It improves overall auditing performance.
C. It guarantees zero-loss auditing.
D. The audit trail cannot be easily modified because it is read-only.
E. It automatically audits Recovery Manager (RMAN) events.
Explanation: A: Starting with 12c, Oracle has unified all of the auditing types into one single unit called Unified auditing. You don’t have to turn on or off all of the different auidting types individually and as a matter of fact auditing is enabled by default right out of the box. The AUD$ and FGA$ tables have been replaced with one single audit trail table. All of the audit data is now stored in Secure Files table thus improving the overall management aspects of audit data itself.
B: Further the audit data can also be buffered solving most of the common performance related problems seen on busy environments.
E: Unified Auditing is able to collect audit data for Fine Grained Audit, RMAN, Data Pump, Label Security, Database Vault and Real Application Security operations.
* Benefits of the Unified Audit Trail
The benefits of a unified audit trail are many: / (B) Overall auditing performance is greatly improved. The default mode that unified audit works is Queued Write mode. In this mode, the audit records are batched in SGA queue and is persisted in a periodic way. Because the audit records are written to SGA queue, there is a significant performance improvement.
/ The unified auditing functionality is always enabled and does not depend on the initialization parameters that were used in previous releases
/ (A) The audit records, including records from the SYS audit trail, for all the audited components of your Oracle Database installation are placed in one location and in one format, rather than your having to look in different places to find audit trails in varying formats. This consolidated view enables auditors to co-relate audit information from different components. For example, if an error occurred during an INSERT statement, standard auditing can indicate the error number and the SQL that was executed. Oracle Database Vault-specific information can indicate whether this error happened because of a command rule violation or realm violation. Note that there will be two audit records with a distinct AUDIT_TYPE. With this unification in place, SYS audit records appear with AUDIT_TYPE set to Standard Audit.
/ The management and security of the audit trail is also improved by having it in single audit trail.
/ You can create named audit policies that enable you to audit the supported components listed at the beginning of this section, as well as SYS administrative users. Furthermore, you can build conditions and exclusions into your policies.
* Oracle Database 12c Unified Auditing enables selective and effective auditing inside the Oracle database using policies and conditions. The new policy based syntax simplifies management of auditing within the database and provides the ability to accelerate auditing based on conditions.
* The new architecture unifies the existing audit trails into a single audit trail, enabling simplified management and increasing the security of audit data generated by the database.
Q2. Flashback is enabled for your multitenant container database (CDB), which contains two pluggable database (PDBs). A local user was accidently dropped from one of the PDBs.
You want to flash back the PDB to the time before the local user was dropped. You connect to the CDB and execute the following commands:
SQL > SHUTDOWN IMMEDIATE SQL > STARTUP MOUNT SQL > FLASHBACK DATABASE to TIME “TO_DATE (‘08/20/12’ , ‘MM/DD/YY’)”;
Examine following commands:
1. ALTER PLUGGABLE DATABASE ALL OPEN;
2. ALTER DATABASE OPEN;
3. ALTER DATABASE OPEN RESETLOGS;
Which command or commands should you execute next to allow updates to the flashback back schema?
A. Only 1
B. Only 2
C. Only 3
D. 3 and 1
E. 1 and 2
Explanation: Example (see step23):
Run the RMAN FLASHBACK DATABASE command.
You can specify the target time by using a form of the command shown in the following
FLASHBACK DATABASE TO SCN 46963;
TO RESTORE POINT BEFORE_CHANGES;
FLASHBACK DATABASE TO TIME
When the FLASHBACK DATABASE command completes, the database is left mounted and recovered to the specified target time.
Make the database available for updates by opening the database with the RESETLOGS option. If the database is currently open read-only, then execute the following commands in SQL*Plus:
ALTER DATABASE OPEN RESETLOGS;
Q3. You upgraded from a previous Oracle database version to Oracle Database version to Oracle Database 12c. Your database supports a mixed workload. During the day, lots of insert, update, and delete operations are performed. At night, Extract, Transform, Load (ETL) and batch reporting jobs are run. The ETL jobs perform certain database operations using two or more concurrent sessions.
After the upgrade, you notice that the performance of ETL jobs has degraded. To ascertain the cause of performance degradation, you want to collect basic statistics such as the level of parallelism, total database time, and the number of I/O requests for the ETL jobs.
How do you accomplish this?
A. Examine the Active Session History (ASH) reports for the time period of the ETL or batch reporting runs.
B. Enable SQL tracing for the queries in the ETL and batch reporting queries and gather diagnostic data from the trace file.
C. Enable real-time SQL monitoring for ETL jobs and gather diagnostic data from the V$SQL_MONITOR view.
D. Enable real-time database operation monitoring using the DBMS_SQL_MONITOR.BEGIN_OPERATION function, and then use the DBMS_SQL_MONITOR.REPORT_SQL_MONITOR function to view the required information.
Explanation: * Monitoring database operations Real-Time Database Operations Monitoring enables you to monitor long running database tasks such as batch jobs, scheduler jobs, and Extraction, Transformation, and Loading (ETL) jobs as a composite business operation. This feature tracks the progress of SQL and PL/SQL queries associated with the business operation being monitored. As a DBA or developer, you can define business operations for monitoring by explicitly specifying the start and end of the operation or implicitly with tags that identify the operation.
Q4. Examine the query and its output:
SQL> SELECT REASON, metric_value FROM dba_outstanding_alerts;
Tablespace [TEST] is [28 perce 28.125 nt] full
Metrics "Current Logons Count"29
Metrics "Database Time Spent99.0375405 waiting (%)" is at 99.03754 for event class "Application" db_recovery_file_dest_size of97 4294967296 bytes is 97.298 used and has 116228096 remaining bytes available.
After 30 minutes, you execute the same query:
SQL> SELECT reason, metric_value FROM dba_outstanding_alerets;
Tablespace [TEST] is [28 percs 28.125 nt] full
What might have caused three of the alerts to disappear?
A. The threshold alerts were cleared and transferred to d0A_alert_history.
B. An Automatic Workload Repository (AWR) snapshot was taken before the execution of the second
C. An Automatic Database Diagnostic Monitor (ADOM) report was generated before the execution of the second query.
D. The database instance was restarted before the execution of the second query.
Q5. 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 zero.
What must you do to activate the new default value for numeric full redaction?
A. Re-enable redaction policies that use FULL data redaction.
B. Re-create redaction policies that use FULL data redaction.
C. Re-connect the sessions that access objects with redaction policies defined on them.
D. Flush the shared pool.
E. Restart the database instance.
Explanation: 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.
* 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.
Reference: Oracle Database Advanced Security Guide 12c, About Altering the Default Full Data Redaction Value
Renewal 1z0-062 ebook:
Q6. Which three activities are supported by the Data Recovery Advisor?
A. Advising on block checksum failures
B. Advising on inaccessible control files
C. Advising on inaccessible block change tracking files
D. Advising on empty password files
E. Advising on invalid block header field values
Explanation: * Data Recovery Advisor can diagnose failures such as the following:
/ (B) Components such as datafiles and control files that are not accessible because they do not exist, do not have the correct access permissions, have been taken offline, and so on
/ (A, E) Physical corruptions such as block checksum failures and invalid block header field values
/ Inconsistencies such as a datafile that is older than other database files / I/O failures such as hardware errors, operating system driver failures, and exceeding operating system resource limits (for example, the number of open files)
* The Data Recovery Advisor automatically diagnoses corruption or loss of persistent data on disk, determines the appropriate repair options, and executes repairs at the user's request. This reduces the complexity of recovery process, thereby reducing the Mean Time To Recover (MTTR).
Q7. A senior DBA asked you to execute the following command to improve performance:
SQL> ALTER TABLE subscribe log STORAGE (BUFFER_POOL recycle);
You checked the data in the SUBSCRIBE_LOG table and found that it is a large table
containing one million rows.
What could be a reason for this recommendation?
A. The keep pool is not configured.
B. Automatic Workarea Management is not configured.
C. Automatic Shared Memory Management is not enabled.
D. The data blocks in the SUBSCRIBE_LOG table are rarely accessed.
E. All the queries on the SUBSCRIBE_LOG table are rewritten to a materialized view.
Explanation: The most of the rows in SUBSCRIBE_LOG table are accessed once a week.
Q8. Your multitenant container database, CDB1, is running in ARCHIVELOG mode and has two pluggable databases, HR_PDB and ACCOUNTS_PDB. An RMAN backup exists for the database.
You issue the command to open ACCOUNTS_PDB and find that the USERDATA.DBF data file for the default permanent tablespace USERDATA belonging to ACCOUNTS_PDB is corrupted.
What should you do before executing the commands to restore and recover the data file in ACCOUNTS_PDB?
A. Place CDB1 in the mount stage and then the USERDATA tablespace offline in ACCOUNTS_PDB.
B. Place CDB1 in the mount stage and issue the ALTER PLUGGABLE DATABASE accounts_pdb CLOSE IMMEDIATE command.
C. Issue the ALTER PLUGGABLE DATABASE accounts_pdb RESTRICTED command.
D. Take the USERDATA tablespace offline in ACCOUNTS_PDB.
Explanation: * You can take an online tablespace offline so that it is temporarily unavailable for general use. The rest of the database remains open and available for users to access data. Conversely, you can bring an offline tablespace online to make the schema objects within the tablespace available to database users. The database must be open to alter the availability of a tablespace.
Q9. Examine the following impdp command to import a database over the network from a pre-12c Oracle database (source):
Which three are prerequisites for successful execution of the command?
A. The import operation must be performed by a user on the target database with the DATAPUMP_IMP_FULL_DATABASE role, and the database link must connect to a user on the source database with the DATAPUMP_EXD_FULL_DATABASE role.
B. All the user-defined tablespaces must be in read-only mode on the source database.
C. The export dump file must be created before starting the import on the target database.
D. The source and target database must be running on the same platform with the same endianness.
E. The path of data files on the target database must be the same as that on the source database.
F. The impdp operation must be performed by the same user that performed the expdp operation.
Explanation: In this case we have run the impdp without performing any conversion if
endian format is different then we have to first perform conversion.
Q10. The hr user receiver, the following error while inserting data into the sales table:
ERROR at line 1:
ORA-01653; unable to extend table HR.SALES by 128 in tablespace USERS
On investigation, you find that the users tablespace uses Automnrif Segment Space Management (ASSM). It is the default tablespace for the HR user with an unlimited quota on it.
Which two methods would you use to resolve this error?
A. Altering the data life associated with the USERS tablespace to ex automatically
B. Adding a data life to the USERS tablespace
C. Changing segment space management for the USERS tablespace to manual
D. Creating a new tablespace with autoextend enabled and changing the default tablespace of the HR user to the new tablespace
E. Enabling resumable space allocation by setting the RESUMABLE_TIMEOUT parameter to a nonzero value