Computer Knowledge
Database Management Systems
5,543 Questions
Database Management Systems (DBMS) form the core framework for data storage, retrieval, and security in modern software applications. Concepts such as the E-R model, backup planning, SQL integration, and big data architecture are essential for computer knowledge sections. This hub offers a comprehensive set of practice questions to master DBMS fundamentals and advanced database operations.
E-R Model ConceptsBackup and RecoverySQL Server UpgradesJDBC and ODBCBig Data CharacteristicsData VirtualizationOracle Database
Database Management Systems Questions
-
After the P1 partition is dropped, all global B-tree and function-based indexes are automatically rebuilt.
-
After the P1 partition is dropped, all global indexes that were marked UNUSABLE will be automatically rebuilt.
-
All global indexes on the ITEM table remain intact throughout the DDL operation.
-
Other DML statements can continue to use the any global B-tree indexes without interruption.
D
Correct answer
Explanation
The UPDATE GLOBAL INDEXES clause ensures that dropping a partition does not invalidate global indexes. Instead of marking indexes UNUSABLE, Oracle asynchronously maintains them during the DDL operation. This allows concurrent DML operations to continue accessing global indexes without interruption, improving availability during partition maintenance.
-
A file containing a SQL statement which will re-create the database.
-
A text copy to the control file.
-
A binary copy of the control file.
-
A file containing a SQL statement which will re-create the control file.
C
Correct answer
Explanation
The BACKUP CONTROL FILE TO trace creates a binary copy of the control file at the specified location. This is different from the TO TRACE option which creates a text file with SQL commands. The binary backup preserves the exact state of the control file including data file info, checkpoint details, and recovery metadata - essential for disaster recovery scenarios.
-
DBMS_REPCAT_AUTH
-
DBMS_REPCAT_ADMIN
-
DBMS_RESOURCE_MANAGER
-
DBMS_RESOURCE_MANAGER_PRIVS
D
Correct answer
Explanation
DBMS_RESOURCE_MANAGER_PRIVS is the specific package used to grant resource group privileges and administer the Resource Manager. It provides procedures like GRANT_SYSTEM_PRIVILEGE and GRANT_SWITCH_CONSUMER_GROUP to authorize users for resource management tasks. The other packages listed serve different purposes - DBMS_REPCAT packages handle replication, while DBMS_RESOURCE_MANAGER creates and configures plans but doesn't handle privilege grants.
-
Horizontal partitioning`
-
Vertical partitioning
-
Range partitioning
-
Hash partitioning
A
Correct answer
Explanation
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
-
ALL_TAB_PRIVS
-
USER_TAB_PRIVS
-
ALL_TAB_PRIVS_MADE
-
rman target system/manager nocatalog
-
rman system/manager catalog=no
-
rman system/manager without catalog
-
rman target system/manager rcvcat no
A
Correct answer
Explanation
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 database
-
tables
-
views
-
both (2) and (3)
A
Correct answer
Explanation
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.
-
Tune the number of latches by setting it to db_cache_size(50*db_block_size)
-
Tune the number of latches by setting to large_pool_size/1000
-
Tune the number of latches by setting it to Number of CPUs *1 *2
-
Oracle9i would automatically calculate the number of latches required, based on the environment defined by the initialization parameters for the database and the operating system level parameters
D
Correct answer
Explanation
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.
-
After the archival of online redo log files to the two mandatory destinations occurs, the online redo logs may be overwritten.
-
After the archival of online redo log files to the two local destinations occurs, the online redo logs may be overwritten.
-
No effect because the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value is NOT equal to the number of local mandatory archive destinations.
-
After the archival of online redo log files to the one local mandatory destination occurs, the online redo logs may be overwritten.
B
Correct answer
Explanation
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.
-
Only the names of all the tables that can be accessed.
-
Only the names of all the objects that can be accessed.
-
Only the names of the objects that are owned.
-
Only the names of the tables that are owned.
A
Correct answer
Explanation
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.
-
Database Buffer Cache
-
Redo log Buffer
-
PGA
-
Shared Pool
C
Correct answer
Explanation
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_TABLES
-
DBA_INDEXES
-
DBA_SEGMENTS
-
DBA_TABLESPACES
C
Correct answer
Explanation
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.
C
Correct answer
Explanation
A database job is marked BROKEN after 16 consecutive failed executions. This is Oracle's default threshold to prevent repeatedly failing jobs from continuing to consume system resources and clutter the job queue.
-
Oracle forms runs server-side PL/SQL while app forms run client side.
-
Apps forms use uses exact positioning while Oracle forms dont
-
Oracle forms runs client-side PL/SQL while app forms run server side.
-
Oracle forms Flash Charts as its integrated charting engine while app forms dont
C
Correct answer
Explanation
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
-
V$ENDIAN FORMAT
-
V$PLATFORM
-
V$COMPATIBILITY_LEVEL
A
Correct answer
Explanation
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.