[Free] 2018(Jan) Latesttests Testking Oracle 1z0-053 Dumps with VCE and PDF Download 451-460

Latesttests 2018 Jan Oracle Official New Released 1z0-053
100% Free Download! 100% Pass Guaranteed!
http://www.Latesttests.com/1z0-053.html

Oracle Database 11g: Administration II

Question No: 451 – (Topic 13)

Which two activities are NOT supported by the Data Recovery Advisor? (Choose two.)

  1. Diagnose and repair a data file corruption offline.

  2. Diagnose and repair a data file corruption online.

  3. Diagnose and repair failures on a standby database.

  4. Recover from failures in the Real Application Cluster (RAC) environment.

Answer: C,D

Question No: 452 – (Topic 13)

View the Exhibit and note the contents of V$DIAG_INFO. Which statement is true about the ADR?

Exhibit:

Latesttests 2018 PDF and VCE

  1. The text alert log file will be available in Diag Trace

  2. A copy alert log file will be kept in Diag Incident for every incident.

  3. The XML version of the alert log file will be available in Diag Trace.

  4. An Automatic Database Diagnostic Management (ADDM) report is generated and stored in the Health Monitor whenever an incident occurs.

Answer: A Explanation:

Latesttests 2018 PDF and VCE

C:\Users\albo\Desktop\1-1.jpg

alert, The XML-formatted alert log cdump, Core files

incident, Multiple subdirectories, where each subdirectory is named for a particular incident, and where each contains dumps pertaining only to that incident

trace, Background and server process trace files, SQL trace files, and the text-formatted alert log

(others), Other subdirectories of ADR home, which store incident packages, health monitor reports, and other information

Question No: 453 – (Topic 13)

Which statement is true when Automatic Workload Repository (AWR) baselines are created using baseline templates?

  1. AWR baselines are always created as repeating baselines.

  2. AWR baselines can be created on the basis of two time values.

  3. AWR baselines are always created with infinite expiration duration.

  4. AWR baselines are always created using the Automatic Workload Repository (AWR) retention period as expiration duration.

Answer: B

Question No: 454 – (Topic 13)

You executed the following commands:

SQLgt; ALTER SESSION SET OPTIMIZER_USE_PENDING_STATISTICS = false;

