ASM LOCAL_LISTENER using incorrect port after GIPSU was installed
(Doc ID 2201573.1)
Last updated on AUGUST 29, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.2 to 12.1.0.2 [Release 12.1]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
o The issue has been seen after installing 12.1.0.2.160119 GIPSU (Jan-2016) or 12.1.0.2.160719 GIPSU (Jul-2016). But the issue even can happen on 12.1.0.2.161018 GIPSU (Oct-2016).
o The agent is changing the value for LOCAL_LISTENER from port 1521, where the node listener is running (ora.LISTENER.lsnr), to port 1522, where the ASM listener is running (ora.ASMNET1LSNR_ASM.lsnr)
o The alert for ASM showes around the same time:
ALTER SYSTEM SET local_listener='(ADDRESS=(PROTOCOL=TCP)(HOST=<node IP>)(PORT=1522))' SCOPE=MEMORY SID='+ASM1';
o This is a Flex ASM configuration, where we have ASM listeners running (e.g. ora.ASMNET1LSNR_ASM.lsnr)
o On this issue, the cluster have two networks used for interconnect and ASM, like:
eth0 <public subnet> global public
eth1 <interconnect subnet 1> global cluster_interconnect,asm
eth2 <interconnect subnet 2> global cluster_interconnect,asm
Changes
Applied the GIPSU.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |