多选题Which two statements regarding a SQL profile are true?（）AIt is built by Automatic Tuning Optimizer.BIt cannot be stored persistently in the data dictionary.CIt can be used by the query optimizer automatically.DIt can be created manually by using the CR

An SPFILE is a binary file.

An SPFILE cannot reside on a client.

An SPFILE cannot contain static parameters.

An SPFILE can store changes persistently across instance restarts.

An SPFILE can be read by the database server， but it is not written to by the server.

An SPFILE must be created manually， before creating a database， even if you use the DatabaseConfiguration Assistant （DBCA） to create the database

It is ignored by the query optimizer.

It is not used while the index is being rebuilt.

The index cannot be rebuilt， and has to be re-created.

The index is automatically rebuilt when used the next time

A subquery can retrieve zero or more rows

Only two subqueries can be placed atone level

A subquery can be used only in SQL query statements

A subquery can appear on either side of a comparison operator

There is no limit on the number of subquery levels in the WHERE clause of a SELECT statement

It cannot be created without a package specification.

It cannot invoke subprograms defined in other packages.

It can contain only the subprograms defined in the package specification.

It can be changed and recompiled without making the package specification invalid.

A single row subquery can retrieve data from only one table.

A SQL query statement cannot display data from table B that is referred to in its subquery, unless table B is included in the main query's FROM clause.

A SQL query statement can display data from table B that is referred to in its subquery, without including table B in its own FROM clause.

A single row subquery can retrieve data from more than one table.

A single row subquery cannot be used in a condition where the LIKE operator is used for comparison.

A multiple-row subquery cannot be used in a condition where the LIKE operator is used for comparison.

It is ignored by the query optimizer.

It is not used while the index is being rebuilt.

The index cannot be rebuilt， and has to be re-created.

The index is automatically rebuilt when used the next time

A subquery should retrieve only one row.

A subquery can retrieve zero or more rows.

A subquery can be used only in SQL query statements.

Subqueries CANNOT be nested by more than two levels.

A subquery CANNOT be used in an SQL query statement that uses group functions.

When a subquery is used with an inequality comparison operator in the outer SQL statement, the column list in the SELECT clause of the subquery should contain only one column.

A subquery that defines a view cannot include the GROUP BY clause

A view that is created with the subquery having the DISTINCT keyword can be updated

A view that is created with the subquery having the pseudo column ROWNUM keyword cannot be updated

A data manipulation language (DML) operation can be performed on a view that is created with the subquery having all the NOT NULL columns of a table

It contains only SQL profiles generated by SQL Tuning Advisor.

It stores plans generated by the optimizer using a stored outline.

It is part of the data dictionary and stored in the SYSAUX tablespace.

It is part of the data dictionary and stored in the SYSTEM tablespace.

It contains the statement log, the plan history, plan baselines, and SQL profiles.

It can be used to join a maximum of three tables

It can be used to restrict the number of columns used in a NATURAL join

It can be used to access data from tables through equijoins as well as nonequijoins

It can be used to join tables that have columns with the same name and compatible data types

It contains only SQL profiles generated by SQL Tuning Advisor.

It stores plans generated by the optimizer using a stored outline.

It is part of the data dictionary and stored in the SYSAUX tablespace.

It is part of the data dictionary and stored in the SYSTEM tablespace.

It contains the statement log, the plan history, plan baselines, and SQL profiles.

Both USING and ON clauses can be used for equijoins and nonequijoins

Amaximum of one pair of columns can be joined between two tables using the ON clause

The ON clause can be used to join tables on columns that have different names but compatible data types

The WHERE clause can be used to apply additional conditions in SELECT statements containing the ON or the USING clause

It is built by Automatic Tuning Optimizer.

It cannot be stored persistently in the data dictionary.

It can be used by the query optimizer automatically.

It can be created manually by using the CREATE PROFILE command.

A single row subquery can retrieve data from only one table.

A SQL query statement cannot display data from table B that is referred to in its subquery, unless table B is included in the main query's FROM clause.

A SQL query statement can display data from table B that is referred to in its subquery, without including B in its own FROM clause.

A single row subquery can retrieve data from more than one table.

A single row subquery cannot be used in a condition where the LIKE operator is used for comparison.

A multiple-row subquery cannot be used in an INSERT statement to insert multiple rows at a time.

It can be set at the system， session， or table level.

It is used only across statements in the same session.

It can store the results from normal as well as flashback queries.

It can store the results of queries based on normal，temporary，and dictionary tables.

It is executed first in the query execution

It must be the last clause in the SELECT statement

It cannot be used in a SELECT statement containing a HAVING clause

You cannot specify a column name followed by an expression in this clause

You can specify a combination of numeric positions and column names in this clause