Oracle Database Discussions

Hi folks,

We come across a problem that our instance was down suddenly. When checking with the alert log file, it shows that the instance was terminated due to error 472. Did you come across such situation before? Any suggestions would be welcomed.

Following are some information about our Oracle and the log file, trace file.

Oracle Database 10g Release 10.2.0.2.0 - Production
ORACLE_HOME = /app/oracle/lmes
System name: Linux
Node name: lmes-oracle2.ust.hk
Release: 2.4.21-32.ELsmp
Version: #1 SMP Fri Apr 15 21:17:59 EDT 2005
Machine: i686

Alert Log File
Fri Feb 23 09:11:07 2007
Shutting down archive processes
Fri Feb 23 09:11:12 2007
ARCH shutting down
ARC2: Archival stopped
Fri Feb 23 15:16:09 2007
The value (30) of MAXTRANS parameter ignored.
kupprdp: master process DM00 started with pid=32, OS id=1072
to execute - SYS.KUPM$MCP.MAIN('SYS_EXPORT_SCHEMA_01', 'SYSTEM', 'KUPC$C_1_20070223151610', 'KUPC$S_1_20070223151610', 0);
kupprdp: worker process DW01 started with worker id=1, pid=33, OS id=1077
to execute - SYS.KUPW$WORKER.MAIN('SYS_EXPORT_SCHEMA_01', 'SYSTEM');
Fri Feb 23 15:16:28 2007
Thread 1 advanced to log sequence 1309
Current log# 3 seq# 1309 mem# 0: /app/oracle/oradata/elop/redo03.log
Fri Feb 23 15:20:29 2007
The value (30) of MAXTRANS parameter ignored.
kupprdp: master process DM00 started with pid=32, OS id=1526
to execute - SYS.KUPM$MCP.MAIN('SYS_EXPORT_SCHEMA_01', 'SYSTEM', 'KUPC$C_1_20070223152029', 'KUPC$S_1_20070223152029', 0);
kupprdp: worker process DW01 started with worker id=1, pid=33, OS id=1528
to execute - SYS.KUPW$WORKER.MAIN('SYS_EXPORT_SCHEMA_01', 'SYSTEM');
Fri Feb 23 22:15:35 2007
Thread 1 advanced to log sequence 1310
Current log# 1 seq# 1310 mem# 0: /app/oracle/oradata/elop/redo01.log
Fri Feb 23 23:04:10 2007
USER: terminating instance due to error 472
Instance terminated by USER, pid = 7779

Trace File - elop_lgwr_2312.trc
/app/oracle/admin/elop/bdump/elop_lgwr_2312.trc
Oracle Database 10g Release 10.2.0.2.0 - Production
ORACLE_HOME = /app/oracle/lmes
System name: Linux
Node name: lmes-oracle2.ust.hk
Release: 2.4.21-32.ELsmp
Version: #1 SMP Fri Apr 15 21:17:59 EDT 2005
Machine: i686
Instance name: elop
Redo thread mounted by this instance: 1
Oracle process number: 6
Unix process pid: 2312, image: oracle@lmes-oracle2.ust.hk (LGWR)

*** SERVICE NAME:() 2007-02-23 09:10:07.372
*** SESSION ID:(331.1) 2007-02-23 09:10:07.372
LGWR: Archivelog for thread 1 sequence 1308 will NOT be compressed
tkcrrsarc: (WARN) Failed to find ARCH for message (message:0x1)
tkcrrpa: (WARN) Failed initial attempt to send ARCH message (message:0x1)
Maximum redo generation record size = 156160 bytes
Maximum redo generation change vector size = 150672 bytes
tkcrrsarc: (WARN) Failed to find ARCH for message (message:0x10)
tkcrrpa: (WARN) Failed initial attempt to send ARCH message (message:0x10)
*** 2007-02-23 15:16:27.116
LGWR: Archivelog for thread 1 sequence 1309 will NOT be compressed
*** 2007-02-23 22:15:35.383
LGWR: Archivelog for thread 1 sequence 1310 will NOT be compressed

Trace File - elop_ora_2336.trc
/app/oracle/admin/elop/udump/elop_ora_2336.trc
Oracle Database 10g Release 10.2.0.2.0 - Production
ORACLE_HOME = /app/oracle/lmes
System name: Linux
Node name: lmes-oracle2.ust.hk
Release: 2.4.21-32.ELsmp
Version: #1 SMP Fri Apr 15 21:17:59 EDT 2005
Machine: i686
Instance name: elop
Redo thread mounted by this instance: 1
Oracle process number: 15
Unix process pid: 2336, image: oracleelop@lmes-oracle2.ust.hk

*** SERVICE NAME:() 2007-02-23 09:10:05.988
*** SESSION ID:(324.3) 2007-02-23 09:10:05.988
Thread 1 checkpoint: logseq 1307, block 2, scn 27684035
cache-low rba: logseq 1307, block 30724
on-disk rba: logseq 1307, block 33205, scn 27699991
start recovery at logseq 1307, block 30724, scn 0
----- Redo read statistics for thread 1 -----
Read rate (ASYNC): 1240Kb in 0.03s => 40.38 Mb/sec
Total physical reads: 4096Kb
Longest record: 21Kb, moves: 0/1975 (0%)
Change moves: 1/24 (4%), moved: 0Mb
Longest LWN: 285Kb, moves: 0/245 (0%), moved: 0Mb
Last redo scn: 0x0000.01a6ab16 (27699990)
----------------------------------------------
----- Recovery Hash Table Statistics ---------
Hash table buckets = 32768
Longest hash chain = 2
Average hash chain = 346/345 = 1.0
Max compares per lookup = 1
Avg compares per lookup = 4783/5281 = 0.9
----------------------------------------------
*** 2007-02-23 09:10:06.132
KCRA: start recovery claims for 346 data blocks
*** 2007-02-23 09:10:07.153
KCRA: blocks processed = 346/346, claimed = 346, eliminated = 0
*** 2007-02-23 09:10:07.154
Recovery of Online Redo Log: Thread 1 Group 1 Seq 1307 Reading mem 0
----- Recovery Hash Table Statistics ---------
Hash table buckets = 32768
Longest hash chain = 2
Average hash chain = 346/345 = 1.0
Max compares per lookup = 2
Avg compares per lookup = 3424/5126 = 0.7
----------------------------------------------
tkcrrsarc: (WARN) Failed to find ARCH for message (message:0x1)
tkcrrpa: (WARN) Failed initial attempt to send ARCH message (message:0x1)
Error in executing triggers on database startup
*** 2007-02-23 09:10:11.557
ksedmp: internal or fatal error
ORA-00604: error occurred at recursive SQL level 1
ORA-12663: Services required by client not available on the server
ORA-36961: Oracle OLAP is not available.
ORA-06512: at "SYS.OLAPIHISTORYRETENTION", line 1
ORA-06512: at line 15


Thanks & Regards,
Liona