ORA-65169 ORA-17627 ORA-12154 ORA-17629 on PDB remote clone copy

Tim_Hussar

On a single Exadata cluster, from a 3-node RAC Multitenant DB with TDE at CDB$ROOT level (remote CDB), attempting to copy a PDB that's in the same cluster and is a 2-node RAC Multitenant DB with TDE (source CDB), and getting errors ORA-65169, ORA-17627, ORA-12154, ORA-17629.   Confirmed both CDBs are using the default TNS_ADMIN ($OH/network/admin).  Tried the service/tnsnames setup in two ways - First, used the existing multi-node service for the source CDB; second, created a single-node service for the source CDB - both resulted in the same errors.  For both tests, placed the service connect info for both DBs in the default tnsnames.ora location on all 3 nodes.

SQL> CREATE PLUGGABLE DATABASE qaefctora23 FROM [email protected] keystore identified by "<pswd>";

CREATE PLUGGABLE DATABASE qaefctora23 FROM [email protected] keystore identified by "<pswd>"

*

ERROR at line 1:

ORA-65169: error encountered while attempting to copy file +DATAC1/DEV01CDB/<file_dir_hash>/DATAFILE/datafile_indx.<number_hash>

ORA-17627: ORA-12154: TNS:could not resolve the connect identifier specified

ORA-17629: Cannot connect to the remote database server

User_HBNAJ

Can any one find this Solution for this problem.?

skorupeck

Can you check if DB link works correctly? Please run simple check of: desc [email protected]

user10016140

I received the same errors you described when attempting to hot clone an unencrypted PDB between two exadata machines (create pluggable database xyz_clone from [email protected]_link;)  after re-imaging the target machine. In my case we failed to recreate the sqlnet.ora file. The copy worked after creating the sqlnet file on the target machine in the TNS_ADMIN path like this:

     NAME.DIRECTORY_PATH=(TNSNAMES, EZCONNECT)

YMMV, but hope this helps. (Credit to my coworker who discovered the problem.)

Arsalan Dehghanisariyarghan

Hi,

I think the relevant "tns" entries were not added in ALL the nodes "tnsnames.ora" file in your environment. So, check "tnsnames.ora" on ALL the Cluster nodes,

then add the relevant '<tnsname entry>' in "tnsnames.ora" file on ALL the Cluster nodes.

Regards,

Arsalan

Facundo Ezequiel Grande

Hi, 

I had the same issue. 

The entry of my tnsnames.ora had a service_name with domain, so I removed the domain of that entry in only one node, but the issue continued. 

So, I had to remove the domain in all RAC's nodes, then it worked fine. 

Regards.