• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer navigation

The Geek Diary

  • OS
    • Linux
    • CentOS/RHEL
    • Solaris
    • Oracle Linux
    • VCS
  • Interview Questions
  • Database
    • oracle
    • oracle 12c
    • ASM
    • mysql
    • MariaDB
  • DevOps
    • Docker
    • Shell Scripting
  • Big Data
    • Hadoop
    • Cloudera
    • Hortonworks HDP

What are the .lok files used in WebLogic

by admin

Question: There are several files with a .lok extension in the WebLogic Server (WLS) domain directory. What are these files used for?

There are config.lok, EmbeddedLDAP.lok and XXXserver.lok files which are used by the admin server and managed server. Another lock file named edit.lok is used for the admin server only.

Why are .lok files used?

There are cases where we see the error such as:

Lock is owned by Another Session

Or

weblogic.management.ManagementException: [Deployer:149164]The domain edit lock is owned by another session in exclusive mode - hence this deployment operation cannot proceed.

These errors essentially say about the lock being owned by another process. During these cases, we need to make sure that the process releases the lock.

Here are some more details on each type of .lok file:

config.lok

The config.lok file is just used for getting a file lock on the config.xml file, in order to ensure that config file updates run serially. It will not cause any problems if it exists in the directory.

Location:

cfgdir/config/config.xml

edit.lok

The edit lock is used to ensure that only one user at a time is editing the configuration. The edit lock is only used on the Admin server.

Location:

cfgdir/

EmbeddedLDAP.lok

This file locks access to the embedded LDAP server, in order to ensure that only a single process has access to this directory server. if two processes write to the same directory server, the directory server could be corrupted.

Location:

/cfgdir/servers/[Server Name]/data/ldap/ldapfiles/

XXXServer.lok

The [server name].lok indicates that the server with name [server name] is running. This is used to prevent a server from being booted twice. If you are sure that this server process is shut down, you can delete it.

Location:

/cfgdir/servers/[Server Name]/servername.lok
Note: When a webloigc server is stopped, the embeddedLDAP.lok and XXXservername.lok are deleted automatically.

Filed Under: oracle, WebLogic

Some more articles you might also be interested in …

  1. How to Turn Archiving ON and OFF in Oracle database
  2. Oracle Database: Redo log operations (Add/Drop/Change Location)
  3. SQL query error when Using Shell Script
  4. How to Create the Oracle Password File using orapwd Command
  5. Oracle ASM 12c – New Features with examples
  6. Steps to relink Oracle Forms 12c in Linux/UNIX
  7. What are Oracle Key Vault Roles
  8. How to Convert STANDARD ASM to FLEX ASM in 12C
  9. How To Create “A CRS Managed” ACFS FileSystem On Oracle RAC Cluster (ASM/ACFS 11.2)
  10. ORA-65208: Lockdown profile P1 does not exist

You May Also Like

Primary Sidebar

Recent Posts

  • aws ec2: CLI for AWS EC2 (Command Examples)
  • aws cur – Create, query, and delete AWS usage report definitions (Command Examples)
  • aws configure – Manage configuration for the AWS CLI (Command Examples)
  • aws cognito-idp: Manage Amazon Cognito user pool and its users and groups using the CLI

© 2023 · The Geek Diary

  • Archives
  • Contact Us
  • Copyright