Links
• Home
• Oracle DBA Forum
Frequent Oracle Errors
•TNS:could not resolve the connect identifier specified
•Backtrace message unwound by exceptions
•invalid identifier
•PL/SQL compilation error
•internal error
•missing expression
•table or view does not exist
•end-of-file on communication channel
•TNS:listener unknown in connect descriptor
•insufficient privileges
•PL/SQL: numeric or value error string
•TNS:protocol adapter error
•ORACLE not available
•target host or object does not exist
•invalid number
•unable to allocate string bytes of shared memory
•resource busy and acquire with NOWAIT specified
•error occurred at recursive SQL level string
•ORACLE initialization or shutdown in progress
•archiver error. Connect internal only, until freed
•snapshot too old
•unable to extend temp segment by string in tablespace
•Credential retrieval failed
•missing or invalid option
•invalid username/password; logon denied
•unable to create INITIAL extent for segment
•out of process memory when trying to allocate string bytes
•shared memory realm does not exist
•cannot insert NULL
•TNS:unable to connect to destination
•remote database not found'>ora-02019
•exception encountered: core dump
•inconsistent datatypes
•no data found
•TNS:operation timed out
•PL/SQL: could not find program
•existing state of packages has been discarded
•maximum number of processes exceeded
•error signaled in parallel query server
•ORACLE instance terminated. Disconnection forced
•TNS:packet writer failure
•see ORA-12699
•missing right parenthesis
•name is already used by an existing object
•cannot identify/lock data file
•invalid file operation
•quoted string not properly terminated
Recovery Help?

Recovery Help?

2004-08-19       - By rstevenson@(protected)

Reply:     1     2     3     4     5     6     7     8  

Thanks for the replies Ian and Ruth.

Ruth 's suggestion below results in the following:

SVRMGR > recover using backup controlfile until cancel;
ORA-00279 (See ORA-00279.ora-code.com): change 3668927078 generated at 07/02/2004 02:42:41 needed for thread 1
ORA-00289 (See ORA-00289.ora-code.com): suggestion : /u06/archive/SDS0000166990.ARC
ORA-00280 (See ORA-00280.ora-code.com): change 3668927078 for thread 1 is in sequence #166990
Specify log: { <RET >=suggested | filename | AUTO | CANCEL}
CANCEL
ORA-01547 (See ORA-01547.ora-code.com): warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194 (See ORA-01194.ora-code.com): file 3 needs more recovery to be consistent
ORA-01110 (See ORA-01110.ora-code.com): 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@(protected)
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@(protected)
[mailto:oracle-l-bounce@(protected)]On Behalf Of
rstevenson@(protected)
Sent: Thursday, August 12, 2004 8:01 PM
To: oracle-l@(protected)
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@(protected)
put 'unsubscribe ' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --