Create Static Listener SI _ RAC Duplication.pdf

How to Create Static Listener for Duplicating Database
VS
Using UR=A to Connect to Oracle Databases in Nomount/Restricted Mode:
Alireza Kamrani
12/08/2024
Problem:
Refreshing a database from production to test/uat using rman duplicate method.
On Test server listener blocked with service name
SQL> startup nomount;
the service on the listener would have a blocked status.
Service "orcldb" has 1 instance(s).
Instance "orcldb", status BLOCKED, has 1 handler(s) for this service...
Any attempt to connect to the instance using service name will fail.
$ sqlplus sys@orcldb as sysdba
SQL*Plus: Release 19.0.0.0.0 - Production on Sat Dec13 23:27:09 2024
Version 19.12.0.0.0
ERROR:
ORA-12528:
TNS:listener: all appropriate instances are blocking new connections
The TNS entry used is shown below.

ORCLDB =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = MyIP)(PORT = 1525))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = orcldb)
)
)
One solution is to create a static listener entries as done when creating data guard
configurations.
Other options is to use UR=A in the TNS entry.
With the use of UR=A in TNS entry there's no need to create a static listener entry.
Dynamic listener would allow connection without any issue.
DEVDB =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = IP)(PORT = 1525))
(CONNECT_DATA =
(SERVICE_NAME = devcdb)
(UR = A)
)
)
After adding a (UR=A) parameter on tnsnames.ora and complete the refresh successfully.
Please note that the (UR=A) clause is intended to work with a dynamically registered handler so the
use of SERVICE_NAME versus SID is preferred.
Also this solution can works with RESTRICTED database.
UR=A stands for "User restricted = accepted". This means, that user are still able to connect to a
database in restricted mode.

Without this setting you will encounter the following error.
ORA-12526: TNS:listener: all appropriate instances are in restricted mode
Of course your user needs the RESTRICTED SESSION privilege.
How to Create Static Listener for Single instance And RAC:
1) Static Listener Registration Syntax for Stand-Alone Listener :
SID_LIST_listener_name_here=
(SID_LIST=
(SID_DESC=
(SID_NAME= <instance_name>)
==> The instance name which needs to appear on listener
(GLOBAL_DBNAME = <service_name> )
(ORACLE_HOME= <oracle home path>)
===> ORACLE_HOME path must be set correct.
)
)
SID_NAME = obtain the SID value from the INSTANCE_NAME parameter in the initialization
parameter file.
GLOBAL_DBNAME = The listener tries to match the value of this parameter with the value of the
SERVICE_NAME parameter in the client connect descriptor.
The value for this parameter is typically obtained from the combination of the DB_NAME and
DB_DOMAIN parameters (DB_NAME.DB_DOMAIN) in the initialization parameter file,
But the value can also contain any valid name used by clients to identify the service.
2) Static Listener Registration Syntax for RAC Listener :
SID_LIST_listener_name_here=
(SID_LIST=
(SID_DESC=
(GLOBAL_DBNAME=<db_unique_name>) ===> The service name which needs to appear on

(GLOBAL_DBNAME=<db_unique_name>) ===> The service name which needs to appear on
listener
(ORACLE_HOME= <oracle_home path>)
(SID_NAME=<sid_name_1>))
===> The instance name which needs to appear on listener
(SID_DESC=
(GLOBAL_DBNAME=<db_unique_name>)
(ORACLE_HOME=<oracle_home path>)
(SID_NAME=<sid_name_2>)
)
)
For RAC One Node databases the SID_LIST entries in the listener.ora files on each possible host
must each contain two SID_DESC clauses, one for each of the SID_NAME values that correspond to
the two possible RAC One Node instances.
3) Static Listener Registration Syntax on a Primary , Standby Database for shipping
logs :
Primary :
Unique name is decided updated in pfile :
db_unique_name=orcl_p
Update Listener with static entry Listener.ora file :
SID_LIST_listener_name_here =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = orcl_p)
===> db_unique_name on Primary db (ORACLE_HOME = /u01/app/oracle/product/12.2.0/db_1)
(SID_NAME = orcl)
===> Instance_name in Primary db
)
)

Standby:
Unique name is decided updated in pfile :
db_unique_name=orcl_s
Update Listener with static entry :
SID_LIST_listener_name_here =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = orcl_s)
===> db_unique_name on Standby db
(ORACLE_HOME = /u01/app/oracle/product/12.2.0/db_1)
(SID_NAME = orcls)
===> Instance_name in Standby db
)
)
How to Add a Static Listener on Public IP for A Local RAC Instance
Example used in this document:
Cluster nodes: node1, node2
VIP listener port: 1521
Static listener name: LSNR1010 port: 1530
Oracle database 12c above.
Note: The following procedure also applies for an individually created single instance database on a
RAC node.
Solution 1: Configure a static listener from GI Home which can be started during GI startup
Steps:
1. Add the following to listener.ora in
<Grid Home>/network/admin

LSNR1010=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(protocol=tcp)(host=<node public IP>)
(port=1530))))
SID_LIST_LSNR1010 =
(SID_DESC =
(GLOBAL_DBNAME = <Name for client to connect>)
(ORACLE_HOME = <RDBMS Home>)
(SID_NAME = <DB instance name>)
)
2. As 'grid' user
$ srvctl add listener -listener lsnr1010 -netnum 1 -endpoints "1530"
3. Take note of the original start and stop dependencies
$ crsctl stat res ora.LSNR1010.lsnr -f |grep -F 'DEPENDENCIES='
4. Adjust clusterware resource dependencies
$ crsctl modify res ora.LSNR1010.lsnr -attr "START_DEPENDENCIES=hard(ora.net1.network)
pullup(ora.net1.network)" -unsupported
5. Disable the listener for remote node(s) since it is planning to run it only on one node
$ srvctl disable listener -listener lsnr1010 -node <remote node name, Ex, 'node2'>
6. TNS client configuration contains
<Tns name 1> =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = <node public IP>)(PORT = 1530))
(CONNECT_DATA =
(SERVICE_NAME = <Name for client to connect>)
)
)

)
7. Optionally, if you have a second public network that the node also has an IP on it, and you want
the static listener is running on that public IP instead of the public IP used for Grid Infrastructure
cluster node, then you can now
1) Modify listener.ora in <Grid Home>/network/admin
LSNR1010=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(protocol=tcp)(host=<the IP on the
second public network>)(port=1530))))
SID_LIST_LSNR1010 =
(SID_DESC =
)
2) Modify TNS client configuration
<Tns name 1> =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = <the IP on the second public network>)(PORT =
1530))
(CONNECT_DATA =
)
)
The method to start / stop the listener is:
As 'grid' user
$ srvctl start listener -listener lsnr1010
$ srvctl stop listener -listener lsnr1010
Solution 2: Configure a static listener from database Home which can only be started manually

Solution 2: Configure a static listener from database Home which can only be started manually
Enter into RDBMS home and create/modify listener.ora under <RAC RDBMS Home>/network/admin
to add the static listener with its port different from GI VIP listener.
Example:
On Server side:
File listener.ora contains:
LSNR4170 =
(DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (protocol=tcp)(host = <node public IP>)(port =
1530))))
SID_LIST_LSNR4170 =
(SID_DESC =
)
As RDBMS owner, start the listener by command:
$ lsnrctl start lsnr4170
On Client side:
File tnsnames.ora contains
<Tns name 2> =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = <node public IP>)(PORT = 1530))
(CONNECT_DATA =
)
)

To establish connection:
$ sqlplus system/<password>@<Tns name 2>
.
.
Connected to:
Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production
Note: Whatever in solution 1 or solution 2, the value of SERVICE_NAME in client TNS string must
match the value of GLOBAL_DBNAME in listener.ora, else connection will fail with:
ORA-12514: TNS:listener does not currently know of service requested in connect
descriptor
Alireza Kamrani.

Create Static Listener SI _ RAC Duplication.pdf

More Related Content

Similar to Create Static Listener SI _ RAC Duplication.pdf (20)

More from Alireza Kamrani (20)

Recently uploaded (20)

Create Static Listener SI _ RAC Duplication.pdf