Skip to Main Content
  • Questions
  • Error while cloning remote database using dblink: ORA-65345: cannot refresh pluggable database

Breadcrumb

more

Connor and Chris don't just spend all day on AskTOM. You can also catch regular content via Connor's blog and Chris's blog. Or if video is more your thing, check out Connor's latest video and Chris's latest video from their Youtube channels. And of course, keep up to date with AskTOM via the official twitter account.

Question and Answer

Chris Saxon

Thanks for the question, Krishna.

Asked: May 02, 2019 - 9:03 am UTC

Answered by: Chris Saxon - Last updated: May 02, 2019 - 1:48 pm UTC

Category: Database Administration - Version: 12.2.0

Viewed 1000+ times

Whilst you are here, check out some content from the AskTom team: On Rescue Analytics and Popularity

You Asked

create pluggable database test3 from test32@ttxtest_link1 parallel 8 refresh mode none create_file_dest ='/u02/app/oracle/oradata/test3/'
*
ERROR at line 1:
ORA-65345: cannot refresh pluggable database
ORA-17627: ORA-03135: connection lost contact
Process ID:
Session ID: 254 Serial number: 26445


I am getting above error while cloning remote Non-cdb.

Could you please let me know why I am this error?

Thanks
Krishna.

and we said...

As the text of ORA-65345 says:

The foreign archive log required for refreshing the pluggable database was not found.

So you need the remote database to be in archivelog mode. Or open read-only.

* If the CDB that contains the source PDB (the source CDB) or the source non-CDB is in ARCHIVELOG mode and local undo mode, then the source PDB or the source non-CDB can be open in READ WRITE mode and fully functional during the cloning operation. This is called hot PDB cloning.

* If the source CDB or source non-CDB is not in ARCHIVELOG mode, then the source PDB or non-CDB must be open READ ONLY.


https://docs.oracle.com/en/database/oracle/oracle-database/19/sqlrf/CREATE-PLUGGABLE-DATABASE.html#GUID-F2DBA8DD-EEA8-4BB7-A07F-78DC04DB1FFC

Is this the case?


and you rated our response

  (1 rating)

Is this answer out of date? If it is, please let us know via a Review

Reviews

May 02, 2019 - 11:37 am UTC

Reviewer: Krishna Mohan

Thanks for your reply.

Here are the more input's

1) We do not have control on source DB and we can not open it in read-only mode.

2) Source non-cdb is not in archive mode.

3) we just have a DB link to source DB.

Please let me know if there is an alternative for cloning DB database.

Chris Saxon

Followup  

May 02, 2019 - 1:48 pm UTC

Sooooo.... how are you backing up the remote database? You are backing it up, right?

You can load data from the non-CDB to a PDB using data pump export/import. You can read about other options at https://oracle-base.com/articles/12c/multitenant-migrate-non-cdb-to-pdb-12cr1

More to Explore

Multitenant

All of the benefits of the multi-tenant architecture are covered in this guide