SQLgt; EXECUTE DBMS_STATS.SET_TABLE_PREFS(#39;SH#39;, #39;CUSTOMERS#39;, #39;PUBLISH#39;,#39;false#39;);

SQLgt; EXECUTE DBMS_STATS.GATHER_TABLE_STATS(#39;SH#39;, #39;CUSTOMERS#39;);

Which statement is correct regarding the above statistics collection on the SH.CUSTOMERS table in the above session?

  1. The statistics are stored in the pending statistics table in the data dictionary.

  2. The statistics are treated as the current statistics by the optimizer for all sessions.

  3. The statistics are treated as the current statistics by the optimizer for the current sessions only.

  4. The statistics are temporary and used by the optimizer for all sessions until this session terminates.

Answer: A

Question No: 455 – (Topic 13)

Which of the following are correct about block media recovery? (Choose all that apply.)

  1. Physical and logical block corruption is recorded automatically in V$DATABASE_BLOCK_CORRUPTION.

  2. Logical corruptions are repairable by BMR.

  3. Physical corruptions are repairable by BMR.

  4. RMAN can use any backup for a BMR restore.

  5. ARCHIVELOG mode is not required if you have both a full and incremental backup for

restore.

Answer: A,C Explanation:

Overview of Block Media Recovery (link)

Basic Concepts of Block Media Recovery

Whenever block corruption has been automatically detected, you can perform block media recovery manually with the RECOVER … BLOCK command. By default, RMAN first searches for good blocks in the real-time query physical standby database, then flashback logs and then blocks in full or level 0 incremental backups.

Identification of Corrupt Blocks

->The V$DATABASE_BLOCK_CORRUPTION view displays blocks marked corrupt by database components such as RMAN, ANALYZE, dbv, and SQL queries. The following types of corruption result in the addition of rows to this view: Physical corruption (sometimes called media corruption) The database does not recognize the block: the checksum is invalid, the block contains all zeros, or the block header is corrupt. Physical corruption checking is enabled by default. You can turn off checksum checking by specifying the NOCHECKSUM option of the BACKUP command, but other physical consistency checks, such as checks of the block headers and footers, cannot be disabled.

->Logical corruption:

The block has a valid checksum, the header and footer match, and so on, but the contents are logically inconsistent. Block media recovery may not be able to repair all logical block corruptions. In these cases, alternate recovery methods, such as tablespace point-in-time recovery, or dropping and re-creating the affected objects, may repair the corruption.

Logical corruption checking is disabled by default. You can turn it on by specifying the CHECK LOGICAL option of the BACKUP, RESTORE, RECOVER, and VALIDATE

commands.

The database can detect some corruptions by validating relationships between blocks and segments, but cannot detect them by a check of an individual block. The V$DATABASE_BLOCK_CORRUPTION view does not record at this level of granularity.

Prerequisites for Block Media Recovery (link)

The following prerequisites apply to the RECOVER … BLOCK command:

->The target database must run in ARCHIVELOG mode and be open or mounted with a current control file.

->If the target database is a standby database, then it must be in a consistent state, recovery cannot be in session, and the backup must be older than the corrupted file.

->The backups of the data files containing the corrupt blocks must be full or level 0 backups and not proxy copies.

If only proxy copy backups exist, then you can restore them to a nondefault location on disk, in which case RMAN considers them data file copies and searches them for blocks during block media recovery.

->RMAN can use only archived redo logs for the recovery. RMAN cannot use level 1

incremental backups. Block media recovery cannot survive a missing or inaccessible archived redo log, although it can sometimes survive missing redo

records.

->Flashback Database must be enabled on the target database for RMAN to search the flashback logs for good copies of corrupt blocks.

If flashback logging is enabled and contains older, uncorrupted versions of the corrupt blocks, then RMAN can use these blocks, possibly speeding up the recovery.

->The target database must be associated with a real-time query physical standby

database for RMAN to search the database for good copies of corrupt blocks.

Question No: 456 – (Topic 13)

Which statements are true regarding the creation of an incident package file by using the EM Workbench Support? (Choose all that apply.)

  1. You can add or remove the trace files to the package.

  2. You can create the incremental incident package ZIP file for new or modified diagnostic information for the incident package already created.

  3. You can add SQL test cases to the incident package.

  4. You cannot create an incremental incident package when the physical files are purged from the ADR.

Answer: A,B,C Explanation: 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 quot;Investigating, Reporting, and Resolving a Problemquot;.

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.

Question No: 457 – (Topic 13)

Which of the following are true concerning block media recovery? (Choose all that apply.)

  1. Any gap in archive logs ends the recovery.

  2. If a gap in archive logs is encountered, RMAN will search forward for newer versions of the blocks that are not corrupt.

  3. Uncorrupted blocks from the flashback logs may be used to speed recovery.

  4. The database can be in NOARCHIVELOG mode.

  5. None of the above.

Answer: B,C Explanation:

Overview of Block Media Recovery (link) Basic Concepts of Block Media Recovery

Whenever block corruption has been automatically detected, you can perform block media recovery manually with the RECOVER … BLOCK command. By default, RMAN first searches for good blocks in the real-time query physical standby database, then flashback logs and then blocks in full or level 0 incremental backups.

Prerequisites for Block Media Recovery (link)

The following prerequisites apply to the RECOVER … BLOCK command:

->The target database must run in ARCHIVELOG mode and be open or mounted with a current control file.

->If the target database is a standby database, then it must be in a consistent state,

recovery cannot be in session, and the backup must be older than the corrupted file.

->The backups of the data files containing the corrupt blocks must be full or level 0

backups and not proxy copies.

If only proxy copy backups exist, then you can restore them to a nondefault location on disk, in which case RMAN considers them data file copies and searches them for blocks during block media recovery.

->RMAN can use only archived redo logs for the recovery.

RMAN cannot use level 1 incremental backups. Block media recovery cannot survive a missing or inaccessible archived redo log, although it can sometimes survive missing redo records.

->Flashback Database must be enabled on the target database for RMAN to search

the flashback logs for good copies of corrupt blocks.

If flashback logging is enabled and contains older, uncorrupted versions of the corrupt blocks, then RMAN can use these blocks, possibly speeding up the recovery.

->The target database must be associated with a real-time query physical standby

database for RMAN to search the database for good copies of corrupt blocks.

Restore Failover (link)

RMAN automatically uses restore failover to skip corrupted or inaccessible backups and look for usable backups. When a backup is not found, or contains corrupt data, RMAN automatically looks for another backup from which to restore the desired files.

Question No: 458 – (Topic 13)

Identify the three predefined server-generated alerts. (Choose three.)

  1. Drop User

  2. Tablespace Space Usage

  3. Resumable Session Suspended

  4. Recovery Area Low On Free Space

  5. SYSTEM Tablespace Size Increment

Answer: B,C,D

Question No: 459 – (Topic 13)

Examine the section of the Health Check report given below:

DBMS_HM.GET_RUN_REPORT(#39;HM_RUN_1061#39;)

Run Name : HM_RUN_1061 Run Id : 1061

Check Name : Data Block Integrity Check Mode : REACTIVE

Status : COMPLETED

Start Time : 2007-05-12 22:11:02.032292 -07:00

End Time : 2007-05-12 22:11:20.835135 -07:00

Error Encountered : 0 Source Incident Id : 7418

Number of Incidents Created :0

Which two statements are true regarding the Health Check report? (Choose two.)

  1. Health Check was performed manually.

  2. Health Check was performed to check the disk image block corruptions.

  3. Health Check was performed to check interblock and intersegment corruption.

  4. Health Check was performed to verify the integrity of database files and report failures.

  5. Health Check was performed by the Health Monitor automatically in response to a critical error.

Answer: A,B

Explanation:

About Health Monitor Checks

Health Monitor checks (also known as checkers, health checks, or checks) examine various layers and components of the database. Health checks detect file corruptions, physical and logical block corruptions, undo and redo corruptions, data dictionary corruptions, and more. The health checks generate reports of their findings and, in many cases, recommendations for resolving problems. Health checks can be run in two ways:

->Reactive-The fault diagnosability infrastructure can run health checks automatically in response to a critical error.

->Manual-As a DBA, you can manually run health checks using either the

DBMS_HM PL/SQL package or the Enterprise Manager interface. You can run checkers on a regular basis if desired, or Oracle Support may ask you to run a checker while working with you on a service request.

Health Monitor checks store findings, recommendations, and other information in the Automatic Diagnostic Repository (ADR).

Health checks can run in two modes:

->DB-online mode means the check can be run while the database is open (that is, in OPEN mode or MOUNT mode).

->DB-offline mode means the check can be run when the instance is available but

the database itself is closed (that is, in NOMOUNT mode).

All the health checks can be run in DB-online mode. Only the Redo Integrity Check and the DB Structure Integrity Check can be used in DB-offline mode.

Types of Health Checks:

Health monitor runs the following checks:

->DB Structure Integrity Check-This check verifies the integrity of database files and reports failures if these files are inaccessible, corrupt or inconsistent. If the database is in mount or open mode, this check examines the log files and data files listed in the control file. If the database is in NOMOUNT mode, only the control file is checked.

->Data Block Integrity Check-This check detects disk image block corruptions such

as checksum failures, head/tail mismatch, and logical inconsistencies within the block. Most corruptions can be repaired using Block Media Recovery. Corrupted block information is also captured in the V$DATABASE_BLOCK_CORRUPTION view. This check does not detect inter-block or inter-segment corruption.

->Redo Integrity Check-This check scans the contents of the redo log for

accessibility and corruption, as well as the archive logs, if available. The Redo Integrity Check reports failures such as archive log or redo corruption.

->Undo Segment Integrity Check-This check finds logical undo corruptions. After

locating an undo corruption, this check uses PMON and SMON to try to recover the corrupted transaction. If this recovery fails, then Health Monitor stores

information about the corruption in V$CORRUPT_XID_LIST. Most undo corruptions can be resolved by forcing a commit.

->Transaction Integrity Check-This check is identical to the Undo Segment Integrity

Check except that it checks only one specific transaction. Dictionary Integrity Check-This check examines the integrity of core dictionary objects, such as tab$ and col$. It performs the following operations:

Verifies the contents of dictionary entries for each dictionary object. Performs a cross-row level check, which verifies that logical constraints on rows in the dictionary are enforced. Performs an object relationship check, which verifies that parent-child relationships between dictionary objects are enforced.

The Dictionary Integrity Check operates on the following dictionary objects:

tab$, clu$, fet$, uet$, seg$, undo$, ts$, file$, obj$, ind$, icol$, col$, user$, con$, cdef$, ccol$, bootstrap$, objauth$, ugroup$, tsq$, syn$, view$, typed_view$, superobj$, seq$, lob$, coltype$, subcoltype$, ntab$, refcon$, opqtype$, dependency$, access$, viewcon$, icoldep$, dual$, sysauth$, objpriv$, defrole$, and ecol$.

Question No: 460 – (Topic 13)

Which statement is true regarding the retention policy for the incidents accumulated in the Automatic Diagnostic Repository (ADR)?

  1. The incident metadata is purged when the problem is resolved and the DBA closes the SR.

  2. The incident files and dumps are not retained in the ADR for the manually created incidents.

  3. The incident files are retained but the incident metadata is purged when the problem is resolved and the DBA closes the SR

  4. The default setting is for one year after which the incident metadata is purged from the ADR and the files are retained for one month.

Answer: D Explanation:

Latesttests 2018 PDF and VCE

C:\Users\albo\Desktop\1-1.jpg

100% Free Download!
Download Free Demo:1z0-053 Demo PDF
100% Pass Guaranteed!
Download 2018 Latesttests 1z0-053 Full Exam PDF and VCE

Latesttests ExamCollection Testking
Lowest Price Guarantee Yes No No
Up-to-Dated Yes No No
Real Questions Yes No No
Explanation Yes No No
PDF VCE Yes No No
Free VCE Simulator Yes No No
Instant Download Yes No No

2018 Latesttests IT Certification PDF and VCE