Mantieni tutto organizzato con le raccolte
Salva e classifica i contenuti in base alle tue preferenze.
Configura il nome di accesso per client singolo con Cloud DNS
Puoi accedere a un cluster Oracle® Real Application Clusters (RAC) tramite un nome DNS ad alta disponibilità fornito da Cloud DNS.
Ciò si ottiene indirizzando la voce DNS a un nome di accesso per client singolo (SCAN) RAC, che rimane persistente man mano che la topologia del cluster cambia.
Prima di iniziare
Per completare questa guida, devi disporre dell'accesso alle seguenti risorse e ai seguenti servizi:
Il seguente diagramma mostra l'architettura di sistema utilizzata in questa guida:
Configura Cloud DNS in modo che rimandi al cluster RAC
Per configurare l'accesso con un singolo nome DNS al cluster RAC, completa i seguenti passaggi:
Se non hai mai eseguito Google Cloud CLI, devi eseguire il seguente comando per specificare il nome del progetto e autenticarti con la Google Cloud console:
Configura ogni server Bare Metal Solution in modo che utilizzi l'indirizzo IP del
passaggio precedente per la risoluzione dei nomi. I passaggi sono specifici per il tuo sistema operativo.
Ad esempio, per configurare la risoluzione dei nomi in Red Hat Enterprise Linux 8:
Un nuovo nome di zona per identificare la zona nei comandi di configurazione.
Una descrizione della tua zona per definirne meglio lo scopo.
Il suffisso del nome DNS per la tua zona, ad esempio mycompany.internal. Deve corrispondere al suffisso del nome SCAN restituito nel comando srvctl config scan precedente.
La rete VPC a cui deve essere visibile la zona DNS privata.
[[["Facile da capire","easyToUnderstand","thumb-up"],["Il problema è stato risolto","solvedMyProblem","thumb-up"],["Altra","otherUp","thumb-up"]],[["Difficile da capire","hardToUnderstand","thumb-down"],["Informazioni o codice di esempio errati","incorrectInformationOrSampleCode","thumb-down"],["Mancano le informazioni o gli esempi di cui ho bisogno","missingTheInformationSamplesINeed","thumb-down"],["Problema di traduzione","translationIssue","thumb-down"],["Altra","otherDown","thumb-down"]],["Ultimo aggiornamento 2025-09-04 UTC."],[[["\u003cp\u003eCloud DNS allows access to an Oracle RAC cluster via a highly-available DNS name that is pointed to a persistent Single Client Access Name (SCAN).\u003c/p\u003e\n"],["\u003cp\u003eSetting up Cloud DNS for a RAC cluster involves configuring an inbound server policy, setting the correct entry point IP address on Bare Metal Solution servers, and setting up Cloud DNS for private Google Access.\u003c/p\u003e\n"],["\u003cp\u003eTo configure the RAC cluster's DNS name, a private zone must be created in Cloud DNS matching the SCAN name's suffix, and an "A" record with the SCAN IPs must be added to that zone.\u003c/p\u003e\n"],["\u003cp\u003eTo verify the success of the configuration, use the \u003ccode\u003enslookup\u003c/code\u003e command on the Bare Metal Solution server to ensure the SCAN name correctly resolves to the associated SCAN IPs.\u003c/p\u003e\n"]]],[],null,["# Configure Single Client Access Name with Cloud DNS\n==================================================\n\nYou can access an Oracle® Real Application Clusters (RAC) cluster via a\nhighly-available DNS name provided by [Cloud DNS](https://cloud.google.com/dns).\nThis is achieved by pointing the DNS entry at a RAC\n[Single Client Access Name (SCAN)](https://www.oracle.com/jp/a/tech/docs/technical-resources/single-client-access-name.pdf),\nwhich stays persistent as cluster topology changes.\n| **Note:** Customers are responsible for procuring licenses for the Oracle workloads they choose to run on Bare Metal Solution, and customers are responsible for complying with those licenses. Google does not provide licenses for Oracle workloads.\n\nBefore you begin\n----------------\n\nYou need access to the following resources and services to complete this guide:\n\n- A [configured Bare Metal Solution server](/bare-metal/docs/bms-setup) that connects to a Google [Virtual Private Cloud (VPC)](https://cloud.google.com/vpc) via a [Partner Cloud Interconnect](https://cloud.google.com/network-connectivity/docs/interconnect).\n- A configured RAC cluster on the Bare Metal Solution server, with a SCAN listener active on each node.\n- [Cloud DNS](https://cloud.google.com/dns).\n\nSystem architecture\n-------------------\n\nThe following diagram shows the system architecture used in this guide:\n\nSet up Cloud DNS to point to your RAC cluster\n---------------------------------------------\n\nTo set up single DNS name access to your RAC cluster, complete the following steps:\n\n1. If you haven't run the [Google Cloud CLI](https://cloud.google.com/sdk/gcloud)\n previously, you must run the following command to specify your project name\n and authenticate with the Google Cloud console:\n\n gcloud auth login\n\n2. [Enable the Cloud DNS API](https://console.cloud.google.com/flows/enableapi?apiid=dns&credential=client_key)\n for your Google Cloud project.\n\n3. [Create an inbound server policy in Cloud DNS](https://cloud.google.com/dns/docs/policies#create-in)\n for the VPC connected to your Bare Metal Solution servers. This\n makes sure your Bare Metal Solution servers can communicate with Cloud DNS.\n\n4. [List the inbound forwarder entry points](https://cloud.google.com/dns/docs/policies#list-in-entrypoints)\n to determine the correct entry point IP address for each Bare Metal Solution\n server.\n\n5. Configure each Bare Metal Solution server to use the IP address from the previous\n step for name resolution. The steps involved are specific to your operating\n system.\n\n For example, to configure name resolution in Red Hat Enterprise Linux 8:\n 1. [Disable NetworkManager DNS processing](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_networking/manually-configuring-the-etc-resolv-conf-file_configuring-and-managing-networking).\n 2. Add the following line to `/etc/resolv.conf`, replacing\n \u003cvar translate=\"no\"\u003eENTRY_POINT_IP_ADDRESS\u003c/var\u003e with the entry point IP address:\n\n nameserver \u003cvar translate=\"no\"\u003eENTRY_POINT_IP_ADDRESS\u003c/var\u003e\n\n6. Configure [Cloud DNS for Private Google Access](/vpc/docs/configure-private-google-access#config-domain).\n\n7. Log into a Bare Metal Solution server that hosts a RAC database as the database\n user that was configured at install time.\n\n8. If you haven't set the `ORACLE_HOME` and `PATH` environment variable in your\n shell profile, set it now so you can connect to your database.\n\n9. Request the SCAN configuration with `srvctl` to find the SCAN name:\n\n srvctl config scan\n\n You should receive a response similar to the following example: \n\n SCAN name: cluster01-scan.mycompany.internal, Network: 1\n Subnet IPv4: /192.168.1.0/255.255.255.0/bond0.118, static\n Subnet IPv6:\n SCAN 1 IPv4 VIP: 192.168.1.30\n SCAN VIP is enabled\n SCAN 2 IPv4 VIP: 192.168.1.31\n SCAN VIP is enabled\n SCAN 3 IPv4 VIP: 192.168.1.32\n SCAN VIP is enabled\n\n The SCAN name in the previous response is\n `cluster01-scan.mycompany.internal`.\n10. [Create a private zone in Cloud DNS](/dns/docs/zones#create-private-zone),\n providing the following details:\n\n - A new zone name, to identify the zone in configuration commands.\n - A description for your zone, to better define its purpose.\n - The DNS name suffix for your zone, such as `mycompany.internal`. This should match the suffix of the SCAN name returned in the previous `srvctl config scan` command.\n - The VPC network that the private DNS zone should be visible to.\n11. [Add a record](/dns/docs/records#adding_a_record) to the previous zone,\n providing the following details:\n\n - The name of the zone you created in the previous step.\n - The full DNS name. In this guide, that's `cluster01-scan.mycompany.internal`.\n - The time to live (TTL). This is how long the DNS record is cached before it's refreshed.\n - The resource record type. For SCAN, this is an `A` record.\n - The SCAN IPs returned in the previous `srvctl config scan` command.\n\n Repeat this process for any additional names that need to be resolved.\n12. On the Bare Metal Solution server, validate that SCAN resolution is working with\n `nslookup`:\n\n nslookup cluster01-scan.mycompany.internal\n\n If successful, you should receive a response similar to the following\n example: \n\n Server: 10.158.0.3\n Address: 10.158.0.3#53\n\n Name: cluster01-scan.mycompany.internal\n Address: 192.168.1.32\n Name: cluster01-scan.mycompany.internal\n Address: 192.168.1.30\n Name: cluster01-scan.mycompany.internal\n Address: 192.168.1.31\n\nYou can now access your RAC cluster using a single, highly available, resilient\nDNS name via Cloud DNS.\n\n~Oracle is a registered trademark of Oracle and/or its affiliates.~"]]
