1 / 7

RAC Networking Lab

RAC Networking Lab. 1. Edit your tnsnames.ora file. In notepad or wordpad, open the file C:oracleproduct10.2.0db_1NETWORKADMINtnsnames.ora For the Service name you created at install time, review the settings for TAF. Add the “(ENABLE = BROKEN)” line below the Description line

gad
Télécharger la présentation

RAC Networking Lab

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RAC Networking Lab

  2. 1. Edit your tnsnames.ora file • In notepad or wordpad, open the file C:\oracle\product\10.2.0\db_1\NETWORK\ADMIN\tnsnames.ora • For the Service name you created at install time, review the settings for TAF. • Add the “(ENABLE = BROKEN)” line below the Description line • Edit on both cluster nodes • Test your ability to login to the database with sqlplus (on the server) using your service name, i.e. • sqlplus system@MSnDB • sqlplus system@MSnDB1 • Sqlplus system@MSnDB_SVC

  3. 2. Test TAF Failover • Open two Command Prompt windows • In the first window, log into sqlplus with the service name, i.e • Sqlplus system@MSnDB_SVC • Run the following query: • Select instance_name from v$instance; • In the other window, shut down the instance shown in the query result • Srvctl stop instance –d MSnDB –i MSnDB1 • Repeat the query in the sqlplus session • The instance should have changed

  4. 2. Test TAF Failover • Optional - • Restart all instances • Repeat the exercise, but this time reboot the node of the instance in the query • TCP/IP registry parameters may have to be edited for optimal failover time.

  5. 3. Client Networking • Locate your client (desktop) tnsnames.ora file • Copy in the contents of your server side tnsnames.ora file • Omit the local and remote listener lines • Test connectivity to your database • Test TAF failover from the client • Edit the client tnsnames.ora file to add access to a different class database • Test connectivity to the alternate database

  6. 4. Networking Monitoring Demo • Your instructor will demonstrate using ttcp to test network throughput for the private interconnect

  7. © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

More Related