Log corruption near block 1737

hi,
i am getting an error while open the db
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-00368: checksum error in redo log block
ORA-00353: log corruption near block 1737 change 16680088 time 12/22/2008
10:40:13
ORA-00312: online log 2 thread 1: 'G:\ORACLE\ORADATA\HOTEST\REDO02.LOG'while doing an incomplete recovery it is asking for an archived file which i am not having i.e ARC_801_1.ARC.........
SQL> recover database until cancel;
ORA-00279: change 16679127 generated at 12/22/2008 10:37:11 needed for thread 1
ORA-00289: suggestion : G:\ORACLE\ARCH\ARC_801_1.ARC
ORA-00280: change 16679127 for thread 1 is in sequence #801
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
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: 'G:\ORACLE\ORADATA\HOTEST\SYSTEM01.DBF'
ORA-01112: media recovery not startedpls suggest me for the same....

I am not having a archived log of sequence no. 801 neither i am having backup, is there any other way to up the db....
SMON: enabling tx recovery
Mon Dec 22 10:37:16 2008
Database Characterset is WE8MSWIN1252
replication_dependency_tracking turned off (no async multimaster replication found)
Completed: alter database open
Corrupt block relative dba: 0x0300cc4b (file 12, block 52299)
Bad check value found during buffer read
Data in bad block -
type: 6 format: 2 rdba: 0x0300cc4b
last change scn: 0x0000.000fa127 seq: 0x1 flg: 0x06
consistency value in tail: 0xa1270601
check value in block header: 0x8f85, computed block checksum: 0xcf00
spare1: 0x0, spare2: 0x0, spare3: 0x0
Reread of rdba: 0x0300cc4b (file 12, block 52299) found valid data
Corrupt block relative dba: 0x0300cdfb (file 12, block 52731)
Bad check value found during buffer read
Data in bad block -
type: 6 format: 2 rdba: 0x0300cdfb
last change scn: 0x0000.000fa128 seq: 0x1 flg: 0x04
consistency value in tail: 0xa1280601
check value in block header: 0x446b, computed block checksum: 0x3200
spare1: 0x0, spare2: 0x0, spare3: 0x0
Reread of rdba: 0x0300cdfb (file 12, block 52731) found valid data
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     Dump file g:\oracle\admin\hotest\bdump\alert_hotest.log
Mon Dec 22 10:41:29 2008
ORACLE V9.2.0.4.0 - Production vsnsta=0
vsnsql=12 vsnxtr=3
Windows 2000 Version 5.1 Service Pack 2, CPU type 586
Mon Dec 22 10:41:29 2008
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
SCN scheme 2
Using log_archive_dest parameter default value
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 9.2.0.4.0.
System parameters with non-default values:
processes                = 150
timed_statistics         = TRUE
shared_pool_size         = 50331648
large_pool_size          = 8388608
java_pool_size           = 33554432
control_files            = G:\oracle\oradata\hotest\CONTROL01.CTL, G:\oracle\oradata\hotest\CONTROL02.CTL, G:\oracle\oradata\hotest\CONTROL03.CTL
db_block_size            = 8192
db_cache_size            = 25165824
compatible               = 9.2.0.0.0
log_archive_start        = TRUE
log_archive_dest_1       = location=G:\oracle\arch
log_archive_dest_2       = SERVICE=stand LGWR ASYNC
log_archive_dest_state_1 = ENABLE
log_archive_dest_state_2 = ENABLE
fal_server               = STAND
fal_client               = HOTEST
log_archive_format       = arc_%s_%t.arc
db_file_multiblock_read_count= 16
fast_start_mttr_target   = 300
undo_management          = AUTO
undo_tablespace          = UNDOTBS1
undo_retention           = 10800
remote_login_passwordfile= EXCLUSIVE
db_domain                =
instance_name            = hotest
dispatchers              = (PROTOCOL=TCP) (SERVICE=hotestXDB)
job_queue_processes      = 10
hash_join_enabled        = TRUE
background_dump_dest     = G:\oracle\admin\hotest\bdump
user_dump_dest           = G:\oracle\admin\hotest\udump
core_dump_dest           = G:\oracle\admin\hotest\cdump
sort_area_size           = 524288
db_name                  = hotest
open_cursors             = 300
star_transformation_enabled= FALSE
query_rewrite_enabled    = FALSE
pga_aggregate_target     = 25165824
aq_tm_processes          = 1
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4
CKPT started with pid=5
SMON started with pid=6
RECO started with pid=7
CJQ0 started with pid=8
QMN0 started with pid=9
Mon Dec 22 10:41:36 2008
starting up 1 shared server(s) ...
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=12
ARC0: Archival started
ARC1 started with pid=13
Mon Dec 22 10:41:37 2008
ARCH: STARTING ARCH PROCESSES COMPLETE
Mon Dec 22 10:41:37 2008
ARC0: Thread not mounted
Mon Dec 22 10:41:38 2008
ARC1: Archival started
Mon Dec 22 10:41:38 2008
ARC1: Thread not mounted
Mon Dec 22 10:41:38 2008
alter database mount exclusive
Mon Dec 22 10:41:43 2008
Successful mount of redo thread 1, with mount id 1003521250.
Mon Dec 22 10:41:43 2008
Database mounted in Exclusive Mode.
Completed: alter database mount exclusive
Mon Dec 22 10:41:43 2008
alter database open
Mon Dec 22 10:41:44 2008
Beginning crash recovery of 1 threads
Mon Dec 22 10:41:44 2008
Started first pass scan
ORA-368 signalled during: alter database open...
Mon Dec 22 10:42:35 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Dump file g:\oracle\admin\hotest\bdump\alert_hotest.log
Mon Dec 29 10:14:22 2008
ORACLE V9.2.0.4.0 - Production vsnsta=0
vsnsql=12 vsnxtr=3
Windows 2000 Version 5.1 Service Pack 2, CPU type 586
Mon Dec 29 10:14:22 2008
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
SCN scheme 2
Using log_archive_dest parameter default value
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 9.2.0.4.0.
System parameters with non-default values:
processes                = 150
timed_statistics         = TRUE
shared_pool_size         = 50331648
large_pool_size          = 8388608
java_pool_size           = 33554432
control_files            = G:\oracle\oradata\hotest\CONTROL01.CTL, G:\oracle\oradata\hotest\CONTROL02.CTL, G:\oracle\oradata\hotest\CONTROL03.CTL
db_block_size            = 8192
db_cache_size            = 25165824
compatible               = 9.2.0.0.0
log_archive_start        = TRUE
log_archive_dest_1       = location=G:\oracle\arch
log_archive_dest_2       = SERVICE=stand LGWR ASYNC
log_archive_dest_state_1 = ENABLE
log_archive_dest_state_2 = ENABLE
fal_server               = STAND
fal_client               = HOTEST
log_archive_format       = arc_%s_%t.arc
db_file_multiblock_read_count= 16
fast_start_mttr_target   = 300
undo_management          = AUTO
undo_tablespace          = UNDOTBS1
undo_retention           = 10800
remote_login_passwordfile= EXCLUSIVE
db_domain                =
instance_name            = hotest
dispatchers              = (PROTOCOL=TCP) (SERVICE=hotestXDB)
job_queue_processes      = 10
hash_join_enabled        = TRUE
background_dump_dest     = G:\oracle\admin\hotest\bdump
user_dump_dest           = G:\oracle\admin\hotest\udump
core_dump_dest           = G:\oracle\admin\hotest\cdump
sort_area_size           = 524288
db_name                  = hotest
open_cursors             = 300
star_transformation_enabled= FALSE
query_rewrite_enabled    = FALSE
pga_aggregate_target     = 25165824
aq_tm_processes          = 1
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4
CKPT started with pid=5
SMON started with pid=6
RECO started with pid=7
CJQ0 started with pid=8
QMN0 started with pid=9
Mon Dec 29 10:14:28 2008
starting up 1 shared server(s) ...
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=12
ARC0: Archival started
ARC1 started with pid=13
ARC1: Archival started
Mon Dec 29 10:14:30 2008
ARCH: STARTING ARCH PROCESSES COMPLETE
Mon Dec 29 10:14:30 2008
ARC1: Thread not mounted
Mon Dec 29 10:14:31 2008
ARC0: Thread not mounted
Mon Dec 29 10:14:32 2008
alter database mount exclusive
Mon Dec 29 10:14:37 2008
Successful mount of redo thread 1, with mount id 1004122632.
Mon Dec 29 10:14:37 2008
Database mounted in Exclusive Mode.
Completed: alter database mount exclusive
Mon Dec 29 10:14:37 2008
alter database open
Mon Dec 29 10:14:37 2008
Beginning crash recovery of 1 threads
Mon Dec 29 10:14:38 2008
Started first pass scan
ORA-368 signalled during: alter database open...
Mon Dec 29 10:15:29 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 10:20:44 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 10:25:54 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 10:31:09 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 10:36:24 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 10:41:40 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 10:46:55 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 10:52:10 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 10:57:26 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 11:02:41 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 11:07:56 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 11:13:05 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 11:18:15 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 11:23:30 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 11:28:39 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 11:33:49 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 11:39:04 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 11:44:19 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 11:49:35 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 11:54:44 2008
Restarting dead background process QMN0
QMN0 started with pid=15
Mon Dec 29 11:59:59 2008
Restarting dead background process QMN0
QMN0 started with pid=14
Mon Dec 29 12:03:06 2008
alter database open
Mon Dec 29 12:03:06 2008
Beginning crash recovery of 1 threads
Mon Dec 29 12:03:07 2008
Started first pass scan
ORA-368 signalled during: alter database open...
Mon Dec 29 12:05:09 2008
Restarting dead background process QMN0
QMN0 started with pid=15
Mon Dec 29 12:05:14 2008
ALTER DATABASE RECOVER database until cancel
Mon Dec 29 12:05:14 2008
Media Recovery Start
Starting datafile 1 recovery in thread 1 sequence 801
Datafile 1: 'G:\ORACLE\ORADATA\HOTEST\SYSTEM01.DBF'
Starting datafile 2 recovery in thread 1 sequence 801
Datafile 2: 'G:\ORACLE\ORADATA\HOTEST\UNDOTBS01.DBF'
Starting datafile 3 recovery in thread 1 sequence 801
Datafile 3: 'G:\ORACLE\ORADATA\HOTEST\CWMLITE01.DBF'
Starting datafile 4 recovery in thread 1 sequence 801
Datafile 4: 'G:\ORACLE\ORADATA\HOTEST\DRSYS01.DBF'
Starting datafile 5 recovery in thread 1 sequence 801
Datafile 5: 'G:\ORACLE\ORADATA\HOTEST\EXAMPLE01.DBF'
Starting datafile 6 recovery in thread 1 sequence 801
Datafile 6: 'G:\ORACLE\ORADATA\HOTEST\INDX01.DBF'
Starting datafile 7 recovery in thread 1 sequence 801
Datafile 7: 'G:\ORACLE\ORADATA\HOTEST\ODM01.DBF'
Starting datafile 8 recovery in thread 1 sequence 801
Datafile 8: 'G:\ORACLE\ORADATA\HOTEST\TOOLS01.DBF'
Starting datafile 9 recovery in thread 1 sequence 801
Datafile 9: 'G:\ORACLE\ORADATA\HOTEST\USERS01.DBF'
Starting datafile 10 recovery in thread 1 sequence 801
Datafile 10: 'G:\ORACLE\ORADATA\HOTEST\XDB01.DBF'
Starting datafile 11 recovery in thread 1 sequence 801
Datafile 11: 'G:\ORACLE\ORADATA\HOTEST\CADATA3.ORA'
Starting datafile 12 recovery in thread 1 sequence 801
Datafile 12: 'G:\ORACLE\ORADATA\HOTEST\CADATA.ORA'
Starting datafile 13 recovery in thread 1 sequence 801
Datafile 13: 'G:\ORACLE\ORADATA\HOTEST\CADATAWRO.ORA'
Starting datafile 14 recovery in thread 1 sequence 801
Datafile 14: 'G:\ORACLE\ORADATA\HOTEST\CADATANRO.ORA'
Starting datafile 15 recovery in thread 1 sequence 801
Datafile 15: 'G:\ORACLE\ORADATA\HOTEST\CADATACRO.ORA'
Starting datafile 16 recovery in thread 1 sequence 801
Datafile 16: 'G:\ORACLE\ORADATA\HOTEST\CADATAOTH.ORA'
Starting datafile 17 recovery in thread 1 sequence 801
Datafile 17: 'G:\ORACLE\ORADATA\HOTEST\CADATAERO.ORA'
Starting datafile 18 recovery in thread 1 sequence 801
Datafile 18: 'G:\ORACLE\ORADATA\HOTEST\CADATAHO.ORA'
Starting datafile 19 recovery in thread 1 sequence 801
Datafile 19: 'G:\ORACLE\ORADATA\HOTEST\CADATASRO.ORA'
Starting datafile 20 recovery in thread 1 sequence 801
Datafile 20: 'G:\ORACLE\ORADATA\HOTEST\PAYROLL.ORA'
Starting datafile 21 recovery in thread 1 sequence 801
Datafile 21: 'G:\ORACLE\ORADATA\HOTEST\ORION.ORA'
Starting datafile 22 recovery in thread 1 sequence 801
Datafile 22: 'G:\ORACLE\ORADATA\HOTEST\ATHENA.ORA'
Starting datafile 23 recovery in thread 1 sequence 801
Datafile 23: 'G:\ORACLE\ORADATA\HOTEST\CAL_YEAR_2004.ORA'
Starting datafile 24 recovery in thread 1 sequence 801
Datafile 24: 'G:\ORACLE\ORADATA\HOTEST\CAL_YEAR_2005.ORA'
Starting datafile 25 recovery in thread 1 sequence 801
Datafile 25: 'G:\ORACLE\ORADATA\HOTEST\CAL_YEAR_2006.ORA'
Starting datafile 26 recovery in thread 1 sequence 801
Datafile 26: 'G:\ORACLE\ORADATA\HOTEST\CAL_YEAR_2007.ORA'
Starting datafile 27 recovery in thread 1 sequence 801
Datafile 27: 'G:\ORACLE\ORADATA\HOTEST\CAL_YEAR_2008.ORA'
Starting datafile 28 recovery in thread 1 sequence 801
Datafile 28: 'G:\ORACLE\ORADATA\HOTEST\CAL_YEAR_2009.ORA'
Starting datafile 29 recovery in thread 1 sequence 801
Datafile 29: 'G:\ORACLE\ORADATA\HOTEST\EXAMPLE02.DBF'
Starting datafile 30 recovery in thread 1 sequence 801
Datafile 30: 'G:\ORACLE\ORADATA\HOTEST\EXAMPLE02.RAW'
Media Recovery Log
ORA-279 signalled during: ALTER DATABASE RECOVER database until cancel ...
Mon Dec 29 12:06:24 2008
ALTER DATABASE RECOVER    CANCEL
Mon Dec 29 12:06:24 2008
ORA-1547 signalled during: ALTER DATABASE RECOVER    CANCEL ...
Mon Dec 29 12:06:24 2008
ALTER DATABASE RECOVER CANCEL
ORA-1112 signalled during: ALTER DATABASE RECOVER CANCEL ...
Mon Dec 29 12:06:40 2008
alter database open resetlogs
Mon Dec 29 12:06:41 2008
ORA-1194 signalled during: alter database open resetlogs...
Mon Dec 29 12:06:47 2008
alter database open noresetlogs
Mon Dec 29 12:06:48 2008
Beginning crash recovery of 1 threads
Mon Dec 29 12:06:48 2008
Started first pass scan
ORA-368 signalled during: alter database open noresetlogs...
Mon Dec 29 12:10:24 2008
Restarting dead background process QMN0
QMN0 started with pid=15
Mon Dec 29 12:15:39 2008
Restarting dead background process QMN0
QMN0 started with pid=15
Mon Dec 29 12:20:55 2008
Restarting dead background process QMN0
QMN0 started with pid=15
Mon Dec 29 12:26:10 2008

