Saturday, February 25, 2017

List of background Processes in Oracle Database 12c

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

which process starts first when instance is started?

The first process that will be started when we start instance is PSP process. This is called PROCESS SPAWNER.  This process is introduced in 10g and is responsible for creating and managing other oracle backgroung processes.
As the name specifies, this process can spawn so that you will see the process name as PSP0 in alert log file.

Monday, January 16, 2017

Not Paid Last Month salary



Respected Sir

 I am completing my last month's work with my admirable & Prominent Company ”    Spectrum Engineering ” and I am working as a Jr. Database Administrator .And On behalf of my company [SECL] I am supporting on very much valuable Customer National Board of Revenue which accordingly too much confidential and complex customer database also. I always tried to support NBR of my best effort.

Sir In the mean time I have come an opportunity and just took it. Now I have to join there.
Sir I have too much respect to you .Very few people as like you ever I have seen. You are so kind also on your employee. Sir I never abandon from your affectionate loving behavior. This will always with me.
I love and enjoy my profession. My hand always spread for any kind of support of National board of revenue database problem. I will be very happy if you order any task after my departure when fall any problem.

However Sir, As per Hr Policy they will not pay my last working month salary .Though also I am humbly requesting to you for considering my last working monthly salary issue and if possible please give this.

I always Expect and Pray for my Spectrum Engineering  well growth and stand its own foot strongly.

With Best Regards
Salmondy

Thursday, January 12, 2017

Invalid Archivelog deletion policy




 Data Guard Physical Standby - RMAN configure archivelog deletion policy reports RMAN-08591 (Doc ID 1984064.1)



When attempting to configure the RMAN archivelog deletion policy in a Data Guard environment RMAN reports the following warning:
RMAN> configure archivelog deletion policy to applied on standby;

new RMAN configuration parameters:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
new RMAN configuration parameters are successfully stored
RMAN-08591: WARNING: invalid archived log deletion policy
 
 

Cause:

o eliminate the RMAN warning message when setting the deletion policy for archivelogs, at least one archive destination must be set as a mandatory destination.

As there is a broker configuration in place this MUST be performed through the broker.

The following process details this:

1. Log in to the broker command line utility
[oracle@grid2vm1 ~]$ dgmgrl
DGMGRL for Linux: Version 12.1.0.2.0 - 64bit Production

Copyright (c) 2000, 2013, Oracle. All rights reserved.

Welcome to DGMGRL, type "help" for information.
 dgmgrl sys/welcome1
DGMGRL for Linux: Version 11.2.0.4.0 - 64bit Production

Copyright (c) 2000, 2009, Oracle. All rights reserved.

Welcome to DGMGRL, type "help" for information.
Connected.
DGMGRL> show configuration

Configuration - AWDB_PRIMARY

  Protection Mode: MaxPerformance
  Databases:
    AWDB    - Primary database
    AWCTGFO - Physical standby database

Fast-Start Failover: DISABLED

Configuration Status:
SUCCESS

DGMGRL> show database verbose ORCL
Object "awdb" was not found
DGMGRL> show database verbose ORCLSTBY
Object "awctgfo" was not found
DGMGRL> show database verbose awctgfo
Object "awctgfo" was not found
DGMGRL> show database verbose "ORCLSTBY"

Database - ORCLSTBY

  Role:            PHYSICAL STANDBY
  Intended State:  APPLY-ON
  Transport Lag:   0 seconds (computed 0 seconds ago)
  Apply Lag:       0 seconds (computed 0 seconds ago)
  Apply Rate:      630.00 KByte/s
  Real Time Query: ON
  Instance(s):
    awctgfo1
    awctgfo2 (apply instance)

  Properties:
    DGConnectIdentifier             = 'awctgfo_dg'
    ObserverConnectIdentifier       = ''
    LogXptMode                      = 'ASYNC'
    DelayMins                       = '0'
    Binding                         = 'optional'
    MaxFailure                      = '0'
    MaxConnections                  = '1'
    ReopenSecs                      = '300'
    NetTimeout                      = '30'
    RedoCompression                 = 'DISABLE'
    LogShipping                     = 'ON'
    PreferredApplyInstance          = ''
    ApplyInstanceTimeout            = '0'
    ApplyParallel                   = 'AUTO'
    StandbyFileManagement           = 'AUTO'
    ArchiveLagTarget                = '0'
    LogArchiveMaxProcesses          = '10'
    LogArchiveMinSucceedDest        = '1'
    DbFileNameConvert               = '+DATA_DCAW, +DATA_DRAW, +RECO_DCAW, +RECO                                                                                        _DRAW'
    LogFileNameConvert              = '+DATA_DCAW, +DATA_DRAW, +RECO_DCAW, +RECO                                                                                        _DRAW'
    FastStartFailoverTarget         = ''
    InconsistentProperties          = '(monitor)'
    InconsistentLogXptProps         = '(monitor)'
    SendQEntries                    = '(monitor)'
    LogXptStatus                    = '(monitor)'
    RecvQEntries                    = '(monitor)'
    ApplyLagThreshold               = '0'
    TransportLagThreshold           = '0'
    TransportDisconnectedThreshold  = '30'
    SidName(*)
    StaticConnectIdentifier(*)
    StandbyArchiveLocation(*)
    AlternateLocation(*)
    LogArchiveTrace(*)
    LogArchiveFormat(*)
    TopWaitEvents(*)
    (*) - Please check specific instance for the property value

