How to Modify Listener Ports on the Zero Data Loss Recovery Appliance

Asset ID:	1-71-2160047.1
Update Date:	2016-09-15
Keywords:

Solution Type Technical Instruction Sure

Solution 2160047.1 : How to Modify Listener Ports on the Zero Data Loss Recovery Appliance

Applies to:

Zero Data Loss Recovery Appliance X6 Hardware - Version All Versions to All Versions [Release All Releases]
Zero Data Loss Recovery Appliance X5 Hardware - Version All Versions to All Versions [Release All Releases]
Linux x86-64

Goal

Modify the listener ports on the Zero Data Loss Recovery Appliance post deployment.

Solution

Default port: 1521

Objective:
- Modify the ingest network listener port to 1721.

Procedure

Stop ra_server(As oracle)

Example:

[oracle@zdlra10adm01 ~]$ sqlplus rasys/ra;
SQL> exec dbms_ra.shutdown;

PL/SQL procedure successfully completed.

SQL>

Modify the listener

srvctl modify listener -l LISTENER -p 1721

Modify the scan_listener

srvctl modify scan_listener -p TCP:1721

Bounce the listener and scan_listener

[oracle@zdlra10adm01 ~]$ srvctl stop listener
[oracle@zdlra10adm01 ~]$ srvctl start listener
[oracle@zdlra10adm01 ~]$ srvctl stop scan_listener
[oracle@zdlra10adm01 ~]$ srvctl start scan_listener

Modify local listener

Note:

The HOST in the sqlplus statement below refers to the IP Address of the
ingest-vip of that host.
HOST=
- Node 1: zdlra10ingest01-vip => 192.133.62.75
- Node 2: zdlra10ingest02-vip => 192.133.62.76

Node 1:

SQL> alter system set
local_listener='(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=192.133.62.75)(PORT=1721))))'
scope=both sid='zdlra11';

Node 2:

SQL> alter system set
local_listener='(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=192.133.62.76)(PORT=1721))))'
scope=both sid='zdlra12';

Modify remote listener

Node 1:

SQL> alter system set remote_listener = 'zdlra10ingest-scan1:1721' SCOPE=BOTH SID='*';
System altered.
SQL>

SQL> exit

Edit tnsnames.ora (Both Compute nodes)

Node 1:

[oracle@zdlra10adm01 ~]$ cat
/u01/app/oracle/product/12.1.0.2/dbhome_1/network/admin/tnsnames.ora
# tnsnames.ora Network Configuration File:
# /u01/app/oracle/product/12.1.0.2/dbhome_1/network/admin/tnsnames.ora
# Generated by Oracle configuration tools.

zdlra1 =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = zdlra10ingest-scan1)(PORT = 1721))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = zdlra1)
)
)

[oracle@zdlra10adm01 ~]$

Node 2:

[oracle@zdlra10adm02 ~]$ cat
/u01/app/oracle/product/12.1.0.2/dbhome_1/network/admin/tnsnames.ora
# tnsnames.ora Network Configuration File:
# /u01/app/oracle/product/12.1.0.2/dbhome_1/network/admin/tnsnames.ora
# Generated by Oracle configuration tools.

zdlra1 =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = zdlra10ingest-scan1)(PORT = 1721))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = zdlra1)
)
)

[oracle@zdlra10adm02 ~]$

Stop OSB (As root user)

[root@zdlra10adm01 ~]# /u01/app/12.1.0.2/grid/bin/crsctl stop res osbadmin
CRS-2673: Attempting to stop 'osbadmin' on 'zdlra10adm01'
CRS-2677: Stop of 'osbadmin' on 'zdlra10adm01' succeeded

Stop DBFS (As root user)

