Oracle Database and SQL Query Quiz

DUAL contains exactly one row where DUMMY='X'. COUNT(1) counts the number of rows, which is 1. The GROUP BY clause is properly formed.

MAX(5), MIN(5), and AVG(5) all return 5 because the aggregate functions operate on a single value. So 5*5/5 = 5. The GROUP BY is valid.

AVG() requires numeric input, but DUMMY contains 'X' (a string value in DUAL). Oracle cannot convert 'X' to a number, raising ORA-01722: invalid number.

MIN(DUMMY) returns 'X' and MAX(DUMMY) returns 'X'. UNION ALL combines both results, producing two rows. DUAL has only one row with DUMMY='X'.

ORDER BY cannot appear in the first SELECT of a UNION ALL - it must be at the end of the entire statement. This causes 'SQL command not properly ended'.

CONNECT is an Oracle reserved keyword (used for hierarchical queries: CONNECT BY). Using it as a column name without quotes causes 'missing expression' error.

ROWID is a pseudo-column that exists for every row in Oracle tables. Querying it from DUAL returns the actual 18-character ROWID string (e.g., AAAADeAABAAAAgiAAA) of DUAL's single row.

ROWNUM is a pseudo-column that assigns a number to each row returned. DUAL has one row, so ROWNUM=1 for that row. The query returns 1.

CONNECT BY with LEVEL generates hierarchical rows. LEVEL starts at 1, increments by 1. The condition LEVEL BETWEEN 0 AND 50 is true for LEVEL=1 through 50. Output is values 1 through 50.

Both hierarchical queries generate the same sequence of numbers from 1 to 50. Subtracting the second result set from the first using MINUS results in an empty set, yielding no rows returned.

CONNECT BY generates rows starting at LEVEL=1. The filtering condition LEVEL BETWEEN 3 AND 50 is applied AFTER row generation. But the condition fails for LEVEL=1 and LEVEL=2, stopping generation. Only LEVEL=1 satisfies 1 BETWEEN 3 AND 50 = FALSE, so no rows generated beyond first. Oracle returns just the initial row with LEVEL=1.

In JPA and entity frameworks, every entity MUST have a primary key to uniquely identify each instance. This is a fundamental requirement for entity mapping and database operations. Option B is incorrect because the primary key IS required. Option C is incorrect because @Primary is not a standard JPA annotation for simple primary keys (typically @Id is used). Option D is incorrect since not all statements are valid.

INTERVAL partitioning is an extension of RANGE partitioning. It automatically creates new partitions of a specified range (interval) when data is inserted that falls outside existing partition boundaries, making it fundamentally range-based.

INTERVAL partitioning was introduced in Oracle Database 11g Release 1 as a new feature. This automatic partition creation method was not available in Oracle 10g or any earlier versions, making it an 11g-specific capability.

Mixed notation (combining named and positional parameters in PL/SQL subprogram calls) was introduced in Oracle 11g. Earlier versions required either all positional or all named notation - you couldn't mix the two approaches in a single call.