This section addresses various problems that might arise after installation.
If you have restarted Application Server, the communication between Application Server and Monitoring Console has been disrupted and needs to be reactivated. Monitoring rules that were previously working, no longer work and are in a status of Unknown. If you have restarted the common agent container on the Application Server host, the problem will still exist because the common agent container must also be restarted on the Monitoring Console host.
As root, restart the common agent container on the host where Application Server resides. For example:
Then go to the host where Monitoring Console resides and restart the common agent container. For example:
If common agent container is already running, stop it, then start it with these commands.
On Solaris OS:
/usr/sbin/cacaoadm stop /usr/sbin/cacaoadm start
On Linux and HP-UX:
/opt/sun/cacao/bin/cacaoadm stop /opt/suncacao/bin/cacaoadm start
This can occur when you deploy an Application Server sample that uses Java DB after running the default Application Server command to restart Java DB (asadmin stop-databsse then asadmin start-database). Portal Server samples are no longer be accessible.
Suggested Fix. There are a number ways to approach this problem
Do not stop Java DB.
If Java DB was stopped, restart Java DB with the following command allowing the Application Server database to be created in an alternate location.
Solaris OS: /asadmin start-database --dbhome /var/opt/SUNWportal/derby
Linux and HP-UX: /asadmin start-database --dbhome /var/opt/sun/portal/derby
If you want the database to be located in the default location, start a second instance of Java DB using a non-default port, then specify the correct Derby port in the Application Server samples common.properties file. For example: asadmin start-database --dbport 1528