-
Alert Log Error
The Following Errors popup in our production alert_log
ARC0: Completed archiving log# 5 seq# 24376
Tue Mar 23 22:03:14 2004
Errors in file /dbdata03/ora8174/rdbms/log/iway_ora_2182.trc:
Tue Mar 23 22:16:31 2004
Thread 1 advanced to log sequence 24378
This error is followed by
Thread 1 advanced to log sequence 24381
Current log# 10 seq# 24381 mem# 0: /dbdata01/IWAY/REDO/log10a.log
Current log# 10 seq# 24381 mem# 1: /dbdata03/IWAY/REDO/log10b.log
Tue Mar 23 22:40:01 2004
ARC1: Beginning to archive log# 8 seq# 24379
ARC1: Failed to archive log# 8 seq# 24379
ARC1: Beginning to archive log# 9 seq# 24380
Tue Mar 23 22:40:03 2004
ARC0: Completed archiving log# 8 seq# 24379
ARC0: Beginning to archive log# 9 seq# 24380
ARC0: Failed to archive log# 9 seq# 24380
Tue Mar 23 22:40:04 2004
ARC1: Completed archiving log# 9 seq# 24380
Tue Mar 23 23:00:01 2004
The Trace file looks like
*** SESSION ID:(174.929) 2004-03-23 22:03:14.311
FATAL ERROR IN TWO-TASK SERVER: error = 12592
*** 2004-03-23 22:03:14.337
ksedmp: internal or fatal error
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
-------------------- -------- -------------------- ----------------------------
ksedmp()+168 CALL ksedst()+0 188 ? 1 ? FFBED680 ?
FFBED124 ? FFBED108 ? 0 ?
opitsk()+5344 CALL ksedmp()+0 2 ? 0 ? 0 ? 800 ? 941DAD1C ?
0 ?
opiino()+1792 CALL opitsk()+0 0 ? 1A15E10 ? 1A1888C ? 0 ?
0 ? 3130 ?
opiodr()+5748 PTR_CALL 00000000 FFBEFA08 ? 80005000 ?
1A17000 ? 1A4E560 ? 0 ?
1A02E80 ?
opidrv()+1308 CALL opiodr()+0 16632B0 ? FFBEF60C ?
1A18400 ? 0 ? 16983CA ?
1A22458 ?
sou2o()+20 CALL opidrv()+0 3C ? FFBEF71C ? 1A14000 ?
2F6C6F67 ? 0 ? 2F ?
main()+160 CALL sou2o()+0 FFBEFA18 ? 3C ? 4 ?
FFBEFA08 ? 175D914 ?
1A22458 ?
_start()+220 CALL main()+0 0 ? FFBEFBC4 ? 1A3AB80 ?
1A14000 ? 0 ? 0 ?
----- Argument/Register Address Dump -----
Argument/Register addr=ffbed680.
Dump of memory from 0xFFBED640 to 0xFFBED780
FFBED640 00000000 00000000 01A144BC FFBED6CA [..........D.....]
FFBED650 015B03AC 0000003E FFBED68C 00000000 [.[.....>........]
FFBED660 FFBEDCA0 001625FC 00000000 00000000 [......%.........]
FFBED670 FFBED7A5 FFBED74C FFBED770 00000000 [.......L...p....]
FFBED680 FFBECE88 00000006 00000006 FFBEDCA0 [................]
FFBED690 00000006 00000006 FFBEDD20 00000006 [........... ....]
FFBED6A0 00000006 FFBEF110 00000006 00000006 [................]
FFBED6B0 FFBEF380 00000006 00000006 FFBEF680 [................]
FFBED6C0 00000006 00000006 FFBEF938 00000006 [...........8....]
FFBED6D0 00000006 FFBEF998 00000006 00000006 [................]
FFBED6E0 00000000 00000000 00000000 00000000 [................]
Repeat 1 times
FFBED700 FFBED857 0000001E 00000000 00000000 [...W............]
FFBED710 00000000 00000000 00000000 00000000 [........
similarly in the Alert during hot backup
alter tablespace indux begin backup
Completed: alter tablespace indux begin backup
Wed Mar 24 01:40:01 2004
Thread 1 advanced to log sequence 24390
Current log# 9 seq# 24390 mem# 0: /dbdata01/IWAY/REDO/log9a.log
Current log# 9 seq# 24390 mem# 1: /dbdata03/IWAY/REDO/log9b.log
Wed Mar 24 01:40:01 2004
ARC0: Beginning to archive log# 8 seq# 24389
ARC0: Completed archiving log# 8 seq# 24389
Wed Mar 24 01:58:35 2004
alter tablespace indux end backup
Wed Mar 24 01:58:35 2004
Completed: alter tablespace indux end backup
Wed Mar 24 01:58:36 2004
This Archive file when applying to the standby prompts the followingf error
ORA-279 signalled during: ALTER DATABASE RECOVER standby database ...
Wed Mar 24 02:24:01 2004
ALTER DATABASE RECOVER CONTINUE DEFAULT
Media Recovery Log /dbdata03/IWAY/STDBYARCH/iway_24389.arc
Recovery is repairing media corrupt block 173592 of file 17
Recovery is repairing media corrupt block 172908 of file 17
Recovery is repairing media corrupt block 382499 of file 17
Wed Mar 24 02:24:26 2004
ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
Wed Mar 24 02:24:26 2004
ALTER DATABASE RECOVER CONTINUE DEFAULT
Media Recovery Log /dbdata03/IWAY/STDBYARCH/iway_24390.arc
ORA-308 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
Wed Mar 24 02:24:26 2004
ALTER DATABASE RECOVER CANCEL
How do we go about this.
Red - alert log in production
Blue- Trace file
Orange- Alert log in standby.
We are on Sun Solaris Oracle 8.1.7
Last edited by Rohit; 03-24-2004 at 12:41 AM.
Success Consists of Getting Up Just One More Time Than You've Fallen Down
Be Blessed
-
i guess u have corrupted online redo log.. by seeing the error you are not even mirror your redolog files.
tried to do this...
_allow_resetlogs_corruption=true at init.ora
The man called Zorro
-
The redo files are mirrored ..
Current log# 10 seq# 24381 mem# 0: /dbdata01/IWAY/REDO/log10a.log
Current log# 10 seq# 24381 mem# 1: /dbdata03/IWAY/REDO/log10b.log
Success Consists of Getting Up Just One More Time Than You've Fallen Down
Be Blessed
-
yea.. i think i need more sleep...
The man called Zorro
-
Originally posted by Rohit
How do we go about this.
It looks like recovery has taken place and the standby now requires iway_24390.arc
Originally posted by zainalj
_allow_resetlogs_corruption=true at init.ora
Why would you use this on a standby database????
Would it even let you?
-
Originally posted by Rickenbacker
It looks like recovery has taken place and the standby now requires iway_24390.arc
Why would you use this on a standby database????
Would it even let you?
I told you.. i need more sleep.. kind a sleepless in seatle..
The man called Zorro
-
how did you create the hot standby, is all hardware same/same for primary and standbdy
have you every been able to apply arch logs or is this a new config?
the ora 279 and ora 308 are ok , the media corrupt block sounds worrysome though
I'm stmontgo and I approve of this message
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|