Similar Messages

RMAN-05501: RMAN-11003 ORA-00353: log corruption near block 2048 change

Hi Gurus,
I've posted few days ago an issue I got while recreating my Dataguard.
The Main issue was while duplicating target from active database I got this errors during the recovery process.
The Restore Process Went fine, RMAN Copied the Datafiles very well, but stop when at the moment to start the recovery process from the auxiliary db
Yesterday I took one last try,
I follow same procedure, the one described in all Oracle Docs, Google and so on ... it's not a secret I guess.
The I got the same issue, same errors.
I read soemthing about archivelogs, and the Block corruption and so on, I've tried so many things (register the log... etc etc ), and than I read something about "catalog the logfile)
and that's waht I did.
But I was just connect to the target db.
contents of Memory Script:
set until scn 1638816629;
recover
standby
clone database
delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 14-MAY-13
starting media recovery
archived log for thread 1 with sequence 32196 is already on disk as file /archives/CMOVP/stby/1_32196_810397891.arc
archived log for thread 1 with sequence 32197 is already on disk as file /archives/CMOVP/stby/1_32197_810397891.arc
archived log for thread 1 with sequence 32198 is already on disk as file /archives/CMOVP/stby/1_32198_810397891.arc
archived log for thread 1 with sequence 32199 is already on disk as file /archives/CMOVP/stby/1_32199_810397891.arc
archived log for thread 1 with sequence 32200 is already on disk as file /archives/CMOVP/stby/1_32200_810397891.arc
archived log for thread 1 with sequence 32201 is already on disk as file /archives/CMOVP/stby/1_32201_810397891.arc
archived log for thread 1 with sequence 32202 is already on disk as file /archives/CMOVP/stby/1_32202_810397891.arc
archived log for thread 1 with sequence 32203 is already on disk as file /archives/CMOVP/stby/1_32203_810397891.arc
archived log for thread 1 with sequence 32204 is already on disk as file /archives/CMOVP/stby/1_32204_810397891.arc
archived log for thread 1 with sequence 32205 is already on disk as file /archives/CMOVP/stby/1_32205_810397891.arc
archived log for thread 1 with sequence 32206 is already on disk as file /archives/CMOVP/stby/1_32206_810397891.arc
archived log for thread 1 with sequence 32207 is already on disk as file /archives/CMOVP/stby/1_32207_810397891.arc
archived log for thread 1 with sequence 32208 is already on disk as file /archives/CMOVP/stby/1_32208_810397891.arc
archived log for thread 1 with sequence 32209 is already on disk as file /archives/CMOVP/stby/1_32209_810397891.arc
archived log for thread 1 with sequence 32210 is already on disk as file /archives/CMOVP/stby/1_32210_810397891.arc
archived log for thread 1 with sequence 32211 is already on disk as file /archives/CMOVP/stby/1_32211_810397891.arc
archived log for thread 1 with sequence 32212 is already on disk as file /archives/CMOVP/stby/1_32212_810397891.arc
archived log for thread 1 with sequence 32213 is already on disk as file /archives/CMOVP/stby/1_32213_810397891.arc
archived log for thread 1 with sequence 32214 is already on disk as file /archives/CMOVP/stby/1_32214_810397891.arc
archived log for thread 1 with sequence 32215 is already on disk as file /archives/CMOVP/stby/1_32215_810397891.arc
archived log for thread 1 with sequence 32216 is already on disk as file /archives/CMOVP/stby/1_32216_810397891.arc
archived log for thread 1 with sequence 32217 is already on disk as file /archives/CMOVP/stby/1_32217_810397891.arc
archived log for thread 1 with sequence 32218 is already on disk as file /archives/CMOVP/stby/1_32218_810397891.arc
archived log for thread 1 with sequence 32219 is already on disk as file /archives/CMOVP/stby/1_32219_810397891.arc
archived log for thread 1 with sequence 32220 is already on disk as file /archives/CMOVP/stby/1_32220_810397891.arc
archived log for thread 1 with sequence 32221 is already on disk as file /archives/CMOVP/stby/1_32221_810397891.arc
archived log for thread 1 with sequence 32222 is already on disk as file /archives/CMOVP/stby/1_32222_810397891.arc
archived log for thread 1 with sequence 32223 is already on disk as file /archives/CMOVP/stby/1_32223_810397891.arc
archived log file name=/archives/CMOVP/stby/1_32196_810397891.arc thread=1 sequence=32196
released channel: prm1
released channel: stby1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/14/2013 01:11:33
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '/archives/CMOVP/stby/1_32196_810397891.arc'
ORA-00283: recovery session canceled due to errors
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 2048 change 1638686297 time 05/13/2013 22:42:03
ORA-00334: archived log: '/archives/CMOVP/stby/1_32196_810397891.arc'
################# What I did: ################################
Rma target /
RMAN>catalog archivelog '/archives/CMOVP/stby/1_32196_810397891.arc';
The I connect to target and Auxiliary again :Rman target / catalog rman/rman@rman auxiliary
and I run the last content of the failing memory script:RMAN> run
set until scn 1638816629;
recover
standby
clone database
delete archivelog
And The DB start the recovery Process and my Standby complete the recovery very weel with message "Recovery Finnish or Termintaed or Completed"
The I could configure Datagurd
And I check the process and the Log Apply was on and running fine, no gaps, perfect!!!!!
How !!! Just Cataloging an "Supposed Corrupted"archive log !!!!!!
If Any ideas, that ould be great to understand this.
Rgds
Carlos

