Database Management Systems

In RPG IV, the N operation extender is used with input operations like READ or CHAIN to indicate that the record should be read without locking it.

VOL=SER (volume serial) specifications are required for tape datasets that are not cataloged. Cataloged tape datasets have their volume information recorded in the system catalog, so VOL=SER is optional. For uncataloged tape datasets, VOL=SER tells the system which tape volume to mount.

ISM (IBM Tivoli Netcool/ISM) stores its operational logs in /opt/Netcool/log/ism by default. Options A, B, and D are incorrect - they either point to wrong directories or reverse the correct path structure.

When a TABLESPACE clause is omitted, Oracle stores the segment in the user's default tablespace. Each database user has a default tablespace assigned (often USERS or a custom tablespace). The SYSTEM tablespace is reserved for data dictionary objects. Oracle will not give an error - it uses the default tablespace as a fallback.

Oracle automatically detects deadlocks and resolves them by rolling back the specific statement that caused the deadlock, allowing other transactions to proceed. Manual intervention or killing the entire session is usually not required for basic resolution.

In Oracle, a transaction ends with a COMMIT, ROLLBACK, DDL statement, or disconnection. Using a SAVEPOINT with ROLLBACK only reverts to a specific point within the transaction; it does not terminate the transaction itself.

DBA_TABLESPACES is the correct data dictionary view that contains descriptions of all tablespaces in the database. USER_TABLESPACES only shows tablespaces accessible to the current user, while V$TABLESPACE and DBA_TABLESPACE_GROUPS are not valid views for tablespace descriptions.

A user process failure occurs when a single database session encounters an error and terminates. Statement failure refers to individual SQL statement errors, network failure involves connectivity issues, and instance failure is when the entire database instance crashes.

In SQL, 'SELECT' is a reserved keyword. While it can be used as an object name if enclosed in double quotes (e.g., "SELECT"), using it unquoted as an identifier is invalid and will cause a syntax error.

A data warehouse is designed for analytical processing (OLAP) and historical data storage, not for day-to-day operational transactions (OLTP). Operational data stores (ODS) handle day-to-day business data.

Data warehouses have four key characteristics per W.H. Inmon: subject-oriented (organized around major subjects), non-volatile (data is read-only), integrated (data from multiple sources is standardized), and time-variant (provides historical perspective). All options are correct.

Granularity refers to the level of detail stored in the data warehouse - how fine or coarse the data is. For example, sales data stored by day versus by month represents different granularity levels. Facts are measurements, dimensions provide context, and summary is an aggregation.

In Oracle, if a user creates a segment (like a table) without specifying a tablespace, the database automatically assigns it to the default tablespace defined in that specific user's profile configuration.

When no TABLESPACE clause is specified, Oracle automatically stores the segment in the user's default tablespace. This is the tablespace assigned to the user when their account was created or last modified with an ALTER USER statement. The system tablespace is reserved for data dictionary objects, not user data.