RMAN CLONE / DUPLICATE command failed with RMAN-06403 RMAN-04006 RMAN-04015 ORA-19710
(Doc ID 302922.1)
Last updated on DECEMBER 06, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 9.0.1.0 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 Backup Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
Recovery Manager: Release 9.2.0.1.0 - Production
Symptoms: printing stored script: Memory Script
Symptoms: {
Symptoms: shutdown clone;
Symptoms: startup clone nomount ;
Symptoms: }
Symptoms: executing script: Memory Script
Symptoms: database dismounted
Symptoms: Oracle instance shut down
Symptoms: connected to auxiliary database (not started)
Symptoms: Oracle instance started
Symptoms: RMAN-00571: ===========================================================
Symptoms: RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
Symptoms: RMAN-00571: ===========================================================
Symptoms: RMAN-03002: failure of Duplicate Db command at 03/15/2005 17:41:57
Symptoms: RMAN-03015: error occurred in stored script Memory Script
Symptoms: RMAN-06403: could not obtain a fully authorized session
Symptoms: RMAN-04006: error from auxiliary database: ORA-19710: unsupported character set
Symptoms: CL8ISO8859P5
Symptoms: RMAN-04015: error setting target database character set to CL8ISO8859P5
Changes
Specify a valid character set in the environment. This is usually done via the NLS_LANG environment variable.
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 |