Database and SQL

Varrays must start with subscript 1 and can be stored as table columns. Associative arrays have flexible indexing (including negative or string keys) and cannot be column types: they exist only in PL/SQL memory.

Bitmap indexes are highly efficient for columns with low cardinality (high redundancy/few unique values) because they store bitmaps representing row existence. B-tree indexes are better suited for high-cardinality columns.

In Oracle databases, the utlchain.sql script creates the CHAINED_ROWS table, which stores information about chained and migrated rows. This table is used with the ANALYZE command to identify rows that are chained or migrated across multiple blocks, helping optimize database performance.

In Pega, work classes within a class group typically map to the class group table, which defaults to pc_work. However, unless explicitly mapped otherwise, standard behavior for concrete classes not designated as part of a work pool is to fall back to the default pr4_base table.

MONTHS_BETWEEN calculates the difference in months between two dates. Between January 1st and February 2nd, 1995, there is approximately 1 month. The function returns 1 because the dates are in consecutive months.

ADD_MONTHS adds a specified number of months to a date. Starting from June 7, 1994 and adding 1 month gives July 7, 1994. The TO_CHAR then formats it as '07-JUL-1994'.

The SQRT function in SQL calculates the square root of a numeric value. The square root of 25 is 5. Since DUAL is a dummy table in Oracle database, selecting SQRT(25) from it yields a single row containing the value 5.

Lookup transformations can effectively filter records by using the lookup condition - records that match the condition are returned, while non-matching records can be dropped or processed differently. This is a common filtering technique in mappings.

The %TYPE attribute in PL/SQL declares a variable with the same data type as a specified column in a table. %ROWTYPE declares a record type matching an entire row. AS_COLUMN doesn't exist in PL/SQL. %TYPE is useful for maintaining type compatibility without hardcoding specific types.

The statement claims SQL has NO error handling facility, which is False. SQL DOES have programmed error handling: PL/SQL uses EXCEPTION blocks, T-SQL uses TRY/CATCH, MySQL uses DECLARE handlers. Modern SQL implementations support robust error handling mechanisms for data manipulation errors.

In a PL/SQL block, only BEGIN and END are mandatory. The DECLARE section (for declarations) and EXCEPTION section (for error handling) are both optional components that can be omitted if not needed.

ROLLBACK does close a transaction by undoing all changes made since the last COMMIT. The statement claims ROLLBACK cannot close a transaction, which is incorrect - therefore the answer is False.

A local subprogram within ORDERTOTAL is ideal because it's scoped only to that unit (avoiding global scope pollution) while being reusable from multiple places within ORDERTOTAL. Stored procedures or standalone code would be overly broad for this requirement.

Oracle automatically declares implicit cursors for ALL DML statements and PL/SQL blocks. Every INSERT, UPDATE, DELETE, and SELECT operation that processes rows uses an implicit cursor, not just some of them.