Database Status:
SUCCESS



















. Locate the name of the standby site you want to set as a mandatory destination
2 . 
 
DGMGRL> show configuration;

Configuration - dg_db121

  Protection Mode: MaxPerformance
  Members:
  db121    - Primary database
    db121stb - Physical standby database

Fast-Start Failover: DISABLED

Configuration Status:
SUCCESS   (status updated 39 seconds ago)
 
3. For the standby site locate the "Binding" property in the sites broker configuration
DGMGRL> show database verbose db121stb

Database - db121stb

  Role:               PHYSICAL STANDBY
  Intended State:     APPLY-ON
  Transport Lag:      0 seconds (computed 0 seconds ago)
  Apply Lag:          0 seconds (computed 0 seconds ago)
  Average Apply Rate: 14.00 KByte/s
  Active Apply Rate:  594.00 KByte/s
  Maximum Apply Rate: 5.06 MByte/s
  Real Time Query:    OFF
  Instance(s):
    db1211 (apply instance)
    db1212

  Properties:
    DGConnectIdentifier             = 'db121_stb'
    ObserverConnectIdentifier       = ''
    LogXptMode                      = 'ASYNC'
    RedoRoutes                      = ''
    DelayMins                       = '0'
    Binding                         = 'optional'     ****** controls whether the destination is mandatory or not
..
.

Database Status:
SUCCESS
 

Also, you can verify BINDING column of the V$ARCHIVE_DEST view of the database or far sync instance that is sending redo data using SQLPLUS by running below script
SQL > select binding from v$archive_dest;

4. Set the "Binding" property to MANDATORY

DGMGRL> edit database db121stb set property Binding='mandatory';
Property "binding" updated
DGMGRL> exit
OR using SQLPLUS
SQL>alter system set log_archive_dest_2='service=ORACLE MANDATORY lgwr async affirm valid_for=(online_logfiles,primary_role) db_unique_name=LARRY';


5. Once the broker configuration has set a standby site as a mandatory destination, the RMAN configuration can be altered to set the archivelog deletion policy to applied on standby.
[oracle@grid2vm1 ~]$ rman target /

Recovery Manager: Release 12.1.0.2.0 - Production on Thu Feb 26 17:43:27 2015

Copyright (c) 1982, 2014, Oracle and/or its affiliates.  All rights reserved.

connected to target database: DB121 (DBID=120781903)

RMAN> show all;

using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name DB121 are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
..
.
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/12.1.0/dbhome_1/dbs/snapcf_db1211.f'; # default

RMAN> configure archivelog deletion policy to applied on standby;

old RMAN configuration parameters:
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
new RMAN configuration parameters:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
new RMAN configuration parameters are successfully stored
 





How resign from you company



Dear Hr

This is Salmon windy, Designation: Junior Database Administrator Department: Software Working Station: Achopal ceramic  USA.

Please accept this letter as formal notification that I am leaving and resigning my position Junior Database Administrator with Spectrum Ltd on 31 January, 2017
Please let me know If Have any assistance during this transition.

Sincerely Yours
Salmon windy

Tuesday, January 10, 2017

How to Clear Cache in Linux | Redhat | Centos

Many times systems faced low memory issues of Linux systems running a while. The reason is that Linux uses so much memory for disk cache is because the RAM is wasted, if it isn’t used. Cache is used to keep data to use frequently by operating system. Reading data from cache if 1000’s time faster than reading data from hard drive.
It’s good for os to get data from cache in memory. But if any data not found in the cache, it reads from hard disk. So it’s no problem to flush cache memory. This article has details about how to Flush Memory Cache on Linux Server.
Clear Linux Memory Buffer Cache:









There are three options available to flush cache of Linux memory. Use one of below as per your requirements.

What Is Sync;

 means sync - synchronize data on disk with memory .

    Free pagecache, dentries and inodes in cache memory in Linux machine

    # sync; echo 3 > /proc/sys/vm/drop_caches

    Free dentries and inodes use following command

    # sync; echo 2 > /proc/sys/vm/drop_caches

    Free pagecache only use following command

    # sync; echo 1 > /proc/sys/vm/drop_caches

Schedule Cron to Flush Cache Regularly
This is very good idea if  schedule following command  in crontab to automatically flush cache on regular interval.

# crontab -l
#crontab -e

 


0 * * *  * sync; echo 3 > /proc/sys/vm/drop_caches

# /etc/init.d/crond restart

The above cron will execute on every hour and flushes the cached memory on system.
Find Cache Memory uses in Linux

Use free command to find out cache memory uses by Linux system. Output of free command is below :   Free -g

Last column is showing cached memory ( 14953 MB) by system. -m option is used for showing memory details in MB’s.