Monday, July 11, 2011

SMON: Parallel transaction recovery tried message

In alert log file................. I am getting
SMON: Parallel transaction recovery tried message .
like below.


Mon Jul 11 11:02:13 2011
Thread 1 advanced to log sequence 93057 (LGWR switch)
Current log# 2 seq# 93057 mem# 0: /d01/oracle/oradata/stlbas/redo02.log
Mon Jul 11 11:31:38 2011
SMON: Parallel transaction recovery tried
Mon Jul 11 11:31:46 2011
Thread 1 advanced to log sequence 93058 (LGWR switch)
Current log# 3 seq# 93058 mem# 0: /d01/oracle/oradata/stlbas/redo03.log
Mon Jul 11 11:36:38 2011
SMON: Parallel transaction recovery tried
Mon Jul 11 11:41:39 2011
SMON: Parallel transaction recovery tried
Mon Jul 11 12:02:43 2011
Thread 1 advanced to log sequence 93059 (LGWR switch)
Current log# 4 seq# 93059 mem# 0: /d01/oracle/oradata/stlbas/redo04.log
Mon Jul 11 12:03:25 2011
Thread 1 advanced to log sequence 93060 (LGWR switch)
Current log# 5 seq# 93060 mem# 0: /d01/oracle/oradata/stlbas/redo05.log
Mon Jul 11 12:30:07 2011


You get this message if SMON failed to generate the slave servers necessary to perform a parallel rollback of a transaction. Check the value for the parameter, FAST_START_PARALLEL_ROLLBACK (default is LOW). LOW limits the number of rollback processes to 2 * CPU_COUNT.
HIGH limits the number of rollback processes to 4 * CPU_COUNT. You may want to set the value of this parameter to FALSE.


you should consider when need to change parallel_max_servers parameter .

In my system, I changed the
"parallel_max_servers" parameter from 2560 to 300 . after that i am finding this message .

because, SMON failed to generate the slave servers(what are define at this "FAST_START_PARALLEL_ROLLBACK" parameter ) necessary to perform a parallel rollback of a transaction

may be its value is HIGH or LOW value is greater then parallel_max_servers parameter .




No comments: