RE: OCP Question

From: Blanchard, William <>
Date: Wed, 16 Dec 2009 14:15:29 -0600
Message-ID: <>

You people with your fancy DataGuard, OID, ASM and OEM. ;-) What's wrong with using 7.3 standards for 10g databases? :-S (Help me please, I'm stuck in the 20th century).

-----Original Message-----

From: Newman, Christopher [] Sent: Wednesday, December 16, 2009 2:07 PM To: Blanchard, William;; Subject: RE: OCP Question

We saw this once on a standby database; the primary was recreated with different datafiles, then the standby was created, but had existing files already on disk.

To make this more clear:

  1. Primary recreated and reorganized so that it contained less datafiles, ie SALES01.dbf, SALES02.dbf instead of SALES01-10.dbf's.
  2. Standby was recreated. The existing datafiles weren't removed, they were merely overwritten (and there would be extras in this case, IE SALES03-10.dbf).

With dataguard, automatic file management set up. So:

  1. Add SALES03.dbf to the primary as the need arises.
  2. SALES03.dbf physical file already exists on the standby, albeit not associated with the database. Because the file exists on disk however, it is not overwritten and you get Oracle renaming the file with the MISSING issue.

-----Original Message-----

From: on behalf of Blanchard, William Sent: Wed 12/16/2009 2:02 PM
To:; Subject: RE: OCP Question  

I believe this is because the controlfile can't find the file (someone correct me if I'm wrong). I would check the path and ensure that the controlfile is pointing to the correct location.

-----Original Message-----

[] On Behalf Of Bill Zakrzewski Sent: Wednesday, December 16, 2009 1:58 PM To:
Subject: OCP Question

Listers -

I took the Oracle 10g OCP exam and one question in the exam was something I have not come across in several years working with Oracle. I searched google, but only found someone has had this happen, but they didn't understand why - it was during a database cloning process.

It went something like - You rebuild your controlfile and open your database and discover several datafiles have been renamed to /somepath/MISSING##### (where ##### is a 5-digit number).

What might that signify?

A. Those are corrupt files?
B. Those are read-only tablespace files?
C. .....
D. .....
E. .....

I don't remember the five choices, but does anyone know why Oracle would rename datafiles to .....MISSING#####.




This email and any information, files, or materials transmitted with it are confidential and are solely for the use of the intended recipient. If you have received this email in error, please delete it and notify the sender.

-- Received on Wed Dec 16 2009 - 14:15:29 CST

Original text of this message