ERROR OGG-00868 Attaching to ASM server +ASM1: (12528) ORA-12528: TNS:listener: all appropriate instances are blocking new connections.

ERROR OGG-00868 Attaching to ASM server +ASM1: (12528) ORA-12528: TNS:listener: all appropriate instances are blocking new connections.

When the extract connects with the ASM instance to Read the data it get's this error due to the blocked connection in the  ASM instance Normally the ASM instance  is Blocked for the remote connectivity We need to add the parameter (UR=A) in the tnsnames.ora file for enabling the remote connection to the ASM instnace

Step 1

check the connectivity to the ASM by connecting the asm instance remotely

oraprod@db01[+ASM1]:$ sqlplus "sys/omoic@+asm1 as sysdba"
SQL*Plus: Release 10.2.0.3.0 - Production on Mon Jun 25 22:58:39 2013
Copyright (c) 1982, 2006, Oracle. All Rights Reserved.
ERROR:
ORA-12528: TNS:listener: all appropriate instances are blocking new connections

Navigate to the TNS_ADMIN and edit the tnsnames.ora file and add the parameter UR=A below the service name parameter

+ASM1 =
  (DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = <hostname>)(PORT = <port number>))
    )
    (CONNECT_DATA =
      (SERVICE_NAME = +ASM)
        (UR=A)
 ))

+ASM2 =
  (DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = <hostname>)(PORT = <port number>))
    )
    (CONNECT_DATA =
      (SERVICE_NAME = +ASM)
        (UR=A)
 ))

If we have Multiple ASM instance's then we need to add this parameter  in all the instance  refer the metalink note How to connect to ASM instance from a remote client (Doc ID 340277.1)

Step 2

Once the Parameter is added then we need to restart the listener services 

oracle@db01[PROD1]:$ lsnrctl reload LISTNER_DB01

oracle@db01[PROD2]:$ lsnrctl reload LISTNER_DB02

Step 3

Check the parameter Remote Log in password in the ASM instance if you have single asm instance it should be exclusive and it it is RAC environment you can use the shared for the password file

Move the existing Password file for the ASM into the new location and then create a new password file for the ASM instnace

oracle@db01[+ASM1]:$ orapwd file=orapw+ASM1 password=<password>

Once the new password file is created then use that password to connect remotely to the ASM instance  once by using the password you are able to connect the ASM instance then check the golden gate's process of extract