Home » RDBMS Server » Networking and Gateways » LISTENER BLOCKED the instance during nomount state (oracle 11.2.0.4 ,11.2.0.1RHEL6.5)
LISTENER BLOCKED the instance during nomount state [message #663841] Wed, 21 June 2017 06:08 Go to next message
arin.oradba
Messages: 33
Registered: January 2016
Location: Kolkata
Member
My requirement:
Listener should be READY in nomount state.


I want to create oracle data guard .
All the configuration I have completed.

$ rman TARGET sys/oracle@ORDB  AUXILIARY sys/oracle@ORDBSTD

Recovery Manager: Release 11.2.0.4.0 - Production on Wed Jun 21 16:05:24 2017

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

connected to target database: ORDB (DBID=537097026)
connected to auxiliary database: ORDBSTD (DBID=537905435, not open)


Now ORDBSTD database is in mount state.
so listener status is shown READY
Instance "ORDBSTD", status READY, has 1 handler(s) for this service...

But when ORDBSTD database is in nomount state, listener blocked the instances.
Instance "ORDBSTD", status BLOCKED, has 1 handler(s) for this service...

I am giving the following information for your convenince.

Listener.ora
LISTENER =
 (DESCRIPTION_LIST =
   (DESCRIPTION =
     (ADDRESS = (PROTOCOL = TCP)(HOST = ordb01.magma.co.in)(PORT = 1521))
     (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
   )
 )

SID_LIST_LISTENER =
  (SID_LIST =
   (SID_DESC =
     (ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1/)
     (SID_NAME = ORDBSTD)
     (UR=A)
     (GLOBAL_DBNAME = ORDBS)
    )
  )

tnsname.ora

ORDBSTD =
  (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 182.100.4.204)(PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = ORDBSTD)
      (UR=A)
    )
  )


ORACLE_SID=ORDBSTD
DB_NAME=ORDBS
GLOBAL_NAME=ORDBS


Please help me to solve the problem.
Re: LISTENER BLOCKED the instance during nomount state [message #663842 is a reply to message #663841] Wed, 21 June 2017 06:14 Go to previous messageGo to next message
John Watson
Messages: 8919
Registered: January 2010
Location: Global Village
Senior Member
You have made mistakes. For example:
It appears that your target and auxiliary have different database names. They must be the same.
Your auxiliary is mounted. It must be nomount.
You have UR=A in the both listener.ora and tnsnames.ora

What document are you following?

[Updated on: Wed, 21 June 2017 06:16]

Report message to a moderator

Re: LISTENER BLOCKED the instance during nomount state [message #663849 is a reply to message #663842] Wed, 21 June 2017 06:59 Go to previous messageGo to next message
arin.oradba
Messages: 33
Registered: January 2016
Location: Kolkata
Member
target and auxiliary can have different database names. Because at the time of Duplication of target database,it wll use backup contrlfile for standby and auxiliary is in nomount state.

In my case,listener block the auxiliary instance at nomount state.
I have include later UR=A in both listener.ora and tnsnames.ora one by one for research purpose.but it has no effect.
Re: LISTENER BLOCKED the instance during nomount state [message #663852 is a reply to message #663849] Wed, 21 June 2017 07:18 Go to previous messageGo to next message
John Watson
Messages: 8919
Registered: January 2010
Location: Global Village
Senior Member
You really need to do some reading if you think that primary and standby can have different DB names. You are also mistaken if you think that your auxiliary is in nomount mode. It isn't. How do I know? Because RMAN is reporting its DBID. The DBID is stored in the controlfile, you know. That database is mounted.

It seems that you have not read the Data Guard docs. Better do that before you waste more time.
Re: LISTENER BLOCKED the instance during nomount state [message #663874 is a reply to message #663852] Thu, 22 June 2017 06:40 Go to previous messageGo to next message
arin.oradba
Messages: 33
Registered: January 2016
Location: Kolkata
Member
Yes sir , I know that database is mounted. But During my testing period, it was in nomount state. Later when it fails due to listener blocked the instance,I will bring the database in mount state.


Sorry I mean db_unique_name, not db name.
I have include later UR=A in both listener.ora and tnsnames.ora one by one for research purpose.but it has no effect.
Now I have excluded UR=A from both file.


please help me regarding the problem.

LISTENER BLOCKED the instance during nomount state.


Thank you for your co-operation sir.


[Updated on: Thu, 22 June 2017 06:44]

Report message to a moderator

Re: LISTENER BLOCKED the instance during nomount state [message #663876 is a reply to message #663874] Thu, 22 June 2017 07:05 Go to previous messageGo to next message
John Watson
Messages: 8919
Registered: January 2010
Location: Global Village
Senior Member
Quote:
What document are you following?
Re: LISTENER BLOCKED the instance during nomount state [message #663933 is a reply to message #663876] Tue, 27 June 2017 01:13 Go to previous messageGo to next message
arin.oradba
Messages: 33
Registered: January 2016
Location: Kolkata
Member
ORACLE 11G DATA GUARD BOOK
Re: LISTENER BLOCKED the instance during nomount state [message #663934 is a reply to message #663933] Tue, 27 June 2017 01:18 Go to previous messageGo to next message
John Watson
Messages: 8919
Registered: January 2010
Location: Global Village
Senior Member
What book is that? Does it have a name and an author?
Re: LISTENER BLOCKED the instance during nomount state [message #663936 is a reply to message #663934] Tue, 27 June 2017 01:27 Go to previous messageGo to next message
Michel Cadot
Messages: 68618
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

... a link?

Re: LISTENER BLOCKED the instance during nomount state [message #663939 is a reply to message #663933] Tue, 27 June 2017 03:51 Go to previous message
gazzag
Messages: 1116
Registered: November 2010
Location: Bedwas, UK
Senior Member
This one?
Previous Topic: TNS Packet Length
Next Topic: Lsnrctl stop -> database crashes
Goto Forum:
  


Current Time: Tue Mar 19 05:22:09 CDT 2024