Next Day DBA

Find my article on future roles of DBAs.

https://www.linkedin.com/pulse/next-day-dba-akash-pramanik

Golden gate Administration

Stop OGG
==========================
stop REPLICAT <replicat_name>

stop EXTRACT <extract_name>

stop MANAGER





Start OGG
==========================
start MANAGER

start EXTRACT <extract_name>

start REPLICAT <replicat_name>



Check status
==========================
info MANAGER detail

info EXTRACT <extract_name>

info REPLICAT <replicat_name>


View report file
==========================

view report EXTRACT <extract_name>

view report REPLICAT <replicat_name>



View/edit parameters
==========================

view/edit param EXTRACT <extract_name>

view/edit param REPLICAT <replicat_name>

==========================

Basic Concepts
--------------------------------------------

Manager

The Manager process must be running on both the source as well as target systems before the Extract or Replicat process can be started and performs a number of functions including monitoring and starting other GoldenGate processes, managing the trail files and also reporting.

Extract

The Extract process runs on the source system and is the data caoture mechanism of GoldenGate. It can be configured both for initial loading of the source data as well as to synchronize the changed data on the source with the target. This can be configued to also propagate any DDL changes on those databases where DDL change support is available.

Replicat

The Replicat process runs on the target system and reads transactional data changes as well as DDL changes and replicates then to the target database. Like the Extract process, the Replicat process can also be configured for Initial Load as well as Change Synchronization.

Collector

The Collector is a background process which runs on the target system and is started automatically by the Manager (Dynamic Collector) or it can be configured to stsrt manually (Static Collector). It receives extracted data changes that are sent via TCP/IP and writes then to the trail files from where they are processed by the Replicat process.

Trails

Trails are series of files that GoldenGate temporarily stores on disks and these files are written to and read from by the Extract and Replicat processes as the case may be. Depending on the configuration chosen, these trail files can exist on the source as well as on the target systems. If it exists on the local system, it will be known an Extract Trail or as an Remote Trail if it exists on the target system.

Data Pumps

Data Pumps are secondary extract mechanisms which exist in the source configuration. This is optional component and if Data Pump is not used then Extract sends data via TCP/IP to the remote trail on the target. When Data Pump is configured, the the Primary Extract process will write to the Local Trail and then this trail is read by the Data Pump and data is sent over the network to Remote Trails on the target system.

In the absence of Data Pump, the data that the Extract process extracts resides in memory alone and there is no storage of this data anywhere on the source system. In case of network of target failures, there could be cases where the primary extract process can abort or abend. Data Pump can also be useful in those cases where we are doing complex filtering and transformation of data as well as when we are consolidating data from many sources to a central target.

Data source

When processing transactional data changes, the Extract process can obtain data directly from the database transaction logs (Oracle, DB2, SQL Server, MySQL etc) or from a GoldenGate Vendor Access Module (VAM) where the database vendor (for example Teradata) will provide the required components that will be used by Extract to extract the data changes.

Groups

To differentiate between the number of different Extract and Replicat groups which can potentially co-exist on a system, we can define processing groups. For instance, if we want to replicate different sets of data in parallel, we can create two Replicat groups.

A processing group consisits of a process which could be either a Extract or Replicat process, a corresponding parameter file, checkpoint file or checkpoint table (for Replicat) and other files which could be associated with the process.

Invalid objects in the E-Business Suite Environment

Invalid objects in the E-Business Suite Environment

Invalid objects will appear for several reasons and it is not very easy to identify invalid objects as the root cause of a failure. In many cases invalid objects can be identified for failures reported from the functional area or for any misbehavior identified. In any case you can expect invalid objects, when you have imported a Database or when you have applied a Patch bringing new PL/SQL Packages. If you are using adpatch with the Standard options, a compilation of invalid objects for the APPS Schema is included by default - many DBA's disable this compilation via "adpatch options=nocompile", to save time. In any case, it is a good idea to check the E-Business Suite Instance on a regular basis for invalid objects.

How many invalid objects are in the Database ?

select owner,object_type,COUNT(*)
from dba_objects
where status='INVALID'
group by owner, object_type;

Check for details about the invalid objects :

column owner format A9
column object_name format A31
column object_type format A15
column last_ddl_time format A10
spool invalids.lst
select OWNER, OBJECT_NAME,OBJECT_TYPE,LAST_DDL_TIME
from dba_objects where status='INVALID'
order by owner;

 

Validating invalid objects

Manual compilation of invalid objects:

alter package <owner>.<name of the package> compile;
alter package <owner>.<name of the package> compile body;
alter view <owner>.<name of the view> compile;
alter alter java class "<owner>.<name of Java Class>" resolve;
alter procedure <owner>.<name of the procedure> compile;
alter function <owner>.<name of the function> compile;
alter materialized view <owner>.<name of the materialized view> compile;

 

The script 'adcompsc.pls' under the $AD_TOP/sql :

cd $AD_TOP/sql
sqlplus @adcompsc.pls <SCHEMA_NAME> <SCHEMA_PASSWORD> %

 

The script 'utlrp.sql' under the DATABASE $ORACLE_HOME/rdbms/admin/

* This script must be run using SQL*PLUS.
* You must be connected AS SYSDBA to run this script.
* There should be no other DDL on the database while running the script.

 

Creating your own compilation script

With the following script, you will create a new sql-script to compile the invalid objects, which can be used to compile your individual invalid objects.

set pagesize 0 head off feedb off echo off
spool validate_all.sql

select 'alter '||object_type||' '||owner||'.'||object_name||' compile;'
from dba_objects where object_type in ('PROCEDURE','FUNCTION','VIEW','TRIGGER','MATERIALIZED VIEW')
and status='INVALID' order by owner
/
select 'alter package '||owner||'.'||object_name||' compile package;'
from dba_objects where object_type in ('PACKAGE')
and status='INVALID' order by owner
/
select 'alter package '||owner||'.'||object_name||' compile body;'
from dba_objects where object_type in ('PACKAGE BODY')
and status='INVALID' order by owner
/
select 'ALTER JAVA SOURCE "' || object_name || '" COMPILE;'
from user_objects where object_type = 'JAVA SOURCE' and status = 'INVALID';
/
select 'ALTER JAVA CLASS "' || object_name || '" RESOLVE;'
from user_objects where object_type = 'JAVA CLASS' and status = 'INVALID';
/
spool off
exit

 

 

Some Questions & Answers

1. Why do invalid objects occur? What causes them?

Invalid objects can and will occur for many reasons. You will usually find invalid objects after running (or failing to run) database preparation scripts, doing an export/import,
upgrading, or applying patches. Invalid objects are usually caused by missing grants, synonyms, views, tables or packages, but can also be caused by corrupted packages.

2. Why it is important to recompile the invalid objects?

Compiling invalid objects on your database is almost the equivalent of running scandisk on a PC hard drive. This should be one of the first things you check if you start experiencing problems with your Oracle database. It is also a good idea to schedule regular checks for invalid objects.

When you call in to Oracle Support with a database or installation issue, one of the first questions they will probably ask is whether you have checked for and resolved any invalid objects.

3. Are invalid objects ever acceptable? How many is too many?

If the invalid objects exist for a Product that is not installed, it may be OK to have some, but it is preferable to have no invalid objects existing at all. If invalid objects exist
for a Product that you do have installed and are using, then it should be considered unacceptable and any existing invalid objects should be resolved before further issues can occur.

There is no set number of invalid objects that could be considered 'acceptable' as each situation will vary widely from one Installation to the next. You could just have a few invalid objects or they could number in the hundreds or even thousands, but every effort should be made to resolve them.

4. If we do not use the Product with the invalid objects, can we delete them?

In an E-Business Suite Installation are several dependencies between Products and therefore you should never delete any invalid object, if not advised by Metalink Support, that these invalid objects can be deleted.

5. How can I use adadmin to recompile my invalid objects ?

If you don't want to use the methods shown above, you can use adadmin in an E-Business Suite Environment to compile the invalid objects. Please execute following steps to initiate the compilation via 'adadmin':

1.      Open a new Shell and source the APPS User Environment

2.      Start 'adadmin' and pass the values requested for

3.      Select the menu '3. Compile/Reload Applications Database Entities menu'

4.      Select the menus '1. Compile APPS schema'

NOTE: Please be aware, that using adadmin to compile invalid objects, only the invalid objects for APPS will be compiled.

Background Processes in Oracle Database 12c

