This content has been marked as final. Show 15 replies
I cloned from TEST to DEV. I copied all the datafiles to DEV......but
in create control file command, I forgot to add newly added index data file to control file command....
Does you have added the index data file to TEST before Cloning.. ??
How can I add this datafile to DEV instance now?
I suggest that you can add New Data File to Cloned instace (i.e., DEV).
and then go for Transportable Tablespaces...
that might be useful..
Else let us see for some replies from other..friends..
Pavan Kumar N
If that datafile was part of the database (ie in the data dictionary) but
not included in the create controlfile, you would have seen a warning
message about a missing datafile in the alert.log. If you query
DBA_DATA_FILES now, that file would appear as $ORACLE_HOME/MISSSINGxx
(where xx is the filenumber).
Normally, if both conditions are true
a. You do not do a resetlogs
b. The source database is in archivelog
c. You have ALL the archivelogs since the time the datafile was added in the
then you could do an ALTER DATABASE CREATE DATAFILE ... AS
and then RECOVER DATAFILE using the ArchiveLogs from the source.
However, in your case,
a. because you were renaming the database, you have done a resetlogs
b. also the source database is unlikely to be in archivelog
c. quite unlikely
I can't think of a way that you can add that file back. You can drop the
MISSINGxx file if you want !
Yes this file is shown with RECOVERY status in dba_data_files table......
Finally I renamed this file to old missed file and when trying to online the file i am getting the following error
SQL> alter database datafile 16 online;
alter database datafile 16 online
ERROR at line 1:
ORA-01190: control file or data file 16 is from before the last RESETLOGS
ORA-01110: data file 16: '/oradata/app/oracle/oradata/CRMSYSR2/siebel_index_tbs04.dbf'
As Hemant has already suggested, you will never be able to use that file. The reason is that the file is from before the last resetlogs.
Oracle is aware of the missing file because the information is has about its tablespaces don't match up with the info in dba_data_files (it's more complicated than that - but you get the idea).
Your only options at this point are to:
1) Perform the refresh again
2) Drop the tablespace that the file was part of