Skip to Content
0
Former Member
Mar 01, 2007 at 07:55 PM

SolutionManager 4.0 installation error due to the 'ImportMonitor.lck'

106 Views

Hi ,

At Phase 17 => “Import ABAP” phase installation stopped due to the following error:

Lock file 'ImportMonitor.lck' is locked by other process.

We tried all the following options to resolve the issue:

1. Checked the Java environment version

2. Logged as <SID>adm and tried to continue with old installation

3. Could not locate a physical 'ImportMonitor.lck' file in the UNIX file system

4. Checked for suspicious processes using ps -ef grep commands

5. Applied the latest patch of Migmon as per note 784118 - archive 'MIGMON.SAR'

6. Checked if users <sid>adm and ora<sid> should be assigned to ‘sapinst’ group

7. Checked for Filepermissions of all files should be at least '777'

And few other basic sanity checks but no luck.

Our environment:

HP-UNIX, Oracle 10.2 , Java 1.4.2.12

Help Questions:

1. Does anyone know where SAP generally stores the lock files (in some table, inside some flat file, a file itself for lock)?

2. How to delete a .lck file such as this?

3. How to check lock files at a particular point of time and lock files by a process?

Thanks,

Kamal janumala