Problem Opening the Database.

the corruption might be only in 1 of the online redo logs.

first attempt would be to copy them from one other multiplexed locations
i hope they are multiplexed ...

to find all:

select member from v$logfile

Select allOpen in new window

Hi,

  They are all in the same location.  But i have three of them.  Is there something i can do ?

SQL> select member from v$logfile;

MEMBER
--------------------------------------------------------------------------------

E:\ORADATA\QMS01QA\REDO03.LOG
E:\ORADATA\QMS01QA\REDO02.LOG
E:\ORADATA\QMS01QA\REDO01.LOG

If they aren't multiplexed or if all copies of the log are corrupted, you need to perform instance recovery.

Simple first step:
rman target /

recover database;

If this is an important/production database, I would contact Oracle Support and open an SR for down system.

>>But i have three of them

You have three groups with one member each.  You don't have multiple copies of each one.

You need to perform a recover/restore.

you didn't multiplex them ?
ooo ... bad habit

and if you start correcting that, at least make sure they are on different drives
so when you lose a drive, you at least have a copy

i encounter this problem about once year

I am getting the below error when trying to recover it.


RMAN> recover database;

Starting recover at 08-MAY-18
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=148 devtype=DISK

starting media recovery
media recovery failed
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 05/08/2018 09:48:30
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database reco
ver if needed
 start
ORA-00283: recovery session canceled due to errors
ORA-00399: corrupt change description in redo log
ORA-00353: log corruption near block 4343 change 10073170157523 time 05/03/2018
06:00:01
ORA-00312: online log 2 thread 1: 'E:\ORADATA\QMS01QA\REDO02.LOG'

RMAN>

How important is the data in this database?

step 1:
stop the database and make a file based copy of all it's files:
initfile or spfile, control files, those 3 online redo logs, data files and archived logs

then try :

recover database until time "to_date('05/03/2018 05:59:59', 'mm/dd/yyyy hh24:mi:ss')";

Select allOpen in new window

go further back until it no longer fails (it that's even possible)

as you have corruption, you'll have to open it with resetlogs

alter database open resetlogs;

Select allOpen in new window

and then mutliplex the controlfile and online redo logs !

It is a QA database.   It is a recently copy of production.   It  is a 1.5 TB Database

Unfortunately it is not running in Archive Mode.

What can i do ?   -

ah ... redo the copy ?

i hope your production db is setup with multiplexed redo logs and controlfiles

another option ... run, run away as far as possible

Here are the scenarios to recover from a missing online redo log:
https://docs.oracle.com/en/database/oracle/oracle-database/12.2/bradv/user-managed-recovery-advanced.html#GUID-BF09DCB4-AB6F-4886-AAC1-C2747BDF05D2

>>There is an undocumented parameter that allows opening the DB with some lose of data

CAUTION: This will leave the database in an unsupported configuration. I would not suggest using it.

I found the below article, and it worked.

http://osamamustafa.blogspot.de/2012/07/opening-database-with-corrupted-redo.html

Using this article really worked.

Remember:  You are now in an unsupported configuration.

Yeah, it is a Dev database.

I'll configure better the red and controlfile multiplexing.