Database and SQL

DML (Data Manipulation Language) statements are used to manipulate data within existing table structures. Modifying rows (using UPDATE, INSERT, DELETE) is DML operation. Adding a column is DDL (Data Definition Language) because it changes the table structure, not just the data. The question tests understanding of DML vs DDL distinction.

The ORDER BY clause is used in SQL to sort the result set in ascending or descending order based on one or more columns. ORDER alone is not a valid clause - it must be followed by BY. SORT is not a standard SQL keyword for sorting results. GROUP BY is used for aggregation, not sorting.

The standard execution and syntax order of clauses in a SQL SELECT statement is WHERE (I), followed by GROUP BY (II), then HAVING (III), and finally ORDER BY (IV). This ensures rows are filtered, grouped, groups are filtered, and then results are sorted.

Views containing columns defined by expressions (calculated/computed columns) cannot be used directly for INSERT operations because the database cannot determine how to map values back to base table columns. The other options (FROM, WHERE) are standard SQL clauses that do not prevent data insertion through views.

Teradata Fast Load supports loading into multiset tables, which by definition allow duplicate rows. Unlike set tables that enforce uniqueness, multiset tables accept duplicates, and Fast Load can load them without error.

The %TYPE attribute in PL/SQL allows you to declare a variable that automatically inherits the datatype of a specific column in a database table. This provides maintainability - if the column's datatype changes, variables using %TYPE automatically adapt without code modification.

Standard SQL does not have built-in procedural error handling mechanisms like try-catch blocks. While modern SQL implementations (PL/SQL, T-SQL) extend SQL with programming constructs for exception handling, pure SQL itself is a declarative language without explicit error handling facilities.

A PL/SQL block consists of optional DECLARE and EXCEPTION sections, and mandatory BEGIN and END sections. The options contain typos ('DELCARE' or 'DECALRE'), but the concept identifies the DECLARE (spelled DECALRE here) and EXCEPTION clauses as the optional parts of the block structure.

A local subprogram defined within ORDERTOTAL is the most appropriate choice because the code is only needed within that specific program unit. Stored procedures (server-wide) or PL/SQL libraries (broader scope) would be excessive when the functionality has a single, specific use case.

Fatal errors in Informatica are conditions that completely stop session execution. Key constraint violations (A) and loading nulls into not-null fields (B) are data-level errors but don't always halt execution - they may be redirected or handled based on session settings. Database trigger responses (C) depend on trigger logic. However, lack of database space (D) is a system-level failure that cannot be handled within the session - it's truly fatal.

In Normalizer transformation for COBOL files, a Generated Key port is created for each REDEFINES clause (identifies which redefinition is active). A Generated Column ID is created for each OCCURS clause (identifies the occurrence position). The reverse mappings in options B and D are incorrect.