Oracle Database Administration 12c and 19c | 1Z0-082 exam

Explore Oracle database architecture: memory (shared global area and PGA), process (server and background processes), and storage (control files and data files), and how they map to memory and disk.

An Oracle database comprises the database and an Oracle instance, where the instance is memory plus background processes that access data stored on disk.

Explore the Oracle instance as memory and background processes, including the SGA and PGA. Learn how real application clusters and primary–standby replication ensure data availability.

The database buffer cache, the largest component of the SGA, stores copies of the most recently accessed data blocks from disk in memory to speed retrieval and reduce disk access.

Explore how the shared pool, data dictionary cache, and library cache speed SQL execution by compiling statements and reusing execution paths with bind variables to avoid hard passes.

Discover how the redo log buffer enables recovery by storing change vectors and redo entries for in-memory updates, such as a salary changing from 2000 to 5000.

Identify other SGA components and memory management in Oracle databases, including the large pool and Java pool, and understand the shift from Oracle Streams to Oracle GoldenGate.

Recap of the SGA's mandatory components includes the dvd buffer cache, the shared pool, and the dialogue buffer, plus optional components like the large pool, the java pool, and streams.

The database writer flushes modified blocks from the buffer cache to disk using an LRU strategy, keeping hot data in memory for fast access during shutdowns and recovery.

Discover buffer states in the DB buffer cache: free, unused, pinned, picked, clean, edged out, overwritten, and ducked buffers. Learn when to flush to disk to avoid buffer busy waits.

Identify and configure the default, key, keep, and recycle db block buffers and their in-memory behavior. Note LRU/MRU flushing and that the default block size cannot be changed after creation.

The log writer (LGWR) flushes the redo log buffer to online redo log files, writes on commit every 3 seconds, and before the database writes, ensuring recoverability and a checkpoint.

Understand how the process monitor (pmon) oversees user processes, cleans up after abnormal termination, and releases resources to other users, while tracking idle timers and terminating inactive tasks.

The system monitor (smon) automatically recovers an instance after failure, handles checkpoint-related updates, cleans up temporary files, and ensures redo logs, control files, and data files are synchronized at startup.

Pinpoint how the checkpoint process updates the control file and data file headers with checkpoint information and system change numbers (SCN), marking changed blocks and defining the recovery start point.

Discover how the archiver process ARCn, an optional component, archives online redo log contents to archived redo log files to safeguard recovery as log writers cycle through files.

Understand the manageability monitor, memory manager, and listener registration background processes, and how Oracle collects memory statistics for the automatic workload repository on disk to aid tuning and memory management.

Learn how user, server, and network processes interact: user processes issue queries, server processes create execution plans and use the buffer cache, network processes enable cross-server access.

Understand the difference between a connection and a session in Oracle: a connection links a user process to the server, while a session represents the user’s presence inside an instance.

Learn how data files store user and administrative data, how control files and the data dictionary manage metadata, and how online, archive, alert logs, password files, and backups support recoverability.

On a fresh instance, the server authenticates the user, builds an execution plan via the optimizer and data dictionary, then fetches blocks from disk via the buffer cache.

Learn how online redo logs are generated and switched across groups and members, archived redo logs enable recovery, and db buffer cache and library cache hit ratios influence performance.

Explore the Oracle Universal Installer (oui) as the tool to install Oracle software, maintain the inventory of Oracle homes, and view the inventory location, logs, contents, and the database version.

Use the database configuration assistant to create and configure a database, choose single or pluggable databases, set file locations and listeners, manage samples and passwords.

Perform a hands-on lab to switch from one Oracle SID to another by connecting to a different database instance, using show parameter db_name and the export method for multiple instances.

Master database upgrade tools, network configuration and listener utilities, data pump for data movement, RMAN for backup and recovery, and enterprise manager cloud controller for multi-instance monitoring.

Configure EM Express for a non container Oracle database by starting the listener, identifying the port, and using the portal to monitor performance and manage memory, storage, and security.

Introduce Oracle instance management, covering parameter files, shutdown and startup procedures, test files and a latrobe file, and dynamic performance views.

Learn how the parameter file and instance parameters configure an Oracle database and how adjusting settings like open_costs and memory_target can improve performance.

Explore spfile versus pfile initialization parameter files, their startup order, binary versus text formats, and how to convert between them and modify values in memory.

Explore how spfile and pfile determine startup configuration for an Oracle instance, where control files reside, and how memory and sizing parameters are read and edited.

Explore how to view and modify Oracle database parameters using show parameters and describe, identify data types (string, boolean, integer) and which of 445 parameters are basic and modifiable.

Explore static vs dynamic parameters in Oracle; most are dynamic, enabling in-memory changes on the running instance, while static changes require restart with session or system level scope.

participants perform a hands-on lab to modify dynamic session-level parameters, like date format and language, observe session-specific changes, and note they do not affect other sessions or defaults.

Adjust dynamic parameters at the system level to increase open cursors from 300 to 1500 in memory. Sessions reflect the new value until the instance is bounced, then memory resets.

Modify static parameters with spfile scope, and learn why changes do not take effect in memory until instance bounces. See how derived parameters like sessions respond to changes in processes.

Modify the pfile to change a static parameter, then create an spfile and restart the instance to apply the change; dynamic parameters can be altered in memory.

Recap distinguishes static and dynamic parameters, noting subject parameters cannot be modified for the current running instance. It covers initialization parameter files, sd and pdf, read at startup.

Understand the Oracle database startup sequence from shutdown to mount and open, including memory allocation, background processes, and how the control file coordinates file locations for data and logs.

Learn how restricted open mode limits access to privileged users during maintenance or data loads, and monitor how regular users connect before and after enabling the mode.

Explore Oracle database open modes, default to read write, compare read only with read write, switch modes by restarting, altering database; redo logs are not created in read only.

Learn how open suspend mode prevents writing to data files by altering the database to suspend mode, enabling maintenance and resuming with pending transactions committed.

Put the database in a restricted mode to block new activity, enabling online operations such as index creation and table definition while waiting for active sessions to finish.

Learn Oracle shutdown modes: immediate shuts down and dismounts with no new connections; transactional waits for active transactions; default shutdown also waits for sessions, emphasizing production use and automatic recovery.

Recap of database shutdown modes: immediate blocks new connections and does not wait for sessions or transactions; transactional waits for transaction; normal waits for sessions, with automatic boot recovery.

Explore the alert log file, a chronological Oracle database log of startup, shutdown, and errors; learn to locate, read, tail, and manage its size for troubleshooting.

Analyze Oracle trace files to diagnose internal errors by capturing diagnostic data, assigning an incident number, and storing it in a file-based repository outside the database for post-incident analysis.

Learn to use the adrci utility to view and filter the alert log, tail its contents, and configure max dump file size for log management.

Explore DDL logging in Oracle database administration: enable logging, locate logs under Oracle base, and review a text file and examined file to monitor changes like altering a column name.

Learn how Oracle database generates and routes debug log warnings about conditions, explores trust files and log locations, and reads health and monitor reports to diagnose system status.