General
Acronym	Process Name	Description	Required for basic DB operation	Started by default	New in this release
ABMR	Auto BMR Background Process	Coordinates execution of tasks such as filtering duplicate block media recovery requests and performing flood control.	No	No	No
APnn	Logical Standby / Streams Apply Process Coordinator Process	Obtains transactions from the reader server and passes them to apply servers	No	No	No
ARC 0..t	Archiver Process (30 possible)	Copies the redo log files to archival storage when they are full or an online redo log switch occurs	No	No	No
BMRn	Automatic Block Media Recovery Slave Pool Process	Fetches blocks from a real-time readable standby database	No	No	No
BW nn	Database Writer Process (20 possible)	Writes modified blocks from the database buffer cache to the data files. The names of the 37th through 100th Database Writer Processes are BW36-BW99. See DBWn for more information on these processes.	Yes	Yes	Yes
CJQ0	Job Queue Coordinator Process	Spawns slave processes (Jnnn) to execute jobs in the queue.	No	Yes	No
CKPT	Checkpoint Process	Signals DBWn at checkpoints and updates all the data files and control files of the database to indicate the most recent checkpoint	Yes	Yes	No
CPnn	Database Capture Process	Captures database changes from the redo log by using the infrastructure of LogMiner.	No	No	No
CSnn	Streams Propagation Sender Process	Sends LCRs to a propagation receiver.	No	No	No
CSnn	I/O Calibration Process	Issues I/Os to storage as part of storage calibration. There is one slave process per CPU on each node of the database.	Yes	Yes	No
CTWR	Change Tracking Writer Process	Tracks changed data blocks as part of the Recovery Manager block change tracking feature	No	No	No
DBRM	Database Resource Manager Process	Sets resource plans and performs other Resource Manager tasks.	No	Yes	No
DBW 0..j	Database Writer Process	Writes modified blocks from the database buffer cache to the data files. There can be 1 to 100 Database Writer Processes. The names of the first 36 Database Writer Processes are DBW0-DBW9 and DBWa-DBWz. The names of the 37th through 100th Database Writer Processes are BW36-BW99.	Yes	Yes	No
DIA0	Diagnostic Process 0 (although 10 possible, only 0 is currently used)	Responsible for hang detection and deadlock resolution. Triggers DIAG to perform diagnostic tasks.	Yes	Yes	No
DIAG	Diagnostic Capture Process	Performs diagnostic dumps and executes global oradebug commands.	Yes	Yes	No
DMnn	Data Pump Master Process	Coordinates the Data Pump job tasks performed by Data Pump worker processes and handles client interactions.	No	No	No
Dnnn	Dispatcher Process	In a Shared Server configuration, dispatchers place connection requests in a connection request queue.	No	Yes	No
DWnn	Data Pump Worker Process	Performs Data Pump tasks as assigned by the Data Pump Master Process.	No	No	No
EMNC	EMON Coordinator Process	Coordinates the event management and notification activity in the database, including Streams Event Notifications, Continuous Query Notifications, and Fast Application Notifications. Spawns Ennn processes.	No	No	No
Ennn	EMON Slave Process	Performs database event management and notifications.	No	No	No
FBDA	Flashback Data Archiver Process	Archives historical rows for tracked tables into flashback data archives and manages archive space, organization, and retention	No	No	No
FMON	File Mapping Monitor Process	Spawns FMPUTL, an external non-Oracle Database process that communicates with the mapping libraries provided by storage vendors. Responsible for managing the mapping information.	No	No	No
GEN0	General Task Execution Process	Performs required tasks including SQL and DML.	Yes	Yes	No
Innn	Disk and Tape I/O Slave Process	Serves as an I/O slave process spawned on behalf of DBWR, LGWR, or an RMAN backup session.	No	No	No
Jnnn	Job Queue Slave Processes	Processes jobs in the queue. Spawned by CJQ0.	No	Yes	No
LGn	Log Writer Slave	On multiprocessor systems, LGWR creates slave processes to improve the performance of writing to the redo log. LGWR slaves are not used when there is a SYNC standby destination.	No	No	Yes
LGWR	Log Writer Process	Writes the log buffer out to the redo logs.	Yes	Yes	No
Lnnn	Pooled Server Process	Handles client requests in Database Resident Connection Pooling.	No	No	No
LREG	Listener Registration Process	LREG notifies the listeners about instances, services, handlers, and endpoint.	Yes	Yes	Yes
MMAN	Memory Manager Process	Serves as the SGA Memory Broker and coordinates the sizing of the memory components.	No	Yes	No
MMNL	Manageability Monitor Lite Process	Performs frequent and lightweight manageability-related tasks, such as session history capture and metrics computation.	No	Yes	No
MMON	Manageability Monitor Process	Collects statistics for the Automatic Workload Repository.	No	Yes	No
Mnnn	MMON Slave Process	Performs manageability tasks on behalf of MMON.	No	No	No
MSnn	LogMiner Worker Process	Reads redo log files and translates and assembles into transactions.	No	No	No
Nnnn	Connection Broker Process	Monitors idle connections and hands off active connections in Database Resident Connection Pooling	No	No	No
OFSD	Oracle File Server Background Process	This background process listens for new file system requests, both management (like mount, unmount, and export) and I/O requests, and executes them using Oracle threads.	Yes	Yes	No
PMON	Process Monitor	Recovers failed process resources. If Shared Server architecture is used, PMON monitors and restarts any failed dispatcher or server processes.	Yes	Yes	No
Pnnn	Parallel Query Slave Process	Started and stopped as needed to participate in parallel query operations.	No	No	No
PRnn	Parallel Recovery Process	Performs tasks assigned by the coordinator process performing parallel recovery	No	No	No
PSP0	Process Spawner Process	Starts and stops Oracle processes. Reduces workload of RBAL by starting / stopping ASM rebalance slaves.	No	Yes	No
RCBG	Result Cache Background Process	Supports SQL query and PL/SQL function result caches.	No	No	No
RECO	Recoverer Process	Resolves failures involving distributed transactions.	No	Yes	No
RM	RAT Masking Slave Process	This background process is used with Data Masking and Real Application Testing.	No	Yes	Yes
RPnn	Capture Processing Worker Process	Processes a set of workload capture files.	No	No	No
RPOP	Instant Recovery Repopulation Daemon	Responsible for re-creating and/or repopulating data files from snapshot files and backup files. The RPOP process is responsible for re-creating and repopulating data files from snapshots files. It works with the instant recovery feature to ensure immediate data file access. The local instance has immediate access to the remote snapshot file's data, while repopulation of the recovered primary data files happens concurrently. Any changes in the data are managed between the instance's DBW processes and RPOP to ensure the latest copy of the data is returned to the user.	No	No	Yes
RVWR	Recovery Writer Process	Writes flashback data to flashback database logs in the flash recovery area.	No	No	No
SAnn	SG Allocator	A small fraction of SGA is allocated during instance startup. The SAnn process allocates the rest of SGA in small chunks. The process exits upon completion of SGA allocation.	No	Yes	Yes
SMCO	Space Management Coordinator Process	Coordinates the execution of various space management related tasks, such as proactive space allocation and space reclamation.	No	Yes	No
SMON	System Monitor Process	Performs critical tasks such as instance recovery and dead transaction recovery, and maintenance tasks such as temporary space reclamation, data dictionary cleanup, and undo tablespace management	Yes	Yes	No
Snnn	Shared Server Process	In a Shared Server configuration, shared servers check a connection request queue (populated by dispatchers) and services the connection requests.	No	Yes	No
VKRM	Virtual Scheduler for Resource Manager Process	Serves as centralized scheduler for Resource Manager activity.	No	Yes	No
VKTM	Virtual Keeper of Time Process	Responsible for providing a wall-clock time (updated every second) and reference-time counter (updated every 20ms and available only when running at elevated priority).	Yes	Yes	No
Wnnn	Space Management Slave Process	These are slave processes spawned by SMCO to execute space management tasks.	No	Yes	No

