Oracle 12c – Understanding Alert Log Errors

Looks like your oracle directory doesn't exists. You will need to log into the database, create a directory, and retry your import

export ORACLE_HOME=/path/to/oracle/home
export ORACLE_SID=YOUR_SID    
sqlplus / as sysdba
create directory DUMPS as '/path/to/your/dump/files';
exit;

And retry your import. Pending on the user you are using to do the import, you may need to grant read/write access.

Could you please tell us how you connected to rman?

For example:

rman target sys/asdf@prod auxiliary sys/asdf@dev

The reason for you problem is that the two databases have trouble communicating with each other.

If you use auxiliary / because your rman session is located on the dev server this is not going to work. The reason is pretty simple as follows.

Lets say your rman session was opened on server dev. You use this connection:

rman target sys/asdf@prod auxiliary sys/asdf@dev

The auxiliary database uses the TNSalias "prod" to connect to the target database. The prod database uses the TNSalias "dev" to connect to the auxiliary database. This means you have to configure the tnsnames.ora on both sides to be able to connect to the other database. Since the rman session is on dev in this example you have to configure the TNSalias "dev" on dev as well.

Back to the example with auxiliary /, it is obvious now why it cannot work.

Then there are additional stuff to keep in mind. The auxiliary database needs to be restarted several times. In some cases you loose the connection to the auxiliary database when it shuts down. This means you have to configure the dev database in the SID_LIST of the listener on the dev server. And take care that the password file is present.

Well, this sounds like a lot configuration overhead. If you have to refresh your dev database frequently this is not a big deal. But I personally prefer to clone from backup location because this is much more simple. You can also skip the SPFILE clause when you create it manually. In my experience you need 2 or 3 attempts to work out the correct parameter conversion. If some parameters change on your prod database you might have to adjust this clause again.