Solution:

1. Startup the database with the mount option

SQL> startup mount
ORACLE instance started.
2. Find the name of the redo log file which belongs to the active group
SQL> SELECT MEMBER FROM V$LOG G, V$LOGFILE F WHERE G.GROUP# = F.GROUP#
2 AND G.STATUS = 'CURRENT';

MEMBER
--------------------------------------------------------------------------------
/OraRedo/RedoLogFiles/siamst_log01.dbf

3. Using a backup control file, start the cancel based recovery. The system may suggest a non-existing archive
log -- ignore it and specify the log file name {with full path} that you got in the above step
SQL> RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL
ORA-00279: change 21375038 generated at 09/21/2007 20:12:47 needed for thread 1
ORA-00289: suggestion : /export/pspp/oracle/dbs/arch1_4_633901491.dbf
ORA-00280: change 21375038 for thread 1 is in sequence #4

Specify log: {=suggested | filename | AUTO | CANCEL}
/OraRedo/RedoLogFiles/siamst_log01.dbf
Log applied.
Media recovery complete.

4. Finally open the database in RESETLOGS mode. It is recommended to reset the online logs after
incomplete recovery or recovery with a backup control file
SQL> ALTER DATABASE OPEN RESETLOGS;
Database altered.

Shivaraj Netrekar
Monday, 3 June 2013ORA-01194: file 1 needs more recovery to be consistent : No archivelog database
asking for recovery
ORA-01194: file 1 needs more recovery to be consistent
This is the case datafiles were inconsistent and it is asking for recovery when you try to start the
noarchivelog mode database.
Step 1: Start the database in mount.
Startup mount;
Step 2: Check the datafiles which required recovery.
select * from v$recover_file;
Step 3: As you do not have the needed archivelogs to recover those files, you should drop them offline
then recover database and open.
alter database datafile <FILE#> offline drop;
NOTE: For sure you will loose data inside those files.
Step 4: Recover the database.
recover database;
If you come across below error
ORA-00283: recovery session canceled due to errors ORA-01610: recovery using the BACKUP
CONTROLFILE option must be done then, do the following recover database using backup controlfile
until cancel;
It will ask to Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
When the session request a sequence for recovery please point write the path of the each online
redolog one after another untill its say database recovered. You can select the redolog member from
below query.
select group#, member FROM v$logfile;
NOTE: Please repeat the recovery process, When the session request a sequence for recovery please
point write the path of the online redolog:
Step 5: Then open the database resetlog
alter database open resetlog