Hum, I wanted to say a lot after a third time struggling with support package implementation, but I will only talk about some details that I can still remember. Though they might not be that essential for such a process, but I believe they are interesting enough. :)
1. For a CRM system, SPAM’s function is replaced by a specific CRM support package implementation manager. The tricky point is, every time an error occurred and the implementation stopped, I used to directly ‘import’ queue to continue the installation after I got that problem solved. However, I found that the recommended way is to re-call the CRM specified SPAM and in the Wizard, it will ask you if you wanna go on.
Although most time directly ‘importing’ the queue is OK, in case of any potential errors, we should follow the standard process.
2. About the monitoring.
Basically we directly refresh the spam screen to monitor the implementation process. When error happens, we ‘Go to’ the status of the queue or the object list or action log, blabla.
However, from the troubleshooting point of view, monitoring on the operation system is even better, sometimes it can tell u something which might be hidden in the GUI screen.
In the operation system, u first need to open the task manager. Sometimes the implementation hangs on one step without popping up any error on the screen, the task manager will reveal that nothing is happening on the server, and then you can manually stop the tp process and check why it stops.
The second way to monitor is just to open one folder - <sapmnt>/trans/temp. This folder keeps all the logs that are temporarily generated. You can monitor if the latest log is increasing its size. If it is still increasing, then don’t worry about the hang working processes.
Last but not the least, don’t forget the SAPMMC. I really think this is an excellent tool for monitoring and troubleshooting. With SAPMMC and task manager, you can feel the heartbeat of your dear SAP system.
3. Trouble shooting
Yes, as always, trouble shooting is very important.
But one thing that’s more important is to prepare well before you start.
-> Have you checked all the related SAP Notes for your support packages?
-> Have you downloaded all the possible CRTs if your system has any add-ons?
-> Have you finished the tp tool and r3trans tool upgrade? (via either kernel upgrading or updating these two tools.)
-> What about the request management?
Most of the errors are caused by the inadequate preparations, and for sure, you will meet some trouble, then I suggest you establish your own regular way to find out the root cause.
Check the queue status, then the action log, then u might need to check the tp tool’s log, and also the queue log.
On the operating system, you can also go the <sapmnt>/trans/log folder then check the latest logs. Scroll down to the bottom, find the key words ‘Error’ ‘Cancel’ ‘Terminate’ ‘Duplicate’ etc..
According to the types of the errors, you can figure out if you still need to check the logs in the <sapmnt>/<sid>/<CI>/work or the j2ee folder, or database log if you are really unlucky.
4. Tips.
For ‘Main import’ phase, ‘tp r3i’ command might always be a strong backup for possible failure. :)
For file creation/open authority issues, you can always check the security properties of that file, and if possible, give the full control to the Users group.
Dear friend, do you have any interesting but tough experience when you implement the support packages? Sharing is always welcome, thanks for reading.
(end)