Database Management Systems

bpbkar32 is the NetBackup backup process that runs on the client and is responsible for reading data from the client filesystem. It traverses directories, reads files, applies exclude/include lists, and sends the data stream to the NetBackup media server. bprd is the request daemon, bpcd is the client daemon that accepts connections, and bpbackup is a command-line utility that initiates backups but does not perform the actual data reading.

To configure NetBackup database (catalog) backups and resolve the 'Hot catalog backup is not configured' message, you must create a policy with policy type NBU-Catalog. This is a specialized policy type designed specifically for backing up the NetBackup catalog database. Option B (Sybase) is incorrect because while the catalog uses Sybase internals, NBU-Catalog is the correct policy type. Option C (Standard) cannot protect the catalog. Option D (MS-Windows-NT) is for Windows file system backups, not catalog backups.

The bprecover command is the NetBackup utility specifically used for recovering the NetBackup catalog database during disaster recovery scenarios. bprestore is used for restoring client data, not catalogs. dbrecover and ndbrestore are not NetBackup commands, and bpcatrecover does not exist as a standard NetBackup command.

The 'Take checkpoints every' policy attribute allows NetBackup to periodically save backup progress. If a backup fails, it can be restarted from the last checkpoint rather than from the beginning. 'Cross mount points' controls whether backups cross filesystem boundaries. The other options relate to image restore information and disaster recovery, not checkpoint-based restart capability.

The NetBackup catalog consists of three main components: the Image database (contains backup image metadata), a Relational database (stores all catalog information), and NBU configuration (NetBackup configuration data). 'Net backup database' and 'Backup policies' are not catalog components.

To use duplicate tapes as primary copies for restores, use bpchangeprimary (changes a copy from duplicate to primary) or bpimage (manages image information and can change copy attributes). bprecover is for disaster recovery, bpexpdate changes expiration, and bprestore is for performing restores (not changing copy status).

SIZE_DATA_BUFFERS and NUMBER_DATA_BUFFERS are the key NetBackup parameters for performance tuning on media servers. They control how much data is buffered and how many buffers are used during read/write operations. UPDATE_INTERVAL and REFRESH_INTERVAL are for EMM database polling. DENSITY_DATA_BUFFERS is not a valid parameter.

During restoration, NetBackup checks the NetBackup database (backup metadata), EMM database (media and device information), and NetBackup Logs (for detailed operation records). NetBackup Reports (C) is for reporting, not restoration checks. Image database (E) is not a standard NetBackup component.

DB2 Alias can represent remote tables and views, can be used by anyone (public synonym), and does not require DB2 authority because it inherits permissions from the underlying object rather than granting new access.

Static SQL statements are hard-coded or embedded directly within the source code of an application program before compile time. They are bound and prepared prior to execution, unlike dynamic SQL which is constructed and prepared during the application's execution.

SQL*Loader is an Oracle utility used to load data from external flat files. All individual options accurately describe its capabilities, limitations, and standard processes, making 'All the above' the correct choice.

SQL Loader (sqlldr) invocation syntax: 'sqlldr' followed by 'userid=' for credentials, 'control=' for the control file, 'log=' for log file, 'data=' for input data file, and 'direct=' for load path. All four options show valid syntax variations - the command works with just the mandatory control parameter, or with any combination of the optional parameters.

SQL Loader requires: a Control File (defines load rules), Data File (source data), and Target Table (where data loads). The Bad File is an OUTPUT file that records rejected records - it's created during loading, not required beforehand.

Oracle SQL*Loader uses two load types: Conventional path (uses SQL INSERT statements, slower but more compatible) and Direct path (bypasses SQL engine, writes directly to data blocks, much faster). 'Indirect' and 'Insert' are not valid SQL*Loader load type categories.