How to reinstall the Support Package Manager from the command line in SAP Basis

Support Packages are installed using the so-called Support Package Manager (transaction SPAM). As with all software components, newer versions of the Support Package Manager are made available on a regular basis. Their installation processes might look strange at first sight. The old Support Package Manager, available in the system is used to install the new. During the procedure, the old one is replaced with the newer version.

What if something went seriously wrong during the installation of the Support Package Manager? In a best-case-scenario, SPAM offers the option to re-start the installation. In a worst-case-scenario, the failure occurred during a critical phase of the installation process. The installation cannot be repeated, as the tool to install it is no longer there. A full database restore is an option, but not realistic. A database restore just to retrieve the Support Package Manager is a little bit too much to ask for.

As an alternative, the Support Package Manager might be installed from the command line. This is what this tip is all about.

2. Upload and disassemble the SPAM upgrade
During the upload, the support package archive is copied to the transport directory. It is converted to a transpor...

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT SAP Basis administration tips Converting from MDMP to Unicode Can SAP developer include authority check for S_TCODE in a called transaction? How to fix Smart Forms printing double purchase orders Deriving the name of a Smart Style from a Smart Form SAP FI/CO consultant's role during upgrade from R/3 to ECC 6.0 Alternatives to downloading a trial version of SAP IDES ERP software Verifying data consistency in production SAP FI/CO system when restoring a backup How to upgrade DB2 on SAP R/3 4.7 How to create a snapshot from NAS and SAN of Oracle database How to clone an SAP ECC 6.0 instance SAP tips and best practices Minimizing business disruptions during an SAP upgrade or implementation Retrieving content from an SAP workflow attachment Updating URLs in SAP SRM How to change default settings in SAP SRM What are the benefits of implementing SAP SRM? Increase column width in a transaction screen Updating an RT table entry in SAP HR Payroll -- without the ADDWTE option Is this the quickest way to find a BADI? Adding custom fields for retail product comparisons in SAP BW Improving performance with ABAP Objects in SAP Workflow SAP Basis administration and NetWeaver administration Collaboration a must for SAP hardware teams and software teams How to establish communication between SAP Unicode and non-Unicode systems Mission-critical SAP software demands a mission-critical hardware infrastructure In an upgrade to SAP ECC 6.0, when do integrated apps get upgraded? NetWeaver PI 7.1 easier to implement than earlier versions, SAP says SAP Software Deployment Manager vs. Java Support Package Manager Tips for setting up a default SAP BI client after implementation How to reset the SAP transport buffer after abnormal patch termination Installing SAP NetWeaver PI 7.1 on servers running ECC 6.0 How to install an add-on using a SAINT transaction in SAP Basis SAP Basis administration and NetWeaver administration Research

RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary Basis  (SearchSAP.com)

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

t request during the disassemble process. The disassembling is automatically done when the support package is being installed. This cannot be done on the target system because transaction SPAM is no longer there.

However, SAP systems which reside in the same system landscape share the transport directory. Another system can be used to upload and disassemble the SPAM package.
1. Connect to one of the other SAP systems in your landscape. Remember, SPAM is operated from within client 000.
2. From within the Support Package Manager, upload the SPAM archive from the front-end (in the menu 'Support Package' --> 'Load' -- > 'From the front-end').
3. Disassemble the Support Package. In the menu, go to 'Utilities', 'Disassemble Support Package'. Choose the SPAM archive and confirm.

[IMAGE]
Figure 1: Transaction SPAM, disassemble the archive manually

3. Install the Support Package Manager manually
Install the Support Package Manager using the command line.

1. As user <sid>adm, connect to the server.

2. Open a DOS box or Telnet session.

3. Go the transport directory:
# cd H:\usr\sap\trans\bin

4. Use tp to add the transport to the buffer:

NOTE: The <SID> in TP_DOMAIN_<SID>.PFL is the <SID> of the Transport Domain Controller. This is not necessarily the same as the system into which you wish to import the SPAM transport request.

5. Import the transport request:
6. In SAP, try transaction SPAM. Voila, after a few compiles the Support Package Manager reappears!

Rate this Tip To rate tips, you must be a member of SearchSAP.com. Register now to start rating these tips. Log in if you are already a member. DISCLAIMER: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.