okKarol wrote:
Hi Gurus,
I've posted few days ago an issue I got while recreating my Dataguard.
The Main issue was while duplicating target from active database I got this errors during the recovery process.
The Restore Process Went fine, RMAN Copied the Datafiles very well, but stop when at the moment to start the recovery process from the auxiliary db
Yesterday I took one last try,
I follow same procedure, the one described in all Oracle Docs, Google and so on ... it's not a secret I guess.
The I got the same issue, same errors.
I read soemthing about archivelogs, and the Block corruption and so on, I've tried so many things (register the log... etc etc ), and than I read something about "catalog the logfile)
and that's waht I did.
But I was just connect to the target db.
contents of Memory Script:
set until scn 1638816629;
recover
standby
clone database
delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 14-MAY-13
starting media recovery
archived log for thread 1 with sequence 32196 is already on disk as file /archives/CMOVP/stby/1_32196_810397891.arc
archived log for thread 1 with sequence 32197 is already on disk as file /archives/CMOVP/stby/1_32197_810397891.arc
archived log for thread 1 with sequence 32198 is already on disk as file /archives/CMOVP/stby/1_32198_810397891.arc
archived log for thread 1 with sequence 32199 is already on disk as file /archives/CMOVP/stby/1_32199_810397891.arc
archived log for thread 1 with sequence 32200 is already on disk as file /archives/CMOVP/stby/1_32200_810397891.arc
archived log for thread 1 with sequence 32201 is already on disk as file /archives/CMOVP/stby/1_32201_810397891.arc
archived log for thread 1 with sequence 32202 is already on disk as file /archives/CMOVP/stby/1_32202_810397891.arc
archived log for thread 1 with sequence 32203 is already on disk as file /archives/CMOVP/stby/1_32203_810397891.arc
archived log for thread 1 with sequence 32204 is already on disk as file /archives/CMOVP/stby/1_32204_810397891.arc
archived log for thread 1 with sequence 32205 is already on disk as file /archives/CMOVP/stby/1_32205_810397891.arc
archived log for thread 1 with sequence 32206 is already on disk as file /archives/CMOVP/stby/1_32206_810397891.arc
archived log for thread 1 with sequence 32207 is already on disk as file /archives/CMOVP/stby/1_32207_810397891.arc
archived log for thread 1 with sequence 32208 is already on disk as file /archives/CMOVP/stby/1_32208_810397891.arc
archived log for thread 1 with sequence 32209 is already on disk as file /archives/CMOVP/stby/1_32209_810397891.arc
archived log for thread 1 with sequence 32210 is already on disk as file /archives/CMOVP/stby/1_32210_810397891.arc
archived log for thread 1 with sequence 32211 is already on disk as file /archives/CMOVP/stby/1_32211_810397891.arc
archived log for thread 1 with sequence 32212 is already on disk as file /archives/CMOVP/stby/1_32212_810397891.arc
archived log for thread 1 with sequence 32213 is already on disk as file /archives/CMOVP/stby/1_32213_810397891.arc
archived log for thread 1 with sequence 32214 is already on disk as file /archives/CMOVP/stby/1_32214_810397891.arc
archived log for thread 1 with sequence 32215 is already on disk as file /archives/CMOVP/stby/1_32215_810397891.arc
archived log for thread 1 with sequence 32216 is already on disk as file /archives/CMOVP/stby/1_32216_810397891.arc
archived log for thread 1 with sequence 32217 is already on disk as file /archives/CMOVP/stby/1_32217_810397891.arc
archived log for thread 1 with sequence 32218 is already on disk as file /archives/CMOVP/stby/1_32218_810397891.arc
archived log for thread 1 with sequence 32219 is already on disk as file /archives/CMOVP/stby/1_32219_810397891.arc
archived log for thread 1 with sequence 32220 is already on disk as file /archives/CMOVP/stby/1_32220_810397891.arc
archived log for thread 1 with sequence 32221 is already on disk as file /archives/CMOVP/stby/1_32221_810397891.arc
archived log for thread 1 with sequence 32222 is already on disk as file /archives/CMOVP/stby/1_32222_810397891.arc
archived log for thread 1 with sequence 32223 is already on disk as file /archives/CMOVP/stby/1_32223_810397891.arc
archived log file name=/archives/CMOVP/stby/1_32196_810397891.arc thread=1 sequence=32196
released channel: prm1
released channel: stby1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/14/2013 01:11:33
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '/archives/CMOVP/stby/1_32196_810397891.arc'
ORA-00283: recovery session canceled due to errors
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 2048 change 1638686297 time 05/13/2013 22:42:03
ORA-00334: archived log: '/archives/CMOVP/stby/1_32196_810397891.arc'
################# What I did: ################################
Rma target /
RMAN>catalog archivelog '/archives/CMOVP/stby/1_32196_810397891.arc';
The I connect to target and Auxiliary again :Rman target / catalog rman/rman@rman auxiliary
and I run the last content of the failing memory script:RMAN> run
set until scn 1638816629;
recover
standby
clone database
delete archivelog
And The DB start the recovery Process and my Standby complete the recovery very weel with message "Recovery Finnish or Termintaed or Completed"
The I could configure Datagurd
And I check the process and the Log Apply was on and running fine, no gaps, perfect!!!!!
How !!! Just Cataloging an "Supposed Corrupted"archive log !!!!!!
If Any ideas, that ould be great to understand this.
Rgds
CarlosHi,
Can you change standby database archive destination from /archives/CMOVP/stby/ other disk?
I think this problem on your disk.
Mahir
p.s. I remember you before thread, too

