SERVER COMPONENT id=UTLRP_BGN: timestamp=2010-03-24 11:58:41

tolywang發表於2010-03-15
Server

Oracle 10.2.0.4  RAC  ,  3nodes  ,  64bit  , RH  Linux AS 5.3 

Oracle alert log  : 

 

Wed Mar 24 11:37:32 2010
Thread 3 advanced to log sequence 11451 (LGWR switch)
  Current log# 37 seq# 11451 mem# 0: /ocfs_ctrl_redo/mxdell/redo37_a.log
  Current log# 37 seq# 11451 mem# 1: /ocfs_data/mxdell/redo37_b.log
Wed Mar 24 11:58:41 2010
SERVER COMPONENT id=UTLRP_BGN: timestamp=2010-03-24 11:58:41
Wed Mar 24 12:00:15 2010
SERVER COMPONENT id=UTLRP_END: timestamp=2010-03-24 12:00:15
Wed Mar 24 12:07:33 2010
Thread 3 advanced to log sequence 11452 (LGWR switch)
  Current log# 38 seq# 11452 mem# 0: /ocfs_ctrl_redo/mxdell/redo38_a.log
  Current log# 38 seq# 11452 mem# 1: /ocfs_data/mxdell/redo38_b.log
Wed Mar 24 12:37:33 2010
Thread 3 advanced to log sequence 11453 (LGWR switch)
  Current log# 39 seq# 11453 mem# 0: /ocfs_ctrl_redo/mxdell/redo39_a.log
  Current log# 39 seq# 11453 mem# 1: /ocfs_data/mxdell/redo39_b.log
Wed Mar 24 13:07:33 2010
Thread 3 advanced to log sequence 11454 (LGWR switch)
  Current log# 40 seq# 11454 mem# 0: /ocfs_ctrl_redo/mxdell/redo40_a.log

 

You don't need to fix it. Somebody recompiled all invalid objects in database with script. $ORACLE_HOME/rdbms/admin/utlrp.sql

If You use this script. then in alert.log is generated suchlines.
No action is needed, it is just for information.

 

 

來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/35489/viewspace-630342/，如需轉載，請註明出處，否則將追究法律責任。

相關文章