Weblogic server not starting because servers are unable to lock files.

1. From your …domains/[DOMAIN] directory (and below) find and move all *.DAT files to *.OLD and then rename them back.
– ex: find . -name *.DAT
-ex:
Manually unlock the logs and JMS data files and start the servers by creating a copy of the locked persistence store file and using the copy for subsequent operations.

To create a copy of the locked persistence store file, rename the file, and then copy it back to its original name.

The following sample steps assume that transaction logs are stored in the /shared/tlogs directory and JMS data is stored in the /shared/jms directory.

cd /shared/tlogs
mv _WLS_SOA_SERVER1000000.DAT _WLS_SOA_SERVER1000000.DAT.old
cp _WLS_SOA_SERVER1000000.DAT.old _WLS_SOA_SERVER1000000.DAT

cd /shared/jms
mv SOAJMSFILESTORE_AUTO_1000000.DAT SOAJMSFILESTORE_AUTO_1000000.DAT.old
cp SOAJMSFILESTORE_AUTO_1000000.DAT.old SOAJMSFILESTORE_AUTO_1000000.DAT
mv UMSJMSFILESTORE_AUTO_1000000.DAT UMSJMSFILESTORE_AUTO_1000000.DAT.old
cp UMSJMSFILESTORE_AUTO_1000000.DAT.old UMSJMSFILESTORE_AUTO_1000000.DAT

2. Find and remove all lok files in a similar method
– ex: find . -name *.lok

3. If necessary use netstat -lntp to find any processes started and using your AdminServer port

4. Restart servers