Log Corruption Issue

I erceived the following error in my alert log file:
Errors in file /app/oracle/diag/rdbms/peptest/PEPTEST1/trace/PEPTEST1_ora_8981.trc (incident=651420):
ORA-00353: log corruption near block 79361 change 6409669490 time 07/17/2013 11:59:33
ORA-00334: archived log: '+FLASH/peptest/archivelog/2013_07_17/thread_1_seq_118356.469.821016003'
ORA-07445: exception encountered: core dump [kzvd_objprivCheck()+1622] [SIGSEGV] [ADDR:0x38] [PC:0x193ECBE] [Address not mapped to object] []
Incident details in: /app/oracle/diag/rdbms/peptest/PEPTEST1/incident/incdir_651420/PEPTEST1_ora_8981_i651420.trc
The database version is Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production running on Linux wwhpepotst1 2.6.18-128.el5 #1 SMP Wed Jan 21 08:45:05 EST 2009 x86_64 x86_64 x86_64 GNU/Linux.
This is a RAC database with ASM.
The following is the extract from the trace file:
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x38] [PC:0x193ECBE, kzvd_objprivCheck()+1622]
Incident 651419 created, dump file: /app/oracle/diag/rdbms/peptest/PEPTEST1/incident/incdir_651419/PEPTEST1_ora_8981_i651419.trc
ORA-07445: exception encountered: core dump [kzvd_objprivCheck()+1622] [SIGSEGV] [ADDR:0x38] [PC:0x193ECBE] [Address not mapped to obj
ect] []
Incident 651420 created, dump file: /app/oracle/diag/rdbms/peptest/PEPTEST1/incident/incdir_651420/PEPTEST1_ora_8981_i651420.trc
ORA-00353: log corruption near block 79361 change 6409669490 time 07/17/2013 11:59:33
ORA-00334: archived log: '+FLASH/peptest/archivelog/2013_07_17/thread_1_seq_118356.469.821016003'
ORA-07445: exception encountered: core dump [kzvd_objprivCheck()+1622] [
Can I please have a suggestion on how to procced with resolving this issue?

submit Service Request to My Oracle Support

How to practice "Archived log sequences loss- Block corruptions recovery"

Hello,
Prepare and test a recovery scenarios
- System Tablespace loss
- Online Redolog loss
- Controlfile loss
- Data Tablespace loss
- Single/multiple datafile loss
- Archived log sequences loss- Block corruptions recovery
- Total loss (database)
- Total loss (server = database/software/parameter files)
11g on windows
I am practicing my rman recovery and found this list of recovery scenarios. I have completed all scenarios
besides "Archived log sequences loss- Block corruptions recovery"
How do I break the database for the snenario "Archived log sequences loss- Block corruptions recovery"?
Do I delete the acr.001 files in directory I:\oracle\product\11.1.0\db_1\RDBMS? Then recovery as far forward as I can?
thanks for your help.

thanks for the tips
11g on windows 2003
I broke the database like this:
rman backup
shutdown immediate;
deleted datafile 5
delete most recent archivelogs seq 5 and 6;
recovered like this:
startup mount;
restore datafile 5;
recover datafile 5;
alter database open;
This does not seem correct? Did this also apply my archivelogs seq 5 and 6? Should I also do a point in time recovery?
Should I also run this?
run (set until sequence 6 thread 1; restore database; recover database;)
thanks for any help

ORA-00333: redo log read error block

ORA-01033: ORACLE initialization or shutdown in progress ...
/ as sysdba
SQL> shutdown immediate;
SQL> startup nomount;
SQL> alter database mount;
SQL> alter database open;
ORA-00333: redo log read error block 8299 count 8192
SQL> SELECT * FROM V$VERSION;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Product
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
TNS for 32-bit Windows: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
SQL> select group#,members,THREAD, STATUS,ARCHIVED,BYTES,FIRST_TIME,FIRST_CHAGE#,SEQUENCE# from v$log;
GROUP# MEMBERS,THREAD,STATUS,ARCHIVED,BYTES,FIRST_TIME,FIRST_CHAGE#,SEQUENCE#
1 1 1 CURRENT NO 52428800 29-FEB-12 1597643 57
2 1 1 INACTIVE NO 52428800 29-FEB-12 1573462 56
Dump file c:\oraclexe\app\oracle\admin\xe\bdump\alert_xe.log
Wed Feb 29 19:46:38 2012
Recovery of Online Redo Log: Thread 1 Group 1 Seq 56 Reading mem 0
Mem# 0 errs 0: C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_1_7LZYZK8S_.LOG
Wed Feb 29 19:46:40 2012
Completed redo application
Wed Feb 29 19:46:40 2012
Completed crash recovery at
Thread 1: logseq 56, block 6568, scn 1597642
270 data blocks read, 270 data blocks written, 1460 redo blocks read
Wed Feb 29 19:46:43 2012
Thread 1 advanced to log sequence 57
Thread 1 opened at log sequence 57
Current log# 2 seq# 57 mem# 0: C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_7LZYZL5V_.LOG
Successful open of redo thread 1
Wed Feb 29 19:46:43 2012
SMON: enabling cache recovery
Wed Feb 29 19:46:55 2012
Successfully onlined Undo Tablespace 1.
Wed Feb 29 19:46:55 2012
SMON: enabling tx recovery
Wed Feb 29 19:46:56 2012
Database Characterset is AL32UTF8
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=19, OS id=3024
Wed Feb 29 19:47:09 2012
Completed: alter database open
Wed Feb 29 19:47:14 2012
db_recovery_file_dest_size of 10240 MB is 0.98% 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.
Wed Feb 29 20:33:30 2012
MMNL absent for 1537 secs; Foregrounds taking over
Wed Feb 29 20:33:31 2012
MMNL absent for 1540 secs; Foregrounds taking over
Wed Feb 29 20:33:31 2012
MMNL absent for 1540 secs; Foregrounds taking over
MMNL absent for 1540 secs; Foregrounds taking over
Wed Feb 29 20:33:32 2012
MMNL absent for 1540 secs; Foregrounds taking over
Wed Feb 29 20:33:33 2012
MMNL absent for 1540 secs; Foregrounds taking over
Wed Feb 29 21:45:24 2012
MMNL absent for 4318 secs; Foregrounds taking over
MMNL absent for 4318 secs; Foregrounds taking over
MMNL absent for 4322 secs; Foregrounds taking over
Dump file c:\oraclexe\app\oracle\admin\xe\bdump\alert_xe.log
Wed Feb 29 22:30:01 2012
ORACLE V10.2.0.1.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows XP Version V5.1 Service Pack 3, v.3244
CPU : 2 - type 586, 2 Physical Cores
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:3097M/3546M, Ph+PgF:5143M/5429M, VA:1943M/2047M
Wed Feb 29 22:30:01 2012
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =10
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
sessions = 49
__shared_pool_size = 201326592
__large_pool_size = 8388608
__java_pool_size = 4194304
__streams_pool_size = 0
spfile = C:\ORACLEXE\APP\ORACLE\PRODUCT\10.2.0\SERVER\DBS\SPFILEXE.ORA
sga_target = 805306368
control_files = C:\ORACLEXE\ORADATA\XE\CONTROL.DBF
__db_cache_size = 587202560
compatible = 10.2.0.1.0
db_recovery_file_dest = C:\oraclexe\app\oracle\flash_recovery_area
db_recovery_file_dest_size= 10737418240
undo_management = AUTO
undo_tablespace = UNDO
remote_login_passwordfile= EXCLUSIVE
dispatchers = (PROTOCOL=TCP) (SERVICE=XEXDB)
shared_servers = 4
local_listener = (ADDRESS=(PROTOCOL=TCP)(HOST=winsp3ue)(PORT=1522))
job_queue_processes = 4
audit_file_dest = C:\ORACLEXE\APP\ORACLE\ADMIN\XE\ADUMP
background_dump_dest = C:\ORACLEXE\APP\ORACLE\ADMIN\XE\BDUMP
user_dump_dest = C:\ORACLEXE\APP\ORACLE\ADMIN\XE\UDUMP
core_dump_dest = C:\ORACLEXE\APP\ORACLE\ADMIN\XE\CDUMP
db_name = XE
open_cursors = 300
os_authent_prefix =
pga_aggregate_target = 268435456
PMON started with pid=2, OS id=2176
PSP0 started with pid=3, OS id=2204
MMAN started with pid=4, OS id=2208
DBW0 started with pid=5, OS id=2212
LGWR started with pid=6, OS id=2220
CKPT started with pid=7, OS id=2240
SMON started with pid=8, OS id=2460
RECO started with pid=9, OS id=2464
CJQ0 started with pid=10, OS id=2480
MMON started with pid=11, OS id=2484
Wed Feb 29 22:30:02 2012
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=12, OS id=2492
Wed Feb 29 22:30:02 2012
starting up 4 shared server(s) ...
Oracle Data Guard is not available in this edition of Oracle.
Wed Feb 29 22:30:02 2012
alter database mount exclusive
Wed Feb 29 22:30:06 2012
Setting recovery target incarnation to 2
Wed Feb 29 22:30:06 2012
Successful mount of redo thread 1, with mount id 2657657770
Wed Feb 29 22:30:06 2012
Database mounted in Exclusive Mode
Completed: alter database mount exclusive
Wed Feb 29 22:30:07 2012
alter database open
Wed Feb 29 22:30:07 2012
Beginning crash recovery of 1 threads
Wed Feb 29 22:30:07 2012
Started redo scan
Wed Feb 29 22:30:15 2012
Errors in file c:\oraclexe\app\oracle\admin\xe\udump\xe_ora_2544.trc:
ORA-00333: redo log read error block 10347 count 6144
ORA-00312: online log 2 thread 1: 'C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_7LZYZL5V_.LOG'
ORA-27070: async read/write failed
OSD-04016: Error queuing an asynchronous I/O request.
O/S-Error: (OS 23) Data error (cyclic redundancy check).
Waiting for Help
Regards

Errors in file c:\oraclexe\app\oracle\admin\xe\udump\xe_ora_2544.trc:
ORA-00333: redo log read error block 10347 count 6144
ORA-00312: online log 2 thread 1: 'C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_7LZYZL5V_.LOG'
ORA-27070: async read/write failed
OSD-04016: Error queuing an asynchronous I/O request.
O/S-Error: (OS 23) Data error (cyclic redundancy check).Might your redo log file is corrupted or not exist, check physically. -> C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_7LZYZL5V_.LOG
is it archivelog mode?
perform fake recovery and open resetlogs.

Corrupting the block to continue recovery in physical standby

Hi,
Just like to inquire how I will be able to corrupt the block to be able to continue the recovery in the physical standby.
DB Version: 11.1.0.7
Database Type: Data Warehouse
The setup we have is primary database and standby database, we are not using dataguard, and our standby setup is another physical copy of production which act as standby and being sync using script that being run from time to time to apply the archive log came from production (its not configured to sync using ARCH or LGWR and its corresponding configurations).
Then, the standby database is not sync due to errors encountered while trying to apply the archive log, error is below:
Fri Feb 11 05:50:59 2011
ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
ALTER DATABASE RECOVER CONTINUE DEFAULT
Media Recovery Log /u01/archive/<sid>/1_50741_651679913.arch
Fri Feb 11 05:52:06 2011
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x7FFFD2F18FF8] [PC:0x60197E0, kdr9ir2rst0()+326]
Errors in file /u01/app/oracle/diag/rdbms/<sid>/<sid>/trace/<sid>pr0028085.trc (incident=631460):
ORA-07445: exception encountered: core dump [kdr9ir2rst0()+326] [SIGSEGV] [ADDR:0x7FFFD2F18FF8] [PC:0x60197E0] [Address not mapped to object] []
Incident details in: /u01/app/oracle/diag/rdbms/<sid>/<sid>/incident/incdir_631460/<sid>pr0028085_i631460.trc
Fri Feb 11 05:52:10 2011
Trace dumping is performing id=[cdmp_20110211055210]
Fri Feb 11 05:52:14 2011
Sweep Incident[631460]: completed
Fri Feb 11 05:52:17 2011
Slave exiting with ORA-10562 exception
Errors in file /u01/app/oracle/diag/rdbms/<sid>/<sid>/trace/<sid>pr0028085.trc:
ORA-10562: Error occurred while applying redo to data block (file# 36, block# 1576118)
ORA-10564: tablespace <tablespace name>
ORA-01110: data file 36: '/u02/oradata/<sid>/<datafile>.dbf'
ORA-10561: block type 'TRANSACTION MANAGED DATA BLOCK', data object# 14877145
ORA-00607: Internal error occurred while making a change to a data block
ORA-00602: internal programming exception
ORA-07445: exception encountered: core dump [kdr9ir2rst0()+326] [SIGSEGV] [ADDR:0x7FFFD2F18FF8] [PC:0x60197E0] [Address not mapped to object] []
Based on the error log it seems we are hitting some bug from metalink (document id 460169.1 and 882851.1)
my question is, the datafile # is given, block# is known too and the data object is also identified. I just verified that object is not that important, is there a way to set the block# to corrupted to be able the recovery to continue? Then I will just drop the table from production so that will also happen in standby, and the block corrupted will be gone too. Is this feasible?
If its not, can you suggest what's next I can do so the the physical standby will be able to sync again to prod aside from rebuilding the standby?
Please take note that I also tried to dbv the file to confirm if there is marked as corrupted and the result for that datafile is also good:
dbv file=/u02/oradata/<sid>/<datafile>_19.dbf logfile=dbv_file_36.log blocksize=16384
oracle@<server>:[~] $ cat dbv_file_36.log
DBVERIFY: Release 11.1.0.7.0 - Production on Sun Feb 13 04:35:28 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved.
DBVERIFY - Verification starting : FILE = /u02/oradata/<sid>/<datafile>_19.dbf
DBVERIFY - Verification complete
Total Pages Examined : 3840000
Total Pages Processed (Data) : 700644
Total Pages Failing (Data) : 0
Total Pages Processed (Index): 417545
Total Pages Failing (Index): 0
Total Pages Processed (Other): 88910
Total Pages Processed (Seg) : 0
Total Pages Failing (Seg) : 0
Total Pages Empty : 2632901
Total Pages Marked Corrupt : 0
Total Pages Influx : 0
Total Pages Encrypted : 0
Highest block SCN : 3811184883 (1.3811184883)
Any help is really appreciated. I hope to hear feedback from you.
Thanks

damorgan, i understand the opinion.
just new with the organization and just inherit a data warehouse database without rman backup. I am still setting up the rman backup thats why i can't use rman to resolve the issue, the only i have is physical standby and its not a standby that automatically sync using dataguard or standard standby setup, i am just checking solution that is applicable in the current situation

Unable to drop materialized view with corrupted data blocks

Hi,
The alert log of our database is giving this message
Wed Jan 31 05:23:13 2007
ORACLE Instance mesh (pid = 9) - Error 1578 encountered while recovering transaction (6, 15) on object 13355.
Wed Jan 31 05:23:13 2007
Errors in file /u01/app/oracle/admin/mesh/bdump/mesh_smon_4369.trc:
ORA-01578: ORACLE data block corrupted (file # 5, block # 388260)
ORA-01110: data file 5: '/u03/oradata/mesh/mview.dbf'
No one is using this mview still oracle is trying to recover this transaction (6, 15).
when i tried to drop this mview it gives me this error
ERROR at line 1:
ORA-01578: ORACLE data block corrupted (file # 5, block # 388260)
ORA-01110: data file 5: '/u03/oradata/mesh/mview.dbf'
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2255
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2461
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2430
ORA-06512: at line 1
I have tried to fix the corrupted data blocks by using dbms_repair package, but of no use.
I have marked this block to be skipped by using dbms_repair.skip_block but still unable to drop it.
Please suggest what should I do?
Thanks in advance
Anuj

You are lucky if only your undesirable MV is affected by theese corrupted blocks. This is an advice to do a complete-super-full-hot-cold-middle backup of ypur database and search for any disk for a "possible replace".
God save us!

Redo log corruption

In a 2 node RAC Node1 crashes due to the online redo-log file corruption.
During this scenario...,Node2 should perform instance recovery; but since redo-log is corrupted, it cannot do the instance recovery.
what will happen at this point ? Will the other node2 continue working ?

please note that I hav'nt tested this to validate this ..
this is a theoritical answer based on what I believe how it might work ..
a) Node:2 attempts to perform an Instance Recovery by reading the Shared
Redo Log threads of Node:1
b) It runs into the same corrupt Redolog block messages and reports an
Internal error { ora-00600 / ora-07445 }
c) Depending on whether it was a fatal or non-fatal error , Node:2 might crash or
continue to work .. if it is the latter , everytime any access is needed to blocks
which still have those uncommitted transactions from Node:1 , you would
see an error / trace generated ..
Vishwa

