When a table is dropped, the corresponding indexes are automatically dropped.
For each DML operation performed, the corresponding indexes are automatically updated.
Indexes should be created on columns that are frequently referenced as part of an expression.
A non-deferrable PRIMARY KEY or UNIQUE KEY constraint in a table automatically creates a uniqueindex.
第1题:
The RECYCLEBIN parameter is set to ON for your database. You drop a table, PRODUCTS, from the SCOTT schema. Which two statements are true regarding the outcome of this action? ()(Choose two)
第2题:
Which two statements are TRUE regarding Coherence Indexes ? ()
第3题:
Which statements are correct regarding indexes? ()
第4题:
The RECYCLEBIN parameter is set to ON for your database. You drop a table,PRODUCTS,from the SCOTT schema. Which two statements are true regarding the outcome of this action?()
第5题:
Which parameter allows SQL*Loader to load data into a table with the indexes in the unusable state, prior to the load operation?()
第6题:
Which two are true regarding external tables? ()
第7题:
All the related indexes and views are automatically dropped
The flashback drop feature can recover only the table structure
Only the related indexes are dropped whereas views are invalidated
The flashback drop feature can recover both the table structure and its data
第8题:
Only the ORD_CUSTOMER_IX1 index created.
Both the indexes are updated when a row is inserted, updated, or deleted in the ORDERS table.
Both the indexes are created: however, only ORD_CUSTOMERS_IX1 is used by the optimizer for queries on the ORDERS table.
The ORD_CUSTOMER_IX1 index is not used by the optimizer even when the OPTIMIZER_USE_INVISIBLE_INDEXES parameters is set to true.
Both the indexes are created and used by the optimizer for queries on the ORDERS table.
Both the indexes are created: however, only ORD_CUSTOMERS_IX2 is used by the optimizer for queries on the ORDERS table.
第9题:
indexes are maintained by cache entry ownes
an application should not suggest an index that another aplication had suggested
indexes cannot be sorted
each application using Coherence may suggest the same set of indexes when it starts
第10题:
All the related indexes and views are automatically dropped
The flashback drop feature can recover only the table structure
Only the related indexes are dropped whereas views are invalidated
The flashback drop feature can recover both the table structure and its data
第11题:
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
第12题:
Only a single partitioning key column can be specified.
All DML statements must use partition-extended syntax.
The same physical attributes must be specified for each partition.
Unique local indexes cannot be created on a system-partitioned table.
Traditional partition pruning and partitionwise joins are not supported on these tables.
第13题:
Which statements are correct about temporary tables()
第14题:
Which statements are true regarding system-partitioned tables?()
第15题:
Which statement is true regarding online redefinition for the migration of BasicFile LOBs to SecureFile LOBs?()
第16题:
Which three statements are correct about temporary tables?()
第17题:
You executed the following SQL statement to shrink the EMPLOYEES table segment stored in the EXAMPLE tablespace: ALTER TABLE employees SHRINK SPACE CASCADE; Which statement is correct in this scenario?()
第18题:
What are three benefits of performing data definition language (DDL) statements against a partitioned table with the UPDATE GLOBAL INDEXES clause?()
第19题:
The data in the segment will be compacted but the high water mark will not be adjusted
The EMPLOYEES table will be changed to read-only mode during the shrink operation
The indexes created on the EMPLOYEES table will need to be rebuilt after the shrink operation is over
The shrink behavior will be cascaded to all dependent segments of the table that support a shrink operation
Data manipulation language (DML) operations will not be possible on the EMPLOYEES table during the COMPACTION phase of the shrink operation
第20题:
Flashback Table can be performed on system tables.
Flashback Table operation does not shrink the segments.
Flashback Table uses log mining to extract SQL_REDO and SQL_UNDO statements.
Flashback Table operation acquires exclusive data manipulation language (DML) locks.
第21题:
It cannot be done in parallel.
It can be done at the table level or partition level.
It does not require additional storage because the operation is done online.
Local and global indexes are maintained automatically during the operation.
第22题:
INDEXES
SKIP_INDEXES_MAINTENANCE
SKIP_UNUSABLE_INDEXES
RESUMABLE
INDEXES_UNUSABLE
第23题:
Global indexes are rebuilt automatically at the end of the DDL operation thereby avoiding problems with the UNUSABLE status.
You do not have to search for invalid global indexes after the DDL command completes and rebuild them individually.
Global indexes are maintained during the operation of the DDL command and therefore can be used by any concurrent query.
Global indexes remain intact and available for use by data manipulation language (DML) statements even for sessions that have not enabled the skipping of unusable indexes.
第24题:
When a table is dropped, the corresponding indexes are automatically dropped.
For each DML operation performed, the corresponding indexes are automatically updated.
Indexes should be created on columns that are frequently referenced as part of an expression.
A non-deferrable PRIMARY KEY or UNIQUE KEY constraint in a table automatically creates a uniqueindex.