Document ID: 275940
http://support.veritas.com/docs/275940
E-Mail Colleague IconE-Mail this document to a colleague

When a database has Oracle Managed Files (OMF) datafiles, creating a clone database from an 'instant checkpoint' deletes the OMF datafiles from the primary database.

Details:

Note:  This is not an issue when you create a clone database using an online or offline checkpoint.
This issue occurs in VERITAS Storage Foundation (tm) for Oracle (Solaris) 4.0 and 4.1. The affected Oracle versions are:
- 10gR1    (10.1.0.2 and 10.1.0.3)
- 9iR2       ( 9.2.0.6 and 9.2.0.5 )
       
For 9iR2, versions 9.2.0.1 - 9.2.0.4, creation of a clone database from an instant checkpoint fails with the following error:
ORA-01511: error in renaming log/data files

For 9iR1 versions  9.0.1.x, creation of a clone database from an instant checkpoint fails with the following error:
ORA-01157: cannot identify/lock data file <number> - see DBWR trace file
ORA-01110: data file <number>: '/<OMF dir>/<omf file>'
 
Workaround:  
- If your database has OMF datafiles, create a clone database always using online or offline checkpoints
- If your database has OMF datafiles, and you would like to create a clone database using an instant checkpoint, make sure you use Oracle Disk Manager (ODM). Using ODM protects you from losing OMF datafiles from the primary database when creating a clone database from an instant checkpoint.



Products Applied:
 Storage Foundation for Oracle 4.0 (Solaris), 4.1 (Solaris)

Last Updated: March 26 2005 12:24 AM GMT
Expires on: 365 days from publish date
Subscribe Via E-Mail IconSubscribe to receive critical updates about this document

Subjects:
 Storage Foundation for Oracle
   Application: Compatibility, Informational

Languages:
 English (US)

Operating Systems:
Solaris

10, 7.0, 8.0, 9.0