"ORA-19715: invalid format b for generated name" when duplicate is attempted with set newname "..%b"
(Doc ID 2771480.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.2 and laterInformation in this document applies to any platform.
Symptoms
Error 19715 when all below are TRUE,
1. RMAN duplicate using recovery catalog
2. Intended duplicate site information exists in "list db_unique_name of database" commands output which is stale (most probably we see it as STANDBY). Please note that unless specified "db_unique_name" is same "db_name". Hence, <DB_NAME> we see in above duplicate command will be part of below listed command as <DB_UNIQUE_NAME_2>
$rman catalog <recovery catalog owner>/<password>@<tns string>
RMAN> set dbid <DBID>;
RMAN> list db_unique_name of database;
Example:
List of Databases
DB Key DB Name DB ID Database Role Db_unique_name
------- ------- ----------------- --------------- ------------------
<db_key_1> <DB_NAME> <DBID> PRIMARY <DB_UNIQUE_NAME_1>
<db_key_2> <DB_NAME> <DBID> STANDBY <DB_UNIQUE_NAME_2>
3. Clause "set newname" is used with format '%b'.
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 |
Cause |
Solution |