that is what i suspected too... but we copy the data over... so shouldnt have any lost data... hmmm, am i right?Quote:
Originally posted by pando
you will start crying after a while when data in that lost datafile is needed
Printable View
that is what i suspected too... but we copy the data over... so shouldnt have any lost data... hmmm, am i right?Quote:
Originally posted by pando
you will start crying after a while when data in that lost datafile is needed
Copy from where, u said you had lost the data file ?? where do you get the lost data from ??Quote:
Originally posted by yls177
that is what i suspected too... but we copy the data over... so shouldnt have any lost data... hmmm, am i right?
Well, how about using RMAN? Live and learn, right :-)Quote:
Originally posted by yls177
a successful backup cos, we have a script which reads in the list of filesystems from a file.
select * from v$recover_file;
select file#, status from v$datafile;
and look the output :D
Quote:
Originally posted by pando
you will start crying after a while when data in that lost datafile is needed
u are right... i started to cry.. as my functional team has some problems with the new restoration. however, they couldnt pinpoint to the loss of data. my colleague has to restore once again..
my question is that when we do the below
1) copy the datafile to the restored database
2) startup
3) of course, there will be errros
4) re-create control file
5) recover database using backup controlfile until cancel
6) will prompt for which online log file
7) alter dataabse open resetlogs;
though , the database can be started, but we will surely lose some data?
also-> no rows are selectedQuote:
select * from v$recover_file;
no file# with offline statusQuote:
select file#, status from v$datafile;
does that mean that the database is fine?