NLS_NCHAR_CHARACTERSET Of Mounted Standby after Active Duplicate is Not Reflecting Correct Value
(Doc ID 2045443.1)
Last updated on MARCH 10, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.4 and laterOracle 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 Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
RMAN duplicate from active database does not change/update the NLS_NCHAR_CHARACTERSET parameter when the standby database is mounted.
Primary Database:
PARAMETER VALUE
-------------------------------------------------------------
NLS_CHARACTERSET UTF8
NLS_NCHAR_CHARACTERSET UTF8
Standby Database:
Before Duplicate:
PARAMETER VALUE
-------------------------------------------------------------------
NLS_CHARACTERSET US7ASCII
NLS_NCHAR_CHARACTERSET AL16UTF16
After Duplicate when standby is mounted:
PARAMETER VALUE
--------------------------------------------------------------------
NLS_CHARACTERSET UTF8
NLS_NCHAR_CHARACTERSET AL16UTF16
Before doing RMAN duplicate for Standby Db, the value of NLS_NCHAR_CHARACTERSET was set to AL16UTF16. Thus after the duplicate completes, the value remained the same when the standby database is mounted. Thus the RMAN duplicate is not setting the NLS_NCHAR_CHARACTERSET parameter value to that of the primary database.
Changes
Created physical standby database using rman duplicate from active database.
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 |