What Practical 1Z0-053 Training Tools Is

Using RMAN REPORT NEED BACKUP with Different Retention Policies (link)
You can specify different criteria for REPORT NEED BACKUP, using one of the following forms of the command:
REPORT NEED BACKUP RECOVERY WINDOW OF n DAYS
Displays objects requiring backup to satisfy a recovery window-based retention policy REPORT NEED BACKUP REDUNDANCY n
Displays objects requiring backup to satisfy a redundancy-based retention policy REPORT NEED BACKUP DAYS n
Displays files that require more than n days' worth of archived redo log files for recovery REPORT NEED BACKUP INCREMENTAL n
Displays files that require application of more than n incremental backups for recovery

None

View the Exhibit 1.
In the CUSTOMERS_OBE table, when the value of CUST_STATE_PROVINCE is "CA", the value of COUNTRY_ID is "US."
View the Exhibit exhibit2 to examine the commands and query plans. The optimizer can sense 8 rows instead of 29 rows, which is the actual number of rows in the table.
What can you do to make the optimizer detect the actual selectivity? desc-customers_obe (exhibit):

C:\Users\albo\Desktop\1-1.jpg
sql-select-customers_obe (exhibit):

C:\Users\albo\Desktop\1-1.jpg
A. Change the STALE_PERCENT value for the CUSTOMERS_OBE table.
B. Set the STATISTICS_LEVEL parameter to TYPICAL.
C. Create extended statistics for the CUST_STATE_PROVINCE and CUSTOMERS_OBE columns.
D. Set the OPTIMIZER_USE_PENDING_STATISTICS parameter to FALSE. Answer: C
Real example refer to here. Determining Single Column Statistics
A good example of correlated or related columns are the country_id and cust_state_province columns in the CUSTOMERS_OBE table. When the value of cust_state_province is 'CA' , the value of country_id is 'US'. There is a skew in the data in these two columns, which means the majority of rows in the table have the values 'CA' and 'US'. Both the relationship between the columns and the skew in the data make it difficult for the optimizer to calculate the selectivity or cardinality of these columns correctly when they are used together in a query. Extended statistics should help in this situation.

About Automated Maintenance Tasks (link)
Oracle Database has three predefined automated maintenance tasks:
✑ Automatic Optimizer Statistics Collection
✑ Automatic Segment Advisor
✑ Automatic SQL Tuning Advisor
By default, all three automated maintenance tasks are configured to run in all maintenance windows.

None

None

C:\Users\albo\Desktop\1-1.jpg
Use the CATALOG command to do the following:
Add backup pieces and image copies on disk to the RMAN repository
Record a data file copy as a level 0 incremental backup in the RMAN repository, which enables you to use it as part of an incremental backup strategy START WITH 'string_pattern'
Catalogs all valid backup sets, data file and control file copies, and archived redo log files whose name start with string_pattern. The string pattern can be an ASM disk group, Oracle-managed files directory, or part of a file name (see Example 2-32).
RMAN reports any files in the disk location that it cannot catalog. RMAN must be connected to a mounted target database.
If the string pattern specifies a file name, then it matches the left part of the file name pattern. For example, / tmp/arc matches everything in directory /tmp/arc_dest and
/tmp/archive/january as well as file /tmp/arc.cpy. Note: You cannot use wildcard characters in the string pattern, only a strict prefix.

None

None

None

None

None

Making User-Managed Backups of Online Read/Write Tablespaces
You must put a read/write tablespace in backup mode to make user-managed data file backups when the tablespace is online and the database is open. The ALTER TABLESPACE ... BEGIN BACKUP statement places a tablespace in backup mode. In backup mode, the database copies whole changed data blocks into the redo stream. After you take the tablespace out of backup mode with the ALTER TABLESPACE ... END BACKUP or ALTER DATABASE END BACKUP statement, the database advances the data file checkpoint SCN to the current database checkpoint SCN.
When restoring a data file backed up in this way, the database asks for the appropriate set of redo log files to apply if recovery is needed. The redo logs contain all changes required to recover the data files and make them consistent.

