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

[Former Member]

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

[Former Member]

Try this

1. All files in the installation directory below

'/tmp/sapinst_instdir/...' should belong to user 'root' and group

'sapinst'.

2. Users <sid>adm and ora<sid> should be assigned to that group.

3. Filepermissions of all files should be at least '777'

4. Umask-setting should be '022'.

5. Applied latest patch of Migmon as per note 784118 -

archive 'MIGMON.SAR' - simply

download and extract the archive to your installation directory

6. Recursively change the permissions of the sapisnt directory

and the installation CDs directory to 777

[Former Member]

On windows...Stop the install....log off the system.....start installation....and continue with the old install...this will remove the lock and installation will continue from there on

[Former Member]

This is solved and Installation is done perfect

If anyone needs assistance regarding the issues on these installation let me know

thanks

kamal

[Former Member]

Kamal.

How did you fix this.

Thanks.

[Former Member]

There will be a process called importmonitor already running on your host. Just check that using ps -ef|grep process. after theat kill the process and start it again..Else when u start the installation again, it will work...( Not complete installation) just start the installation with existing instdirectory.

[Former Member]

Hi,

I'm facing the same problem and can't find a process called importmonitor.

My OS is LINUX.

Any ideas?

Thank you.

Ines

[yuri_shikunov]

Hint: NFS directory cannot be used as working directory for migmon. Process should be started in local directory.