/usr/app/oracle/admin/sirokko/bdump/pmon_14895.trc
Oracle8i Enterprise Edition Release  8 . 1 . 7 . 0 . 1  - Production
With the Partitioning option
JServer Release  8 . 1 . 7 . 0 . 1  - Production
ORACLE_HOME = /usr/app/oracle/ 8 . 1 . 7 
System name:	Linux
Node name:	oracle
Release:	 2 . 4 . 18 - 3 
Version:	# 1  Thu Apr  18   07 : 37 : 53  EDT  2002 
Machine:	i686
Instance name: sirokko
Redo thread mounted by this instance:  0  <none>
Oracle process number:  2 
Unix process pid:  14895 , image: oracle@oracle (PMON)

*** SESSION ID:( 1 . 1 )  2003 - 02 - 03   15 : 01 : 01 . 429 
Load Indicator not supported by OS !

...
Thread  1  advanced to log sequence  2472 
  Current log#  3  seq#  2472  mem#  0 : /usr/app/oracle/oradata/sirokko/redo03.log
Thread  1  cannot allocate new log, sequence  2473 
Checkpoint not complete
  Current log#  3  seq#  2472  mem#  0 : /usr/app/oracle/oradata/sirokko/redo03.log
Thread  1  advanced to log sequence  2473 
  Current log#  1  seq#  2473  mem#  0 : /usr/app/oracle/oradata/sirokko/redo01.log
...

Problem Description 
 -------------------  
 
Messages regarding Load Indicator are reported once every few seconds
in the alert log. These messages would fill up your alert log.  
eg.
         PMON started with pid= 2 
         OER  536879337  in Load Indicator : Error Code =  562331928  !
         DBW0 started with pid= 3 
         LGWR started with pid= 4 
         ...
         Wed Jan   5   10 : 00 : 22   2000 
         Load Indicator not supported by OS !
         Wed Jan   5   10 : 00 : 23   2000 
         Thread  1  cannot allocate new log, sequence  23 
         ...
         Load Indicator not supported by OS !
         Thu Jan   6   15 : 49 : 50   2000 
         Load Indicator not supported by OS !
         Thu Jan   6   15 : 50 : 24   2000 
         Load Indicator not supported by OS !
         Thu Jan   6   15 : 50 : 58   2000 
         Load Indicator not supported by OS !
         Thu Jan   6   15 : 51 : 32   2000 

Problem Explanation
 -------------------  
 
This problem is two fold.  

 1 . PMON reports bogus error message on LINUX:    
   'OER 536879337 in Load Indicator : Error Code = 562331928 !'     

   see Solution # 1  and BUG: 987647   

 2 . Messages 'Load Indicator not supported by OS !' filled up the
   alert log.

   see Solution # 2  for workarounds  

SOLUTION # 1 :  

Solution Description: 
 ---------------------
 
Apply patch for [BUG: 987647 ].   
This bug is port specific for LINUX.  
Note that this patch only fixes the problem with inccorect PMON messages.
It does not eliminate the 'Load Indicator not supported by OS !' messages.

SOLUTION # 2 :

Solution Description: 
 ---------------------  
 
There are a couple of workarounds for eliminating these 
messages - 'Load Indicator not supported by OS !':  

 1 . Run crontab on alert.log to save good error and drop Load Indicator errors:
   eg.  cat alert.log | grep -v  "Load Indicator ...."  > alert.good  
 2 . Disable MTS may eliminate these messages.

There have been a number of bugs reported on this issue.
Currently, these bugs are still under investigation and no patch
is available at this time.

Disable MTS may work as this is related to [BUG: 723579 ]. This bug is
fixed in  8 . 1 . 4  but this fix does not appear to be included in
 8 . 1 . 5 . Please see [BUG: 1109425 ] and [BUG: 1103673 ].

EXPLANATION:
============

There have been a number of bugs reported on this problem and these
bugs can be divided into  2  catagories.

 1 . This is not a bug. The message indicates that the kernel load statictics
   is not supported.
   see [BUG: 984456 ] and [BUG: 1164889 ]

 2 . The cumulation of 'Load Indicator not supported by OS !' messages
   could casue PMON to return ora- 000601  and crash.

   [BUG: 1109425 ] PMON crashed with ora- 601  on LINUX
   [BUG: 1103673 ] PMON crashed with ora- 601  on SGI

   - The fixes of this problem are to be verified.