Database Management Systems

Horizontal partitioning divides table rows based on a key or range - different subsets of rows go into different tables. This differs from vertical partitioning (splitting columns), range partitioning (a specific horizontal method), and hash partitioning (using a hash function). The question asks about the general concept of putting different rows into different tables, which is horizontal partitioning.

DBA_TAB_PRIVS

To connect to RMAN without a recovery catalog, use 'rman target nocatalog'. This connects to the target database using the control file for metadata instead of a catalog database. Options B, C, and D use incorrect syntax - 'catalog=no', 'without catalog', and 'rcvcat no' are not valid RMAN connection parameters.

A profile in Oracle is a database-level resource limit that can only be assigned to users, not to schema objects like tables or views. Profiles control password settings (expiration, complexity, failed login attempts) and resource limits (CPU time, sessions, idle time). They are assigned with the CREATE USER or ALTER USER commands using the PROFILE clause.

Oracle9i introduced automatic latch calculation based on initialization parameters and OS configuration. Manual latch tuning formulas are obsolete in Oracle9i. The database now determines optimal latch counts dynamically using db_cache_size, db_block_size, CPU count, and other parameters.

With LOG_ARCHIVE_MIN_SUCCEED_DEST=2, Oracle requires successful archival to at least 2 destinations before overwriting redo logs. Since there are 2 local destinations (1 mandatory + 1 optional), once both local destinations succeed, the requirement is met even if the remote destination hasn't finished.

The ALL_OBJECTS data dictionary view shows all objects accessible to the current user, including objects owned by the user plus those on which privileges have been granted. By filtering WHERE object_type='TABLE', only table names are returned. USER_OBJECTS would show only owned objects.

The SGA (System Global Area) is a shared memory region in Oracle that includes the Database Buffer Cache, Redo Log Buffer, and Shared Pool - all of which are accessible by multiple processes. PGA (Program Global Area) is private memory specific to each server process and is NOT part of the SGA. Each Oracle process has its own PGA containing session-specific variables and runtime areas.

DBA_SEGMENTS is the correct view because it contains information about ALL segments allocated to a user, including both tables and indexes. Tables and indexes are both stored as segments in the database. DBA_TABLES and DBA_INDEXES would require querying two separate views and joining them. DBA_TABLESPACES shows tablespace information, not user-specific object locations. DBA_SEGMENTS provides a comprehensive view of all storage segments owned by a user.

Oracle Forms (standard) runs PL/SQL code on the client side in the Forms runtime, while Oracle Apps Forms (E-Business Suite) runs PL/SQL server-side for better performance, security, and centralized business logic management.

V$TRANSPORTABLE_PLATFORM shows which platforms can cross-transport tablespaces. It lists platforms and their endian formats, allowing you to verify compatibility between source and target databases before attempting transportable tablespace operations.

When a user creates an object without specifying a tablespace, Oracle stores it in that user's default tablespace. This is set at user creation time with the DEFAULT TABLESPACE clause or inherited from the database default.

When a client abnormally terminates, PMON (Process Monitor) automatically detects the failed session, rolls back the uncommitted transaction, releases locks, and frees resources. No manual intervention by the DBA is needed - PMON handles this cleanup automatically.

When an Oracle client process terminates abnormally, the PMON (Process Monitor) background process automatically detects the failure and rolls back any uncommitted transactions. PMON releases all resources and locks held by the terminated transaction, making them available to other sessions. This is automatic instance recovery at the transaction level. Option A is incorrect because archived redo logs are for media recovery, not transaction rollback. Option B is incorrect because instance recovery doesn't help with incomplete user transactions. Option D is incorrect because point-in-time recovery would lose committed work.

It consists of all the files, structures, processes that form oracle database 9i.