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.
204 IBM Enterprise Workload Manager
If you are running on AIX, you should kill the Java process, and since there is only one for the
domain manager, then the startDM.sh script will exit gracefully and the database will be
released too.
Diagnosis and solution
It is easier to start domain manager and managed server commands in the foreground so if
you need to stop the domain manager or managed servers, you can issue a CONTROL-C
from the window where the server was started. If you need to run these processes in the
background, you need to be familiar with the operating system in order to be able to stop the
correct process.
Problem
The domain manager directory was not deleted during the uninstall.
Error received
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
We tried to delete the domain manager and recreate it but were unable to clean up the entire
environment with the deleteDM.sh command. We then tried to create a new DM using the
same directory but could not since the directory was still there from our previous install.
Diagnosis and solution
To bypass the problem you can either delete the old directory and reissue the createDM
command or you can use a different working directory on the createDM command if you need
to preserve data in the old working directory.
Problem
Cannot display the domain manager properties when the domain manager is running.
Error received
EWLM customization error: loading customized properties
ERROR: Domain Manager must be stopped in order to display properties
Expanded description
At this time, you cannot display the properties of the domain manager when the domain
manager is running.
Diagnosis and solution
At this time, you cannot display or change any of the EWLM components dynamically. In
order to display the properties of the domain manager you need to first stop the domain
manager. Since the domain manager was started in the foreground, there should be a
window open where it was started. Go to that window and stop the domain manager with the
CONTROL-C function. Then issue the ./displayDM.sh command again to display the
properties.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.