Exadata
Acronym	Process Name	Description	Required for basic DB operation	Started by default	New in this release
DSKM	Slave Diskmon Process	Acts as conduit between RDBMS and ASM instances and the Master Diskmon daemon to communicate I/O Fencing information, I/O Resource Manager Plans, and Transaction Commit Cache information to Exadata storage. If no Exadata storage is used, the slave diskmon process will exit silently after startup of the instance. Only active if Exadata storage is used.	No	No	No
XDMG	Exadata Automation Manager	Initiates automation tasks involved in managing Exadata storage	No	No	No
XDWK	Exadata Automation Worker	Performs automation tasks requested by XDMG	No	No	No

Oracle Real Application Clusters
Acronym	Process Name	Description	Required for basic DB operation	Started by default	New in this release
ACMS	Atomic Control File to Memory Server Process	Coordinates consistent updates to a control file resource with its SGA counterpart on all instances in an Oracle RAC environment	No	No	No
GTX 0..j	Global Transaction Process (20 possible)	Provides transparent support for XA global transactions in an Oracle RAC environment. The database auto tunes the number of these processes based on the workload of XA global transactions.	No	No	No
IPC0	IPC Service Background Process	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.	No	No	Yes
LCKn	Lock Process	Manages the global enqueue requests and the cross-instance broadcast. Handles all requests for resources other than data blocks.	No	No	No
LDDn	Global Enqueue Service Daemon Helper Slave	Helps the LMDn processes with various tasks. LDDn processes are slaves processes spawned on demand by LMDn processes. They are spawned to help the dedicated LMDn processes with various tasks when certain workloads start creating performance bottlenecks.	No	No	Yes
LMDn	Global Enqueue Service Daemon Process	Manages enqueue manager service requests for Global Cache Service enqueues to control access to global enqueues and resources. The LMD process also handles deadlock detection and remote enqueue requests. Remote resource requests are the requests originating from another instance.LMDn processes enqueue resources managed under Global Enqueue Service. In particular, they process incoming enqueue request messages and control access to global enqueues. They also perform distributed deadlock detections. There can be up to 36 of these processes (LMD0-LMDz).	No	No	No
LMHB	Global Cache / Enqueue Service Heartbeat Monitor	Monitors the heartbeat of LMON, LMD, and LMSn processes.	No	No	No
LMON	Global Enqueue Service Monitor Process	Monitors the entire cluster to manage the global enqueues and the resources. Manages instance and process failures and the associated recovery for the Global Cache Service (GCS) and Global Enqueue Service (GES). In particular, LMON handles the part of recovery associated with global resources. LMON-provided services are also known as cluster group services (CGS).	No	No	No
LMS 0..z	Global Cache Service Process (36 possible)	Handles remote Global Cache Service (GCS) messages. The number of LMS processes varies depending on the amount of messaging traffic among nodes in the cluster.	No	No	No
PING	Interconnect Latency Measurement Process	Assesses the latencies associated with communications for each pair of instances. Every few seconds, the process in one instance (INSTANCE_NUMBER value) sends two messages to each instance (TARGET_INSTANCE value). One message has a size of 500 bytes and the other has a size of 8 KB. The message is received by the PING process on the target instance and is immediately acknowledged. The time for the round-trip is measured and collected.	No	No	No
RMSn	Oracle RAC Management Process	RMSn performs a variety of tasks, including creating resources related to Oracle RAC when new instances are added to a cluster.	No	No	No
RSMN	Remote Slave Monitor Process	Manages background slave process creation and communication on remote instances.	No	No	No

