A. Statistics collection is not done for the CUSTOMERS table when schema stats are gathered.
B. Statistics collection is not done for the CUSTOMERS table when database stats are gathered.
C. Any existing statistics for the CUSTOMERS table are still available to the optimizer at parse time.
D. Statistics gathered on the CUSTOMERS table when schema stats are gathered are stored as pending statistics.
E. Statistics gathered on the CUSTOMERS table when database stats are gathered are stored as pending statistics.

A. Decreasing PCTUSED
B. Decreasing PCTFREE
C. Increasing the number of DBWN process
D. Using Automatic Segment Space Management (ASSM)
E. Increasing db_buffer_cache based on the V$DB_CACHE_ADVICE recommendation

A.2，4，5
B.2，1，4，3，5
C.1，2，3，4，5
D.1，2，4，5

A. Create a SQL Tuning Set (STS) that contains the queries cached in the library cache and run the SQL Tuning Advisor (STA) on the workload captured in the STS.
B. Run the Automatic Workload Repository Monitor (ADDM).
C. Create an STS that contains the queries cached in the library cache and run the SQL Performance Analyzer (SPA) on the workload captured in the STS.
D. Create an STS that contains the queries cached in the library cache and run the SQL Access Advisor on the workload captured in the STS.

A. Execute the query and view Active Session History (ASH) for information about the query.
B. Enable SQL trace for the query.
C. Create a database operation, execute the query, and use the DBMS_SQL_MONITOR. REPORT_SQL_MONITOR function to view the report.
D. Use the DBMS_APPLICATION_INFO.SET_SESSION_LONGOPS procedure to monitor query execution and view the information from the V$SESSION_LONGOPS view.

A. Mount the container database (CDB) and restore the control file from the control file auto backup.
B. Recover and open the CDB in NORMAL mode.
C. Mount the CDB and then recover and open the database, with the RESETLOGS option.
D. Open all the pluggable databases.
E. Recover each pluggable database.
F. Start the database instance in the nomount stage and restore the control file from control file auto backup.

A. None of the data definition language (DDL) statements are logged in the trace file.
B. Only DDL commands that resulted in errors are logged in the alert log file.
C. A new log.xml file that contains the DDL statements is created, and the DDL command details are removed from the alert log file.
D. Only DDL commands that resulted in the creation of new database files are logged.

A. Building and implementing SQL profiles
B. Recommending the optimization of materialized views
C. Checking query objects for missing and stale statistics
D. Recommending bitmap, function-based, and B-tree indexes
E. Recommending the restructuring of SQL queries that are using bad plans

A. The file ‘+data.231.54769’ is physically relocated to ‘+data/prod’ and renamed as ‘myfile.dbf’.
B. The file ‘+data.231.54769’ is renamed as ‘myfile.dbf’, and copied to ‘+data/prod’.
C. The file ‘+data.231.54769’ remains in the same location and a synonym 'myfile.dbf' is created.
D. The file ‘myfile.dbf’ is created in ‘+data/prod’ and the reference to ‘+data.231.54769’ in the data dictionary removed.

A. Data files that belong to only the root container
B. Data files that belong to the root container and all the pluggable databases (PDBs)
C. Data files that belong to only the root container and PDB$SEED
D. Data files that belong to the root container and all the PDBs excluding PDB$SEED

A. They are created only in the location specified by the LOG_ARCHIVE_DEST_1 parameter.
B. They are created only in the Fast Recovery Area.
C. They are created in the location specified by the LOG_ARCHIVE_DEST_1 parameter and in the default location $ORACLE_HOME/dbs/arch.
D. They are created in the location specified by the LOG_ARCHIVE_DEST_1 parameter and the location specified by the DB_RECOVERY_FILE_DEST parameter.