ora-00205 error in identifying control file

  • 0
  • 1
  • Question
  • Updated 3 years ago
  • Answered
During V2P from VDB (devdb) to source (orcl), got an error message ORA-00205.
In alert log,  
ALTER DATABASE   MOUNT ORA-00210: cannot open the specified control file
ORA-00202: control file: '/u02/app/orcl/data/u01/app/oracle/oradata/orcl/control01.ctl'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-205 signalled during: ALTER DATABASE   MOUNT...
Photo of HJ

HJ

  • 540 Points 500 badge 2x thumb

Posted 3 years ago

  • 0
  • 1
Photo of David Gillespie

David Gillespie, Employee

  • 1,010 Points 1k badge 2x thumb
Hi Heungjae,
What Delphix Version is being used here?
What is the Oracle Database version? Please confirm that this is Oracle Enterprise edition?

Is this file created and in the place where you expect it to be? What are it's permissions and group ownership etc.
ls -al /u02/app/orcl/data/u01/app/oracle/oradata/orcl/control01.ctl
Is the orcl database shutdown when running the V2P from a snapshot of devdb to the target server for the orcl database?

We may need to create a case, upload the support bundle and alert log for the "orcl" instance (on the new V2P database). Please add the case number when you upload the support bundle.

Best practice for uploading support bundles can be found here:
https://support.delphix.com/hc/en-us/articles/201655216-Best-Practice-Uploading-Support-Logs

Cheers,
Dave G.
Photo of HJ

HJ

  • 540 Points 500 badge 2x thumb
Hi,

1. Delphix engine is Demo 4.1.2.0 LSDE, and Oracle version is 11.2.0.1.0,
2. Changed the permission /u02/app/orcl/data/u01/app/oracle/oradata/orcl from  755 to 775.
3. I could not found control01.ctl in this directory.
4. Yes, shutdown orcl database before running the v2p from VDB.

This problem could be recreated under LSDE.
Thanks,
Photo of Kyle Hailey

Kyle Hailey, Alum

  • 878 Points 500 badge 2x thumb
The Landshark demo lab is not set up with enough room to do a V2P. First the source has provisioning disabled and second the source doesn't have enough room to host a second full physical copy.
Did you enable provisioning to the source machine? Did you add more disk space to the source machine VM?
The target machine has provisioning enabled but like the source machine it doesn't have enough room for a full physical copy.

Thanks
- Kyle