BEA-141281 unable to get file lock, will retry ...[Fixed] Weblogic Error

Dear DBA-mates, Hope you all are doing great!!!

[Fixed] Weblogic Error: ><BEA-141281> <unable to get file lock, will retry ...>

Recently, while starting the weblogic services we found this below error. This is very common error for any weblogic DBAs. And almost people may know the solution.

But if a DBA working in PROD, at least once he will check either in google or colleagues to kill the process in PROD.

So, we thought lets share this error with you all for future references without any doubts.

weblogic java error:

<Sep 16, 2019 11:04:18 AM EDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 20.45-b01 from Sun Microsystems Inc.>

<Sep 16, 2019 11:04:29 AM EDT> <Info> <Management> <BEA-141281> <unable to get file lock, will retry ...>

<Sep 16, 2019 11:04:39 AM EDT> <Info> <Management> <BEA-141281> <unable to get file lock, will retry ...>

<Sep 16, 2019 11:04:49 AM EDT> <Info> <Management> <BEA-141281> <unable to get file lock, will retry ...>

$tail -f nohup.out

<Sep 16, 2019 11:04:18 AM EDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 20.45-b01 from Sun Microsystems Inc.>

<Sep 16, 2019 11:04:29 AM EDT> <Info> <Management> <BEA-141281> <unable to get file lock, will retry ...>

<Sep 16, 2019 11:04:39 AM EDT> <Info> <Management> <BEA-141281> <unable to get file lock, will retry ...>

Solution:

$ps ucx

Here, it will show all the running process.

Check for the JAVA process and kill it.

$kill -9 <java process>

Again start the services, it will work.

Work around -2:

If still not working then you need to check the .lok file and remove that and then again start the services.

First either bring down the weblogic services or kill the process including java process and then remove the .lok file.

Expected Path:

../Middleware/user_projects/domains/<your domain name>/servers/<mostly AdminServer>/tmp

You can find out .lok file. You either rename it or remove it.

From AdminServer directory, you can use below commands to find out the *.lok files also:

$find . –name *.lok –exec ls –ltr {} \;

Note: Always be careful and 100 % sure while removing any files.

Some more useful links:

ORA-01110 datafile 1: system01.dbf recovery

R12.2 ADOP Patching Phases Finalize and Cutover

Concurrent Manager Performance Tuning Tips in Oracle EBS R12

TKPROF Concepts with Syntax and Real time example

Why We are notRich

Regards,