Skip to main content

How to Handle ORA-00205 Error When Using Virtual Databases (VDBs) (KBA1563)






During provision or when starting a virtual database (VDB), you received the following error: ORA-00205: error in identifying control file. 


1. Examine the message provided in the Dashboard or in the Action pane for the provision/start failure. It should look similar to this:

["Failed to mount database instance. See command output for more information.","Make sure that the parameters in init<sid>.ora file are valid. Review the Oracle alert log for more details if applicable
"VDB_/vl","rm -f $ORACLE_HOME/dbs/spfile${ORACLE_SID}.ora
DELPHIX>$DLPX_SHELL $DB_SCRIPT_DIR/ "restrict pfile='/delphix/Mounts/vl/datafile/init.ora.rename'
ERROR : SQL*Plus: Release Production on Thu Jul 21 15:50:32 2016
ERROR : Copyright (c) 1982, 2013, Oracle. All rights reserved.
ERROR : Connected to an idle instance.
ERROR : SQL> ORACLE instance started.
ERROR : Total System Global Area 4275781632 bytes
ERROR : Fixed Size 2260088 bytes
ERROR : Variable Size 4194304904 bytes
ERROR : Database Buffers 67108864 bytes
ERROR : Redo Buffers 12107776 bytes
ERROR : ORA-00205: error in identifying control file, check alert log for more info
ERROR : SQL> Disconnected from Oracle Database 11g Enterprise Edition Release - 64bit Production
ERROR : With the Partitioning, OLAP, Data Mining and Real Application Testing options
target_name | VDB_/vl
timestamp | 2016-07-21 18:51:14.826
pending | f
severity | CRITICAL

2. Examine the Oracle alert log to determine if it contains an ORA-27086 and error stack like the one shown below: 

ORA-00210: cannot open the specified control file
ORA-00202: control file: '/u02/oradata/mp/control01.ctl'
ORA-27086: unable to lock file - already in use
Linux-x86_64 Error: 11: Resource temporarily unavailable

3. If it does, verify that the lock manager is up and running on the Target host by running the following command: 

ps -ef | grep rpc.statd

The expectation is that it will return nothing if the rpc.statd service that provides locking for NFS, is not running.


If rpc.statd which provides NFS lock management services was stopped or not enabled, a sysadmin will need to enable/restart the nfs lock service.

Below is an example of starting the lock manager from a Redhat Enterprise Linux system: 

 # service nfslock start
Starting NFS statd:                                        [  OK  ]

Once you have thenfslockservice started you can either:

  1. Enable the VDB


2. Re-provision the VDB

*For additional options and steps please see Provisioning an Oracle VDB

  1. Click the Object you wish to provision from.
  2. Click the TimeFlow tab.
  3. Select a SnapShot

  4. Click Provision and the Provision VDB wizard will open:
    1. For Oracle Single Instance the fields Installation HomeDatabase Unique NameSIDDatabase NameMount Base, and Environment User will auto-populate with information from the parent.
    2. For Oracle RAC the fields Installation HomeDatabase Unique NameSIDDatabase NameMount BaseInstance Number, Instance Name and Environment User will auto-populate with information from the parent.

  5. Review the information for Installation HomeDatabase Unique NameSID, and Database Name. Edit as necessary.
  6. Review the Mount Base and Environment User.
  7. Select Provide Privileged Credentials if you want to use login credentials on the target environment that are different from those associated with the Environment User.
  8. Click Advanced to customize the VDB online log size and log groups, archivelog mode, local_listener parameter (TCP/IPC protocol addresses), additional VDB configuration settings or file mappings, or custom environment variables. 

  9. Click Next.
  10. Select a Target Group for the VDB.
  11. Select a Snapshot Policy for the VDB.
  12. Enable Auto VDB Restart to allow the VDB to be automatically restarted when target host reboot is detected by Delphix.
  13. Click Next .
  14. Enter any operations that should be run at Hooks during the provisioning process.
  15. Click Next.
  16. Click Finish.


My Oracle Support knowledge base article Doc ID 18290.1