Clarification on Data Guard Broker Config Files in ASM
(Doc ID 1508241.1)
Last updated on APRIL 03, 2020
Applies to:Oracle Database - Enterprise Edition - Version 184.108.40.206 to 220.127.116.11 [Release 11.2]
Oracle Database Cloud Schema 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.
GI 18.104.22.168.4 + ASM + RAC One Node 22.214.171.124.4 for RHEL6.3 (x86_64)
Created a Data Guard Broker Configuration and it works fine.
Here are the Steps:
1. Created Directories using asmcmd:
"DATAGUARDCONFIG" has not been created manually.
So what are "DATAGUARDCONFIG/tb19.424.798731653" and "DATAGUARDCONFIG/tb19.1324.798731653" files for ?
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