My Oracle Support Banner

RMAN Recover Table Against Application PDB Fails By ORA-65054 (Doc ID 3017417.1)

Last updated on AUGUST 04, 2024

Applies to:

Oracle Database - Enterprise Edition - Version 19.3.0.0.0 and later
Information in this document applies to any platform.

Symptoms

RMAN "RECOVER TABLE" OR "RECOVER TABLESPACE" command fails by ORA-65054 when target table/tablespace is creted on application pdb of multitenant database.

RMAN> recover table <schema>."<TABLE>" of pluggable database <Application PDB> until scn <recovery SCN>;
 :
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at <Date>
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of sql command on clone_default channel at <Date>
RMAN-11003: failure during parse/execution of SQL statement: alter pluggable database  <Application Root>, <Application PDB> open
ORA-65054: Cannot open a pluggable database in the desired mode.

When this problem reproduces, "CREATE SMALLFILE UNDO TABLESPCE" on auxiliary instance fails by ORA-1552.

* alert.log of auxiliary instance

2023-10-16T13:41:17.142756+09:00
<Appplication Root>(5):Opening pdb with no Resource Manager plan active
<Appplication Root>(5):CREATE SMALLFILE UNDO TABLESPACE undo_1 DATAFILE  SIZE 104857600 AUTOEXTEND ON NEXT 5242880 MAXSIZE 34359721984 ONLINE
2023-10-16T13:41:19.080039+09:00
<Appplication Root>(5):ORA-1552 signalled during: CREATE SMALLFILE UNDO TABLESPACE undo_1 DATAFILE  SIZE 104857600 AUTOEXTEND ON NEXT 5242880 MAXSIZE 34359721984 ONLINE...
2023-10-16T13:41:19.080210+09:00
<Appplication Root>(5):Automatic creation of undo tablespace failed with error 604 1552
Pluggable database <Appplication Root> opened read write
ORA-65054 signalled during: alter pluggable database  <Appplication Root>, <Application PDB> open...
Shutting down ORACLE instance (abort) (OS id: 6887)



Changes

This problem reproduces when following all conditions are sastified.

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.