OCS locked by SPAM

[Former Member]

Hi all,

I facing issue in applying the support package. The SAINT giving message "OCS is locked by transaction SPAM. Process all the steps of the transaction SPAM until they are completed.".

On the other hand SPAM is running in display mode due to the lock therefore I am unable to run the transport unless SPAM is unlocked.

Please advise how to get around this issue.

Regards.

[former_member185031 · Accepted solution]

You have to check in SPAM, that session must be lock by some other user. If any other user is not working you can kill his session in SM50 or delete the lock in Sm12. You hav to complete the update process then only you can work on SAINT.

Regards,

Subhash

[Former Member · Accepted solution]

Subhash,

I have checked SM12 and no object is locked there. SM50 shows report SAPLTHFB in running status and is first in the queue. All of the remaining processes are waiting in queue for this report to complete. Further details show the last sql statment ran is below:

SELECT

/*+

first_rows

*/

s.module, s.action, t.sql_text

FROM

v$session s, v$sqltext t

WHERE

s.sql_address = t.address and s.sql_hash_value = t.hash_value and s.machine like :A0 and s.process

like :A1 and s.client_info = :A2

ORDER BY

t.piece#

Rohit,

No other user is authorized currently to load package or patches. So no issue is the sense that another has already locked the queue.

Regards.

Edited by: Mohammad Shoaib Ali on Jun 9, 2009 12:02 PM

[former_member185031 · Accepted solution]

If you execute SPAM. It will give you a message queue is locked by user XYZ. So you can reset the password of that user then you can login with user XYZ and update the support pack.

Regards,

Subhash

[Former Member · Accepted solution]

Okay,

Seems there is bit of misunderstanding here.

It's not locked because of a user. The message displayed in SAINT is "OCS is locked by transaction SPAM". Currently I am upgrading the NW04s system to SP12. Also, I am working in SPAM but since it is in lock status it is not possible to continue the transport. Yet again, STMS shows all transports went through but with warnings. Now the issue here is that:

1. The system is not upgraded successfully even though the transports are displayed successful in 000 under STMS.

2. SPAM is locked and SM50 shows the first process in the list is still running, leaving the remaining process in waiting status.

3. SM12 shows no object is locked.

4. SAINT (not using currently) shows OCS is locked by SPAM... which is true... but then it's over 14hrs and still the first process is running without completion and without any error.

In fact I was using DDIC to carry out the support package and during the process, ddic got logged out for unknown reason. After logging back in, it's showing the above scenario especially with regards to SM50 where it's still processing report SAPLTHFB for over 14hrs now.

Please suggest.

Regards.

[former_member185031 · Accepted solution]

You should not use DDIC. You should use any other user who has SAP_ALL & SAP_NEW. So now if any job is running the you should check under the /usr/sap/trans/tmp & /usr/sap/trans/log directory. During the update process it generates some temorary files which can tell you the job log. from there you can see the problem.

Regards,

Subhash

[Former Member]

Hi Every Body,

Below is the corect answer for the this issue.

Symptom: The import of a SPAM/SAINT update has terminated at the end as described above. When you restart the Support Package Manager, it looks as though the SPAM/SAINT update has been imported completely, and the traffic light icon in the "Status" frame on the right-hand side shows a green traffic light. However, when you call the Add-On Installation Tool, the system displays the error message TN 401 "OCS locked by user xxx with transaction SPAM".

Reason: Due to the termination with a runtime error, inconsistent table entries may remain in the system. These have to be cleaned up.

"Solution: Start the Support Package Manager and choose "Support Package" -> "Import SPAM/SAINT Update". Since the SPAM/SAINT update has already been imported completely, no other actions will be carried out except for cleaning up possible inconsistencies.

If another SPAM/SAINT update is offered for import, you can cancel it at this point; the inconsistencies are cleaned up despite this."

[j_raymakers]

Hi all,

Correct! had the same issue.

Solved by Starting the Support Pack Manager as written above did solve the problem.

Many thanks!

Best Regards,

Jacco Raymakers

[Former Member]

Hi

If possbile can you bounce the server once and see still the problem exists.

Regards

Uday

[former_member204746]

you probably forgot to confirm your last supoprt pack from SPAM:

in client 000, go into transaction SPAM and CONFIRM the queue with the double-green checkmark button. This will unlock SPAM and SAINT.

other case, you might have created a queue in SPAM but never applied it:

so, reset OCS queue in SPAM.

Third option:

you have not completed applying your support pack in SPAM. go into SPAM and click on the TRUCK icon.

good luck.

[Former Member]

Thanks all,

The problem is resolved. However, I had to restore the backup and carry out upgrade again, this time it did went through successfully without OCS getting locked by SPAM.

Thanks to all who contributed and points have been awarded to all.

Regards.

[Former Member]

Mohammed

you will not be able to use SAINT as SPAM is running,someone might have run some patches through SPAM and unless they complete you can't use SPAM

Rohit