Redo Log Files Created With File Names Broken[x] While Creating Active Standby Database
(Doc ID 3044641.1)
Last updated on SEPTEMBER 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 19.0.0.0 and laterOracle Cloud Infrastructure - Exadata Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Gen 2 Exadata Cloud at Customer - Version N/A and later
Information in this document applies to any platform.
Symptoms
Creating a standby database using active duplicate for standby option creates redo log files with file names broken[x] when the source and destination databases have the same filesystem structure and they are not
using OMF.
Changes
Executing the duplicate for standby using the below statement using nofilenamecheck as shown below.
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |