Database Management Systems

Current tables load data on a monthly basis, providing regular snapshots of current state without requiring daily refresh cycles. This monthly frequency balances data freshness with system performance and resource utilization.

CARD_RUNSTAT specifically tracks active card member status and runtime information. The other tables serve different purposes: CARD_ACCT_XREF maps card-account relationships, CARD_LOOKUP provides reference data, and option D incorrectly claims all tables contain the same data.

In network domains (specifically Windows Active Directory or similar directory services), a node represents a single machine or computer account within the domain structure. It's the logical representation of that physical or virtual machine's identity and membership in the domain.

In distributed systems and domain architecture, a node is the logical representation of a physical or virtual machine within a domain. Option A correctly defines this relationship. A node is NOT a collection of domains (B), administrative services (C), or application services (D).

The SystemPilotDatabase Management Object in BSSM contains both PDB (Pilot Database) and Cell ID related data. This MO serves as the central repository for pilot information and cell identification data.

PDB data structure includes PDB Table, CELL ID Table, and FPC Array. Non FPC Array is not part of the standard PDB data composition.

PDB data is stored on DSFP (Data Storage Facility Peripheral) cards. Oracle/MySQL are databases, Objectivity is an ODBMS, and PCUFP is unrelated to PDB storage.

Performance tuning in database systems involves collaboration across roles: DBAs handle database-level optimization, system admins manage hardware and OS configuration, and application developers optimize SQL queries and application code.

"Checkpoint not complete" occurs in Oracle databases when the DBWR cannot write dirty blocks fast enough before the redo logs wrap around. Adding more redo log groups or increasing their size gives DBWR more time to complete checkpoints. SHUTDOWN IMMEDIATE does not resolve this runtime performance issue.

Buffer busy waits occur when multiple sessions attempt to read or modify the same data block concurrently in the buffer cache. It's a contention issue, not a space or free buffer problem. Dirty buffer checkpointing affects write performance, not read contention.

IMS DB uses a hierarchical data model where data is organized in a tree structure with parent-child relationships. This is different from relational (tables), network (many-to-many), or object-oriented models.

Maximum cardinality specifies the maximum number of entity occurrences that can be associated with a single occurrence of a related entity. Minimum cardinality defines the lower bound, while ERD is the diagram format itself.

In a one-to-many relationship, the entity on the 'one' side is called the parent entity because it can have multiple related child entities, but each child relates to exactly one parent. This is a fundamental concept in hierarchical and relational data modeling. The child entity is on the 'many' side.

An instance entity represents an actual occurrence or realization of a generalized entity type. This is a core modeling concept where you define a generalized template (archetype or supertype) and then create specific instances that conform to that template. In ER modeling, this maps to concrete data records representing the abstract entity definition.

Option A is correct because TKPROF is Oracle's native tool for analyzing SQL performance - it formats trace files to show execution plans, statistics, and timing information for SQL statements. Options B (Jensor), C (SQLProfiler), and D (Strobe) are not Oracle performance analysis tools. TKPROF has been part of Oracle Database for decades and is the standard tool for SQL performance investigation.