RE: RE: Recovery Help?
- From: "Powell, Mark D" <mark.powell@xxxxxxx>
- To: "'oracle-l@xxxxxxxxxxxxx'" <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 19 Aug 2004 09:35:29 -0400
The file in question appears from its naming to be an index tablespace. =
If
this is true you can remove the index tablespace data files from Oracle =
via
an alter database, run recovery, use the dictionary to extract the =
index
source (also get FK, PK, UK definitions), drop the tablespace including
contents, recreate the tablespace, and manually recreate the indexes =
from
the generated scripts.
We have done this but you need to be able to recover all the data data
files, system, and rbs for this to be a useful option.
Oracle has a utility that can read raw data files and extract data, but =
I
believe you have to hire support to get this. But as the database is =
or
maybe was a production db this might be a necessity.
Even a firm too small to afford a full time DBA should hire part-time =
DBA
support. Someone who logs in once a week and verifies that the hot =
backups
and exports are 1- running and 2- appear successful and 3- makes a =
quick
check of the system for space utilization.
You would think the system administrators would have detected this =
problem.
IMHO -- Mark D Powell --
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Ruth Gramolini
Sent: Thursday, August 19, 2004 8:40 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: RE: RE: Recovery Help?
You could try using a later "until time" which might eliminate the need =
of
the 7/2/04 archivelog. I have done this successfully several times.
You can call me if you think I could help better in person.
=A0
Ruth Gramolini
Oracle DBA
Vermont Department of Taxes
Phone 802-828-5708
Email rgramolini@xxxxxxxxxxxxxxx <mailto:rgramolini@xxxxxxxxxxxxxxx> =
=A0
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of
rstevenson@xxxxxxxxxxxxxx
Sent: Thursday, August 19, 2004 8:05 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: RE: RE: Recovery Help?
Thanks for the replies Ian and Ruth.
Ruth's suggestion below results in the following:
SVRMGR> recover using backup controlfile until cancel;
ORA-00279: change 3668927078 generated at 07/02/2004 02:42:41 needed =
for
thread 1
ORA-00289: suggestion : /u06/archive/SDS0000166990.ARC
ORA-00280: change 3668927078 for thread 1 is in sequence #166990
Specify log: {<RET>=3Dsuggested | filename | AUTO | CANCEL}
CANCEL
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get =
error
below
ORA-01194: file 3 needs more recovery to be consistent
ORA-01110: data file 3: '/u02/oraindex/sds/usrindex01.dbf'
SVRMGR>
Mount U02 is the drive that was lost and now has the newer dated db =
files...
Any ideas from here ?
Thanks.
----- Original Message -----
From: Ruth Gramolini
To: oracle-l@xxxxxxxxxxxxx
Sent: August 13, 2004 08:16
Subject: RE: Recovery Help?
Have they tried: 'recover using backup controlfile until cancel;' and
cancelling when it asks for the archivelog from July 2.
Just a thot!
Ruth
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of
rstevenson@xxxxxxxxxxxxxx
Sent: Thursday, August 12, 2004 8:01 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: Recovery Help?
I'm seeking help/advice from the list on behalf of a client that no =
longer
has a DBA - and has a production DB utterly screwed up - hope you can =
help
me point them in the right direction.... I've tried the basics ... but =
then
I'm only knowledgeable enough in this area to be dangerous!
Situation: Remote DB (Linux/8.1.7) - they lost a drive/mount point - =
and
then lost the frame relay for best part of 3 weeks (thanks to Sprint
efficiency). The system tried to perform automated disk-to-disk =
backups
(cold, via crontab) then to tape, but failed when it hit the bad drive =
-
each day!
Result: Their DB is mostly at July 14 - with the restore of the bad =
drive at
Aug 3rd (includes a System datafile, 1 data and an index datafile). =
When I
try to recover for them, it calls for archive logs dated July 2nd - and =
they
only have ones going back to July 3rd..... Their backup cycle is a =
7-day
cycle (with no secure copy archived off) - so they have no good =
consistent
backup to restore from...
At this stage, they'd be real happy just to get a db back, even if =
several
weeks old. My viewpoint at this stage is that there are no options ... =
but
then I'm hoping for them that maybe one of you knows differently???
Thanks for thoughts ...
Richard
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
Other related posts:
