Oracle Oracle Certifications 1Z0-053 Questions & Answers

• Question 361:

  Which two statements are true regarding Health Monitor checks in Oracle Database 11g? (Choose two.)

  A. Health Monitor checks can be used to scan the contents of the redo log and archive logs for accessibility and corruption.

  B. Health Monitor checks can be used to verify the integrity of database files and report failures if these files are inaccessible, corrupt or inconsistent.

  C. Health Monitor checks can be used to verify the contents of dictionary entries for each dictionary object and fix it automatically.

  D. Health Monitor checks are always initiated manually when there is some critical error.

  Correct Answer: AB

• Question 362:

  View the Exhibit to examine the Automatic Database Diagnostic Monitor (ADDM) tasks. You executed the following commands:

  SQL> VAR tname VARCHAR2(60);

  SQL> BEGIN

  :tname := 'my_instance_analysis_mode_task';

  DBMS_ADDM.INSERT_SEGMENT_DIRECTIVE(:tname,'Sg_directive','SCOTT'); END;

  Which statement describes the consequence?

  Exhibit:

  

  A. The ADDM task is filtered to suppress the Segment Advisor suggestions for the SCOTT schema.

  B. The ADDM task is filtered to produce the Segment Advisor suggestions for the SCOTT schema only.

  C. The PL/SQL block produces an error because the my_instance_analysis_mode_task task has not been reset to its initial state.

  D. All subsequent ADDM tasks including my_instance_analysis_mode_task are filtered to suppress the Segment Advisor suggestions for the SCOTT schema.

  Correct Answer: C

  sys@TEST1107> VAR tname VARCHAR2(60);

  sys@TEST1107> BEGIN :tname := 'my_instance_analysis_mode_task'; 2

  DBMS_ADDM.INSERT_SEGMENT_DIRECTIVE(:tname,'Sg_directive','SCOTT'); 3 END;

  4 /

  PL/SQL procedure successfully completed.

  sys@TEST1107> SELECT DBMS_ADVISOR.GET_TASK_REPORT(:tname, 'TEXT', 'ALL') FROM

  DUAL;

  ERROR:

  ORA-13631: The most recent execution of task my_instance_analysis_mode_task contains no results.

  ORA-06512: at "SYS.PRVT_ADVISOR", line 3189

  ORA-06512: at "SYS.DBMS_ADVISOR", line 590

  ORA-06512: at line 1

  no rows selected

• Question 363:

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

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

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

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

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

  Correct Answer: ABC

  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 anually 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 364:

  You plan to collect the Automatic Workload Repository (AWR) data every Monday morning for a month. You want Oracle Database to automatically create a baseline every Monday and remove the old baseline. What is the correct action to achieve this?

  A. Create and populate a SQL Tuning Set from the AWR on every Monday.

  B. Change the RETENTION setting for the AWR snapshots to 7 days on Monday.

  C. Create a repeating baseline template.

  D. Insert a finding directive for future ADDM tasks.

  Correct Answer: C

• Question 365:

  Which tasks can be accomplished using the Enterprise Manager Support Workbench in Oracle Database 11g? (Choose all that apply.)

  A. Generate reports on data failure such as data file failures.

  B. You can track the Service Request (SR) and implement repairs.

  C. You can package and upload diagnostic data to Oracle Support.

  D. You can manually run health checks to gather diagnostic data for a problem.

  Correct Answer: BCD

• Question 366:

  Which statements are true regarding the concept of problems and incidents in the fault diagnosability infrastructure for Oracle Database 11g? (Choose all that apply.)

  A. Only the incident metadata and dumps are stored in the Automatic Diagnostic Repository (ADR).

  B. The problem key is the same as the incident number.

  C. The database sends an incident alert to the Oracle Enterprise Manager Database Home page.

  D. Every problem has a problem key, which is a text string that describes the problem.

  E. The database makes an entry into the alert log file when problems and incidents occur.

  Correct Answer: CDE

  Reference at here

  Fault Diagnosability Infrastructure Overview

  The fault diagnosability infrastructure aids in preventing, detecting, diagnosing, and resolving problems.

  The problems that are targeted in particular are critical errors such as those caused by code bugs, metadata corruption, and customer data corruption. When a critical error occurs, it is assigned an incident number, and diagnostic data for the

  error (such as trace files) are immediately captured and tagged with this number. The data is then stored in the Automatic Diagnostic Repository (ADR)--a file-based repository outside the database--where it can later be retrieved by incident

  number and analyzed.

  About Incidents and Problems

  A problem is a critical error in a database instance, Oracle Automatic Storage Management (Oracle ASM) instance, or other Oracle product or component. Critical errors manifest as internal errors, such as ORA-00600, or other severe errors,

  such as ORA-07445 (operating system exception) or ORA-04031 (out of memory in the shared pool). Problems are tracked in the ADR. Each problem has a problem key, which is a text string that describes the problem. It includes an error

  code (such as ORA 600) and in some cases, one or more error parameters. An incident is a single occurrence of a problem. When a problem (critical error) occurs multiple times, an incident is created for each occurrence. Incidents are

  timestamped and tracked in the Automatic Diagnostic Repository (ADR). Each incident is identified by a numeric incident ID, which is unique within the ADR. When an incident occurs, the database:

  Makes an entry in the alert log.

  Sends an incident alert to Oracle Enterprise Manager (Enterprise Manager). Gathers first-failure diagnostic data about the incident in the form of dump files (incident dumps).

  Tags the incident dumps with the incident ID.

  Stores the incident dumps in an ADR subdirectory created for that incident.

• Question 367:

  You need to perform a block media recovery on the tools01.dbf data file in the SALES database by using Recovery Manager (RMAN).

  Which two are the prerequisites to perform this operation? (Choose two)

  A. You must configure block change tracking file

  B. You must have first level 1 backups for RMAN to restore blocks

  C. You must ensure that the SALES database is mounted or open

  D. You must have full or level 0 backups for RMAN to restore blocks

  E. You must take the tools01.dbf data file offline before you start a block media recovery

  Correct Answer: CD

  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 368:

  View the Exhibit and note the contents of V$DIAG_INFO.

  Which statement is true about the ADR?

  Exhibit: A. The text alert log file will be available in Diag Trace

  

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

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

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

  Correct Answer: A

  

  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 369:

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

  A. Drop User

  B. Tablespace Space Usage

  C. Resumable Session Suspended

  D. Recovery Area Low On Free Space

  E. SYSTEM Tablespace Size Increment

  Correct Answer: BCD

• Question 370:

  Examine the following values of the initialization parameters in the database having the SID ORCL:

  BACKGROUND_DUMP_DEST=/u01/app/oracle/product/11.1.0/db_1/bdump USER_DUMP_DEST=/u01/app/oracle/product/11.1.0/db_1/udump CORE_DUMP_DEST=/u01/app/oracle/product/11.1.0/db_1/cdump DIAGNOSTIC_DEST=

  The environment variables have the following value:

  ORACLE_BASE=/u01/app/oracle ORACLE_HOME=/u01/app/oracle/product/11.1.0/db_1

  What is the location of the Automatic Diagnostic Repository (ADR) home?

  A. /u01/app/oracle/product/11.1.0/db_1

  B. /u01/app/oracle

  C. $ORACLE_HOME/bdump

  D. $ORACLE_HOME/log

  Correct Answer: B

  The Automatic Diagnostic Repository (ADR) is a directory structure that is stored outside of the database.

  It is therefore available for problem diagnosis when the database is down. 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.