[root@zdlra10adm01 ~]# /u01/app/12.1.0.2/grid/bin/crsctl stop res ob_dbfs rep_dbfs
CRS-2673: Attempting to stop 'ob_dbfs' on 'zdlra10adm02'
CRS-2673: Attempting to stop 'rep_dbfs' on 'zdlra10adm01'
CRS-2673: Attempting to stop 'ob_dbfs' on 'zdlra10adm01'
CRS-2673: Attempting to stop 'rep_dbfs' on 'zdlra10adm02'
CRS-2677: Stop of 'ob_dbfs' on 'zdlra10adm02' succeeded
CRS-2677: Stop of 'rep_dbfs' on 'zdlra10adm01' succeeded
CRS-2677: Stop of 'rep_dbfs' on 'zdlra10adm02' succeeded
CRS-2677: Stop of 'ob_dbfs' on 'zdlra10adm01' succeeded
[root@zdlra10adm01 ~]#

Stop the DB (As oracle user)

[oracle@zdlra10adm01 ~]$ srvctl stop database -d zdlra1

Start the DB (As oracle user)

[oracle@zdlra10adm01 ~]$ srvctl start database -d zdlra1

Start DBFS (As root user)

[root@zdlra10adm01 ~]# /u01/app/12.1.0.2/grid/bin/crsctl start res ob_dbfs rep_dbfs
CRS-2672: Attempting to start 'rep_dbfs' on 'zdlra10adm02'
CRS-2672: Attempting to start 'ob_dbfs' on 'zdlra10adm01'
CRS-2672: Attempting to start 'ob_dbfs' on 'zdlra10adm02'
CRS-2672: Attempting to start 'rep_dbfs' on 'zdlra10adm01'
CRS-2676: Start of 'rep_dbfs' on 'zdlra10adm02' succeeded
CRS-2676: Start of 'rep_dbfs' on 'zdlra10adm01' succeeded
CRS-2676: Start of 'ob_dbfs' on 'zdlra10adm01' succeeded
CRS-2676: Start of 'ob_dbfs' on 'zdlra10adm02' succeeded
[root@zdlra10adm01 ~]#

Start OSB

[root@zdlra10adm01 ~]# /u01/app/12.1.0.2/grid/bin/crsctl start res osbadmin

Start ra_server (As oracle user)

[oracle@zdlra10adm01 ~]$ sqlplus rasys/ra;
SQL> exec dbms_ra.startup;

PL/SQL procedure successfully completed.

SQL>

Validation

Run the following commands to validate that ports were modified: (As oracle user)

[oracle@zdlra10adm01 ~]$ srvctl config listener
[oracle@zdlra10adm01 ~]$ srvctl config scan_listener
[oracle@zdlra10adm01 ~]$ lsnrctl status

Login / as sysdba

[oracle@zdlra10adm01 ~]$ sqlplus / as sysdba

Confirm the local and remote listener ports have been modified

SQL> show parameter listener;

Instructions to Configure Enterprise Manager after changing the Recovery Appliance ingest ports by updating the Listener Ports

Cluster Target SCAN Ports

Update the cluster target's Monitoring Configuration-> SCAN Port

Find the cluster database associated with the Recovery Appliance.

This can be done from the Recovery Appliance home page by expanding the Target Navigation tree in the left pane and finding the cluster database target.

Go to the cluster database home page, click on the Information icon next to the target name, then click on the Cluster target name.
On the cluster home page menu, select Cluster -> Target Setup -> Monitoring Configuration
Update SCAN Port with the new value, then click Update.

Cluster Database Listener Ports

Update each instance of the RA cluster database's Monitoring Configuration->Port

Find the cluster database associated with the Recovery Appliance.

This can be done from the Recovery Appliance home page by expanding the Target Navigation tree in the left pane and finding the cluster database target.

Go to the cluster database home page.
On the cluster database home page menu, select Cluster Database -> Target Setup -> Monitoring Configuration
Under the Instances section, edit the properties of each instance by selecting each and clickin Edit.
Update Port with the new value, click Text Connection, then Save.
After all instances are updated, click Next, then Submit.

Zero Data Loss Recovery Appliance SCAN Ports

Update the RA's Monitoring Configuration-> Backup SCAN Port

On the Recovery Appliance home page menu, select Recovery Appliance -> Target Setup -> Monitoring Configuration
Update Backup SCAN Port with the new value, then click OK.

Listener targets may also need to have their ports updated.

