What technique can be used to reduce the number of calculations in a query?

Given the following statements: CREATE TABLE T1 (COL1 INT NOT NULL PRIMARY KEY, COL2 CHAR, COL3 CLOB (40K), COL4 VARCHAR(10)); CREATE UNIQUE INDEX IND_1 ON T1 (COL1, COL2) INCLUDE (COL3) ALLOW REVERSE SCANS; The CREATE UNIQUE INDEX statement will fail because:

Which allows index data to be stored on separate devices from table data?

Is the parameter, “database_memory” configured automatically?

What does the term EXPLAIN denote?

Which is required to import data into a table?

What should be considered when specifying an optimization level?

What condition would lead to distribution statistics not being collected?

Where would the optimizer gather information to estimate the amount of prefetching for a tablespace?

At which times is the access control authorization routine (DSNX@XAC) invoked?

If an object is created statically by a role within a trusted context and the ROLE AS OBJECT OWNER clause is specified, who becomes the object owner when executing the package?