LGWR workers are not used when there is a SYNC standby destination. Each LMS has its own set with similar name. If an apply server cannot resolve an error, then it rolls back the transaction and places the entire transaction, including all of its messages, in the error queue. The ONLINE operation is handled by XDWK. Starting with Oracle Database 19c, IMXT (In-Memory External Table) segments are dropped by the IMCO background process. Oracle processes including the following subtypes: Background processes start with the database instance and perform maintenance tasks such as performing instance recovery, cleaning up processes, writing redo buffers to disk, and so on. Performs tasks assigned by the coordinator process performing parallel recovery. Its primary tasks are to watch for when inaccessible disks and cells become accessible again, and to initiate the ASM ONLINE operation. These background processes are spawned or reused during the start of a parallel statement. The V$PROCESS view lists database processes running in these container processes. ORA-00443: background process "string" did not start Cause The specified process did not start. Provides database service run-time load balancing and topology information to clients. It performs manageability tasks dispatched by MMON, which include taking Automatic Workload Repository snapshots and performing Automatic Database Diagnostic Monitor analysis. The Data Pump worker process is responsible for performing tasks that are assigned by the Data Pump master process, such as the loading and unloading of metadata and data. Mnnn performs manageability tasks dispatched to them by MMON. Performs manageability tasks for Oracle RAC. System might be adversely affected. Search. When a connection becomes active, the connection broker hands off the connection to a compatible pooled server process. The time for the round trip is measured and collected. Under normal operation on non-Exadata hardware and on Exadata hardware that is not utilizing ASM volumes, these processes will not be started. In this context, a background process is defined as any process that is listed in V$PROCESS and has a non-null value in the PNAME column. Performs tasks relating to manageability, including active session history sampling and metrics computation. See the Long Description for MZnn in this table for more information about the MZnn processes. LMON maintains instance membership within Oracle RAC. DSKM performs operations related to Exadata I/O fencing and Exadata cell failure handling. Query V$STREAMS_APPLY_READER, V$XSTREAM_APPLY_READER, and V$GG_APPLY_READER for information about the reader server background process. Provides transparent support for XA global transactions in an Oracle RAC environment. At specific times CKPT starts a checkpoint request by messaging DBWn to begin writing dirty buffers. LMDn processes enqueue resources managed under Global Enqueue Service. They also perform distributed deadlock detections. In Database Resident Connection Pooling, clients connect to a connection broker process. The propagation receiver passes the LCRs to an apply process. If required, MARK can also be started on demand when disks go offline in the Oracle ASM redundancy disk group. When I try to run the process without any background submission , it takes around 20-30 minutes, and give the expected results and workd just fine. Database instances, Oracle ASM instances, Manages incoming remote resource requests from other instances. The process detects instance transitions and performs reconfiguration of GES and GCS resources. The pooled server process performs network communication directly on the client connection and processes requests until the client releases the server. For GoldenGate Integrated Replicat, query V$GG_APPLY_SERVER. Auto BMR Background Process. There is one slave process per CPU on each node of the database. Coordinates the application of redo on a physical standby database. The RMON process is spawned on demand to run the protocol for transitioning an ASM cluster in and out of rolling migration mode. Also, the processes help perform two-phase commit for global transactions anywhere in the cluster so that an Oracle RAC database behaves as a single system to the externally coordinated distributed transactions. The GLOBAL_TXN_PROCESSES initialization parameter specifies the number of GTXn processes, where n is 0-9 or a-j. When a process submits a block media recovery request to ABMR, it dynamically spawns slave processes (BMRn) to perform the recovery. The coordinator process name is ASnn, where nn can include letters and numbers. When a process submits a block media recovery request to ABMR, it dynamically spawns slave processes (BMRn) to perform the recovery. The background processes perform maintenance tasks required to operate the database and to maximize performance for multiple users. Archives historical rows for tracked tables into flashback data archives and manages archive space, organization, and retention. The dispatcher slave processes enable scaling of Direct NFS connections to a clustered NAS storage. Performs database event management and notifications. The Data Pump master (control) process is started during job creation and coordinates all tasks performed by the Data Pump job. The IMCO background process initiates population (prepopulation) of in-memory enabled objects with priority LOW/MEDIUM/HIGH/CRITICAL. Possible processes are ARC0-ARC9 and ARCa-ARCt. LMSn and LMnn processes maintain a lock database for Global Cache Service (GCS) and buffer cache resources. Performs monitoring management tasks related to Data Guard on behalf of DMON. This background process is used with Data Masking and Real Application Testing. Parallel Query has two components: a foreground process that acts as query coordinator and a set of parallel slaves (Pnnn) that are background processes. The Data Pump master (control) process is started during job creation and coordinates all tasks performed by the Data Pump job. By default, parallel_level is null. This slave exists only if DLM statistics collection is enabled. The coordinator process name is ASnn, where nn can include letters and numbers. This background process coordinates the execution of various space management tasks, including proactive space allocation and space reclamation. I/O slave process can be configured on platforms where asynchronous I/O support is not available. Concepts and Oracle Database Net The scope can be the process, instance, or even cluster. Performs Data Guard broker communication among instances in an Oracle RAC environment. It also handles checkpoints, file open synchronization, and logging of Block Written records. Thanks Sheik DECLARE l_sql long; l_job number; l_return Varchar2 (32767) ; l_messages dbms_output.chararr; l_numlines integer := 1000000; Begin I/O errors can be emulated on Oracle ASM disk I/O through named events. Writes redo entries to the online redo log. The I/O slaves simulate the asynchronous I/O behavior when the underlying platform does not have native support for asynchronous I/O. INSV is created when the DG_BROKER_START initialization parameter is set to true. Performs maintenance actions on Oracle ASM disk groups. Issues I/Os to storage as part of storage calibration. . Performs automation tasks requested by XDMG. These slaves are started by setting the corresponding slave enable parameter in the server parameter file. You can disable these processes by setting the parameter to 0. These processes are fatal processes, if any of them is killed, it will result in instance termination. See Also: Oracle Database Development Guide, Oracle ASM Stale FD Cleanup Slave Process, Cleans up Oracle ASM stale file descriptors on foreground processes. Acts as the conduit between the database, Oracle ASM instances, and the Master Diskmon daemon to communicate information to Exadata storage. The shared server then reads the data from the virtual circuit and performs the database work necessary to complete the request. The LSP2 process is created as needed during startup of SQL Apply to update the list of objects that are protected by the database guard. If a resource plan is not enabled, then this process is idle. Services Administrator's Guide, Perform parallel execution of a SQL statement (query, DML, or DDL). If the query is a GV$ query, then these background processes are numbered backward, starting from PPA7. The VKTM timer service centralizes time tracking and offloads multiple timer calls from other clients. MRP0 is spawned at the start of redo apply on a physical standby database. After the shared server completes the client request, the server releases the virtual circuit back to the dispatcher and is free to handle other clients. The capture process includes one reader server that reads the redo log and divides it into regions, one or more preparer servers that scan the redo log, and one builder server that merges redo records from the preparer servers. The ACFS process delivers CSS membership changes to the cluster file system. Each RSnn process is a slave process for LMSn to handle remastering work. Once released, the server class processes are moved to a free server pool. The capture process includes one reader server that reads the redo log and divides it into regions, one or more preparer servers that scan the redo log, and one builder server that merges redo records from the preparer servers. PMAN monitors, spawns, and stops the following as needed. DSKM performs operations related to Exadata I/O fencing and Exadata cell failure handling. This process is active only if Exadata Storage is used. The process terminates itself after being idle for a long time. Oracle's background check process in Latin America is performed by background screening services in each country. OracleprocessDB SIDOracle instanceOracle instanceSIDADEVDBSIDATESTprocess . XDMG monitors all configured Exadata cells for state changes, such as a bad disk getting replaced, and performs the required tasks for such events. VKTM publishes two sets of time: a wall clock time using a seconds interval and a higher resolution time (which is not wall clock time) for interval measurements. FENC receives and processes the fence request from CSSD. 6.Archiver Process. VBGn can run as multiple processes, where n is 0-9. LMS, where n is 0-9 or a-z, maintains a lock database for Global Cache Service (GCS) and buffer cache resources. Unnn processes are database container operating system processes where database backgrounds processes like SMON, CJQ0, and database foreground processes run. Performs Oracle ASM disk scrubbing verify operation. Responsible for re-creating and/or repopulating data files from snapshot files and backup files. See the Long Description for the DBWn process in this table for more information about the BWnn process. The default number of these processes is based on number of CPUs. The I/O slaves simulate the asynchronous I/O behavior when the underlying platform does not have native support for asynchronous I/O. In-memory enabled objects with priority NONE will not be prepopulated but will be populated on demand via Wnnn processes when queried. These tasks include preallocating space into locally managed tablespace and SecureFiles segments based on space usage growth analysis, and reclaiming space from dropped segments. The principal parameters are: DISPATCHERS, SHARED_SERVERS, MAX_SHARED_SERVERS, LOCAL_LISTENER, REMOTE_LISTENER. This relationship is maintained until the master requires services of a particular service process. Assesses latencies associated with communications for each pair of cluster instances. SCRn acts as a slave process for SCRB and performs the repairing operations. Job slaves gather all the metadata required to run the job from the data dictionary. Concepts. VKRM manages the CPU scheduling for all managed Oracle processes. Wnnn processes are utilized by the IMCO background process for prepopulation of in-memory enabled objects with priority LOW/MEDIUM/HIGH/CRITICAL, and for repopulation of in-memory objects. The number of these processes vary depending on the active database processes. Query V$PROPAGATION_SENDER for information about a propagation sender. The ACMS process works with a coordinating caller to ensure that an operation is executed on every instance in Oracle RAC despite failures. Every 30 seconds the process processes and publishes run-time load-balancing information and keeps the topology information current. Onnn slave processes are spawned on demand. Maintains cluster membership on behalf of the Oracle ASM volume driver. Initiates automation tasks involved in managing Exadata storage. These processes are fatal processes, if any of them is killed, it will result in instance termination. Background processes asynchronously perform I/O and monitor other Oracle Database processes to provide increased parallelism for better performance and reliability. and Administration, Reads redo log files and translates and assembles into transactions. Cause: The specified process did not start after the specified time. Up to five process (B000 to B004) can exist depending on the load. IPC0 handles very high rates of incoming connect requests, as well as, completing reconfigurations to support basic messaging and RDMA primitives over several transports such as UDP, RDS, InfiniBand and RC. Coordinates Oracle ASM disk scrubbing operations. Offline timer processing and drop of the disk are performed in this slave. The capture process name is CPnn, where nn can include letters and numbers. Manages background slave process creation and communication on remote instances in Oracle RAC. Bnnn performs actions that require waiting for resources on behalf of GMON. Manages mapping information for the Oracle Database file mapping interface. The names of the 37th through 100th Database Writer Processes are BW36-BW99. This process performs the resizing of memory components on the instance. Processes a set of workload capture files. LMDn processes enqueue resources managed under Global Enqueue Service. XDWK gets started when asynchronous actions such as ONLINE, DROP, and ADD an Oracle ASM disk are requested by XDMG. The RSnn processes were named RMVn in Oracle Database 12c and earlier releases. Note that if the AQ_TM_PROCESSES initialization parameter is set to 0, this process will not start. Coordinates Oracle ASM disk scrubbing operations. This process cleans up Oracle ASM stale file descriptors on foreground processes if an Oracle ASM disk is globally closed. Source:- http://docs.oracle.com/cd/E16655_01/server.121/e17615/bgprocesses.htm Some of the parameters that names have been changed, for example NSA1 (Redo transport services has been named as TTnn etc) These processes communicate with the Oracle ASM instance. If the process is specific to a particular feature, then the column names the feature. Performs Oracle ASM disk scrubbing check operation. Performs remastering for cluster reconfiguration and dynamic remastering. QMNC dynamically spawns Qnnn processes as needed for performing these tasks. CJQ0 is automatically started and stopped as needed by Oracle Scheduler. DMON maintains profiles about all database objects in the broker configuration in a binary configuration file. They receive and perform units of work sent from the query coordinator. Virtual Scheduler for Resource Manager Process, Serves as centralized scheduler for Resource Manager activity. ASMB also runs with Oracle Cluster Registry on Oracle ASM. An Oracle Database background process is defined as any process that is listed in V$PROCESS and has a non-null value in the PNAME column. LSP0 is also responsible for detecting and enabling run-time parameter changes for the SQL Apply product as a whole. You can disable these processes by setting the parameter to 0. Manages background slave process creation and communication on remote instances in Oracle RAC. 5.Process Monitor Process. XDWK gets started when asynchronous actions such as ONLINE, DROP, and ADD an Oracle ASM disk are requested by XDMG. LSP0 is the initial process created upon startup of Data Guard SQL Apply. There can be up to 100 of these processes, named as follows: Registers the instance with the listeners. When a process submits a block media recovery request to ABMR, it dynamically spawns slave processes (BMRn) to perform the recovery. Performs Oracle ASM post-rebalance activities. Every few seconds, the process in one instance sends messages to each instance. Database instances, XStream Outbound servers, XStream Inbound servers, GoldenGate Integrated Replicat, Automatic Block Media Recovery Slave Pool Process, Fetches blocks from a real-time readable standby database. An apply server receives the transactions from the coordinator background process, and either applies database changes in LCRs or sends LCRs or messages to apply handlers. SCRn acts as a slave process for SCRB and performs the repairing operations. In the shared server architecture, clients connect to a dispatcher process, which creates a virtual circuit for each connection. In previous releases, IMXT segments were dropped by foreground processes. Manages and monitors a database that is part of a Data Guard broker configuration. When the reader server finishes computing dependencies between LCRs and assembling transactions, it returns the assembled transactions to the coordinator process. JPn patches and updates the Java in the database classes. VBGn handles messages originating from the volume driver in the operating system and sends them to the Oracle ASM instance. This relationship is maintained until the master requires services of a particular service process. To maximize performance and accommodate many users, a multiprocess Oracle database system uses background processes. Instance Membership Recovery Slave Process, Performs synchronous tasks on behalf of LMON, The IMR0 background process performs the Instance Member Recovery synchronous operations on behalf of LMON, Oracle RAC, Database instances, Oracle ASM instances, Performs Data Guard broker communication among instances in an Oracle RAC environment. Selects jobs that need to be run from the data dictionary and spawns job queue slave processes (Jnnn) to run the jobs. The RPOP process is responsible for re-creating and repopulating data files from snapshots files. When you have multiple instances on a UNIX server and need to release a semaphore set for an Oracle database, you must first determine which semaphore set belongs to your crippled instance. Global Cache/Enqueue Service Heartbeat Monitor, Monitor the heartbeat of several processes. GMON must be highly available and cannot wait. Background processes are the processes r. These background slave processes perform tasks on behalf of a coordinating process running in another cluster instance. The process terminates itself after being idle for a long time. The number of slaves will be proportional to the amount of cleanup work to be done and the current efficiency of cleanup. When the RDBMS instance terminates due to a failure, all the outstanding I/O's from the RDBMS instance should be drained and any new I/O's rejected. The DB_WRITER_PROCESSES initialization parameter specifies the number of Database Writer Processes. CKPT checks every three seconds to see whether the amount of memory exceeds the value of the PGA_AGGREGATE_LIMIT initialization parameter, and if so, takes the action described in "PGA_AGGREGATE_LIMIT".