Yesterday, colleagues said there is a set of RAC cluster customer requirements to modify the database listening port, in the process of processing, found that the relevant information on the Internet is not very comprehensive, so tidy up a bit, I hope to other needy friends to provide a bit of favorable reference. The procedure is as follows:--Modify the port information saved in configuration information using a grid user to modify Srvctl modify Listener-l listener-p 15210
Srvctl Modify Scan_listener-p 15210--Modify the local monitoring and scan listening ports to log on as an Oracle user, performing the following modifications: Alter system set local_listener= ' (DESCRIPTION = (address_list= (address= (protocol=tcp) (host=10.100.8.94) (port=15210))) ' Scope=both sid= ' DB1 '; alter system set Local_listener= ' (description= (address_list= (address= (protocol=tcp) (host=10.100.8.96) (PORT=15210))) ' Scope=both Sid= ' DB2 ';alter system set remote_listener= ' gisscan:15210 ' Scope=bothsid= ' db1 '; alter system set remote_listener= ' gisscan:15210 ' Scope=bothsid= ' DB2 '; Log in as a grid user and perform the following modifications: Alter system set local_listener= ' (Description= (address_list= (address= (protocol=tcp) (host= 10.100.8.94) (port=15210))) ' Scope=both sid= ' +ASM1 '; alter system set Local_listener= ' (Description= (address_list= ( Address= (PROTOCOL=TCP) (host=10.100.8.96) (port=15210))) ' Scope=both sid= ' +asm2 ';alter system set remote_listener= ' gisscan:15210 ' Scope=bothsid= '+asm1'; alter system set remote_listener= ' gisscan:15210 ' Scope=bothsid= '+asm2'; Srvctl Stop Listener
Srvctl Start Listener
Srvctl Stop Scan_listener
Srvctl Start Scan_listener