Skip to Main Content
Forums

Database Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Avoid GUID path for PDB datafiles in ASM when create PDB using database link from nocdb

mantovamMar 30 2018 — edited Mar 30 2018

Hi folks

When created PDB from nocdb database using the command:

CREATE PLUGGABLE DATABASE pdbtest FROM NON$CDB@clone_non_cdb_test

This command works, but put the datafiles in path :

+DG_DATA/CDB12/68A4A953A4D72D16E0536900A8C0E85A/DATAFILE/system.307.972136815

Is there some option to avoid this created using the GUID - "68A4A953A4D72D16E0536900A8C0E85A" in path of datafile?

We want some like this:

+DG_DATA/PDBTEST/DATAFILE/system.271.970791477

A path without GUID, and using OMF. I tried FILE_NAME_CONVERT, create_file_dest and other command option in CREATE PLUGGABLE DATABASE  but no sucess.

Oracle version 12.1.0.2

Comments

mdtaylor

You can only do this if the application tiers on both source and target are identical, i.e. have the exact same patches and code migrations in any custom tops.

If that is the case, you can refresh the DB only, still execute fnd_conc_clone.setup_clean, then run autoconfig from DB tier, patch FS, then run FS.  Autoconfig will not complete successfully on the patch FS, but it will still populate ad_appl_top and tns tables.

1 person found this helpful
1 - 1
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Apr 27 2018
Added on Mar 30 2018
#database-key-features, #multitenant
4 comments
2,476 views