1Z0-043 · Question #180
The loss of the control file forced you to re-create the control file. After re-creating it and opening the database, you find that some of the data files are named as MISSINGnnnnn, where nnnnn is a…
The correct answer is C. There is a read-only tablespace in your database. See the full explanation below for the reasoning.
Question
The loss of the control file forced you to re-create the control file. After re-creating it and opening the database, you find that some of the data files are named as MISSINGnnnnn, where nnnnn is a five-digit number starting with 0. What could be the possible reason?
Options
- AThese are the data files that are corrupted.
- BThere is no SYSAUX tablespace in your database
- CThere is a read-only tablespace in your database.
- DThese are the data files that cannot be recovered.
How the community answered
(28 responses)- A7% (2)
- B18% (5)
- C71% (20)
- D4% (1)
Community Discussion
6
Fatima Z.Jan 2, 2026The answer is C, read-only tablespace in your database, and here is your sticky hook to never forget it: think "READ ONLY, MISSING ONLY" because when you recreate a control file, Oracle rebuilds file info from redo logs, but read-only files never write to redo, so Oracle goes "who are you?" and slaps a MISSINGnnnnn placeholder on them. You have to manually rename those entries back to the real file paths with ALTER DATABASE RENAME FILE, and boom, your database knows its old friends again.
Dervla O.Jan 2, 2026Good mnemonic, though worth adding that you also need RESETLOGS after the control file recreation, which wipes archived log history and starts sequence numbering over, so document your backup chain before you get there.
Dervla O.Jan 15, 2026The wording "re-create the control file" should have already put you on alert for the read-only tablespace trap, because when you manually script a new control file you have to account for read-only datafiles separately or Oracle substitutes those placeholder MISSING names. D is the classic panic pick here, but unrecoverable files would give you a hard stop on OPEN, not a renamed placeholder, so C is your answer.
Fatima Z.Jan 18, 2026Nail on the head, Dervla, and here is the sticky hook to lock it in: remember READ-ONLY equals RENAMED-ONLY, because Oracle quietly swaps those datafile paths to MISSING placeholders and lets you keep going, while a truly unrecoverable file throws up a full roadblock at OPEN and never lets you sneak through to answer C.
Mei-Ling H.Jan 22, 2026I pick B because when you recreate the control file manually, Oracle does not know about the SYSAUX tablespace if it was not included in the script, so it marks those data files as MISSINGnnnnn to show it cannot locate them in the new control file. The keyword here is "re-create," which means you are building the control file from scratch and any tablespace you forget to list will show up exactly like this.
Dervla O.Jan 23, 2026Mei-Ling, the MISSINGnnnnn label actually appears when Oracle reads a backup control file and finds data files it has no current record of, which is the restore scenario in C, not a manual re-create where any omitted tablespace simply would not be registered at all rather than flagged with that placeholder name.