Ora-00333 redo log read error block on 11g express

Hi all
I have error
ora-00333 redo log read error block
is there any solution for this?
And I was type
SQL> recovery database until cancel;
but error still exist?
any idea
regards
Gordan

1. Check the OS for performance issues > CentOS 5.6 64 bytes (Space use 9Gbytes of 250gBytes) (Virtual Machine )
decrease the size of the redo logs > ? How to do this? -- any reference
set disk_async_io= false in the pfile > ? How to do this? -- any reference
regards
Gordan
Edited by: useruseruser on Oct 25, 2011 9:24 PM
Edited by: useruseruser on Oct 25, 2011 9:25 PM

ORA-00333: redo log read error block 69855 count 8192

Hello Guys,
where importing a dump to newly created database 10gR2 on Linux i got this error:
ORA-00333: redo log read error block 69855 count 8192
By searching this error, i found that I need to do recovery, but i don't have any backup of this database.
Is there any easy solution for this error?
Regards, Imran

misterimran wrote:
Hello Guys,
where importing a dump to newly created database 10gR2 on Linux i got this error:
ORA-00333: redo log read error block 69855 count 8192
By searching this error, i found that I need to do recovery, but i don't have any backup of this database.
Is there any easy solution for this error?no
00333, 00000, "redo log read error block %s count %s"
// *Cause: An IO error occurred while reading the log described in the
// accompanying error.
// *Action: Restore accessibility to file, or get another copy of the file.what additional clues exist with alert_SID.log file?
do as below so we can know complete Oracle version & OS name.
Post via COPY & PASTE complete results of
SELECT * from v$version;

