Self-Solve Knowledge Search

Minimize Maximize
New messages are not displayed on Java GUI
Title :
New messages are not displayed on Java GUI
Document ID :
KM00485593
Product - Version:
operations manager for unix 9.10 ;
OS :
Updated :
Wed Apr 30 08:22:35 GMT 2014
Summary :
A new messages are not displayed on Java GUIl. The situation doesn't change even if the "refresh" operation is executed.

New messages are not displayed on Java console.

A new messages are not displayed on Java console.
The situation doesn't change even if the "refresh" operation is executed.
Even if the message is acknowledged, it does not move to the message history.

Checking the alert_openview.log file, the following errors are frequently recorded.

"Thread 1 cannot allocate new log, sequence xx"
"Private strand flush not complete"

Solution

When the following messages are frequently recorded in the alert_openview.log file,
there is a possibility that the load of the Oracle data base is very high.

"Thread 1 cannot allocate new log, sequence xxx "
"Checkpoint not complete"

"Private strand flush not complete"

"Cannot allocate new log" and "Checkpoint not complete" shows the bottleneck of REDO.
"Private strand flush not complete" has the possibility of showing the state
of the load of the DBWR process.

When this message has been frequently generated, the size or the number of online REDO
log files is significantly bigger compared to a normal operation of OM.
There is the following possibilities by the bottleneck of Oracle.

It takes time to make the message.
The reflection in JavaGUI is delayed.

The problem might be resolved by executing the tuning of REDO.
Increasing REDO Log size etc.