Database Management Systems

When connecting to Oracle over a non-secure network connection (without OS authentication support), Oracle uses password file authentication for privileged connections like SYSDBA. The password file stores credentials of users with SYSDBA/SYSOPER privileges. OS authentication works only when the client is on the same host as the database or has a trusted secure connection. Control files store database structure, not authentication data.

Rebuilding an index creates a new index using the existing index as the data source, requiring sufficient temporary disk space to hold both the old and new indexes simultaneously. The new index will not contain deleted entries, and online rebuilds allow concurrent queries.

STARTUP NOMOUNT is used when creating a new database because it starts the instance (SGA and background processes) without mounting a database. At this stage, Oracle reads the parameter file but doesn't look for a control file (which doesn't exist yet for a new database). STARTUP MOUNT requires an existing control file, STARTUP OPEN requires an existing database, and plain STARTUP is equivalent to STARTUP OPEN.

DBA_FREE_SPACE is the correct Oracle data dictionary view that displays information about free space extents within tablespaces. V$FREESPACE doesn't exist in Oracle, and DBA_EXTENTS shows allocated extents not free space.

Reporting consistency means that all users querying the same InfoCube get identical results. If User A and User B run the same report on the same data, outputs must match - this is fundamental to data warehouse integrity.

Schedules in rulebases allow you to define specific time slots when the rules should execute. This enables targeted monitoring during particular time periods rather than continuous operation.

PROC SQL can create indexes only on tables, NOT on views. Indexes in PROC SQL are classified as Simple (one column) or Composite (multiple columns). Therefore, the statement about views is False, making option B correct.

The TITLE statement cannot be used inside PROC SQL. PROC SQL has its own syntax for titling using the TITLE statement option or must place TITLE statements outside PROC SQL. This is a specific restriction of PROC SQL compared to other SAS procedures.

PROC SQL cannot create indexes on views because views are virtual tables, not physical data storage. Indexes can only be created on physical tables. PROC SQL supports two index types: Simple (single column) and Composite (multiple columns).

In Proc SQL simple index, the index name defaults to the column name but isn't required to match. Indexing significantly speeds up data retrieval by creating lookup structures. Values don't need to be pre-sorted for indexing to work.

The Import Wizard is the official SAP BusinessObjects tool for migrating content from older Business Objects versions (like 5.x or 6.x) to BusinessObjects XI or later versions. It transfers universes, reports, documents, and other metadata while preserving as much configuration and formatting as possible.

In BusinessObjects, a Universe is the semantic layer that resides between the database and the reporting tools, translating complex database structures into user-friendly business terms. Country, World, and Galaxy are not standard terms for this layer.

In IMS DB, the key field of a segment CAN be updated, though this requires care. The key field uniquely identifies segment occurrences within a parent segment. This is a database operation that must maintain data integrity.

IMS DB has three control blocks: DBD (Database Descriptor) describes the database structure, PSB (Program Specification Block) describes the program's view of the database, and PCB (Program Communication Block) is the actual interface used by the program. IMSCB is not a standard IMS control block.