Shulou(Shulou.com)05/31 Report--

Editor to share with you how Oracle 11gr2 modifies the scan ip of RAC clusters and deals with ORA-12514 problems. I hope you will get something after reading this article. Let's discuss it together.

1. Check the status information of scanip grid@cwgsdb1:~$ srvctl config scanSCAN name: rac-scanip, Network: 1/100.100.100.0/255.255.255.0/ipmp0SCAN VIP name: scan1, IP: / rac-scanip/100.100.100.2192. Stop scan_listener, scangrid@cwgsdb1:~$ srvctl stop scan_listenergrid@cwgsdb1:~$ srvctl stop scan3. Confirm the status of scan_listener,scan

Grid@cwgsdb1:~$ srvctl status scan_listenerSCAN Listener LISTENER_SCAN1 is enabledSCAN listener LISTENER_SCAN1 is not runninggrid@cwgsdb1:~$ srvctl status scanSCAN VIP scan1 is enabledSCAN VIP scan1 is not runninggrid@cwgsdb1:~$ crs_stat-t | grep scanora.scan1.vip ora....ip.type OFFLINE OFFLINE grid@cwgsdb1:~$ crs_stat-t | grep lsnrora....ER.lsnr ora....er.type ONLINE ONLINE cwgsdb1 ora....N1.lsnr ora... .er.type OFFLINE OFFLINE ora....B1.lsnr application ONLINE ONLINE cwgsdb1 ora....B2.lsnr application ONLINE ONLINE cwgsdb24. Modify the iproot@cwgsdb1:~$ cat / etc/hosts## Copyright 2009 Sun Microsystems corresponding to scan in the / etc/hosts file of all nodes Inc. All rights reserved.# Use is subject to license terms.## Internet host table#::1 cwgsdb1 localhost 100.100.100.215 cwgsdb1 localhost loghost 100.100.100.216 cwgsdb2100.100.100.217 cwgsdb1-vip100.100.100.218 cwgsdb2-vip1.1.1.1 cwgsdb1-priv1.1.1.2 cwgsdb2-priv 100.100.100.219 rac-scaniproot@cwgsdb1:~$ vi / etc/hostsroot@cwgsdb1:~$ cat / etc/hosts## Copyright 2009 Sun Microsystems Inc. All rights reserved.# Use is subject to license terms.## Internet host table#::1 cwgsdb1 localhost 100.100.100.215 cwgsdb1 localhost loghost 100.100.100.216 cwgsdb2100.100.100.217 cwgsdb1-vip100.100.100.218 cwgsdb2-vip1.1.1.1 cwgsdb1-priv1.1.1.2 cwgsdb2-priv 100.100.100.103 rac-scanip5. Look at the folder where the srvctl command is located, grid@cwgsdb1:~$ cd $ORACLE_HOMEgrid@cwgsdb1:/u01/app/11.2.0/grid$ cd bin/grid@cwgsdb1:/u01/app/11.2.0/grid/bin$ pwd/u01/app/11.2.0/grid/bin6. Use the root command to modify scan-ip That is, modify to iproot@cwgsdb1:/u01/app/oracle/product/11.2.0/dbhome_1/bin# cd / u01/app/11.2.0/grid/binroot@cwgsdb1:/u01/app/11.2.0/grid/bin#. / srvctl modify scan- n rac-scaniproot@cwgsdb1:/u01/app/11.2.0/grid/bin#. / srvctl config scanSCAN name: rac-scanip corresponding to scan-ip in / etc/hosts Network: 1/100.100.100.0/255.255.255.0/ipmp0SCAN VIP name: scan1, IP: / rac-scanip/100.100.100.103

Note:-n is followed by the name of scan under / etc/hosts