Once the ports have been updated on the above components
go through each component of each of the Recovery Appliance host's agent and confirm all ports have been modified.
...if not change them as required.

Find all of the host associated with the Recovery Appliance.

This can be done from the Recovery Appliance home page by expanding the Target Navigation tree in the left pane and finding the compute node targets

Go to each host's home page
Click on the Information icon next to the target name
Then click on the agent target name.
In the Monitoring->Details-> Monitored Targets table, look for targets which are down.

Update the mgmt_rcvcat_config table's entry for the base catalog user and any vpc users, e.g.

1) Connect to the repository database

[oracle@EM_OMS_HOST~]$ORACLE_HOME/bin/sqlplus sysman/welcome1@$ORACLE_SID

2) Query the repository for the list of entries that must be modified

The database target name can be determined by looking at the value of $ORACLE_SID.

[oracle@zdlra10adm01 ~]$ echo $ORACLE_SID
zdlra11
[oracle@zdlra10adm01 ~]$

The last number (1) is the value of the instance and should be omitted in the SQLPlus statements below:

Database target name: zdlra1

SQL> select RCVCAT_GUID, RCVCAT_CONNECT_STR from mgmt_rcvcat_config where target_guid=(select target_guid from mgmt_targets where target_name='zdlra1' and target_type='rac_database');

3729838183F4738EE0530EF3850ABBA2
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=zdlra10ingest01-vip.us.or
acle.com)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=zdlra10ingest02-vip.us.oracle.c
om)(PORT=1721))(LOAD_BALANCE=yes))(CONNECT_DATA=(SERVICE_NAME=zdlra1)))

3729835CD5D8734EE0530EF3850AD3E9
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=zdlra10ingest01-vip.us.or
acle.com)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=zdlra10ingest02-vip.us.oracle.c
om)(PORT=1721))(LOAD_BALANCE=yes))(CONNECT_DATA=(SERVICE_NAME=zdlra1)))

Update the ports in the select statements

3) Update the port entries

SQL> update mgmt_rcvcat_config set
RCVCAT_CONNECT_STR=‘(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=zdlra10ingest01-vip.us.oracle.com)(PORT=1721))(ADDRESS=(PROTOCOL=TCP)(HOST=zdlra10ingest02-vip.us.oracle.com)(PORT=1721))(LOAD_BALANCE=yes))(CONNECT_DATA=(SERVICE_NAME=zdlra1)))’
where RCVCAT_GUID='3729838183F4738EE0530EF3850ABBA2';

SQL> update mgmt_rcvcat_config set
RCVCAT_CONNECT_STR='(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=zdlra10ingest01-vip.us.oracle.com)(PORT=1721))(ADDRESS=(PROTOCOL=TCP)(HOST=zdlra10ingest02-vip.us.oracle.com)(PORT=1721))(LOAD_BALANCE=yes))(CONNECT_DATA=(SERVICE_NAME=zdlra1)))'
where RCVCAT_GUID='3729835CD5D8734EE0530EF3850AD3E9';

SQL> commit;

On each protected client database:

The Recovery Appliance wallet in each protected database Oracle home (usually located in $ORACLE_HOME/dbs/zdlra) must be modifed as follows:

Note:
If there is a params file, it may have to get updated with the correct
port information.

Example:
[oracle@client_db_host dbs]$ cat radb1212sc.ora
RA_WALLET='LOCATION=file:/u01/app/oracle/product/12.1.0.2/dbhome_1/dbs/zdlra
CREDENTIAL_ALIAS=zdlra10ingest-scan1:1721/zdlra1:dedicated'
[oracle@client_db_host dbs]$

1. Remove old entries from the wallet:

First list the existing wallets
Then, remove the wallet associated with the scanname, port and username

[oracle@client_db_host ~]$ mkstore -wrl
file:/u01/app/oracle/product/12.1.0.2/dbhome_1/dbs/zdlra -listCredential
Oracle Secret Store Tool : Version 12.1.0.2
Copyright (c) 2004, 2014, Oracle and/or its affiliates. All rights reserved.

List credential (index: connect_string username)
2: zdlra10ingest-scan1:1721/zdlra1:dedicated ravpc1
1: zdlra10ingest-scan1:1521/zdlra1:dedicated ravpc1
[oracle@client_db_host ~]$

[oracle@client_db_host ~]$ mkstore -wrl file:/u01/app/oracle/product/12.1.0.2/dbhome_1/dbs/zdlra
-deleteCredential zdlra10ingest-scan1:1521/zdlra1b:dedicated ravpc1 <password>
Oracle Secret Store Tool : Version 12.1.0.2
Copyright (c) 2004, 2014, Oracle and/or its affiliates. All rights reserved.

Delete credential
Delete 1

[oracle@client_db_host ~]$

Reset the Protected Database Backup Configurations

2) In Enterprise Manager, clear and reset the Recovery Appliance backup configuration for the protected database as follows:

On the protected database home page menu, go to Availability->Backup and Recovery -> Backup Settings
In the Recovery Appliance Settings section, click Clear Configuration.
Reset the Recovery Appliance and Virtual Private Catalog User selections, then click Apply.
Once the Backup Configuration deployment procedure has successfully completed, click Test Backup to verify the settings.

Validate that Backup Works

Schedule/Run an immediate Backup

Test Restore

RMAN> restore database validate;

Starting restore at 11-JUL-16
allocated channel: ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: SID=1183 device type=SBT_TAPE
channel ORA_SBT_TAPE_1: RA Library (ZDLRA1B)
SID=37642956415759A7E0530AF3850A13D6
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=1232 device type=DISK

channel ORA_SBT_TAPE_1: starting validation of datafile backup set
channel ORA_SBT_TAPE_1: reading from backup piece VB$_2178808614_64893_1
channel ORA_SBT_TAPE_1: piece handle=VB$_2178808614_64893_1
tag=BACKUP_DB1212SC_SC_071116024003
channel ORA_SBT_TAPE_1: restored backup piece 1
channel ORA_SBT_TAPE_1: validation complete, elapsed time: 00:00:15
channel ORA_SBT_TAPE_1: starting validation of datafile backup set
channel ORA_SBT_TAPE_1: reading from backup piece VB$_2178808614_64893_3
channel ORA_SBT_TAPE_1: piece handle=VB$_2178808614_64893_3
tag=BACKUP_DB1212SC_SC_071116024003
channel ORA_SBT_TAPE_1: restored backup piece 1
channel ORA_SBT_TAPE_1: validation complete, elapsed time: 00:02:35
channel ORA_SBT_TAPE_1: starting validation of datafile backup set
channel ORA_SBT_TAPE_1: reading from backup piece VB$_2178808614_64893_4
channel ORA_SBT_TAPE_1: piece handle=VB$_2178808614_64893_4
tag=BACKUP_DB1212SC_SC_071116024003
channel ORA_SBT_TAPE_1: restored backup piece 1
channel ORA_SBT_TAPE_1: validation complete, elapsed time: 00:00:03
channel ORA_SBT_TAPE_1: starting validation of datafile backup set
channel ORA_SBT_TAPE_1: reading from backup piece VB$_2178808614_64893_5
channel ORA_SBT_TAPE_1: piece handle=VB$_2178808614_64893_5
tag=BACKUP_DB1212SC_SC_071116024003
channel ORA_SBT_TAPE_1: restored backup piece 1
channel ORA_SBT_TAPE_1: validation complete, elapsed time: 00:00:45
channel ORA_SBT_TAPE_1: starting validation of datafile backup set
channel ORA_SBT_TAPE_1: reading from backup piece VB$_2178808614_64893_6
channel ORA_SBT_TAPE_1: piece handle=VB$_2178808614_64893_6
tag=BACKUP_DB1212SC_SC_071116024003
channel ORA_SBT_TAPE_1: restored backup piece 1
channel ORA_SBT_TAPE_1: validation complete, elapsed time: 00:00:03
Finished restore at 11-JUL-16

RMAN>

Attachments

This solution has no attachment