How to Change 11.2 ASM Configuration to Match ASM Instance Name to the Node Where It Runs? (example, +ASM2 on Node2, etc)
(Doc ID 1419424.1)
Last updated on MARCH 09, 2024
Applies to:
Oracle Database Cloud Schema Service - Version N/A and laterGen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Goal
How to correct a Grid Infrastructure (GI) configuration where the ASM instance number does not match the node number where it runs? Example: +ASM2 is running on Node3 and +ASM3 is running on Node2
Need the steps to correct from this configuration so in the corrected environment the +ASM2 instance will be running on Node2 and the +ASM3 instance will be running on node3.
Solution
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
Goal |
Solution |
References |