7. Start scan_listener Scan and check the status root@cwgsdb1:/u01/app/11.2.0/grid/bin# su-gridOracle Corporation SunOS 5.11 11.3 September 2015gridholders cwgsdb1VR srvctl status scanSCAN VIP scan1 is enabledSCAN VIP scan1 is not runninggrid@cwgsdb1:~$ srvctl start scan_listenergrid@cwgsdb1:~$ srvctl start scanPRCC-1014: scan1 was already runningPRCR-1004: Resource ora.scan1.vip is already runningPRCR-1079: Failed to start resource ora.scan1.vipCRS-5702: Resource 'ora.scan1.vip' is already running On 'cwgsdb2' grid@cwgsdb1:~$ srvctl status scanSCAN VIP scan1 is enabledSCAN VIP scan1 is running on node cwgsdb2grid@cwgsdb1:~$ srvctl status scan_listenerSCAN Listener LISTENER_SCAN1 is enabledSCAN listener LISTENER_SCAN1 is running on node cwgsdb2grid@cwgsdb1:~$ srvctl config scanSCAN name: rac-scanip Network: 1/100.100.100.0/255.255.255.0/ipmp0SCAN VIP name: scan1, IP: / rac-scanip/100.100.100.1038. Test the connection using the new scan ip

Prompt ORA-12514 TNS:listener does not currently know of service requested in connect descriptor

Use the keyword "scan ip ORA-12514" to find a solution on MOS

Top Issues That Cause Troubles with SCAN VIP and Listeners (document ID 1373350.1)

Issue # 5: Service not getting registered with SCAN listener after failover of the SCAN listener

After SCAN VIP and SCAN listener failover, instance does not register with the SCAN listener. It might happen for only 1 of the scan listener. Client connection gets intermittent ORA-12514 TNS:listener does not currently know of service requested in connect descriptor.

Causes:1. Unpublished Bug 12659561 after scan listener failover, database instance might not register to the scan listener (refer Note 12659561.8), fixed in 11.2.0.3.2, merge patch 13354057 for 11.2.0.2 available for certain platform.

2. Unpublished Bug 13066936 Instance does not register services when scan fails over (refer Note 13066936.8)

Solutions:

1) For both above bugs, the workaround is to unregister and register remote listener on the database instance which does not register to a SCAN listener with following steps.

Show parameter remote_listener

Alter system set remote_listener=''

Alter system register

Alter system set remote_listener=':'

Alter system register

2) Other points to check if service is not registered with SCAN listener:

A. Remote_listener and local_listener is defined correctly

B. EZCONNECT is defined in sqlnet.ora, eg: NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)

C. SCAN name with 3 IPs should NOT be defined in / etc/hosts, it should be defined in DNS

D. Running nslookup multiple times should display SCAN VIP in round-robin fashion

E. do not set SECURE_REGISTER_ in listener.ora if the class of secure transports (COST) is not configured.

9. Try to restart each node listening, but the problem still exists oracle@cwgsdb2:~$ srvctl stop listener-n cwgsdb2oracle@cwgsdb2:~$ srvctl stop listener-n cwgsdb1oracle@cwgsdb2:~$ srvctl start listener-n cwgsdb1oracle@cwgsdb2:~$ srvctl start listener-n cwgsdb210. Solve this problem by modifying the remote_listener parameter and registering the database

SQL > show parameter remote NAME TYPE VALUE-- remote_dependencies_mode string TIMESTAMPremote_listener String rac-scanip:1521remote_login_passwordfile string EXCLUSIVEremote_os_authent boolean FALSEremote_os_roles boolean FALSEresult_cache_remote_expiration integer 0SQL > alter system set remote_listener='' System altered. SQL > alter system register; System altered. SQL > alter system set remote_listener='rac-scanip:1521'; System altered.

It has been verified that you can successfully connect to the database using the new scan ip. At this point, the scan ip modification is complete.

After reading this article, I believe you have some understanding of "how Oracle 11gr2 modifies the scan ip of RAC clusters and deals with ORA-12514 problems". If you want to know more about it, you are welcome to follow the industry information channel. Thank you for reading!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.