Here's a list of background processes:
The System Monitor carries out a crash
recovery when a crashed insance is started up again. In a
Real Application Clusters database, the SMON process of one instance
can perform instance recovery for other instances that have failed.
SMON also cleans up temporary segments that are no longer in use and
recovers dead transactions skipped during system failure and instance
recovery because of file-read or offline errors. These transactions are
eventually recovered by SMON when the tablespace or file is brought
The process monitor performs process recovery when a user process
fails. PMON is responsible for cleaning up the cache and freeing
resources that the process was using. PMON also checks on the
dispatcher processes and server processes and restarts them if they
The Database Writer writes modified
blocks) from the database buffer
to the datafiles. The amount of DBWn Processes to start is
determined by the initialization
DB_WRITER_PROCESSES. DBWR also writes the actual
SCN with the Block.
The Log Writer writes the redo
log buffer from the SGA to the online
redo log files.
Managed recovery process: the process that applies archived redo log to
The remote file server process on the standby
database receives archived redo logs from the primary
The recoverer process is used to resolve distributed transactions that
are pending due to a network or system failure in a distributed
database. At timed intervals, the local RECO attempts to connect to
remote databases and automatically complete the commit or rollback of
the local portion of any pending distributed transactions.
The Checkpoint Process reqularly
initiates a checkpoint which uses DBWR to write all
dirty blocks back to the datafiles, thus synchronizing the database.
Since a Checkpoint records the current SCN, in a recovery only redo
records with a SCN higher than that of the last checkpoint need to be
The Archiver Process archives redo log files
The Dispatcher Process is used in a shared
The Shared Server Process is used in a shared
The lock manager.
AQ Time Manager. A queue monitor process which monitors the message
queues. Used by Oracle Streams Advanced Queuing.
The wakeup monitor process.
Inter-instance locking process.
The snapshot process.
Guard Broker process.
SGA Background Process
The Automatic Shared Memory Management feature uses a new background
process named Memory Manager (MMAN). MMAN serves as the SGA
Memory Broker and coordinates the sizing of the memory components. The
SGA Memory Broker keeps track of the sizes of the components and
pending resize operations
- This a new feature introduced in 10g.
- Flashbacking a database means going back to a previous database state.
- The Flashback Database feature provides a way to quickly revert an
entire Oracle database to the state it was in at a past point in time.
- This is different from traditional point in time recovery.
- A new background process Recovery Writer ( RVWR) introduced which is
responsible for writing flashback logs which stores pre-image(s) of
- One can use Flashback Database to back out changes that:
- Have resulted in logical data corruptions.
- Are a result of user error.
- This feature is not applicable for recovering the database in case of
- The time required for flashbacking a database to a specific time in
past is DIRECTLY PROPORTIONAL to the number of changes made and not on
the size of the database.
These are job queue processes which are spawned as needed by CJQ0 to
complete scheduled jobs. This is not a new process.
This is a new process Change Tracking Writer (CTWR) which works with
the new block changed tracking features in 10g for fast RMAN
The Memory Monitor Light (MMNL) process is a new process in 10g which
works with the Automatic Workload Repository new features (AWR) to
write out full statistics buffers to disk as needed.
The memory monitor (MMON) process was introduced in 10g and is
associated with the Automatic Workload Repository new features used for
automatic problem detection and self-tuning. MMON writes out the
required statistics for AWR on a scheduled basis.
This is the Job Queue monitoring process which is initiated with the
job_queue_processes parameter. This is not new. More Info DOCID=222190.1