SQL and Oracle Database Fundamentals

SQL has several limitations including inability to directly drop or rename columns (historically required workarounds), lack of direct memory management, no indexed indexes or indexed views in early versions, and view update restrictions. These are well-known disadvantages of standard SQL compared to procedural programming languages.

UNION in Oracle requires compatible data types across the combined result sets. The first SELECT returns numeric (1), the second returns character ('A'). Oracle cannot implicitly convert these to a common type for UNION, causing a type mismatch error. UNION ALL would also fail with the same error.

Standard views in relational databases are virtual tables containing query definitions rather than physical data, meaning they cannot be directly indexed. Distractors are incorrect because only materialized or indexed views support index creation.

Standard SQL INTEGER is typically implemented as a 32-bit signed integer in most database systems including Oracle. This provides a range of approximately -2 billion to +2 billion. While some systems support 64-bit integers (BIGINT), the standard INTEGER type is conventionally 32-bit.

Oracle database supports multiple embedded languages. Java can run within the database via Java Virtual Machine (JVM). SQL and PL/SQL are native languages. While C can interact through OCI (Oracle Call Interface), option B about 'any other language linked to OCI' is misleading - not all OCI-linked languages can run INSIDE the database, only Java, SQL, and PL/SQL are truly embedded.

The DUAL table in Oracle is technically a regular table that can be manipulated with DDL/DML operations like DROP, DELETE, ALTER, UPDATE, or INSERT. However, Oracle strongly recommends against modifying DUAL as it's used internally for SELECT statements and system functions. While these operations are possible, altering DUAL can break critical system functionality.

Oracle indexes are typically bypassed for inequality operators (<>, !=), NOT functions, and expressions that wrap columns in functions or operations. The LIKE operator with a leading wildcard ('%...') prevents index usage, and expressions like field+constant or field||'' (concatenation) similarly disable indexes. The AND operator, when used with sargable (searchable) conditions, can effectively use indexes.

Grid computing is a general computing paradigm, not a concept owned or invented by Oracle. Oracle implemented Grid Computing features in their database and middleware products starting with Oracle 10g, but the concept predates Oracle's involvement and is used across the industry. Oracle markets their Grid features but has no exclusive rights to the concept.

The Grid abstraction layer in Oracle is designed to hide complexity from developers and DBAs. Application developers write SQL and PL/SQL code without needing to understand the underlying Grid infrastructure, resource management, or clustering details. The Grid manages resources transparently, allowing developers to focus on business logic rather than infrastructure implementation.

Grid computing capabilities require physical infrastructure support from hardware vendors (servers, storage, networking equipment) and operating systems (resource management, clustering, virtualization). Hardware provides the physical resources, while operating systems manage and pool these resources. Developers and DBAs work at higher abstraction layers, while network/transport layers are communication protocols, not Grid infrastructure providers.

Oracle Grid Computing dynamically manages resource pools, automatically scaling application servers and database instances based on workload demand. The Grid infrastructure monitors load and adds or removes resources to maintain optimal performance. This ensures that resources are available when needed without manual intervention, providing elasticity and efficient resource utilization.

To delete duplicate records while keeping one copy, use ROWID comparisons. Options A and C identify duplicates by matching columns (col1) and then keeping records with ROWID less than the MAX or greater than the MIN respectively. Options B and D incorrectly use <= and >=, which would delete all duplicates including the one you want to keep. The subquery finds the group, and the outer query filters based on ROWID position.