Questions de cour DBA

1. Process User: A process user refers to an operating system user account that is
associated with an Oracle database process. Each client connection to the database is
associated with a process user, and it is used to authenticate and authorize the user's
actions within the database.
2. Process Server: Process servers, also known as background processes, are dedicated
Oracle processes that run in the background to perform specific tasks required for the
functioning of the database. These processes handle activities such as managing
memory, writing data to disk, performing backups, and handling communication with
clients.
3. Instance: An instance is a combination of memory structures (SGA and PGA) and
background processes (process servers) that work together to manage and access an
Oracle database. It represents the running environment of a specific Oracle database
on a server.
4. PGA (Program Global Area): PGA is a memory area allocated for an Oracle database
session or process. It holds data and control structures specific to that process, such as
variables, arrays, and other runtime information. Each user process has its own PGA,
which is used for sorting, hashing, and other session-specific operations.
5. SGA (System Global Area): SGA is a shared memory region that is accessible by all Oracle
database users and processes. It holds data and control structures shared among
multiple processes, such as data buffers, shared SQL areas, and other caches. The SGA
improves performance by reducing disk I/O and facilitating data sharing.
6. Shared Pool: The shared pool is a component of the SGA that stores shared memory
structures for caching frequently used SQL statements, parsed SQL queries, and PL/SQL
code. It helps improve performance by reducing the need to parse and optimize SQL
statements repeatedly.
7. Large Pool: The large pool is an optional component of the SGA that provides additional
memory for large-scale operations such as backup and recovery, parallel execution, and
shared server processes. It is used to allocate memory for sessions that require a
significant amount of memory beyond the PGA.
8. Buffer Cache: The buffer cache is a part of the SGA that stores data blocks read from
the database files. It holds frequently accessed data in memory, reducing the need for
disk I/O and improving database performance.
9. Redo Log Pool: The redo log pool is a part of the SGA that caches frequently accessed
redo log data. Redo logs contain a record of all changes made to the database and are
crucial for database recovery and transaction durability.
10. Java Pool: The Java pool is a component of the SGA that stores Java objects and
metadata used by Oracle's Java Virtual Machine (JVM). It provides memory for Java-
related operations such as executing Java stored procedures, triggers, and functions.
11. Processes Background: Processes in the background refer to the dedicated Oracle
background processes that run independently of user sessions. These processes handle
tasks such as writing data to disk, performing backups, managing locks, and managing
memory.
12. Parameter File: A parameter file is a text-based file that contains initialization
parameters for an Oracle database instance. It specifies various settings and
 configuration options such as memory allocation, file locations, network parameters,
and other database-specific settings.
13. Password File: A password file is a binary file that stores encrypted passwords for Oracle
database users who are granted administrative privileges such as SYSDBA or SYSOPER.
It is used for authentication and allows authorized users to connect to the database
with elevated privileges.
14. Archive Log File: An archive log file is a copy of a redo log file that has been filled and
archived. In archivelog mode, Oracle automatically archives filled redo log files, enabling
point-in-time recovery and ensuring data durability.
15. Control File: The control file is a binary file that contains metadata about the database
structure, such as the database name, data files, redo log files, and other critical
information. It is crucial for database startup, recovery, and maintaining data
consistency.
16. Database File: Database files refer to the physical files on disk that store the actual data
of an Oracle database. They include data files, which hold table data, indexes, and other
objects, as well as temporary files and undo files.
17. Redo Log File: Redo log files are a set of files that record all changes made to the
database. They ensure transaction durability and provide the ability to recover the
database to a specific point in time or restore it in the event of a failure.
18. CDB (Container Database): CDB is an abbreviation for Container Database. It is a feature
introduced in Oracle Database 12c that allows multiple pluggable databases (PDBs) to
be consolidated within a single container. The CDB provides a centralized infrastructure
for managing and administering multiple databases as a unit.
19. CDB Root: CDB Root is the top-level container in a multitenant architecture. It contains
common metadata and provides shared resources and services to all the pluggable
databases (PDBs) within the container database (CDB).
20. PDB (Pluggable Database): PDB refers to a pluggable database, which is a self-contained
database within a container database (CDB). Each PDB has its own set of data files,
tablespaces, users, and resources, and can be plugged in or unplugged from the CDB
without affecting other PDBs.
21. Restricted PDB: A restricted PDB is a pluggable database that is only accessible to
privileged users. It is useful in scenarios where specific PDBs need to be restricted to
prevent unauthorized access.
22. Difference between Oracle 12c and previous versions: Oracle 12c introduced significant
changes, including the introduction of the multitenant architecture, which allows
multiple pluggable databases (PDBs) to be managed as a single unit within a container
database (CDB). It also introduced enhancements in areas such as performance,
security, and manageability.
23. Multitenant Database in Oracle: A multitenant database is an Oracle database that
includes a container database (CDB) that can hold multiple pluggable databases (PDBs).
The CDB provides a shared infrastructure for managing and administering the PDBs,
allowing for consolidation, resource sharing, and easier management.
24. SPFILE (Server Parameter File) & PFILE (Parameter File): Both SPFILE and PFILE are
parameter files used to specify initialization parameters for an Oracle database. The
difference lies in their format and how they are managed. SPFILE is a binary file stored
in the server's file system and can be modified using the ALTER SYSTEM command. PFILE
 is a text-based file that can be edited manually, and changes take effect after a database
restart.
25. Privileges & Roles: Privileges and roles are security mechanisms in Oracle that control
access and permissions within the database. Privileges grant specific permissions to
individual users, such as the ability to create tables or execute certain SQL statements.
Roles are named groups of privileges that can be granted to users, simplifying the
administration of permissions by assigning roles to users instead of individual privileges.
26. Difference between Database in ARCHIVELOG & NOARCHIVELOG mode: In
ARCHIVELOG mode, the Oracle database automatically archives filled redo log files,
allowing for point-in-time recovery and the ability to restore the database to a specific
moment. This mode provides data protection and is typically used in production
environments. In NOARCHIVELOG mode, the database does not archive redo log files,
which means that point-in-time recovery is not possible. This mode is generally used in
non-production or test environments where point-in-time recovery is not a
requirement.
27. Tablespace: A tablespace is a logical storage container within an Oracle database. It
consists of one or more data files that store the actual data of tables, indexes, and other
database objects. Tablespaces provide a way to organize and manage database storage
efficiently.
28. Group & Member Differences: In the context of tablespaces, a group refers to a
collection of data files that belong to the same tablespace. Members, on the other hand,
are individual data files within a group. Groups provide a way to manage multiple data
files together, while members represent the individual files that make up the group.
29. Profile : in Oracle is a database object that allows administrators to enforce resource
limitations, password policies, and other restrictions on user sessions. It defines various
parameters and limits that control how users can interact with the database.
o By using profiles, administrators can exercise granular control over user access
and resource utilization, ensuring a balance between security, performance, and
efficient database operation. Profiles provide a means to enforce consistent
policies and manage user sessions effectively.