Home » Server Options » Data Guard » High number of DG slave processes on primary when link to standby is down (Oracle 10g - Solaris)
High number of DG slave processes on primary when link to standby is down [message #507340] Fri, 13 May 2011 15:25
malalation
Messages: 12
Registered: April 2011
Junior Member
Hello Guys,

I've noticed that when the link to secondary DB is down, the primary DB spawns a high number of dataguard slave processes (RSM0 and NSV0), this was clear from the alert log.

When querying primary:

select count(*) from v$process;


gives a very large number, and sometimes it hits the maximum number of processes specified in the initialization parameter called "processes".

I can only guess that these processes are trying to connect to the standby database, but when I checked the parameter LOG_ARCHIVE_DEST_STATE_2 is set to DEFER.

How can I disable such behavior 'till the link gets active again?
Previous Topic: How to delete archivelog in Standby Database when it is applied successfully
Next Topic: Rac Dataguard Gap Query
Goto Forum:
  


Current Time: Wed Aug 12 04:56:18 CDT 2020