Create Pluggable Database Command Fails After Dropping The Same DB With DNFS (Doc ID 2138969.1)

Last updated on FEBRUARY 20, 2019

Applies to:

Symptoms

After creating pluggable database as clone command for a cloning environment with NetApp storage and dNFS. The first time a PDB is created in a CDB it works. If we drop the PDB, recreate the NFS filesystem containing the PDB, and try to recreate the PDB the create pluggable database command fails with:
ORA-19505: failed to identify file "/oradata_CL084CDV/db/D0804CLD/system.dbf"
ORA-17502: ksfdcre:3 Failed to create file /oradata_CL084CDV/db/D0804CLD/system.dbf

The alert log shows:
create pluggable database D0804CLD as clone using '/nav_db_dir_rdc/D0101CLD_Manual_99004.xml' source_file_name_convert=('/oradata_CL010CDV/db/D0101CLD/', '/oradata_CL084CDV/db/D0804CLD/', '/oradata_CL010CDV/temp/temp1D0101CLD.dbf', '/oradata_CL084CDV/temp/temp1D0804CLD.dbf') nocopy tempfile reuse
Thu Mar 31 15:54:45 2016
Direct NFS: NFSERR 70 Stale file handle provided. Server inapfs09-smo path inapfs09-smo
Thu Mar 31 15:54:45 2016
**************************************************************
Undo Create of Pluggable Database D0804CLD with pdb id - 3.
**************************************************************
ORA-19505 signalled during: create pluggable database D0804CLD as clone using '/nav_db_dir_rdc/D0101CLD_Manual_99004.xml' source_file_name_convert=('/oradata_CL010CDV/db/D0101CLD/', '/oradata_CL084CDV/db/D0804CLD/', '/oradata_CL010CDV/temp/temp1D0101CLD.dbf', '/oradata_CL084CDV/temp/temp1D0804CLD.dbf') nocopy tempfile reuse...

Applied patch 20720667 but when trying to unmount the filesystem with the new procedure introduced by this patch, we get:
SQL> exec dbms_dnfs.UNMOUNTVOLUME('inapfs09-smo','/vol/cln_D4302CLD/nfs');
BEGIN dbms_dnfs.UNMOUNTVOLUME('inapfs09-smo','/vol/cln_D4302CLD/nfs'); END;
*
ERROR at line 1:
ORA-19744: Message 19744 not found; product=RDBMS; facility=ORA ; arguments: [inapfs09-smo] [/vol/cln_D4302CLD/nfs]
ORA-06512: at "SYS.DBMS_DNFS", line 20
ORA-06512: at line 1

despite no session is accessing that filesystem nor file is stored there (as all are dropped after dropping PDB instance).

Restarting the database clears the memory and PDB can be created again.

Changes

 dNFS was recently enabled and the problem did not exists without dNFS

Cause

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