error importing support pack SAPKH60011 (SAP_APPL)

[Former Member]

Dear All,

I am faceing one error when applying support pack SAPKH60011 can not apply showing error " The import was stopped since an error occurred during tha phase IMPORT _PROPER ....". for details i here attached screenshot .

Pls. reply ,

Thanks and regards,

Mayur

[Former Member]

Dear Mayur,

please check the below.

go to T code spam-->click on go to menu --> action log.

it will display a list of locked object.

you can select the locked object name after the word R3TRPROG

go to se03> click on display repaired object>double click on the your selected object-->click on lock over view

it will shows the request no which is locked.

now again go to T code se03> click on unlock object> give the request no.

after that you can try to import again it will work

Regards

Robin

[Former Member]

Instead of presuming it's best to have the contents of SLOG file to identify what has gone wrong. Logs can only tell you where you are stuck and analyze the issue further.

Regards

Sourabh Majumdar

[Former Member]

Hi Tandel,

Try to restart the import, it should continue from the point the error occured.

Basisman.

[paul_power]

Hi Mayur,

You need to check the latest alog, ulog and slog.

Check the main import log SAPI<package name> which should be in usr/sap/trans/log

This will cotnain details of why the import failed.

It it failed due to a deadlock occuring which can occur if someone is using the system while import is occuring, you should restart the database to clear any locks before attmpting the import again.

Another cause of failure during import can be the use of out of date transport tools. Please ensure you are using the latest tp and R3trans available for your release from the service marketplace.

Are you still able to access the system and repeat the import via SPAM?

******************************************************************************************************************************

If every transaction is resulting in a dump and Syntax errors, then please open a message with SAP and provide the alog, ulog and slog along with the main import log and screenshots of the results of

tp showbuffer <sid> pf=<path to transport profile> tag=SPAM

and screenshots of the contents of usr/sap/trans/tmp

for further analysis. Also, please do NOT make any manual commands or changes to the buffer or it can make the situation worse.

*******************************************************************************************************************

Ensure if the import has failed, that the related SAPKK<package name> is renamed / moved from usr/sap/trans/tmp if it is still there from the failed import attempt. If they are still there when you try a new import, the slog will filll with entries of

warning file ...... is already in use, waiting 30 seconds

and the import will not progress.

These files will be created once the new import is started.

When repeating the import, please monitor the SLOG entries and see that usr/sap/trans/log and usr/sap/trans/tmp are being updated regularly, this will allow you to see the progress of the import.

Please update with the contents of SAPI...... if the import still fails.

Best regards,

Paul

[former_member126060]

Hello Mayur,

Just check the SAPIH60011 log file under the trans/log directory and check what was the error due to which the import aborted.

Additionally also check the SLOG file and find if any error occured.Then proceed accordingly.

Best Regards

Niraj

Edited by: Niraj Kumar Soni on Mar 26, 2010 12:22 PM

[Former Member]

Mayur,

Please paste the contents of latest SLOG file residing in the directory /usr/sap/trans/log.

Regards

Sourabh Majumdar