ORA-00333: redo log read error block 283081 count 8192

I am starting the database..it mount but after that it gives me this error
ORA-00333: redo log read error block 283081 count 8192
Below are the contents of alert Log.._Please advice_
Completed: ALTER DATABASE MOUNT
Tue Jan 20 10:24:45 2009
ALTER DATABASE OPEN
Tue Jan 20 10:24:45 2009
Beginning crash recovery of 1 threads
parallel recovery started with 2 processes
Tue Jan 20 10:24:45 2009
Started redo scan
Tue Jan 20 10:25:00 2009
Errors in file /d01/oracle/PROD1/db/tech_st/10.2.0/admin/PROD1_prod1/udump/prod1_ora_32356.trc:
ORA-00333: redo log read error block 283081 count 8192
ORA-00312: online log 2 thread 1: '/d01/oracle/PROD1/db/apps_st/data/log02a.dbf'
ORA-27072: File I/O error
Linux-x86_64 Error: 2: No such file or directory
Additional information: 4
Additional information: 283081
Additional information: 257536
Tue Jan 20 10:25:16 2009
Errors in file /d01/oracle/PROD1/db/tech_st/10.2.0/admin/PROD1_prod1/udump/prod1_ora_32356.trc:
ORA-00333: redo log read error block 283081 count 8192
ORA-00312: online log 2 thread 1: '/d01/oracle/PROD1/db/apps_st/data/log02a.dbf'
ORA-27091: unable to queue I/O
ORA-27072: File I/O error
Linux-x86_64 Error: 2: No such file or directory
Additional information: 4
Additional information: 283081
Additional information: 257536
Tue Jan 20 10:25:31 2009

