CREATE PLUGGABLE DATABASE Using Standby CDB Fails W/ ORA-65342 (Doc ID 2479825.1)

Last updated on JULY 20, 2024

Applies to:

Symptoms

Cloning of production standby pluggable database into dev/staging environments by running the following steps:

1. Running "recover managed standby database cancel;" in the real-time apply standby database.
2. In dev/staging container:
create public database link <dblink_name> connect to <standby_database>;
alter pluggable database <dest_db> close abort instances=all;
drop pluggable database <dest_db> including datafiles;
create pluggable database <dest_db> from <db_name>@<dblink_name> <<<<<
alter pluggable database <dest_db> open instances=all;
3. Running "recover managed standby database using current logfile disconnect from session;" in the real-time apply standby database.

This was working reliably for over a year, but after the July 2018 QFSDP + Gi Upgrade to 12.2 was applied getting the error:
ERROR at line 1:
ORA-17628: Oracle error 65342 returned by remote Oracle server
ORA-65342: source pluggable database has unrecovered transaction

And a typical trace file message is:
pdb unplug failed transactional consistency check: pdbid=3, xid=145:11:119245, xsta=10, cfl=128, extfl=1
ORA-65342: source pluggable database <db_name> has unrecovered transaction

We did not see this error before July 2018 QFSDP was applied, but we've seen it 47 times after it was applied. 

Cause

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