Database and SQL

PL/SQL packages can group related program units including procedures, functions, cursors, and variables. Option A (Cursor) is correct - cursors CAN be declared in a package specification. Triggers (B), Sequences (C), and Views (D) are standalone schema objects that CANNOT be part of packages.

DROP PROCEDURE removes standalone procedures. Packaged procedures cannot be dropped individually - you must drop or recreate the entire package body. Option A is correct. Options B and C are wrong because DROP PROCEDURE doesn't work on packaged procedures. Option D is nonsense - REUSE SETTINGS doesn't exist and ALTER PROCEDURE doesn't remove procedures.

The question asks which statement is FALSE. Options A, C, and D are TRUE - triggers with compilation errors are still created (as INVALID), and you CAN view errors via SHOW ERRORS or USER_ERRORS. Option B claims you can use USER_TRIGGERS to see compilation errors, which is FALSE - compilation errors are in USER_ERRORS, not USER_TRIGGERS.

In dynamic SQL processing, the execute phase runs the actual SQL statement and returns the count of affected rows. For INSERT/UPDATE/DELETE, this is when data modification happens and row counts are returned. Selecting/ordering rows (A) happens for queries. Validity checking (B) is parse phase. Memory allocation (C) is define/prepare phase.

Trigger TYPE determines execution frequency. Row-level triggers fire once per ROW affected. Statement-level triggers fire once per STATEMENT regardless of rows. Trigger body (B) is the code executed. Trigger event (C) is what fires it (INSERT/UPDATE/DELETE). Trigger timing (D) is before/after/in stead-of.

USER_OBJECTS is the standard dictionary view containing LAST_DDL_TIME, which shows when any schema object (including procedures) was last compiled or modified. USER_PROCEDURES and USER_PROCS are not standard Oracle views. USER_PLSQL_UNITS may exist in some versions but USER_OBJECTS is the canonical source for compilation timestamps.

All four options are valid JOIN types in SQL. LEFT JOIN returns all rows from left table plus matching right table rows. RIGHT JOIN returns all rows from right table plus matching left table rows. FULL JOIN returns all rows when there's a match in either table. SELF JOIN joins a table to itself. All are standard SQL JOIN types.

The UNION operator in SQL combines the result sets of two or more SELECT statements and automatically removes duplicate rows, selecting only distinct values by default. To retain duplicates, UNION ALL must be used. Therefore, the statement is true.

Constraints can be added at table creation time using CREATE TABLE with constraints like PRIMARY KEY, FOREIGN KEY, UNIQUE, CHECK, or NOT NULL. However, constraints can also be added AFTER table creation using ALTER TABLE statements, making the statement false.

In relational database design, the primary key of a referenced table becomes a foreign key in the referencing table. The question is slightly ambiguous as the primary key itself is a primary key, but in the context of referencing, it acts as a foreign key. An alternate or alias key is incorrect.

SUM() is the aggregate function that returns the total (sum) of values in a numeric column. COUNT() returns the number of rows, not a sum. GROUP BY is used for grouping rows, not aggregation. MAX() returns only the maximum value, not the total.

In database systems, index names must be unique within a schema or table to avoid conflicts. This allows the database to uniquely identify which index to maintain or query when referenced by name in DDL or DML statements.

In COBOL, index names used with table SEARCH operations CAN be manipulated using the SET verb. The SET statement allows you to increment, decrement, or set an index to a specific value, which is essential for controlling table traversal.

Purchaser_Product is a junction table resolving a many-to-many relationship between Purchaser and Product. Its primary key must be the composite of both foreign keys (credit_card, product_id) to ensure each combination is unique and prevent duplicate purchaser-product associations. Neither credit_card nor product_id alone is sufficient.

DML (Data Manipulation Language) statements manipulate data: MERGE combines insert/update operations, UPDATE modifies existing rows, and DELETE removes rows. COMMIT is a transaction control statement (TCL). CREATE and DROP are DDL (Data Definition Language) statements that define schema structures, not manipulate data.