Chapter 8. Troubleshooting and diagnostics 203
Diagnostics and solution
After looking through the createDM log, and some trial and error, we discovered that the VE
install directory cannot be defined to be in the root directory(/). We created a new directory,
/opt/ewlmdm, and used it instead of /ewlmdm.
8.2.2 Operations
Problem
EWLM activation error opening internal database.
Error received
EWLM activation error: opening internal database
EWLM activation error: db2j.p.j
EWLM activation error: Failed to start database ‘PolicyDB’ see the next exception for
details.
PROCESING COMPLETE
Expanded description
When the domain manager is started it uses an internal database. Lock files are created for
the various databases in use to assure integrity of the data. When the domain manager does
not stop successfully there are locks open on the database. Therefore, we are not able to
successfully restart the domain manager because it cannot open the database since the
database has locks against it.
Diagnosis and solution
In our directory, /opt/EWLMDM/eWLMData, there are several subdirectories for each of the
databases we are using. If we go into one of the directories (PolicyDB, for example), we see a
file called dbex.lck. This is the lock on the PolicyDB database. In order to safely restart the
domain manager, we need to successfully close these locks. We recommend rebooting the
machine which the domain manager is trying to start because this will release the locks
safely.
Problem
EWLM activation error starting the EWLM domain manager.
Error received
Starting EWLM Domain Manager ...
EWLM activation error: opening internal databases
EWLM activation error: db2j.p.j
EWLM activation error: Failed to start database ‘ReportingDB’, see the next exception for
details.
PROCESSING COMPLETE
Expanded description
After encountering a problem with the domain manager, we killed the ./startDM.sh process
via the kill command. However, this did not terminate all of the domain manager processes
that were running. When we tried to restart the domain manager, one (or more) of these
processes were using the database and thus we were not able to start it.
Killing the shell script doesn't stop the actual Java process, especially if you are running the
domain manager on Linux where each Java thread looks like a Java process in "ps -ef". In
this case you need to issue a "ps -eH" and kill all the Java processes under the startDM.sh
script to completely shut down the domain manager.