I did what Prabhu told me..But i recovered using backup controlfile and when i was asked to apply logs..i applied my oldest logs and it worked
Like i have two groups with two members each
I applied log1a.dbf and it said media recovery completee
I opened the database But then it started giving me errors for undo tablespace
I made another undo tablespace..tried dropping the old one but it did not permitted as it had some segments with status "needs recovery"
Than i added this parameter in pfile with the correupted segment and than tried to drop the segment but it still did not permit
corruptedrollback_segments =(corrupted_undo segment_name)
Next what i did was I mounted the database, ran another session of media recovery and opened the databse using resetlogs
Than i dropped the old undo and it went through successfully..
If you think anything i did wrong than please advice..
I hope this action plans helps you in case you come across same errors some day
I would be very thankful if you can refer me a document of recovery which covers all kinds of recoveries and scenarios and commands too
Thanks alot

ORA-00333: redo log read error block 65538 count 8192

Hi,
I wanted to alter user hr's password, but I couldn't open the database first. What should I do? Here is my demo: Thank you for your response.
C:\>sqlplus /nolog
SQL*Plus: Release 9.2.0.1.0 - Production on Sun May 16 12:12:43 2004
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
SQL> connect sys/oracle as sysdba
Connected.
SQL> show user
USER is "SYS"
SQL> select * from v$controlfile;
STATUS
NAME
C:\ORACLE\ORADATA\SARAH\CONTROL01.CTL
C:\ORACLE\ORADATA\SARAH\CONTROL02.CTL
C:\ORACLE\ORADATA\SARAH\CONTROL03.CTL
SQL> select * from dba_users;
select * from dba_users
ERROR at line 1:
ORA-01219: database not open: queries allowed on fixed tables/views only
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-00333: redo log read error block 65538 count 8192
SQL> desc v$instance
Name Null? Type
INSTANCE_NUMBER NUMBER
INSTANCE_NAME VARCHAR2(16)
HOST_NAME VARCHAR2(64)
VERSION VARCHAR2(17)
STARTUP_TIME DATE
STATUS VARCHAR2(12)
PARALLEL VARCHAR2(3)
THREAD# NUMBER
ARCHIVER VARCHAR2(7)
LOG_SWITCH_WAIT VARCHAR2(11)
LOGINS VARCHAR2(10)
SHUTDOWN_PENDING VARCHAR2(3)
DATABASE_STATUS VARCHAR2(17)
INSTANCE_ROLE VARCHAR2(18)
ACTIVE_STATE VARCHAR2(9)
SQL> select instance_name, status from v$instance;
INSTANCE_NAME STATUS
sarah MOUNTED
SQL>
*******************************

