Installation error on SOLMAN 4.0 HPUX Oracle as 'ImportMonitor.lck' is lock

[Former Member]

Hi,

While installing SOLMAN 4.0 on oracle 10.2 and HPUX 11.23 - IA64 (Central and DB instance installation)

The installation has an error at 17 of 44th step as

Another instance of application is already running.

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

Try to trouble shoot the issue by

1. Checked the Java environment and pointing directories ( found ok)

2. Logged as <SID>adm and tried to continue with old installation, but had same error

3. Checked the concerned .lck file but unable to locate it.

Seeking for a solution .

Error Log as follows:

Phase 17 of 44

Import Abap

WARNING 2007-02-28 08:41:04

Execution of the command "/opt/java1.4/bin/java -classpath migmon.jar -showversi

on -d64 com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs /SAPInstal

lationMedia/SOLMAN/Export/EXP1:/SAPInstallationMedia/SOLMAN/Export/EXP2:/SAPInst

allationMedia/SOLMAN/Export/EXP3:/SAPInstallationMedia/SOLMAN/Export/EXP4 -insta

llDir /oracle/SMS/102_64/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS -orderBy "

" -r3loadExe /usr/sap/SMS/SYS/exe/run/R3load -tskFiles yes -extFiles yes -dbCode

page 4102 -jobNum 3 -monitorTimeout 30 -loadArgs " -stop_on_error" -trace all -s

apinst" finished with return code 3. Output:

java version "1.4.2.12"

Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2.12-061213-02:03)

Java HotSpot(TM) 64-Bit Server VM (build 1.4.2 1.4.2.12-061213-10:06-IA64W IA64W

, mixed mode)

Another instance of application is already running.

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

ERROR 2007-02-28 08:41:04

CJS-30022 Program 'Migration Monitor' exits with error code 3. For details see

log file(s) import_monitor.java.log, import_monitor.log.

ERROR 2007-02-28 08:41:04

FCO-00011 The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|in

d|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|9

0

NW_ABAP_Import_Dialog

ind

ind

ind

ind

5

0

NW_ABAP_Import

ind

ind

ind

ind

0

0

runMigrationMonitor was executed with status ERROR .

Any comment would be of great help.

Thanks,

Kamal Janumala

[Former Member]

If it helps, I faced this issue with NW2004S Installation -- the solution of recursively changing ownership to root:sapinst worked for me (somehow it was changed to orasid). This was on Solaris 10

[DoloresCorrea]

Hi Kamal,

Please check:

1. Another instance of Migration Monitor is already running,

verify this using (ps -ef grep java),check for entries like

/usr/java14_64/bin/java -classpath migmon.jar

or run: ps -ef grep migmon

2.Check the existance of import_monitor.log file.

It you don´t have this file try the following:

Recursively change the permissions of the sapisnt directory

and the installation CDs directory to 777. Sometimes it can happen that

the parent directory is set to 777 but the sub directories are not.

Best regards,

Dolores

[Former Member]

Hi Dolores,

We tried as you suggested but facing the same error.

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

[DoloresCorrea]

Hello Kamal,

Still not working? try the following:

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'.

For other customers the latest patch of Migmon as per note 784118 solved the issue.

There is a message open with the same issue in Development, I will follow it.

If I get something now I will tell you.

Dolores

[Former Member]

Hi Dolores,

We got the same reply(4 steps) from SAP and tried to fix it. But still facing the same error . I appreciate your quick response on this issue. Interesting to know that you are encountering same error in your DEV environment. Hope we will fix it soon.

If we solved the error , I will let you know.

Thanks

Kamal

[DoloresCorrea]

Hello Kamal,

Sorry for the confusion, I am working for SAP in the Support Center of Spain.

So I have access to see all messages from other customers, so what I did in

your case was check for similar issues in other customers.

If you have already open a message in SAP the support center processing the message will help you.

To open a message in SAP was my next recommendation if the previous did not work.

Best regards,

Dolores

[Former Member]

Hi Dolerus

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]

Will you please post the detailed resolution. Thank you very much in advance!

[Former Member]

Hi Kamal

Can you tell how you fixed this problem. I am having exactly the same problem on exactly the same environment. However I am doing a ECC 6.0 install.

Your help much appreciated. You can also email me.

Sridhar

ouremailnews@gmail.com

[Former Member]

Hi Wade

Did you 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

If you still face the error

let me know

thanks

Kamal

[Former Member]

Hi sridhar

This is the error which occuring with SOLMAN 4.0 and ECC 6.0 in the HPUX , Oracle environements

Try to trouble shoot with the below solutions,

Did you 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

If you still face the error

let me know

thanks

Kamal

[Former Member]

Hi Kamal.

I have tried all the above including getting the latest MIGMON. Still same error. Any additional information on this is highly appreciated. Thanks.

Sridhar

[Former Member]

Hi sridhar,

Did you check the minimum patch level requirements before install

The OS patch level should be

HP-UX 11.23 Itanium (HP-UX 11iv2)

QPKBASE B.11.23.0603.040a Base Quality Pack Bundlefor HP-UX 11i v2, March 2006

QPKAPPS B.11.23.0603.040a Applications QualityPack Bundle for HP-UX 11i v2, March 2006

FEATURE11i B.11.23.0603.040 Feature EnablementPatches for HP-UX 11i v2, March 2006

OS-Patch

PHCO_34021

PHSS_34043

PHSS_34041

PHCO_32489

regards

Kamal

[Former Member]

Thanks Kamal for the quick response. The following patches are applied.

QPKAPPS B.11.23.0609.053a Applications Quality Pack Bundle for HP-UX 11i v2, September 2006

QPKBASE B.11.23.0609.053a Base Quality Pack Bundle for HP-UX 11i v2, September 2006

FEATURE11i B.11.23.0609.051 Feature Enablement Patches for HP-UX 11i v2, September 2006

OS Patches

PHCO_34021

PHSS_34043

PHSS_34041

PHCO_32489

Are not applied. Prerequisite Check did not complain - it said it could not find these patches, however it was LOW priority.

Sridhar

[Former Member]

Hi sridhar

Though it shows low priority, the patches are mandatory. Atleast you need to have these patches or the superceeded patches below

check if these patches are applied

PHCO_34944

PHSS_35055

PHSS_34859

PHCO_35377

Because these are superceeded patches than the recommended. ( We had this error for both SOLMAN and ECC 6, and we are working with SAP to trouble shoot it). Some of the solutions I mentioned are from SAP recommendations.

So once check with these patches and reply me

regards

kamal

[Former Member]

Very useful