Agent unable to identify state of the ASMDG resource - ORA-00020: maximum number of processes (100) exceeded .

Issue :-
Agent unable to identify state of the ASMDG resource. . The asm_diskstring parameter is not set correctly in the ASM initialization parameter file. (3)

Not able to connect to ASM 

oracle@server1$sqlplus "/ as sysdba"

SQL*Plus: Release 11.2.0.2.0 Production on Wed Sep 6 15:38:30 2017

Copyright (c) 1982, 2010, Oracle.  All rights reserved.

ERROR:

ORA-00020: maximum number of processes (100) exceeded

 Enter user-name:

Solution 1: 

Step 1 :- If you try to connect to ASM then below error will pop up  

oracle@server1$sqlplus "/ as sysdba"

SQL*Plus: Release 11.2.0.2.0 Production on Wed Sep 6 15:38:30 2017

Copyright (c) 1982, 2010, Oracle.  All rights reserved.

ERROR:

ORA-00020: maximum number of processes (100) exceeded

 Enter user-name:

Step 2 :- check ASM session

ps -ef | grep -i LOCAL=YES | grep -i asm

oracle 27154 9375 0 Jul 18 ? 0:00 oracle+ASM (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq))) 
oracle 28021 9375 0 Jul 07 ? 0:00 oracle+ASM (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq))) 
oracle 5515 9375 0 Jul 08 ? 0:00 oracle+ASM (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq))) 
oracle 22722 9375 0 Jul 15 ? 0:00 oracle+ASM (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq))) 
oracle 927 9375 0 Sep 01 ? 0:00 oracle+ASM (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq))) 
oracle 7843 9375 0 Jul 19 ? 0:00 oracle+ASM (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq))) 
oracle 6962 9375 0 Jul 01 ? 0:00 oracle+ASM (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq))) 
oracle 17643 9375 0 Jul 18 ? 0:00 oracle+ASM (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq))) 
oracle 6163 9375 0 15:40:13 ? 0:00 oracle+ASM (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq))) 
oracle 27152 9375 0 Jul 18 ? 0:00 oracle+ASM (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq))) 
oracle 84 9375 0 Aug 13 ? 0:00 oracle+ASM (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq))) 

Step 3 :- you can try to reduce some session by removing Above old processes without impacting ASM

oracle@server1$ kill -9 27154 28021 5515 

*********************************************************************************************************************

Solution 2:- 

Perform below as planned activity with proper downtime

Increase the Maximum Number of Processes in the Database with the SQL below :

1. Connect database as sysdba user

SQL> conn / as sysdba

2. Increase maximum number of database process 

SQL> alter system set processes=250 scope=spfile;    // set processes as per capacity of server/DB 

3. Restart DB to take effect.

4. Retest the issue.