SAP Note

    1751798 - don't unpack kernel archives using Software Prov. Man. 1.0  
Version   2     Validity: 22.05.2013 - active   Language   English

Header Data
Released On 22.05.2013 15:34:34
Release Status Released for Customer
Component BC-INS Installation Tools
Priority Recommendations / Additional Info
Category Installation information

Symptom
You are installing an additional application server instance (AAS), respectively a dialog instance
using the Software Provisioning Manager 1.0 SP1 or higher for a system which is still using a kernel
release lower than 7.20 or 7.20_EXT.

Other Terms
additional application server dialog instance software provisioning manager, SWPM

Reason and Prerequisites

The kernel of the central instance / primary application server instance has a lower version than
the kernel of a dialog instance / additional application server instance being installed. You have
to make sure that the kernel version used by the primary application server is not overwritten
accidentially.

Solution
To make sure both the primary application server and the additional application server are using the
same kernel-version, you have to make sure that the kernel archives are not extracted from the 7.20
kernel DVD. To achieve this follow the steps described below:

Unix:

1. When you reach the "Unpack Archives" screen, deselect the relevant
archives SAP*.SAR, IGSEXE.SAR from the "Archives to Be Unpacked" checklist. The dialog screen
"Unpack Archives" is only visible when     you choose the "custom" mode for the installation or when
you choose   'revise' in the summary screen of the installation parameters before starting the
installation.

2. When SAPinst prompts you to manually unpack the archives you have
   deselected, stop SAPinst.

3.  Restart SAPinst from the command line as follows:

    ./sapinst SAPINST_SKIP_ERRORSTEP=true
Windows:

1.  When you reach the "Unpack Archives" screen, deselect the relevant
    archives SAP*.SAR, IGSEXE.SAR from the "Archives to Be Unpacked"
    checklist.

2.  When SAPinst prompts you to manually unpack the archives you have
    deselected, stop SAPinst.

3.  Edit the keydb.xml file which you can find in the installation
    directory (sapinst_instdir), and replace [CDATA[ERROR]]with
    [CDATA[OK]] for the unpack step.

4.  Restart SAPinst, on the "What do you want to do?" screen, choose

    "Continue with the old option".
5.  When SAPinst fails while trying to create the SAPOsCol service, stop
    SAPinst again.

6.  Edit the keydb.xml file which you can find in the installation
    directory (sapinst_instdir), and replace [CDATA[ERROR]] with
    [CDATA[OK]] for the createOsCol step.

7.  Restart SAPinst, on the "What do you want to do?" screen, choose

    "Continue with the old option".
Note:
If you do not follow this procedure, you might experience problems when
you continue the installation such as that the dialog instance /
additional application server fails to start. Then you can only overcome this issue by manually
updating the kernel of the central instance / primary application server instance of the existing
system.
Do NOT uncheck IGSHELPER.SAR.

Do not uncheck the extraction of kernel archives for the Solution Manager Diagnostics Agent (DAA).
When installing a dialog instance/additional application server instance for a system which includes
a Java Stack, please make sure that the Primary Application Server and other involved instances are
using SAP JVM. Otherwise perform a JVM Switch as per note # 1665953 before the installation.

Validity
Software Component From Rel. To Rel. And Subsequent
SAP_BASIS 700 702  

References
This document refers to:
SAP Notes
1701575   Don't unpack old kernel archives when installing DI/AAS
1680045   Release Note for Software Provisioning Manager 1.0 SP05
1665953   SAP JVM Switch Tool Composite Note

This document is referenced by:

SAP Notes (3)
1701575   Don't unpack old kernel archives when installing DI/AAS
1680045   Release Note for Software Provisioning Manager 1.0 SP05
1665953   SAP JVM Switch Tool Composite Note