DB6: SAP NetWeaver Inst. based on Kernel 7.11 – Windows

[] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] []

Related:

  1. DB6:Inst.NW 7.0 EHP2 – WindowsSymptom SAP NetWeaver 7.0 incl.EHP 2 on Windows with DB2...
  2. DB6: SAP NetWeaver Inst. based on Kernel 7.11 – UNIXSymptom SAP NetWeaver Installation based on Kernel 7.11 – UNIX...
  3. DB6: SAP System Inst. with DB2 V9 only – UNIXSymptom SAP System Installation based on SAP Kernel 7.0 with...
  4. DB6: Installation of FixPaks for DB2 V9.5 (UNIX+Linux)Symptom This note relates to installing FixPaks for DB2 V9.5...
  5. DB6: Installing FixPaks for DB2 V9.1 (UNIX+Linux)Symptom This note relates to installing FixPaks for DB2 V9.1...
  6. DB6:Inst. NW7.0 EHP2 – UNIXSymptom SAP NetWeaver 7.0 incl.EHP 2 on UNIX with DB2...
  7. DB6: Installation of FixPaks for DB2 V9.5 (Windows)Symptom This note relates to installing FixPaks for DB2 V9.5...
  8. DB6: Installing FixPaks for DB2 V9.1 on WindowsSymptom This note relates to installing FixPaks for DB2 V9.1...

Symptom

SAP NetWeaver Installation based on Kernel 7.11 – Windows
IBM DB2 V9.5 for Linux, UNIX, and Windows

Other terms

NW2007 installation, SAPinst, DB2 for Linux, UNIX and Windows, DB6
SAP Web AS
Reason and Prerequisites

Problems discovered after publication of the installation guide.
Solution

Welcome to the installation of SAP systems based on kernel 7.11 -
Windows – IBM DB2 V9.5 for Linux, UNIX, and Windows
Provide any feedback, questions or comments on this or platform-related notes on our SDN Expert Forum at:
https://www.sdn.sap.com/irj/sdn/forum?forumID=187
This note contains the following sections:
I. PRE-INSTALLATION
II. INSTALLATION PROCESS
III. POST-INSTALLATION
IV. INSTALLATION DOCUMENTATION – CHANGES
V. UNINSTALL

Note:
=====
This note comprises information relevant to the installation of the SAP systems based on kernel 7.11
SAP NetWeaver Process Integration 7.1 incl. EHP1ACC 7.1 in SAP NetWeaver 7.1 incl. EHP1SAP NetWeaver Mobile 7.1 incl. EHP1

Table of Contents:
==================

The following is a chronological summary of all changes or entries applied to this SAP Note.

Date Topic Type of entry
=====================================================
16.04.2009 II Error installing DB2 V9.5 in domains
with underscore in the domain name
======================================================================

I. PRE-INSTALLATION

You must not have any DB2 user that SAPinst creates (for example, the user DB2) locally and in the domain.

Provide enough free space for the database file systems (sapdata*):
ForSAP NetWeaver PI 7.1 incl. EHP1, the default spaces are:
File system Unicode
sapdata, n=1,2,3,4 (ABAP+Java) 18 GB
ForSAP NetWeaver PI 7.1 incl. EHP1, the default spaces are:
File system Unicode
sapdata, n=1,2,3,4 (ABAP) TBD GBInstallation of a MCOD system:
Increase the database configuration parameter DBHEAP to double the value. Log on as user db2 and enter the following command:
db2 update db cfg for using dbheap
For example, if the value of DBHEAP was 25000, set it to 50000.

Using multiple database partition server only:
Before you install additional database partition(s) on a new database partition server, include user \db2 in the local administrator group of the new database partition server.

=======================================================================
II. INSTALLATION PROCESS

The following errors can occur during SAP system installation: .

MCOD Installation:
To avoid an error during step “testDatabaseConnection” in your MCOD installation, you have to grant a privilege to user sap.
Otherwise, you will see an error like the following:
ERROR [sixxcstepexecute.cpp:956]
FCO-00011 The step testDatabaseConnection with step key …
Solution:
Enter the following as user db2:
db2 GRANT DROPIN ON SCHEMA SAPTOOLS TO USER SAP

AS ABAP
Using a high number of parallel R3load processes can lead to a “Log full” situation. If this happens, choose “Retry” on SAPinst dialog.

Error installing DB2 V9.5 in domains with underscore in the domain name
SAPinst aborts during the DB2 V9. 5 software installation with return code 87 generated by setup.exe. In the files db2setup.log and db2setup.trc in the installation directory, you find the following errormessage:
ERROR:A Response file error occurred. The value “” is not valid for the keyword “DB2_ADMINGROUP_DOMAIN”.

For information about how to solve this problem, follow the instructionsin the relatedSAP Note 1329554.

=======================================================================
III. POST-INSTALLATION

MCOD uninstall
If you unsintall a MCOD system and you have used deferred table creation, there is a slight chance that not all tablespaces, which belong to your deleted SAP system, are dropped.
Solution:
Check your tablespaces after the MCOD system uninstall. If required, drop any tablespace that is left over manually.

Using multiple database partition server only:
After installing additional database partition(s) on a new database partition server, you must update the DB2 Registry according to the settings of the instance owning database partition server, for example, “DB2SET DB2COMM=TCPIP”. .

=====================================================================

IV. INSTALLATION DOCUMENTATION – CHANGES

No entries so far!
=======================================================================

V. UNINSTALL

Deinstallation of SAP systems with DB2 V9.5 only:
After the deinstallation, the port range entries DB2_DB2< DBSID>, DB2_DB2_1, …, DB2_DB2_END remain in the services file %WINDIR%\system32\drivers\etc\services.
Remove these entries manually by editing the services file.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Leave a Comment