None

SCN
System Change Number. A database ordering primitive.
The value of an SCN is the logical point in time at which changes are made to a database. Refer to v11.2 document

DG_DROP_TIME is an invalid DG attribute. Disk Group Attributes
The DISK_REPAIR_TIME disk group attribute specifies how long a disk remains offline
before ASM drops the disk.
The COMPATIBLE.ASM attribute determines the minimum software version for an ASM instance that uses the disk group.
The COMPATIBLE.RDBMS attribute determines the minimum COMPATIBLE database initialization parameter setting for any database instance that uses the disk group.
The AU_SIZE attribute determines the allocation unit size of the disk group. The values can be 1, 2, 4, 8, 16, 32, and 64 MB.

None

Implementing the SQL Access Advisor Recommendations (link)
A SQL Access Advisor recommendation can range from a simple suggestion to a complex solution that requires partitioning a set of existing base tables and implementing a set of database objects such as indexes, materialized views, and materialized view logs. You can select the recommendations for implementation and schedule when the job should be executed.

None

The ADR root directory is known as ADR base. Its location is set by the DIAGNOSTIC_DEST initialization parameter. If this parameter is omitted or left null, the database sets DIAGNOSTIC_DEST upon startup as follows:
✑ If environment variable ORACLE_BASE is set, DIAGNOSTIC_DEST is set to the directory designated by ORACLE_BASE.
✑ If environment variable ORACLE_BASE is not set, DIAGNOSTIC_DEST is set to ORACLE_HOME/log.

Deciding When to Resynchronize the Recovery Catalog
RMAN automatically resynchronizes the recovery catalog when
✑ RMAN is connected to a target database and recovery catalog
✑ And you have executed RMAN commands.
Thus, you should not need to manually run the RESYNC CATALOG command very often.

Refer to here
About Quick Packaging and Custom Packaging
The Enterprise Manager Support Workbench provides two methods for creating and uploading an incident package: the quick packaging method and the custom packaging method.
Quick Packaging—This is the more automated method with a minimum of steps, organized in a guided workflow (a wizard). You select a single problem, provide a package name and description, and then schedule upload of the package contents, either immediately or at a specified date and time. The Support Workbench automatically places diagnostic data related to the problem into the package, finalizes the package, creates the zip file, and then uploads the file. With this method, you do not have the opportunity to add, edit, or remove package files or add other diagnostic data such as SQL test cases. However, it is the simplest and quickest way to get first-failure diagnostic data to Oracle Support. Quick packaging is the method used in the workflow described in "Investigating, Reporting, and Resolving a Problem".
Note that when quick packaging is complete, the package that was created by the wizard remains. You can then modify the package with custom packaging operations at a later time and manually reupload.
Custom Packaging—This is the more manual method, with more steps. It is intended for expert Support Workbench users who want more control over the packaging process. With custom packaging, you can create a new package with one or more problems, or you can add one or more problems to an existing package. You can then perform a variety of operations on the new or updated package, including:
✑ Adding or removing problems or incidents
✑ Adding, editing, or removing trace files in the package
✑ Adding or removing external files of any type
✑ Adding other diagnostic data such as SQL test cases
✑ Manually finalizing the package and then viewing package contents to determine if you must edit or remove sensitive data or remove files to reduce package size.
You might conduct these operations over a number of days, before deciding that you have enough diagnostic information to send to Oracle Support.
With custom packaging, you create the zip file and request upload to Oracle Support as two separate steps. Each of these steps can be performed immediately or scheduled for a future date and time.
Select the Full or Incremental option to generate a full package zip file or an incremental package zip file.
For a full package zip file, all the contents of the package (original contents and all correlated data) are always added to the zip file.
For an incremental package zip file, only the diagnostic information that is new or modified since the last time that you created a zip file for the same package is added to the zip file. For example, if trace information was appended to a trace file since that file was last included in the generated physical file for a package, the trace file is added to the
incremental package zip file. Conversely, if no changes were made to a trace file since it was last uploaded for a package, that trace file is not included in the incremental package zip file.

None

None

None