My Oracle Support Banner

Grid Infrastructure Single Client Access Name (SCAN) Explained (Doc ID 887522.1)

Last updated on OCTOBER 30, 2019

Applies to:

Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud 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 Backup Service - Version N/A and later
Information in this document applies to any platform.

Purpose

11gR2 Grid Infrastructure (CRS) introduced Single Client Access Name (SCAN) to simplify client access to database services, this article is going to explain whats SCAN and how it works.

Scope

Intended audience will be DBAs who is installing/upgrading to 11gR2 Grid Infrastructure or support analyst who is supporting stated product.

Details

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
Purpose
Scope
Details
 SCAN Concepts
 Common Questions Regarding SCAN
 How can we configure the SCAN and SCAN listener?
 Do we still need to configure local listeners on each node?
 How does SCAN work ?
 Instead of DNS or GNS, Can we use '/etc/hosts' to resolve SCAN?
 Can we use the previous method (Using VIP) for client connection?
 Is it mandatory to use SCAN?
 Is it supported to remove SCAN?
 Is it recommended to use COST feature?
 Demo
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.