DBCA Silent Mode Is Not Setting DB_UNIQUE_NAME Even Though It Is Specified In DBCA Template File.
(Doc ID 1508337.1)
Last updated on JANUARY 09, 2025
Applies to:
Oracle Database Configuration Assistant - Version 11.2.0.3 and laterInformation in this document applies to any platform.
Symptoms
DBCA silent mode is not setting DB_UNIQUE_NAME even though it is specified in DBCA template file. The issue occurs both for standalone or RAC config.
After DBCA completes successfully, the DB_UNIQUE_NAME parameter has the same value as the DB_NAME parameter. This is not the expected result.
Example:
Note that DB_UNIQUE_NAME can be set after database creation.
However, this causes database and diagnostic dest files to show up in different directories after the DB_UNIQUE_NAME is set.
Changes
No changes. Just trying to use DBCA in silent mode and set the DB_UNIQUE_NAME in the used template.
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 |