Archive for the ‘Support Pack’ Category:
SAP Spool issue – affects all Releases
SAP have detected a problem in the spool area which affects all customers in the world regardless of the SAP release and any support package level.
As soon as the retention time of a spool request exceeds 2009/12/31 a wrong date 2100/01/01 is entered during creation of the spool request. As a consequence these spool requests will not be deleted anymore from the spool reorg jobs. Using the default retention period this affects all spool requests on each SAP system in the world created since 2009/12/23.
OSS Note 1422843 already contains the correction instructions and the relevant kernel patches for 3.1 –> 46B (one patch) and 46c –> 7.xx (another patch). There’s nothing for anyone (unfortunate enough to be) running any of the original 2.x systems yet.
It is a little ironic – An old friend and I were discussing Y2K and all that in a general “what were you doing ten years ago ?” manner on New Years Eve. Should I tell her that SAP had a Y2K+10 ?
Support Package Manager – Reset Queue
Occassionally, when loading Support Packages or SPAM/SAINT Updates, the Support Package Manager (transaction SPAM) can get a bit ‘confused’. A colleaugue had this problem recently, where she was attempting to update the SPAM tool on a 4.6C system. The result was that the Support Package Manager was reporting Queue_Not_Empty .
Some times the cause is simply forgetting to confirm / finish the last SPAM/SAINT update. Once you’ve eliminated this, you need to start checking what the TMS mechanism thinks has happened. To check what is in the TMS buffers, logon to the Operating System, change directories to /usr/sap/trans/bin and execute the following: Basically you need to reset the SPAM Queue to match the TMS buffers. To remove entries from the internal SPAM Queue, uUse the function module (transaction SE37) OCS_RESET_QUEUE. Execute it with parameters IV_TOOL=SPAM, IV_FORCE=X. To remove entries from the TMS buffer, execute the following command (change directory to /usr/sap/trans/bin first), where SAPKXXXXX is the 'offending' Support package or SPAM/SAINT Update: Before restarting the Support Package import, ensure that you've removed all files from \usr\sap\trans\tmp and make sure there is no other TP process or R3trans process running in the system at Operating system level. Usefull Links:
tp SHOWBUFFER
tp delfrombuffer SAPKXXXXX
Errors During Support Package Manager Phases
SAP Patch Manager (SPAM) PDF
List of OSS Notes in a Support Pack
If Project Managers or Developers want to know if a particular OSS note will be implemented by a particular Support Pack, you can direct them (via http://service.sap.com/notes ) to the details of the particular Note. Sometimes, though, there is a large number of OSS notes, or they want to know ALL the Notes implemented in a given Support pack. You can get this list via the SAP Support Portal. The first step is to search the Software Distribution Centre ( http://service.sap.com/swdc ) for the Support Pack that you wish to list the Notes for.
Note that the Search Term field requires the full name of the Support pack, in this case SAPKE47080, not KE47080.CAR (which is the name of the download)
Searching for the Support Pack (or a list of Support packs, if you get the Search Term syntax correct) will produce a formatted list of the Support Pack(s).
You may recognise this screen as one you have used for downloading Support Packs or adding Support Packs to a Download Basket.
If you select the description (I have circled it in red in the screen shot), the browser will open another tab / window that has a hierarchical list of all Notes in the Support Pack. Follow the instructions on this screen to download the list.
Note that if you wish to drill down the hierarchical list, you can do so by selecting the line containing the SAP Component code
Repeat the search (if necessary) and download steps for each Support Package you need to produce a list for. Please let me know via the comments if this has helped you, if you have any questions about the process, or if you have any other topics you’d like me to write about.
