Cannot reset archive log

Hi
My Oracle 11g is running on Windows Vista.
The database is on archive log mode. I like to set it to no archive log mode.
When I shutdown the database from SQLPLUS [as SYS], it does not start after that!
In Sqlplus, when I issue SHUTDOWN NORMAL - it shuts down database.
When I then run, STARTUP MOUNT
I get this message - ORA-12514: TNS:listener does not currently know of service requested in connect
The only way I can start it again via
net start OracleService<MYDB> command. Then it starts normally - not in mount mode. So I can't issue ALTER DATABASE NOARCHIVELOG command :(
How do I disable archive log?
Thanx for help.

When I then run, STARTUP MOUNT
I get this message - ORA-12514: TNS:listener does not currently know of service requested in connectSQL*net is not required to start the DB.
Log onto the system as the Oracle s/w owner & do the following:
set
sqlplus
/ as sysdba
startup mount
CUT the line above & paste into command window
CUT commands & results and PASTE back here

Similar Messages

ORA-00308: cannot open archived log, ORA-27041

hi All,
here I am making DR server and I copied SAP Data file1,2,3,4 from PRD to DR server and created control file. when I try to run following command for applied archives which i copy from PRD then getting below error.
SQL>Startup
Database mounted.
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL> recover database using backup controlfile;
ORA-00279: change 1209554452 generated at 02/09/2012 17:02:57 needed for thre
1
ORA-00289: suggestion : F:\ORACLE\PRD\ORAARCH\PRDARCH1_59501_657865393.DBF
ORA-00280: change 1209554452 for thread 1 is in sequence #59501
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
auto
ORA-00308: cannot open archived log
'F:\ORACLE\PRD\ORAARCH\PRDARCH1_59501_657865393.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
ORA-00308: cannot open archived log
'F:\ORACLE\PRD\ORAARCH\PRDARCH1_59501_657865393.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
here required PRDARCH1_59501_657865393.DBF while PRD server have PRDARCHARC59501_0657865393.001
I did change the LOG_ARCHIVE_DEST parameter in initSID.ora of DR server and not in PRD.
please tell that, how can i apply PRD's archive (.001 extension) on DR.
Regards,

hi all,
after recommendation , now parameter values on DR server is :
*.log_archive_dest_1='LOCATION=F:\oracle\PRD\oraarch\PRDarch'
*.log_archive_format='%t_%s_%r.001'
when i try to apply
SQL> recover database using backup controlfile;
ORA-00279: change 1211443555 generated at 02/10/2012 23:36:05 needed for thread
1
ORA-00289: suggestion : F:\ORACLE\PRD\ORAARCH\PRDARCH\1_59557_657865393.001
ORA-00280: change 1211443555 for thread 1 is in sequence #59557
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
auto
ORA-00308: cannot open archived log
'F:\ORACLE\PRD\ORAARCH\PRDARCH\1_59557_657865393.001'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
if you see that the required archive is: 1_59557_657865393.001
while copied archive exist with this name: PRDARCHARC59557_0657865393.001
I tried to change in Format parameter to make required format but
Exp:
%t_%s_%r.001
1_59557_657865393.001
ARC%s%r%t.001
ARC595576578653931.001'
ARC%s_%r%t.001
ARC59557_6578653931.001
ARC%s_%r.%t
ARC59557_657865393.1
PRDARCHARC%s_%r.%t
PRDARCHARC59557_657865393.1
Required Format: PRDARCHARC59540_0657865393.001
how can i resolve this different name issue? please suggest me required format.
Regards,

Good One - "ORA-00308: cannot open archived log", No Recovery Going On

Folks,
Oracle 11gR1 SE cluister in archive log mode. Every hour I scp old logs over to a different server and nuke the ones so archived. I always switch the log destination to a new directory before moving and nuking, so I'm not touching logs being written to. Every once in a while I get;
Thu Nov 11 22:08:13 2010
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x0] [PC:0x3201E53, _intel_fast_memcmp()+27]
Errors in file /u01/oracle/diag/rdbms/dekopd78/DEKOPD781/trace/DEKOPD781_ora_30937.trc (incident=805592):
ORA-07445: exception encountered: core dump [_intel_fast_memcmp()+27] [SIGSEGV] [ADDR:0x0] [PC:0x3201E53] [Address not mapped to object] []
Incident details in: /u01/oracle/diag/rdbms/dekopd78/DEKOPD781/incident/incdir_805592/DEKOPD781_ora_30937_i805592.trc
Thu Nov 11 22:09:42 2010
Errors in file /u01/oracle/diag/rdbms/dekopd78/DEKOPD781/incident/incdir_805592/DEKOPD781_ora_30937_i805592.trc:
Linux-x86_64 Error: 2: No such file or directory
Thu Nov 11 22:09:42 2010
Errors in file /u01/oracle/diag/rdbms/dekopd78/DEKOPD781/incident/incdir_805592/DEKOPD781_ora_30937_i805592.trc:
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00308: cannot open archived log '/u01/oracle/ARCHIVE_LOG_DEST/DEKOPD78/archive2/2_2043_716773164.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00308: cannot open archived log '/u01/oracle/ARCHIVE_LOG_DEST/DEKOPD78/archive2/2_2044_716773164.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00308: cannot open archived log '/u01/oracle/ARCHIVE_LOG_DEST/DEKOPD78/archive1/2_2045_716773164.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00308: cannot open archived log '/u01/oracle/ARCHIVE_LOG_DEST/DEKOPD78/archive1/2_2046_716773164.dbf'
ORA-27037: unable to obtain file status
This seems to happen after a core dump (memory leak?). No recovery is going on and the database functions normally afterwards.
Why would the database try to access old log filles when not recovering?
Thanks,
Scott Uhrick
General Reinsurance

After some errors database instance tries to access redo data for the last 12 hours: see My Oracle Support note:
+Oracle Alert Log Is Reporting Archive Log Status Is Not Available For Logs That Have Long Been Backed Up [ID 1161573.1]+
Edited by: P. Forstmann on 15 nov. 2010 21:34

ORA-00308: cannot open archived log '+DATA'

Hello all,
I created new physical standby but I facing problem with shipping archived file between primary and standby.
Primary : RAC (4 nodes)
Standby : single node with ASM
when I run :
alter database recover managed standby database disconnect from session;
in alert log file :
Managed Standby Recovery not using Real Time Apply
Parallel Media Recovery started with 24 slaves
Waiting for all non-current ORLs to be archived...
All non-current ORLs have been archived.
Media Recovery Waiting for thread 1 sequence 25738
Tue Mar 03 12:21:13 2015
Completed: alter database recover managed standby database disconnect from session
and when i checked archived files by
select max(sequence#) from v$archivanded_log;
It was null.
I understand thatno shipping between primary and standby till this point i deiced to use manual recovery by :
alter database recover automatic standby database;
But i get this error in alert log file :
alter database recover automatic standby database
Media Recovery Start
started logmerger process
Tue Mar 03 12:38:38 2015
Managed Standby Recovery not using Real Time Apply
Parallel Media Recovery started with 24 slaves
Media Recovery Log +DATA
Errors with log +DATA
Errors in file /u01/app/oracle/diag/rdbms/oracledrs/oracledrs/trace/oracledrs_pr00_4989.trc:
ORA-00308: cannot open archived log '+DATA'
ORA-17503: ksfdopn:2 Failed to open file +DATA
ORA-15045: ASM file name '+DATA' is not in reference form
ORA-279 signalled during: alter database recover automatic standby database..
when i opened oracledrs_pr00_4989.trc: file i find :
*** 2015-03-03 12:38:39.478
Media Recovery add redo thread 4
ORA-00308: cannot open archived log '+DATA'
ORA-17503: ksfdopn:2 Failed to open file +DATA
ORA-15045: ASM file name '+DATA' is not in reference form
When I created i set these parameter in duplicate command:
set db_file_name_convert='+ASM_ORADATA/oracle','+DATA/oracledrs'
set log_file_name_convert='+ASM_ARCHIVE/oracle','+DATA/oracledrs','+ASM_ORADATA/oracle','+DATA/oracledrs'
set control_files='+DATA'
set db_create_file_dest='+DATA'
set db_recovery_file_dest='+DATA'
What please the mistake here
Thanks in advance,

Yes I have datafiles under +DATA
ASMCMD> cd +DATA/ORACLEDRS/DATAFILE
ASMCMD> ls
ASD.282.873258045
CATALOG.288.873258217
DEVTS.283.873258091
EXAMPLE.281.873258043
FEED.260.873227069
FEED.279.873257713
INDX.272.873251345
INDX.273.873252239
INDX.278.873257337
SYSAUX.262.873227071
SYSTEM.277.873256531
SYSTEM_2.280.873257849
TB_WEBSITE.284.873258135
TB_WEBSITE.285.873258135
TB_WEBSITE.286.873258181
TB_WEBSITE.287.873258183
UNDOTBS1.275.873253421
UNDOTBS2.276.873255247
UNDOTBS3.261.873227069
UNDOTBS4.271.873245967
USERS.263.873227071
USERS.264.873235507
USERS.265.873235893
USERS.266.873237079
USERS.267.873238225
USERS.268.873243661
USERS.269.873244307
USERS.270.873244931
USERS.274.873252585
asd01.dbf
catalog01
dev01.dbf
example.dbf
feed01.dbf
feed02.dbf
indx01.dbf
indx02.dbf
indx03.dbf
sysaux01.dbf
system01.dbf
system02.dbf
undotbs01.dbf
undotbs02.dbf
undotbs03.dbf
undotbs04.dbf
user1.dbf
users01.dbf
users02.dbf
users03.dbf
users04.dbf
users05.dbf
users06.dbf
users07.dbf
users08.dbf
website01.dbf
website02.dbf
website03.dbf
website04.dbf
ASMCMD>
Standby :
[root@oracledrs ~]# id oracle
uid=54321(oracle) gid=54321(oinstall) groups=54321(oinstall),54322(dba)
Primary :
[root@dbn-prod-1 disks]# id oracle
uid=54321(oracle) gid=54321(oinstall) groups=54321(oinstall),54322(dba)
1- yes i have needed archived files at my primary
2- select inst_id,thread#,group# from gv$log;
Primary :
INST_ID,THREAD#,GROUP#
1,1,1
1,1,2
1,2,3
1,2,4
1,3,5
1,3,6
1,4,7
1,4,8
1,1,9
1,2,10
1,3,11
1,4,12
3,1,1
3,1,2
3,2,3
3,2,4
3,3,5
3,3,6
3,4,7
3,4,8
3,1,9
3,2,10
3,3,11
3,4,12
2,1,1
2,1,2
2,2,3
2,2,4
2,3,5
2,3,6
2,4,7
2,4,8
2,1,9
2,2,10
2,3,11
2,4,12
4,1,1
4,1,2
4,2,3
4,2,4
4,3,5
4,3,6
4,4,7
4,4,8
4,1,9
4,2,10
4,3,11
4,4,12
Standby :
INST_ID,THREAD#,GROUP#
1,1,9
1,1,2
1,1,1
1,2,3
1,2,4
1,2,10
1,3,5
1,3,6
1,3,11
1,4,12
1,4,7
1,4,8
3- That's sample from alert log since i started the standby (for standby and primary)
Standby :
alter database mount standby database
NOTE: Loaded library: /opt/oracle/extapi/64/asm/orcl/1/libasm.so
NOTE: Loaded library: System
SUCCESS: diskgroup DATA was mounted
ERROR: failed to establish dependency between database oracledrs and diskgroup resource ora.DATA.dg
ARCH: STARTING ARCH PROCESSES
Tue Mar 03 18:38:16 2015
ARC0 started with pid=128, OS id=4461
ARC0: Archival started
ARCH: STARTING ARCH PROCESSES COMPLETE
ARC0: STARTING ARCH PROCESSES
Tue Mar 03 18:38:17 2015
Successful mount of redo thread 1, with mount id 1746490068
Physical Standby Database mounted.
Lost write protection disabled
Tue Mar 03 18:38:17 2015
ARC1 started with pid=129, OS id=4464
Tue Mar 03 18:38:17 2015
ARC2 started with pid=130, OS id=4466
Tue Mar 03 18:38:17 2015
ARC3 started with pid=131, OS id=4468
Tue Mar 03 18:38:17 2015
ARC4 started with pid=132, OS id=4470
Tue Mar 03 18:38:17 2015
ARC5 started with pid=133, OS id=4472
Tue Mar 03 18:38:17 2015
ARC6 started with pid=134, OS id=4474
Tue Mar 03 18:38:17 2015
ARC7 started with pid=135, OS id=4476
Completed: alter database mount standby database
Tue Mar 03 18:38:17 2015
ARC8 started with pid=136, OS id=4478
Tue Mar 03 18:38:17 2015
ARC9 started with pid=137, OS id=4480
ARC1: Archival started
ARC2: Archival started
ARC3: Archival started
ARC4: Archival started
ARC5: Archival started
ARC6: Archival started
ARC7: Archival started
ARC8: Archival started
ARC8: Becoming the 'no FAL' ARCH
ARC2: Becoming the heartbeat ARCH
ARC2: Becoming the active heartbeat ARCH
Tue Mar 03 18:38:18 2015
Starting Data Guard Broker (DMON)
ARC9: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
Tue Mar 03 18:38:23 2015
INSV started with pid=141, OS id=4494
Tue Mar 03 18:39:11 2015
alter database recover managed standby database disconnect from session
Attempt to start background Managed Standby Recovery process (oracledrs)
Tue Mar 03 18:39:11 2015
MRP0 started with pid=142, OS id=4498
MRP0: Background Managed Standby Recovery process started (oracledrs)
started logmerger process
Tue Mar 03 18:39:16 2015
Managed Standby Recovery not using Real Time Apply
Parallel Media Recovery started with 24 slaves
Waiting for all non-current ORLs to be archived...
All non-current ORLs have been archived.
Media Recovery Waiting for thread 1 sequence 25738
Completed: alter database recover managed standby database disconnect from session
Tue Mar 03 18:41:17 2015
WARN: ARCH: Terminating pid 4476 hung on an I/O operation
Killing 1 processes with pids 4476 (Process by index) in order to remove hung processes. Requested by OS process 4224
ARCH: Detected ARCH process failure
Tue Mar 03 18:45:17 2015
ARC2: STARTING ARCH PROCESSES
Tue Mar 03 18:45:17 2015
ARC7 started with pid=127, OS id=4586
Tue Mar 03 18:45:18 2015
Fatal NI connect error 12170.
VERSION INFORMATION:
        TNS for Linux: Version 11.2.0.4.0 - Production
        Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
        TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
Time: 03-MAR-2015 18:45:18
Tracing not turned on.
Tns error struct:
    ns main err code: 12535
TNS-12535: TNS:operation timed out
    ns secondary err code: 12560
    nt main err code: 505
TNS-00505: Operation timed out
    nt secondary err code: 0
    nt OS err code: 0
Client address: <unknown>
ARC7: Archival started
ARC2: STARTING ARCH PROCESSES COMPLETE
Tue Mar 03 18:47:14 2015
alter database recover managed standby database cancel
Tue Mar 03 18:48:18 2015
Fatal NI connect error 12170.
VERSION INFORMATION:
        TNS for Linux: Version 11.2.0.4.0 - Production
        Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
        TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
Time: 03-MAR-2015 18:48:18
Tracing not turned on.
Tns error struct:
    ns main err code: 12535
TNS-12535: TNS:operation timed out
    ns secondary err code: 12560
    nt main err code: 505
TNS-00505: Operation timed out
    nt secondary err code: 0
    nt OS err code: 0
Client address: <unknown>
Tue Mar 03 18:51:18 2015
Fatal NI connect error 12170.
VERSION INFORMATION:
        TNS for Linux: Version 11.2.0.4.0 - Production
        Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
        TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
Time: 03-MAR-2015 18:51:18
Tracing not turned on.
Tns error struct:
    ns main err code: 12535
TNS-12535: TNS:operation timed out
    ns secondary err code: 12560
    nt main err code: 505
TNS-00505: Operation timed out
    nt secondary err code: 0
    nt OS err code: 0
Client address: <unknown>
Error 12170 received logging on to the standby
FAL[client, USER]: Error 12170 connecting to oracle for fetching gap sequence
MRP0: Background Media Recovery cancelled with status 16037
Errors in file /u01/app/oracle/diag/rdbms/oracledrs/oracledrs/trace/oracledrs_pr00_4500.trc:
ORA-16037: user requested cancel of managed recovery operation
Recovery interrupted!
Tue Mar 03 18:51:18 2015
MRP0: Background Media Recovery process shutdown (oracledrs)
Tue Mar 03 18:51:19 2015
Managed Standby Recovery Canceled (oracledrs)
Completed: alter database recover managed standby database cancel
Tue Mar 03 18:51:56 2015
alter database recover automatic standby database
Media Recovery Start
started logmerger process
Tue Mar 03 18:51:56 2015
Managed Standby Recovery not using Real Time Apply
Parallel Media Recovery started with 24 slaves
Media Recovery Log +DATA
Errors with log +DATA
Errors in file /u01/app/oracle/diag/rdbms/oracledrs/oracledrs/trace/oracledrs_pr00_4617.trc:
ORA-00308: cannot open archived log '+DATA'
ORA-17503: ksfdopn:2 Failed to open file +DATA
ORA-15045: ASM file name '+DATA' is not in reference form
ORA-279 signalled during: alter database recover automatic standby database...
Tue Mar 03 18:53:06 2015
db_recovery_file_dest_size of 512000 MB is 0.13% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Primary :
Tue Mar 03 17:13:43 2015
Thread 1 advanced to log sequence 26005 (LGWR switch)
Current log# 1 seq# 26005 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_1.271.849356883
Tue Mar 03 17:13:44 2015
Archived Log entry 87387 added for thread 1 sequence 26004 ID 0x66aa5a0d dest 1:
Tue Mar 03 18:00:18 2015
Thread 1 advanced to log sequence 26006 (LGWR switch)
Current log# 2 seq# 26006 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_2.270.849356883
Tue Mar 03 18:00:18 2015
Archived Log entry 87392 added for thread 1 sequence 26005 ID 0x66aa5a0d dest 1:
Tue Mar 03 18:55:33 2015
Thread 1 advanced to log sequence 26007 (LGWR switch)
Current log# 9 seq# 26007 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_9.295.853755983
Current log# 9 seq# 26007 mem# 1: +ASM_ARCHIVE/oracle/onlinelog/group_9.10902.853755985
Tue Mar 03 18:55:33 2015
Archived Log entry 87395 added for thread 1 sequence 26006 ID 0x66aa5a0d dest 1:
Tue Mar 03 19:14:22 2015
Dumping diagnostic data in directory=[cdmp_20150303191422], requested by (instance=4, osid=10234), summary=[incident=1692472].
Dumping diagnostic data in directory=[cdmp_20150303191425], requested by (instance=4, osid=10234), summary=[incident=1692473].
Tue Mar 03 20:00:06 2015
Thread 1 advanced to log sequence 26008 (LGWR switch)
Current log# 1 seq# 26008 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_1.271.849356883
Tue Mar 03 20:00:07 2015
Archived Log entry 87401 added for thread 1 sequence 26007 ID 0x66aa5a0d dest 1:
Tue Mar 03 21:00:02 2015
Thread 1 advanced to log sequence 26009 (LGWR switch)
Current log# 2 seq# 26009 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_2.270.849356883
Tue Mar 03 21:00:03 2015
Archived Log entry 87403 added for thread 1 sequence 26008 ID 0x66aa5a0d dest 1:
Thread 1 advanced to log sequence 26010 (LGWR switch)
Current log# 9 seq# 26010 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_9.295.853755983
Current log# 9 seq# 26010 mem# 1: +ASM_ARCHIVE/oracle/onlinelog/group_9.10902.853755985
Tue Mar 03 21:00:06 2015
Archived Log entry 87404 added for thread 1 sequence 26009 ID 0x66aa5a0d dest 1:
Tue Mar 03 22:00:00 2015
Setting Resource Manager plan SCHEDULER[0x32DA]:DEFAULT_MAINTENANCE_PLAN via scheduler window
Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter
Tue Mar 03 22:00:00 2015
Starting background process VKRM
Tue Mar 03 22:00:00 2015
VKRM started with pid=184, OS id=4838
Tue Mar 03 22:00:07 2015
Begin automatic SQL Tuning Advisor run for special tuning task "SYS_AUTO_SQL_TUNING_TASK"
Tue Mar 03 22:00:25 2015
Thread 1 advanced to log sequence 26011 (LGWR switch)
Current log# 1 seq# 26011 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_1.271.849356883
Tue Mar 03 22:00:26 2015
Archived Log entry 87408 added for thread 1 sequence 26010 ID 0x66aa5a0d dest 1:
Tue Mar 03 22:00:58 2015
Thread 1 advanced to log sequence 26012 (LGWR switch)
Current log# 2 seq# 26012 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_2.270.849356883
Tue Mar 03 22:01:00 2015
Archived Log entry 87412 added for thread 1 sequence 26011 ID 0x66aa5a0d dest 1:
Tue Mar 03 22:02:37 2015
Thread 1 cannot allocate new log, sequence 26013
Checkpoint not complete
Current log# 2 seq# 26012 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_2.270.849356883
Thread 1 advanced to log sequence 26013 (LGWR switch)
Current log# 9 seq# 26013 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_9.295.853755983
Current log# 9 seq# 26013 mem# 1: +ASM_ARCHIVE/oracle/onlinelog/group_9.10902.853755985
Tue Mar 03 22:02:41 2015
Archived Log entry 87415 added for thread 1 sequence 26012 ID 0x66aa5a0d dest 1:
Tue Mar 03 22:03:26 2015
Thread 1 cannot allocate new log, sequence 26014
Checkpoint not complete
Current log# 9 seq# 26013 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_9.295.853755983
Current log# 9 seq# 26013 mem# 1: +ASM_ARCHIVE/oracle/onlinelog/group_9.10902.853755985
Thread 1 advanced to log sequence 26014 (LGWR switch)
Current log# 1 seq# 26014 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_1.271.849356883
Tue Mar 03 22:03:29 2015
Archived Log entry 87416 added for thread 1 sequence 26013 ID 0x66aa5a0d dest 1:
Tue Mar 03 22:05:50 2015
Thread 1 cannot allocate new log, sequence 26015
Checkpoint not complete
Current log# 1 seq# 26014 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_1.271.849356883
Tue Mar 03 22:05:52 2015
End automatic SQL Tuning Advisor run for special tuning task "SYS_AUTO_SQL_TUNING_TASK"
Thread 1 advanced to log sequence 26015 (LGWR switch)
Current log# 2 seq# 26015 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_2.270.849356883
Tue Mar 03 22:05:54 2015
Archived Log entry 87418 added for thread 1 sequence 26014 ID 0x66aa5a0d dest 1:
Tue Mar 03 22:07:29 2015
Thread 1 cannot allocate new log, sequence 26016
Checkpoint not complete
Current log# 2 seq# 26015 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_2.270.849356883
Thread 1 advanced to log sequence 26016 (LGWR switch)
Current log# 9 seq# 26016 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_9.295.853755983
Current log# 9 seq# 26016 mem# 1: +ASM_ARCHIVE/oracle/onlinelog/group_9.10902.853755985
Tue Mar 03 22:07:33 2015
Archived Log entry 87421 added for thread 1 sequence 26015 ID 0x66aa5a0d dest 1:
Thread 1 cannot allocate new log, sequence 26017
Checkpoint not complete
Current log# 9 seq# 26016 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_9.295.853755983
Current log# 9 seq# 26016 mem# 1: +ASM_ARCHIVE/oracle/onlinelog/group_9.10902.853755985
Thread 1 advanced to log sequence 26017 (LGWR switch)
Current log# 1 seq# 26017 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_1.271.849356883
Tue Mar 03 22:07:39 2015
Archived Log entry 87422 added for thread 1 sequence 26016 ID 0x66aa5a0d dest 1:
Tue Mar 03 22:16:36 2015
Thread 1 advanced to log sequence 26018 (LGWR switch)
Current log# 2 seq# 26018 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_2.270.849356883
Tue Mar 03 22:16:37 2015
Archived Log entry 87424 added for thread 1 sequence 26017 ID 0x66aa5a0d dest 1:
Tue Mar 03 22:30:06 2015
Thread 1 advanced to log sequence 26019 (LGWR switch)
Current log# 9 seq# 26019 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_9.295.853755983
Current log# 9 seq# 26019 mem# 1: +ASM_ARCHIVE/oracle/onlinelog/group_9.10902.853755985
Tue Mar 03 22:30:07 2015
Archived Log entry 87427 added for thread 1 sequence 26018 ID 0x66aa5a0d dest 1:
Tue Mar 03 22:30:18 2015
Thread 1 advanced to log sequence 26020 (LGWR switch)
Current log# 1 seq# 26020 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_1.271.849356883
Tue Mar 03 22:30:19 2015
Archived Log entry 87428 added for thread 1 sequence 26019 ID 0x66aa5a0d dest 1:
Tue Mar 03 23:07:27 2015
Dumping diagnostic data in directory=[cdmp_20150303230727], requested by (instance=4, osid=25140), summary=[incident=1692496].
Dumping diagnostic data in directory=[cdmp_20150303230730], requested by (instance=4, osid=25140), summary=[incident=1692497].
Thanks in advance sir ,

Recover database but don't have archive log file

Hi
I use old backup set in tape and restore all datafile completed but I cannot recover that show below errror in RMAN
RMAN> recover database;
Starting recover at 08-SEP-09
using channel ORA_DISK_1
starting media recovery
unable to find archive log
archive log thread=1 sequence=29166
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 09/08/2009 21:49:36
RMAN-06054: media recovery requesting unknown log: thread 1 seq 29166 lowscn 1648727512
But in backup set and include archive log already that don't have seq 29166 that have last seg is 29165 when I tyr recover in sqlplus that show below error
SQL> recover database using backup controlfile;
ORA-00279: change 1648727512 generated at 09/05/2009 00:02:07 needed for thread
1
ORA-00289: suggestion : /oradata/archive/hrprd/1_29166_671345511.arc
ORA-00280: change 1648727512 for thread 1 is in sequence #29166
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log
'/oradata/archive/hrprd/1_29166_671345511.arc'
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 3
And I tried to open with reset log that show below error
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: '/oradata/data/hrprd/system01.dbf'
How can I do to open database?
Taohiko.

taohiko wrote:
Hi Werner
I tried and show below error
SQL> recover database using backup controlfile until cancel;
ORA-00279: change 1648727512 generated at 09/05/2009 00:02:07 needed for thread
1
ORA-00289: suggestion : /oradata/archive/hrprd/1_29166_671345511.arc
ORA-00280: change 1648727512 for thread 1 is in sequence #29166
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
CANCEL
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/oradata/data/hrprd/system01.dbf'
ORA-01112: media recovery not started
How to do next step?
TaohikoHi Taohiko
Have you made backup of all archived redo log files? If so, why this one was disappeared?
Have you applied all archived redo log files before that required archived redo log file?
Please try to recover the database using the following command:
RMAN> RESTORE DATABASE;
RMAN> RECOVER DATABASE UNTIL SEQUENCE 29166;
RMAN>ALTER DATABASE OPEN RESETLOGS;

CAPTURE process error - missing Archive log

Hi -
I am getting cannot open archived log 'xxxx.arc' message when I try to start a newly created capture process. The archive files have been moved by the DBAs.
Is there a way to set the capture process to start from a new archive ?
I tried
exec DBMS_CAPTURE_ADM.ALTER_CAPTURE ( capture_name => 'STRMADMIN_SCH_CAPTURE', start_scn =>9668840362577);
I got the new scn from DBMS_FLASHBACK.GET_SYSTEM_CHANGE_NUMBER();.
But I still get the same error.
Any ideas ?
Thanks,
Sadeepa

If you are on 9i, I know that trying to reset the scn that way won't work. You have to drop and recreate the capture process. You can leave all the rules and rulesets in place, but I think you have to prepare all of the tables again.

How to recover the database when some of the archive log file get deleted.

I am facing a problem with Oracle database, which is related to archivelogs.
Our development database is running in archivelog mode, but we don't have backups scheduled and have no recovery catalog.
When the database was in running condition, disk got full, so some archivelogs were deleted manually.
After this they restarted the DB, and now DB is not coming up. Errors are as follows:
SQL> startup
ORACLE instance started.
Total System Global Area 1444383504 bytes
Fixed Size 731920 bytes
Variable Size 486539264 bytes
Database Buffers 956301312 bytes
Redo Buffers 811008 bytes
Database mounted.
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: '/export/home/oracle/dev/ADVFRW/ADVFRW.system'
SQL> recover datafile '/export/home/oracle/dev/ADVFRW/ADVFRW.system'
ORA-00283: recovery session canceled due to errors
ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
SQL> recover database using backup controlfile;
ORA-00279: change 215548705 generated at 09/02/2008 17:06:10 needed for thread
1
ORA-00289: suggestion :
/export/home/oracle/dev/ADVFRW/ADVFRW.archivelog1/LOG_ADVFRW_1107_1.ARC
ORA-00280: change 215548705 for thread 1 is in sequence #1107
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/export/home/oracle/dev/ADVFRW/ADVFRW.archivelog1/LOG_ADVFRW_1107_1.ARC
ORA-00308: cannot open archived log
'/export/home/oracle/dev/ADVFRW/ADVFRW.archivelog1/LOG_ADVFRW_1107_1.ARC'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
CANCEL
Media recovery cancelled.
SQL>
1. How to recover the database and bring it online
Any help will be highly appreciated.
With Regards
Hemant Joshi
Edited by: hem_Kec on Sep 7, 2008 9:07 AM

Hi,
Archive log files are the copies of redolog files.As redo log files are circularly overwritten,oracle generates archive log file of the corresponding redo logfiles being overwritten.So if you have a backup that dates back to 10 am in the morning and if your database creashed at 3 pm,you cannot use the redo log files alone as they have incomplete information.To completely recover the database upto 3 pm,you need archive log files generated between 10 am to 3 pm. In your case since you are missing one archive log file,you cannot perform complete recovery and hence would suffer data loss.

Archive log error

Newbie DBA
DB: Oracle 10 g OS: windows
I have 2 databases A(production) and B(Standby- DR) . I am manually copying the archive log files from A to B and applying it .
SQL> recover standby database;
ORA-00279: change 23515270208 generated at 10/13/2010 10:59:39 needed for
thread 1
ORA-00289: suggestion :
H:\ORACLE\ORA10G\DPM\ARCHP\DPMLOG74498_0665930822_001.ARC
ORA-00280: change 23515270208 for thread 1 is in sequence #74498
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
auto
ORA-00279: change 23515555165 generated at 10/13/2010 11:43:46 needed for
thread 1
ORA-00289: suggestion :
H:\ORACLE\ORA10G\DPM\ARCHP\DPMLOG74499_0665930822_001.ARC
ORA-00280: change 23515555165 for thread 1 is in sequence #74499
ORA-00278: log file 'H:\ORACLE\ORA10G\DPM\ARCHP\DPMLOG74498_0665930822_001.ARC'
no longer needed for this recovery
ORA-00279: change 23515638382 generated at 10/13/2010 12:18:50 needed for
thread 1
ORA-00289: suggestion :
H:\ORACLE\ORA10G\DPM\ARCHP\DPMLOG74500_0665930822_001.ARC
ORA-00280: change 23515638382 for thread 1 is in sequence #74500
ORA-00278: log file 'H:\ORACLE\ORA10G\DPM\ARCHP\DPMLOG74499_0665930822_001.ARC'
no longer needed for this recovery
ORA-00279: change 23515659690 generated at 10/13/2010 12:18:55 needed for
thread 1
ORA-00289: suggestion :
H:\ORACLE\ORA10G\DPM\ARCHP\DPMLOG74501_0665930822_001.ARC
ORA-00280: change 23515659690 for thread 1 is in sequence #74501
ORA-00278: log file 'H:\ORACLE\ORA10G\DPM\ARCHP\DPMLOG74500_0665930822_001.ARC'
no longer needed for this recovery
ORA-00279: change 23516026341 generated at 10/13/2010 12:19:25 needed for
thread 1
ORA-00289: suggestion :
H:\ORACLE\ORA10G\DPM\ARCHP\DPMLOG74502_0665930822_001.ARC
ORA-00280: change 23516026341 for thread 1 is in sequence #74502
ORA-00278: log file 'H:\ORACLE\ORA10G\DPM\ARCHP\DPMLOG74501_0665930822_001.ARC'
no longer needed for this recovery
ORA-00279: change 23516535747 generated at 10/13/2010 12:20:02 needed for
thread 1
ORA-00289: suggestion :
H:\ORACLE\ORA10G\DPM\ARCHP\DPMLOG74503_0665930822_001.ARC
ORA-00280: change 23516535747 for thread 1 is in sequence #74503
ORA-00278: log file 'H:\ORACLE\ORA10G\DPM\ARCHP\DPMLOG74502_0665930822_001.ARC'
no longer needed for this recovery
ORA-00279: change 23516855012 generated at 10/13/2010 12:20:30 needed for
thread 1
ORA-00289: suggestion :
H:\ORACLE\ORA10G\DPM\ARCHP\DPMLOG74504_0665930822_001.ARC
ORA-00280: change 23516855012 for thread 1 is in sequence #74504
ORA-00278: log file 'H:\ORACLE\ORA10G\DPM\ARCHP\DPMLOG74503_0665930822_001.ARC'
no longer needed for this recovery
ORA-00279: change 23516876618 generated at 10/13/2010 12:20:42 needed for
thread 1
ORA-00289: suggestion :
H:\ORACLE\ORA10G\DPM\ARCHP\DPMLOG74505_0665930822_001.ARC
ORA-00280: change 23516876618 for thread 1 is in sequence #74505
ORA-00278: log file 'H:\ORACLE\ORA10G\DPM\ARCHP\DPMLOG74504_0665930822_001.ARC'
no longer needed for this recovery
ORA-00308: cannot open archived log
'H:\ORACLE\ORA10G\DPM\ARCHP\DPMLOG74505_0665930822_001.ARC'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
SQL>Please tell me if there is anything wrong ?
Edited by: Renjith Madhavan on Oct 13, 2010 3:00 PM

Renjith Madhavan wrote:
I was just curious if
ORA-00278: log file 'H:\ORACLE\ORA10G\DPM\ARCHP\DPMLOG74499_0665930822_001.ARC'
no longer needed for this recoveryis an error or not . Doest it mean that all ORA - messages are not errors ? I was told that the archived logs are applied successfully and no need to worry .Have a look into the error message documentation :
http://download.oracle.com/docs/cd/B19306_01/server.102/b14219/e0.htm#sthref202
"+*ORA-00278: log file "string" no longer needed for this recovery *+
+*Cause*: The specified redo log file is no longer needed for the current recovery.+
+*Action*: No action required. The archived redo log file may be removed from its current location to conserve disk space, if needed. However, the redo log file may still be required for another recovery session in the future.+"
Nicolas.

Full Backups, Level 0 Backups, and Archived Logs

We have an active Oracle server and a standby Oracle server. We keep the standby database up to date with a cron script. The script tells the active database to do 'alter system switch logfile;'. We then rsync the archived logs to our standby server and have rman apply them.
This works everyday except Monday (of course!) and it only recently started failing on Mondays. The only change was that our Sunday backups used to be 'Full' backups but are now 'level 0' backups. Ever since that change, the first attempt to apply the archived logs to the standby server after the level 0 is taken on the active server gives us something like this:
ORA-00308: cannot open archived log
'/opt/oracle/flash_recovery_area/ORCL/archivelog/2012_04_16/o1_mf_1_60519_%u_.arc'
ORA-27037: unable to obtain file status
Of course, the file is not there and doesn't exist on the active server either. And of course, the nightly level1 backups fo not give us problems applying archived logs to the standby database the rest of the week.
The only way I know to recover from this is to apply the level 0 backup or take a new level 0 and apply it. After that, all subsequent archive logs just work. Any idea why changing from Full to Level 0 would break this? The Oracle docs insist that a Level 0 is identical to a Full except that level 1s can reference them as parents. This simply cannot be true based on what I'm seeing! I really want to keep the level 0 backups in play if possible. Level 1 cumulatives wont be useful without them.

Here are the RMAN settings:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/opt/oracle/102/dbs/snapcf_ORCL.f'; # default
I'm not sure how changing ARCHIVELOG BACKUP COPIES would help. Can you give me a little more information about how that setting comes into play in this situation?
I actually don't want an archive deletion policy here. We have this done in script three days after the needed archive logs have been applied. Is it possible that the we're deleting archivelogs too soon? Would we ever need to reach back in time to previously applied archive logs to apply new ones?
The %u does resolve, but this message isn't showing it. Here is that same log entry plus a few previous entries that show it does resolve.
ORA-00279: change 1284618956 generated at 04/13/2012 15:30:05 needed for thread
1
ORA-00289: suggestion :
/opt/oracle/flash_recovery_area/ORCL/archivelog/2012_04_16/o1_mf_1_60518_%u_.arc
ORA-00280: change 1284618956 for thread 1 is in sequence #60518
ORA-00278: log file
'/opt/oracle/flash_recovery_area/ORCL/archivelog/2012_04_13/o1_mf_1_60517_7rjzox
0l_.arc' no longer needed for this recovery
ORA-00279: change 1284618958 generated at 04/13/2012 15:30:05 needed for thread
1
ORA-00289: suggestion :
/opt/oracle/flash_recovery_area/ORCL/archivelog/2012_04_16/o1_mf_1_60519_%u_.arc
ORA-00280: change 1284618958 for thread 1 is in sequence #60519
ORA-00278: log file
'/opt/oracle/flash_recovery_area/ORCL/archivelog/2012_04_13/o1_mf_1_60518_7rjzox
0x_.arc' no longer needed for this recovery
ORA-00308: cannot open archived log
'/opt/oracle/flash_recovery_area/ORCL/archivelog/2012_04_16/o1_mf_1_60519_%u_.ar
c'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3

Recovery using Full BCV backup & archive logs

Hello DBA's ,
I have Last Sunday's Full BCV (Buisness Copy Volume) backup (i.e. ..... the tablespaces were taken into Backup mode then Sync the BCV, then split the BCV , take the backup of BCV and take the tabespaces in normal mode in short what we call as HOT BACKUP ........ ) & also I am taking only archive log & control file backup Daily.
Now I want to Run my database on Different Server using the above FULL BCV & daily backed up Archive logs & Control file.
Kindly update me- Can I go for following recovery steps for above scenario.
1) Install ORACLE software on new server.
2) Restore the last Sunday's FULL BCV (Hot backup)
3) Restore the archive log from last Sunday's Full BCV backup.
4) Restore the latest backed up control file.
5) Mount the database.
6) Recover the database using backed up control file & archive logs.
7) Open the database with RESETLOGS option.
Please Guide me whether I can Fully Recover/Start database on this new server using above steps. ---OR---- " Are there any more files except data files that need to be backed up daily after Full BCV ? " ---OR ---- More suggestions are Welcome.
I want to test this scenario bcz.
a) I can't afford daily BCV due to lack of storage with current retention given by buisness.
b) I can't afford long time taken by RMAN for backup & recovery, as it disturbs my other backup shedules, also RTO should be very low as per my buisness requirement.
c) Currently we are not thinking for any another Backup options.
OS platform -- SOLARIS 10
Database version -- ORACLE 9i/10g
Atul.