I did what Prabhu told me..But i recovered using backup controlfile and when i was asked to apply logs..i applied my oldest logs and it worked
Like i have two groups with two members each
I applied log1a.dbf and it said media recovery completee
I opened the database But then it started giving me errors for undo tablespace
I made another undo tablespace..tried dropping the old one but it did not permitted as it had some segments with status "needs recovery"
Than i added this parameter in pfile with the correupted segment and than tried to drop the segment but it still did not permit
corruptedrollback_segments =(corrupted_undo segment_name)
Next what i did was I mounted the database, ran another session of media recovery and opened the databse using resetlogs
Than i dropped the old undo and it went through successfully..
If you think anything i did wrong than please advice..
I hope this action plans helps you in case you come across same errors some day
I would be very thankful if you can refer me a document of recovery which covers all kinds of recoveries and scenarios and commands too
Thanks alot

Block corruption에서 physial block corruption과 soft block corruption 의 차이점

어느 분께서 저에게 block corruption에 대한 질문을 하셨는데
그래서 솔루션을 제시해주었고 block dump를 보니 아래와 같았습니다.
(1번덤프) 제가 잘못 진단한 block dump(soft corrupt로 판단했는데 raid5의
디스크가 나간 physical corrupt이네요)
*** 2007-03-06 09:54:33.103
Start dump data blocks tsn: 6 file#: 6 minblk 102032 maxblk 102032
buffer tsn: 6 rdba: 0x01818e90 (6/102032)
scn: 0x056c.f689329c seq: 0x01 flg: 0x06 tail: 0xa0cf0000
frmt: 0x02 chkval: 0x7675 type: 0x06=trans data
Hex dump of corrupt header 2 = BROKEN
이었습니다.
그런데 저는 이미 이전에 physical block corruption을 경험 한 후
아래와 같이 dump를 떠서 확인한 결과 여러문서를 찾아본 후
이와같이 판단하였습니다.
(2번 덤프) physical corrupt로 확인된 덤프
- 아래의 scn: 0x0000.00000000 seq: 0xff flg: 0x00 tail: 0x000006ff
에서 SCN이 0x0000 이고 seq값이 UB1MAXVAL-1 이 아니므로
physical block corruption 임을 확인
*** SESSION ID:(25.59041) 2005-12-12 11:41:13.132
Start dump data blocks tsn: 7 file#: 8 minblk 169994 maxblk 169994
buffer tsn: 7 rdba: 0x0202980a (8/169994)
scn: 0x0000.00000000 seq: 0xff flg: 0x00 tail: 0x000006ff
frmt: 0x02 chkval: 0x0000 type: 0x06=trans data
Block header dump: 0x0202980a
Object id on Block? Y
seg/obj: 0xef9 csc: 0x00.8c13d2b itc: 2 flg: O typ: 2 - INDEX
fsl: 2 fnx: 0x2024b0f ver: 0x01
Itl Xid Uba Flag Lck Scn/Fsc
0x01 xid: 0x0001.052.0001888b uba: 0x00c07725.2482.02 C--- 0 scn 0x0000.083a0f80
0x02 xid: 0x0007.038.0001a196 uba: 0x00c07574.1f28.0b ---- 232 fsc 0x0f57.00000000
질문..
physial block corruption과 soft block corruption 인지의 여부를 block dump를
통해서 알고 싶은데요. 기존에 제가 잘못 알고 있는 것 같습니다.

좀 이상한 부분이 있어서 직접 login 하여서 조사해보았습니다.
alert 에러 코드는
Errors in file /app/oracle/product/10.2.0/admin/TEST_T_ktrp4vpe/bdump/test_t_smon_12714.trc:
ORA-00604: error occurred at recursive SQL level 1
ORA-01578: ORACLE data block corrupted (file # 2, block # 2714)
ORA-01110: data file 2: '/test_tdata/SYSTEM04.dbf'
상기로 메타 링크를 찾아보면...
제목: FAQ: Physical Corruption
문서 ID: 공지:403747.1 유형: FAQ
(a) ORA-01578 - This error explains physical structural damage with a particular block.
(b) ORA-08103 - This error is a logical corruption error for a particular data block.
(c) ORA-00600 [2662] - This error is related to block corruption , and occurs due to a higher SCN than of database SCN.
-- 좀 이상한게 physical corruption 이란 문서내에
physical corrupt 와 logical corrupt 를 분류하는게 좀 이상한데 ㅡ_ㅡ;
a 항목이라, physical structual damage ... 자연스럽게 physcial corrupt 로 보입니다. dump 내용으로 제가 판독이 안되고, alert 의 error code 로는
physical corrupt 로 보이는데..
alert 의 error code 와 dump 의 내용이 상이 할수 있는건가요 ?
글 수정:
darkturtle

Corrupt logical block

I want to check logical block corruption and repair it with dbms_repair package.
For that first i need to corrupt block logically.
How to corrupt oracle database table block logically? Is there any procedure to do that?
Thanks,

Hello,
Thanks for you resposes.
I tried to corrupt datablock by editing datafile and remove some data and add some data.
1. Execurted below rman commad
RMAN> backup validate check logical database;
Output show block is corrupted.
Below query is also listing corrupted blocks.
SQL> select * from v$database_block_corruption;
But when i am checking corruption with dbms_repair packges it doesn't list any corruption.
SET SERVEROUTPUT ON
DECLARE num_corrupt INT;
BEGIN
num_corrupt := 0;
DBMS_REPAIR.CHECK_OBJECT (
SCHEMA_NAME => 'TEST',
OBJECT_NAME => 'TEST1',
REPAIR_TABLE_NAME => 'REPAIR_TABLE',
CORRUPT_COUNT => num_corrupt);
DBMS_OUTPUT.PUT_LINE('number corrupt: ' || TO_CHAR (num_corrupt));
END;
Please let me know any other scenarios to corrupt LOGICAL block.
Thanks,

IPAM - Event Log Access Status: Blocked (DHCP)

Hi,
I've setup IPAM on a fresh server in our domain. Setup looks like this:
DC1 - DC,DNS,DHCP (Server 2008 R2)
DC2 - DC,DNS,DHCP (Server 2008 R2)
IPAM1 - IPAM Server (Server 2012)
Provisioning was done via GPO. GPO's were successfully applied on both servers. All three servers are in the same subnet and Windows Firewall is disabled for all of them. After setting the status to managed I still get "Event Log Access Status: Blocked
(DHCP)", everything else is unblocked. "IPAMUG" was added both to "Event Log Readers" and "DHCP Users". I've been trying to solve this for a few days now, even retried provisioning, but nothing seems to unblock this.
It would be really nice if someone could help me out.
Thanks

Hi,
Thank you for the post.
Please check that the firewall rules for the target server have been set as per IPAM Access Settings of this
guide. And also check that the servers have been correctly provisioned refer to the section
Manual IPAM Provisioning – Configuring Access Settings.
Regards,
Nick Gu - MSFT

Log corruption near block 1737

Similar Messages

Maybe you are looking for