Reinitializing Cloudscape databases prior to V5.1.21 for reuse during startup
 Technote (troubleshooting)
 
Problem(Abstract)
Setting up a Cloudscape database for reuse by inserting a clean- up routine into the IBM® WebSphere® Application Server start up script on UNIX® platforms.
 
Cause
Cloudscape creates lock files that are no longer needed at the end of a session. They must be removed to successfully restart Application Server when you use Cloudscape.
 
Resolving the problem

To perform a timed startup test, write a script similar to this one:

date
rm -f /opt/WebSphere/AppServer/installedApps/nodename
TechnologySamples.ear/Database/db.lck
rm -f /opt/WebSphere/AppServer/installedApps/
nodename/whatever_else_is_left
/db.lck
startServer.sh server1
date


Refine the delete command (rm) syntax.

The WebSphere Application Server startup script should include a line such as:

find /opt/WebSphere -name "db.lck" -exec rm {} \;

Removing these files can reduce startup time by 30-to-45 seconds per db.lck file.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s): Windows
Software version: 5.1.1
Software edition:
Reference #: 1139850
IBM Group: Software Group
Modified date: Sep 14, 2004