Oracle Data Guard
Acronym	Process Name	Description	Required for basic DB operation	Started by default	New in this release
ASnn	Database Apply Reader or Apply Server	As the Reader Server, computes dependencies between LCRs and assembles messages into transactions. As the Apply Server, applies LCRs to database objects, or passes LCRs to the appropriate apply handlers.	No	No	No
DMON	Data Guard Broker Monitor Process	Starts when Data Guard Broker is started. The server-side component that interacts with the local database and the DMON processes of the other databases to perform the requested function. Also responsible for monitoring the health of the broker configuration and for ensuring that every database has a consistent description of the configuration.	No	No	No
FSFP	Data Guard Broker Fast Start Failover Pinger Process	Observer process integrated in the DGMGRL client-side component. It monitors the DG Broker environment and initiates the failover on detecting a problem with Primary.	No	No	No
INSV	Data Guard Broker Instance Slave Process	Performs Data Guard Broker communication between instances of a RAC database.	No	No	No
LSP0	Logical Standby Coordinator Process	Assigns transactions to different Data Guard appliers and coordinates among them to ensure that dependencies between transactions are honored.	No	No	No
LSP1	Logical Standby Dictionary Build Process	Builds the data dictionary for the Logical Standby.	No	No	No
LSP2	Logical Standby Set Guard Process	Maintains Guard Standby information for the Logical Standby.	No	No	No
MRP0	Managed Standby Recovery Process	Provides transparent support for XA global transactions in RAC	No	No	No
NSSn	Network Server Sync Process	Transfers redo from current online redo logs to remote standby destinations configured for SYNC transport	No	No	No
NSV 0..9	Data Guard Broker NetSlave Process (10 possible)	Performs broker network communications between databases in a Data Guard configuration.	No	No	No
RSM0	Data Guard Broker Worker Server Process	Used by the DMON process to manage and monitor the database.	No	No	No
TMON	Transport Monitor	TMON starts the TMON slave (called the TT processes) and monitors a number of redo transport processes for hangs and death.	No	No	Yes
TTnn	Redo Transport Slave Process	Ships redo from current online and standby redo logs to remote standby destinations configured for ASYNC transport	No	No	Yes

Oracle Advanced Queuing
Acronym	Process Name	Description	Required for basic DB operation	Started by default	New in this release
QMNC	AQ Coordinator Process	Monitors message queues. Spawns Qnnn slave processes.	No	Yes	No
QMnn	AQ Master Class Process	Each of this type of process represents a single class of work item such as AQ notification, queue monitors, and cross process.	No	No	No
Qnnn	AQ Server Class Process	Processes messages in the Streams AQ queue. Spawned by QMNC.	No	Yes	No

Automatic Storage Management
Acronym	Process Name	Description	Required for basic DB operation	Started by default	New in this release
ACFS	ASM Cluster File System CSS Process	Tracks the cluster membership in CSS and informs the file system driver of membership changes.	No	No	No
ARB 0..A	ASM Rebalance Process (11 possible)	Rebalances data extents across the ASM file systems.	No	No	No
ARSn	ASM Recovery Slave Process (10 possible)	The ASM RBAL background process coordinates and spawns one or more of these slave processes to recover aborted ASM transactional operations. These processes run only in the Oracle ASM instance.	No	No	Yes
ASMB	ASM Background Process	Communicates with the ASM instance, managing storage and providing statistics	No	No	No
B00 0..4	ASM Blocking Slave Process for GMON	Performs maintenance actions on ASM disk groups	No	No	No
Bnnn	ASM Blocking Slave Process for GMON	Performs maintenance actions on Oracle ASM disk groups. Bnnn performs actions that require waiting for resources on behalf of GMON. GMON must be highly available and cannot wait.	No	No	Yes
FENC	Fence Monitor Process	Processes fence requests for RDBMS instances which are using Oracle ASM IOServer instances	No	No	Yes
GMON	ASM Disk Group Monitor Process	Maintains disk membership in ASM disk groups.	No	No	No
MARK	Mark AU for Resynchronization Coordinator Process	Marks ASM Allocation Units as stale following a missed write to an offline disk	No	No	No
OCFn	ASM CF Connection Pool Process	Maintains a connection to the ASM instance for metadata operations	No	No	No
Onnn	ASM Connection Pool Process	Maintains a connection to the ASM instance for metadata operations	No	No	No
RBAL	ASM Rebalance Master Process	In an Oracle ASM instance, it coordinates rebalance activity for disk groups. In a database instances, it manages Oracle ASM disk groups.	No	No	No
RMON	Rolling Migration Monitor Process	Manages the rolling migration procedure for an Oracle ASM cluster (The RMON process is spawned on demand to run the protocol for transitioning an ASM cluster in and out of rolling migration mode.	Yes	No	Yes
Rnnn	ASM Block Remap Slave Process	A database instance reading from an Oracle ASM disk group can encounter an error during a read. If possible, Oracle ASM asynchronously schedules a Rnnn slave process to remap this bad block from a mirror copy.	No	No	No
SCCn	ASM Disk Scrubbing Slave Check Process	SCCn acts as a slave process for SCRB and performs the checking operations.	No	No	Yes
SCRB	ASM Disk Scrubbing Master Process	SCRB runs in an Oracle ASM instance and coordinates Oracle ASM disk scrubbing operations.	No	No	Yes
SCRn	ASM Disk Scrubbing Slave Repair Process	SCRn acts as a slave process for SCRB and performs the repairing operations.	No	No	Yes
SCVN	ASM Disk Scrubbing Slave Verify Process	Performs Oracle ASM disk scrubbing verify operation. SCVn acts as a slave process for SCRB and performs the verifying operations. The possible processes are SCV0-SCV9.	No	No	Yes
TEMn	ASM Disk Test Error Emulation Process	Emulates I/O errors on ASM disks through named events.	No	No	No
VBGn	Volume Background Process	Communicates between the ASM instance and the operating system volume driver.	No	No	No
VDBG	Volume Driver Process	Forwards ASM request to perform various volume-related tasks.	No	No	No
VMBO	Volume Membership Process	Maintains cluster membership on behalf of the ASM volume drivers	No	No	No
VUBG	Volume drive Umbilicus Background	Relays messages between Oracle ASM instance and Oracle ASM Proxy instance that is used by ADVM (for ACFS)	No	No	Yes
Xnnn	ASM Disk Expel Slave Process	Performs Oracle ASM post-rebalance activities. This process expels dropped disks at the end of an Oracle ASM rebalance.	No	No	Yes