Database Management Systems

When submitting advisor analysis jobs, the 'Limited' scope adds the least overhead because it performs minimal analysis. 'Restricted' is not a valid job scope option in this context. 'Comprehensive' and 'Thorough' (though 'Thorough' is not standard Oracle terminology) would involve deeper analysis with more system overhead. Limited scope is the lightweight option for minimal system impact.

DBA_ADVISOR_RATIONALE is the view that contains the reasoning and justification behind ADDM recommendations. It explains WHY specific recommendations were made. DBA_ADVISOR_FINDINGS shows what problems were discovered, DBA_ADVISOR_OBJECTS lists affected objects, and DBA_ADVISOR_RECOMMENDATIONS contains the suggested solutions - but RATIONALE provides the explanatory reasoning.

The Memory Advisor in Oracle determines if allocated memory for Shared Pool, Large Pool, and Buffer Cache is adequate. It analyzes memory usage patterns and provides recommendations for SGA component sizing. SQL Tuning Advisor focuses on SQL optimization, not memory allocation. SGA Tuning Advisor and Pool Advisor are not standard Oracle advisor names.

The MTTR (Mean Time To Recover) Advisor evaluates if the estimated instance recovery duration meets service-level agreement requirements. It analyzes Redo log file sizing and configuration to optimize recovery time. Undo Management Advisor focuses on undo tablespace management, while SQL Access and Tuning Advisors deal with SQL optimization - not recovery time estimation.

The SQL Tuning Advisor is the appropriate first tool for analyzing and improving performance of a specific SQL statement showing high disk I/O. The SQL Access Advisor is for overall schema design (indexes/materialized views), not individual statement tuning. The main screen and alert log are for monitoring, not targeted SQL optimization.

The Performance screen in EM Database Control is the primary location to investigate sudden performance degradation, as it provides detailed metrics on wait events, throughput, and resource utilization. The Administration and Maintenance screens are for configuration and maintenance tasks, not performance diagnostics. The main screen only shows high-level alerts.

By default, AWR (Automatic Workload Repository) retains database statistics for 7 days. This is the standard retention period for automatic workload repository snapshots. 30 days is not the default, and 7 hours is too short. Statistics are not retained indefinitely by default.

The three primary sources of performance metrics in the EM Performance screen are Host (operating system metrics), Session (user session activity), and Instance (database instance statistics). Network metrics are not one of the three primary sources - they may be available but are not fundamental to the Performance screen's three-tier view.

Only databases created using the Database Configuration Assistant (DBCA) automatically have the statistics collection job configured. When you create databases manually with scripts, the automatic statistics collection procedure is not set up by default. This is a documented behavior, not a parameter or login issue.

Oracle Database Control supports both warning and critical thresholds for alert configuration. When monitoring tablespace free space, you can set a warning threshold to alert when free space drops to a concerning level, and a critical threshold for more urgent alerts when space becomes critically low.

When no email address is configured, EM Database Control displays alert information on its main console screen. The alerts remain visible in the EM interface for administrators to review. Alerts are not stored in data dictionary views like DBA_ALERTS or dynamic performance views like V$ALERTS when no email is specified.

This appears to be a SAP ABAP-specific question. In SAP, views can be buffered (option to buffer view data in memory for performance), though views themselves don't contain physical data - they store queries that generate data when accessed. The correct answer depends on SAP's view buffering capability, which does exist.

This appears to be a SAP-specific command. In SAP, /$TAB is used to flush database buffers and reset table buffers. The other commands (/nRESET, /nINIT, /nFREE) serve different purposes in the SAP system environment.

The SAP R/3 system architecture consists of three central interfaces that handle different communication layers: the Presentation Interface manages user interactions, the Database Interface handles data persistence and retrieval, and the Operating System Interface manages system-level operations. These three interfaces work together to form the complete R/3 architecture, making option D correct.

The AUTOMATIC_IPC parameter is configured in the sqlnet.ora file on the Oracle server side. It controls whether Oracle uses Inter-Process Communication (IPC) for local database connections automatically. The listener.ora handles listener configuration, tnsnames.ora contains connection descriptors, and the client sqlnet.ora manages client-side network settings.