Pessoal,
Ocorre diversas vezes o erro "minact-scn: got error during useg scan e:1555 usn:54" no alert.log.
Não encontrei este erro no MOS. Além disso, percebo que o processo de backuground SMON fica com CPU em 100% no servidor. Acredito que estes erros ocorrem devido este processamento do SMON. Alguém já passou por isso?
Realizei diversas pesquisas, o erro e:1555 parece remeter ao "Snapshot too old", porém não encontrei problemas de undo e retenção...
Pequeno pedaço do alert.log:
Tue Mar 20 13:30:37 2018
minact-scn: got error during useg scan e:1555 usn:54
minact-scn: useg scan erroring out with error e:1555
Tue Mar 20 13:33:37 2018
minact-scn: got error during useg scan e:1555 usn:54
minact-scn: useg scan erroring out with error e:1555
Tue Mar 20 13:36:37 2018
minact-scn: got error during useg scan e:1555 usn:54
minact-scn: useg scan erroring out with error e:1555
Tue Mar 20 13:39:37 2018
minact-scn: got error during useg scan e:1555 usn:54
minact-scn: useg scan erroring out with error e:1555
Tue Mar 20 13:42:38 2018
minact-scn: got error during useg scan e:1555 usn:54
minact-scn: useg scan erroring out with error e:1555
Tue Mar 20 13:45:38 2018
minact-scn: got error during useg scan e:1555 usn:54
minact-scn: useg scan erroring out with error e:1555
Tue Mar 20 13:48:38 2018
minact-scn: got error during useg scan e:1555 usn:54
minact-scn: useg scan erroring out with error e:1555
Tue Mar 20 13:51:38 2018
minact-scn: got error during useg scan e:1555 usn:54
minact-scn: useg scan erroring out with error e:1555
Características do ambiente:
S.O: Oracle Linux 7.0
Oracle 11g 11.2.0.4 (SE)