Hello everybody ....
Actually I am doing the above scenario practically and I am facing the problem that when I am applying my archive logs using backup controlfile until cancel, the recovery completes upto the available Archive logs/sequence. But it throws the following error along with it ......
ORA-00279: change 7001791222 generated at 01/13/2008 07:23:42 needed for thread
1
ORA-00289: suggestion : /oracle/EPR/oraarch/1_9623_601570270.dbf
ORA-00280: change 7001791222 for thread 1 is in sequence #9623
ORA-00278: log file '/oracle/EPR/oraarch/1_9622_601570270.dbf' no longer needed
for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 7001816252 generated at 01/13/2008 12:53:05 needed for thread
1
ORA-00289: suggestion : /oracle/EPR/oraarch/1_9624_601570270.dbf
ORA-00280: change 7001816252 for thread 1 is in sequence #9624
ORA-00278: log file '/oracle/EPR/oraarch/1_9623_601570270.dbf' no longer needed
for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log '/oracle/EPR/oraarch/1_9624_601570270.dbf'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oracle/EPR/sapdata1/system_1/system.data1'
SQL> SQL> SQL> SQL> SQL> SQL> SQL>
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oracle/EPR/sapdata1/system_1/system.data1'
So, I opened my database using Last (Sunday's) full hot backup only and it opens successfully without applying any archives.
Now, my question is... why my database doesn't open with OPEN RESETLOGS option when I am recovering it using command " RECOVER DATABASE UNTIL CANCEL USING BACKUP CONTROLFILE; "
I want to recover my database upto Saturday then What should I do ?
Please help me out !
Atul.

Incomplete Recovery Fails using Full hot backup & Archive logs !!

Hello DBA's !!
I am doing on Recovery scenario where I have taken One full hot backup of my Portal Database (EPR) and Restored it on New Test Server. Also I restored Archive logs from last full hot backup for next 6 days. Also I restored the latest Control file (binary) to their original locations. Now, I started the recovery scenario as follows....
1) Installed Oracle 10.2.0.2 compatible with restored version of oracle.
2) Configured tnsnames.ora, listener.ora, sqlnet.ora with hostname of Test server.
3) Restored all Hot backup files from Tape to Test Server.
4) Restored all archive logs from tape to Test server.
5) Restored Latest Binary Control file from Tape to Test Server.
6) Now, Started recovery using following command from SQL prompt.
SQL> recover database until cancel using backup controlfile;
7) Open database after Recovery Completion using RESETLOGS option.
Now in Above scenario I completed steps upto 5) successfully. But when I execute the step 6) the recovery completes with Warning : Recovery completed but OPEN RESETLOGS may throw error " system file needs more recovery to be consistent " . Please find the following snapshot ....
ORA-00279: change 7001816252 generated at 01/13/2008 12:53:05 needed for thread
1
ORA-00289: suggestion : /oracle/EPR/oraarch/1_9624_601570270.dbf
ORA-00280: change 7001816252 for thread 1 is in sequence #9624
ORA-00278: log file '/oracle/EPR/oraarch/1_9623_601570270.dbf' no longer needed
for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log '/oracle/EPR/oraarch/1_9624_601570270.dbf'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oracle/EPR/sapdata1/system_1/system.data1'
SQL> SQL> SQL> SQL> SQL> SQL> SQL>
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oracle/EPR/sapdata1/system_1/system.data1'
Let me know What should be the reason behind recovery failure !
Note : I tried to Open the database using Last Full Hot Backup only & not applying any archives. Then Database Opens successfully. It means my Database Installation & Configuration is OK !
Please Let me know why my Incomplete Recovery using Archive logs Goes Fail ?
Atul Patil.

oh you made up a new thread so here again:
there is nothing wrong.
You restored your backup, archives etc.
you started your recovery and oracle applyed all archives but the archive
'/oracle/EPR/oraarch/1_9624_601570270.dbf'
does not exist because it represents your current online redo log file and that is not present.
the recovery process cancels by itself.
the solution is:
restart your recovery process with:
recover database until cancel using backup controlfile
and when oracle suggests you '/oracle/EPR/oraarch/1_9624_601570270.dbf'
type cancel!
now you should be able to open your database with open resetlogs.

How to online datafile of rollback segment of NO archive log available

I set offline datafile of rool back segement and rename it
but when I try to online , get error to recover
I try to recover but unfortunately all archive log was deleted ( kind of cron job in unix aotu delete these file)
Pls advice how can I set this data file online without the archive log ( while databse still up and running) Oracle version is 8i not possible to drop datafile by sql.
in roll back segment I have 3 data files as below and the rb04.dbf is offline
usr/Systems/1354RM_1_7.1_Master/databases/dbsnml/data/rbs01.dbf
/usr/Systems/1354RM_1_7.1_Master/databases/dbsnml/data/rbs03.dbf
/usr/Systems/1354RM_1_7.1_Master/databases/dbsnml/data/rbs04.dbf
sequence of what I did is below:
SQL> alter database datafile '/usr/Systems/1354RM_1/databases/dbsnml/data/rbs04.dbf' offline;
Database altered.
SQL> alter tablespace RBS rename datafile '/usr/Systems/1354RM_1/databases/dbsnml/data/rbs04.dbf' to '/usr/Systems/1354RM_1_7.1_Master/databases/dbsnml/data/rbs04.dbf';
Tablespace altered.
SQL> alter database datafile '/usr/Systems/1354RM_1_7.1_Master/databases/dbsnml/data/rbs04.dbf' online;
alter database datafile '/usr/Systems/1354RM_1_7.1_Master/databases/dbsnml/data/rbs04.dbf' online
ERROR at line 1:
ORA-01113: file 13 needs media recovery
ORA-01110: data file 13:
'/usr/Systems/1354RM_1_7.1_Master/databases/dbsnml/data/rbs04.dbf'
SQL> recover datafile '/usr/Systems/1354RM_1_7.1_Master/databases/dbsnml/data/rbs04.dbf';
ORA-00279: change 71449081 generated at 12/23/2008 20:18:05 needed for thread 1
ORA-00289: suggestion :
/usr/Systems/1354RM_1_7.1_Master/OSRES/data/warm_repl/WarmArchive/arch_1_455922.
arc
ORA-00280: change 71449081 for thread 1 is in sequence #455922
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log
'/usr/Systems/1354RM_1_7.1_Master/OSRES/data/warm_repl/WarmArchive/arch_1_455922
.arc'
ORA-27037: unable to obtain file status
HP-UX Error: 2: No such file or directory
Additional information: 3

SQL> alter tablespace RBS rename datafile '/usr/Systems/1354RM_1/databases/dbsnml/data/rbs04.dbf' to '/usr/Systems/1354RM_1_7.1_Master/databases/dbsnml/data/rbs04.dbf';Did you rename the file at OS level after you issued above command? Oracle will not rename the file at OS level.
Other than that, if you plan to change rollback segment tablespace, better create a new one and create new rollback segment in new tablespace and drop the old one.

Recovery of database with loss of archived logs

Hi,
I tried restoring the database using the standard practice, however, I am encountering errors. It looks like we are missing archive log files, but I am not sure. Could anyone provide more insight to this problem and how to recover the database?
Here are the steps we did.
SVRMGR> connect internal
Connected.
SVRMGR> startup
ORACLE instance started.
Total System Global Area 1117552144 bytes
Fixed Size 48656 bytes
Variable Size 291995648 bytes
Database Buffers 819200000 bytes
Redo Buffers 6307840 bytes
Database mounted.
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SVRMGR> recover database using backup controlfile until cancel;
ORA-00279: change 663652622 generated at 02/13/02 06:20:02 needed for thread 1
ORA-00289: suggestion : /oraclesw8_redolog/ARCHIVE_CP/infr/infr_1_13598.dbf
ORA-00280: change 663652622 for thread 1 is in sequence #13598
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
Log applied.
ORA-00279: change 663654936 generated at 02/13/02 07:04:14 needed for thread 1
ORA-00289: suggestion : /oraclesw8_redolog/ARCHIVE_CP/infr/infr_1_13599.dbf
ORA-00280: change 663654936 for thread 1 is in sequence #13599
ORA-00278: log file '/oraclesw8_redolog/ARCHIVE_CP/infr/infr_1_13598.dbf' no longer needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
AUTO
ORA-00308: cannot open archived log '/oraclesw8_redolog/ARCHIVE_CP/infr/infr_1_13599.dbf'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01195: online backup of file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oraclesw8_data00/oradata/infr/infr_system_01.dbf'

Hi
It looks like you may have to manually apply the last redo log.
SVRMGR> SELECT member FROM v$log l, v$logfile f WHERE l.group# = f.group# AND l.status = 'CURRENT';
Note the path of this log file.
SVRMGR> Recover database until cancel
When you get the message that you mentioned -
Apply the log member from the select statement above. Give it
the full path as it appears on the select statement.
SVRMGR> Alter database open resetlogs;
The system should respond with "Statement processed".
Good Luck,
Bob

ORA-16038: log 1 sequence# 1292 cannot be archived ORA-19809: limit exceede

I am getting this error when starting the database 10g
ORA-16038: log 1 sequence# 1292 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 1 thread 1:
'/usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/onlinelog/o1_mf_1_45ngtrx0_.log'
Can someone help me, it is very urgent.
Zulqarnain

It is resolved when I tried
ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE = 15G SCOPE=BOTH

Log 1 sequence# 638 cannot be archived

Hello,
I've this error when i start my OAS script and i found nothing about these error.
Could you help me to correct this error please ?
ORA-16038: log 1 sequence# 638 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 1 thread 1: '/home/oracle/oradata/orcl/redo01.log'
Then, after that:
opmnctl: starting opmn and all managed processes...
and after a long time to wait opmnctl...I obtain that :
opmnctl: starting opmn and all managed processes...
================================================================================
opmn id=rd-srv-oas:6200
1 of 2 processes started.
ias-instance id=infra.rd-srv-oas
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
ias-component/process-type/process-set:
OC4J/OC4J_SECURITY/default_island
Error
--> Process (pid=1522)
time out while waiting for a managed process to start
Log:
/home/oracle/infra/opmn/logs/OC4J~OC4J_SECURITY~default_island~1
TZ set to Europe/Paris
Oracle Enterprise Manager 10g Application Server Control Release 10.1.2.0.0
Copyright (c) 1996, 2004 Oracle Corporation. All rights reserved.
http://rd-srv-oas:1810/emd/console/aboutApplication
Starting Oracle Enterprise Manager 10g Application Server Control ...... started successfully.
opmnctl: starting opmn and all managed processes...
================================================================================
opmn id=rd-srv-oas:6201
3 of 6 processes started.
ias-instance id=portal.rd-srv-oas
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
ias-component/process-type/process-set:
OC4J/home/default_island
Error
--> Process (pid=3334)
time out while waiting for a managed process to start
Log:
/home/oracle/portal/opmn/logs/OC4J~home~default_island~1
ias-component/process-type/process-set:
OC4J/OC4J_Portal/default_island
Error
--> Process (pid=3335)
time out while waiting for a managed process to start
Log:
/home/oracle/portal/opmn/logs/OC4J~OC4J_Portal~default_island~1
ias-component/process-type/process-set:
OC4J/TestWeb/default_island
Error
--> Process (pid=3336)
time out while waiting for a managed process to start
Log:
/home/oracle/portal/opmn/logs/OC4J~TestWeb~default_island~1
TZ set to Europe/Paris
Oracle Enterprise Manager 10g Application Server Control Release 10.1.2.0.0
Copyright (c) 1996, 2004 Oracle Corporation. All rights reserved.
http://rd-srv-oas:1814/emd/console/aboutApplication
Starting Oracle Enterprise Manager 10g Application Server Control ...... started successfully.
Thanks a lot !!!
M.
Message was edited by:
Manu

[demo oracle test10]$ oerr ora 19809
19809, 00000, "limit exceeded for recovery files"
//*Cause: The limit for recovery files specified by the
//        DB_RECOVERY_FILE_DEST_SIZE was exceeded.
//*Action:The error is accompanied by 19804. See message 19804 for further
//        details.
[demo oracle test10]$ oerr ora 19804
19804, 00000, "cannot reclaim %s bytes disk space from %s limit"
// *Cause: Oracle cannot reclaim disk space of specified bytes from the
//         DB_RECOVERY_FILE_DEST_SIZE limit.
// *Action: There are five possible solutions:
//          1) Take frequent backup of recovery area using RMAN.
//          2) Consider changing RMAN retention policy.
//          3) Consider changing RMAN archivelog deletion policy.
//          4) Add disk space and increase DB_RECOVERY_FILE_DEST_SIZE.
//          5) Delete files from recovery area using RMAN.
[demo oracle test10]$Your DB is not able to archive a logfile, because of no more space in FLASHBACK area. If you have enough space on disk you can increase the value of DB_RECOVERY_FILE_DEST_SIZE parameter, if not you should take one of other actions above to reduce occupied space in directory identified by DB_RECOVERY_FILE_DEST parameter.
Anyway, you should periodically clean up the flashback area in some way.
Paul

Cannot reset archive log

Similar Messages

Maybe you are looking for