Oracle 1Z0-050 : Oracle Database 11g: New Features for Administrators

You upgraded Oracle Database 10g to Oracle Database 11 g. How would this affect the existing users' passwords?

• A. All passwords automatically become case-sensitive.
• B. All passwords remain non-case-sensitive and cannot be changed.
• C. All passwords remain non-case-sensitive until their password attribute in the profile is altered.
• D. All passwords remain non-case-sensitive till they are changed.

Which tasks can be accomplished using the DBMS_LOB.SETOPTIONS procedure?

• A. deduplication, encryption, and compression settings only for SecureFile CLOBs
• B. only encryption and deduplication settings for only SecureFile CLOBs
• C. deduplication, encryption, and compression settings for all SecureFile LOBs
• D. only encryption and compression settings for all SecureFile LOBs

You want to analyze a SQL Tuning Set (STS) using SQL Performance Analyzer in a test database. Which two statements are true regarding the activities performed during the test execution of SQLs in a SQL Tuning Set? (Choose two.)

• A. The execution plan and execution statistics are computed for each SQL statement in the STS.
• B. The effects of DDL and DML are considered to produce the execution plan and execution statistics.
• C. Every SQL statement in the STS is considered only once for execution.
• D. The SQL statements in the STS are executed concurrently to produce the execution plan and execution statistics.

The INVJHISTORY table is created using the command:
SQL>CREATE TABLE INV_HISTORY
(inv_no NUMBER(3),
inv_date DATE,
inv_amtNUMBER(10,2))
partition by range (inv_date)
interval (numtoyminterval(1 ,'month'))
(partition pO values less than (to_date(l01-01-2005llldd-mm-yyyy1)),
partition p1 values less than (to_date('01-01-2006','dd-mm-yyyy')));
The following data has been inserted into the INVJHISTORY table :
INV_NO INV_DATE INV_AMT
1 30-dec-2004 1000
2 30-dec-2005 2000
3 1-feb-2006 3000
4 1-mar-2006 4000
5 1-apr-2006 5000
You would like to store the data belonging to the year 2006 in a single partition and issue the command:
SQL> ALTER TABLE inv_history MERGE PARTITIONS FOR(TO_DATE(l15-feb-2006l,ldd-mon-yyyy,)),FOR(TO_DATE(l15-apr-20061))
INTO PARTITION sys_py;
What would be the outcome of this command?

• A. It produces an error because the partitions specified for merging are not adjacent.
• B. It executes successfully, and the transition point is set to '15-apr-2006'.
• C. It produces an error because the date values specified in the merge do not match the date values stored in the table.
• D. It executes successfully, and the transition point is set to "l-apr-20061.

To generate recommendations to improve the performance of a set of SQL queries in an application, you execute the following blocks of code:
BEGIN
dbms_advisor.create_task(dbms_advisor.sqlaccess_advisor,lTASK1l);
END;
/
BEGIN
dbms_advisor.set_task_parameter(lTASK1l,lANALYSIS_SCOPElllALLl);
dbms_advisor.set_task_parameter(lTASK1,,,MODE,llCOMPREHENSIVEl);
END;
/
BEGIN
dbms_advisor.execute_task('TASK1');
dbms_output.put_line(dbms_advisor.get_task_script('TASK11));
END;
/
The blocks of code execute successfully; however, you do not get the required outcome.
What could be the reason?

• A. A workload needs to be associated with the task.
• B. The type of structures (indexes, materialized views, or partitions) to be recommended need to be specified for the task.
• C. The partial or complete workload scope needs to be associated with the task.
• D. A template needs to be associated with the task.