DE2 EHP4 INSTALLATIONTABLE OF CONTENT

S. No CONTENTS PAGE No.1 Pre-requisites Steps 01 - 49

1.1 Space requirements 21.2 Preventing Loss of Modifications 31.3 Preventing Activation Errors 31.4 Few Known Errors and solution 31.5 Actions Before Starting the Installation Program 31.6 Setting the Operation Mode for the Installation 41.7 Synchronizing the Database and the SDM

Repository5

1.8 Making Database-Specific Preparations for Oracle 51.9 Checking the Number of Background Processes 5

1.10 Installation File systems 5

1.11 System Status and SPAM Queue Check 6

1.12 SCC4 71.13 SAP Data File system 141.14 Tablespace Checks 141.15 SDM Repository Synchronization 151.16 Background WP: 161.17 SM37 161.18 RZ10 Profiles 181.19 OS Details 191.20 Archive Log Mode 191.21 Kernel Upgrade 201.22 Operation Modes Setting: 211.23 Update Records SM13 301.24 Profile Directory 301.25 Generation XML file From SOLUTION Manager 31

2 Starting of Upgrade through SAPehpi Tool 51-1633 Post-Processing: 164 - 1734 EHPI Post Upgrade Steps 1745 EHPI Upgrade Error / Issue Log Excel 175

1

1 Prerequisites before Installation

1.1Space requirements: Prepare free space for the Installation directory “EHPI” of approximately 10-15 GB (temporary requirement).

Prepare free space for the download directory for SAP enhancement package 4 and additional Support Packages of approximately 10-30 GB (temporary requirement).

Prepare free space for the shadow instance of approximately 100 GB. ( Note that the size required depends heavily on the customer situation – temporary requirement.)

Prepare additional space for existing tablespaces (depends on available freespace in each tablespace).

We recommend setting the autoextend setting for tablespaces.

Read the Note 1245473: Installation Keyword

*Note*

2

1.2 Preventing Loss of ModificationsIf the system that you want to update has a Support Package level lower than SAP NetWeaver 7.0 SP 13, and then implement SAP Note 1086728. This prevents the loss of modifications / repairs during the modification adjustment.

1.3Preventing Activation ErrorsUnder certain circumstances, information of runtime objects might get lost during the activation. This can lead to unwanted conversions of cluster tables. To prevent this error, see SAP Note 1283197 and implement the attached correction instruction.

1.4 Few Known Errors and solution

Phase XPRAS_UPGDescription: In this phase, the error "Name xyz has already been used". e065(fdt_core)" can occur in method FDT_AFTER_IMPORT.

Solution:

1. Continue the installation with option "Accept non-severe errors and repeat phase XPRAS_UPG"2. Apply SAP Note 1301695.3. Restart the after import processing for method FDT_AFTER_IMPORT using report FDT_TRANS_Q_RESTART for S-Tables, T-Tables and C-Tables.

Activation ErrorAn activation error for domains can occur that can be solved by repeating the failed phase. For more information, see SAP Note 1242867. If you have already implemented SAP Note 1242867 in your system, the error does not occur.

1.5 Actions Before Starting the Installation Program1. You choose the host for the installation.2. You make sure that the requirements for the modification adjustment have been met.3. You fill the download directory.4. You meet the requirements for the installation directory.5. You call transaction RZ04 to set the operation mode for the installation.6. You download the JCE Jurisdiction Policy Files.

3

7. You synchronize the database and the SDM repository.8. You download the enhancement package and required Support Packages using the Maintenance Optimizer in SAP Solution Manager.9. You make the preparations at the database level.10. You check the number of background processes.11. If your central instance and SCS instance run on different hosts, you update SAP kernel and SAP IGS manually.

1.6 Setting the Operation Mode for the InstallationVarious background jobs are started during the installation. When you schedule jobs, a check is made to see whether the SAP instance on which you want them to run is defined in an operation mode. The operation mode specifies which services are offered by the work processes (dialog, update,background processing, enqueue, spool, and so on).

PrerequisitesNo operation modes must exist that contain servers other than those belonging to the current system.Procedure1. Call transaction RZ04 to check the definition of your operation modes. In addition, check the DUMMY operation mode. The DUMMY operation mode may have <host name>_<SAPSID> entered as the server name. Change this entry to <host name>_<SAPSID>_<instance number>.2. Delete the invalid operation modes. If operation modes contain names of servers other than those belonging to the system, problems may arise in the background interface in some phases. The jobs may be released, but not set as active (in theory, this affects all jobs scheduled to start on a specific server and triggered by an event).3. If the SAP instance on which you want to install the enhancement package is not entered in an operation mode, create the operation mode for the installation as follows:a) Call transaction RZ04.b) Choose Operation mode Create .Enter a name for the operation mode, for example, EHP_Installation. Enter a short description and then save the operation mode.c) Make sure that the instance required for the installation has been started up.d) Position the cursor on the new operation mode and choose Operation mode Maintain instances Instances/OP modes .e) Choose Settings Based on act. status New Instances Create .This displays all instances and their current configuration.

4

f) Choose Save.g) Call transaction SM63 to enter the operation mode you have defined as an active operation mode for 24 hours (select Normal operation (24 hours)).

1.7 Synchronizing the Database and the SDM RepositoryBefore you start with the enhancement package installation process, you need to synchronize the database and the SDM repository.Procedure1. Go to the directory /usr/sap/<SAPSID>/JC<instance number>/SDM/program.2. Run the StopServer.sh script.3. In the command line, enter the following commands:./sdm.sh jstartup “mode=standalone”./sdm.sh systemcomponentstate “mode=activate”./sdm.sh jstartup “mode=integrated”4. Run the StartServer.sh script.

1.8 Making Database-Specific Preparations for Oracle1. Make sure that the statistics are up-to-date for all tables. Out-of-date statistics can increase the runtime of the enhancement package installation significantly. Proceed as described in Oracle:Performing Actions for the Cost-Based Optimizer2. Check the value of parameter shared_pool_size:select NAME, VALUE from v$parameter where name=’shared_pool_size’;select NAME, VALUE from v$parameter where name=’shared_pool_reserved_size’;If the value is lower than 150 MB, increase it to at least 150 MB (400 MB is better), and restart the database.3. Grant unlimited tablespace to saspr3/SAP<SCHEMA-ID>;

1.9 Checking the Number of Background ProcessesMake sure that the central instance of your system is configured to run at least two background processes before you start the SAP Enhancement Package Installer. We highly recommend using three.

1.10 Installation File systemsDownload Dir - /usr/sap/trans/E1_EHP

Installation Dir - /usr/sap/trans/ehde2

*DE2*.XML file location - /usr/sap/trans/E1_EHP

5

1.11 System Status and SPAMDE2 Status:

SPAM:

6

1.12 SCC4:

7

8

9

10

11

12

13

1.13 SAP Data File system: -

1.14 Table spaces:

14

1.15 SDM Repository Synchronization:

15

1.16 Background WP:

1.17 SM37:

16

17

1.18 RZ10 Profiles: RZ10 Parameters:

18

Default.PFLOriginal Settings

Changes Settings for EHP4

1.19 OS Details:

1.20 Archive Log Mode – ON ( AS CLIENT REQUIREMENT) Original Settings

19

Changed to

1.21 Kernel Upgrade:

20

1.22 Operation Modes Setting:Original

21

Changed toSM63

Click Change

22

Click Delete Assignment

23

Save

24

Click yes

In RZ04

Click Delete for Batch & Online

25

Create a Dummy_EHP

26

27

28

1.23 SM13 – Update Records:

1.24 Profile Directory (/sapmnt/DE2/profile):

29

Extra Files moved to /usr/sap/trans/IBM_EXPORT/profile_bkp_1305

1.25 Generation XML file From SOLUTION Manager

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

2 Starting SAPEHPI Tool

50

Start Time: - 11:00 AM IST, 130509

51

52

53

54

55

56

Reset PrepareStarted from Scratch—

57

58

59

60

61

62

63

64

65

66

67

68

69

70

71

72

73

74

75

76

77

78

79

80

81

82

83

84

85

86

87

88

89

90

91

92

93

JAVA Part is still Runninmg

94

95

96

97

Session was terminated here--restarted

98

99

100

Check logfile--

Put IGS SAR file in download directory.

101

Press Continue

102

Press Continue

103

104

Error-

Copy file from X1_EHP and Press Continue

105

106

107

Password=V0d@f0nePress Continue

108

109

110

111

Press Continue

112

113

114

Configuration phase finished here.

4. Checks.

115

Again Press next

116

117

118

119

120

Create tablespace and add datafile, also extend the required space in tablespaces as per requirement(See screenshot for space)

Press Close

121

Press Next

122

123

124

125

Press Close

126

Press Next.

127

5. Post Processing.

128

129

Press OK

130

Session Hanged out---

131

132

133

134

135

We are in the process of EHP4 upgrade, in the preprocessing phasersptbdst_pdit getting SQL statement error:

We are able

2EETG011 ""[DISP_CHK]/OSP/V_RAUI_CDDB missing SQL statement"

Reason : In some Table Modflag is not set correctly

Resolution : SAP Provide the solution

136

Run program again (program RDDGENBB with variant SAP_PARDISTV) and this time the MODFLAG column of table DDXTT has been set correctly.The reason why the MODFLAG hasn't been set for several rows oftable DDXTT is still unclear.

Nevertheless, you can now try to repeat phase RUN_RSPTBFIL_PDIST again. Hopefully, it succeeds this time

After this Installation pass the error step

Press OK

137

138

139

140

141

142

143

144

Issue: Memory Issue

Resolution: Increase memory in Shadow Instances.

145

Error in License Check

DE1:

Error: Error in license check and logon not possible.

With this error we were also getting below error in which some BW tables contained some data and need to be deleted this data from Main system.

Root Cause: Either license was not installed or Problem with Enqueue server. And BW tables contain some data.

Resolution: 1) Tried to install license in the systems again by using below command at OS level:

Saplicense –install –ifile=<location of license file>

146

Above resolution was not successful because in ECC6.0 we cannot install license from OS level as it contains digitally encrypted license key.

2) When BW tables were containing some data and we tried to start main instance manually to delete data from these tables but main instance was not coming up as shadow system was up. During downtime in upgrade only one system can use enqueue server. So, shadonw system was using enqueue server. So, we shutdown the shadow system and start the main instance. Then we deleted the data from these tables.

Note: Both problems came simultaneously so not sure which resolution resolved our problem.

Error:

147

During EHP4 installation, we got error in Downtime phaseMAIN_SWITCH/JOB_RSVCHCK_D. There were update records left. We logged inthe Main Instance and cleared the records. now when we are repeatingthe phase MAIN_SWITCH/JOB_RSVCHCK_D it is giving following error

ERROR: RFC of "subst_start_batchjob" failed.key : RFC_ERROR_COMMUNICATIONmessage : SAP_CMINIT3 : rc=20 > Connect to SAP gateway failedConnect_PM DEST=DE1, GWHOST=avggstah, GWSERV=sapgw06, SYSNR=06

LOCATION CPIC (TCP/IP) on local host with UnicodeERROR partner 'avggstah:3306' not reachedTIME Fri May 29 21:18:49 200RELEASE 710COMPONENT NI (network interface)VERSION 39RC -10MODULE nixxi.cppLINE 2773DETAIL NiPConnect: 192.125.172.4:3306SYSTEM CALL connectERRNO 239ERRNO TEXT Connection refusedCOUNTER 54

It appers that EHPI tool is trying to login to shadow instance but itis not up and running SHadown instance number is 06

Reason Port is used by DB1 system.

Resolution:

148

Stop DB1 Restart DVEBMGS01, DVEBMGS06 instances for DE1 have been restarted. After port 3606 is freed the instances have be restarted, because 06 instance is inoperable presently due to the stopped message server. Kill the message Server process stop both instances.and then start shadow instance

149

150

151

152

153

154

155

156

157

158

159

160

161

162

163

3 Post-Processing:

3.1 Enable archive log mode.

1) Log in to system DE2 and verify ABAP Stack level:

2) Logon to portal of DE2 and verify Java patches:

3) Login into DE2 and run transaction SICK.

164

4) Run saproot.sh and oraroot.shcd /sapmnt/DE2/exe./saproot.sh DE2Also, ./oraroot.sh DE2 DE2

5) Create and Update SAPDBA Role:cd /oracle/DE2/102_64/dbscp /sapmnt/DE2/sapdba_role.sql sapdba_role.sqlsqlplus /nolog@sapdba_role SAPEVO

165

6) Rescheduling Background Jobs:Login to 000 client of DE2 with user DDICGo to transaction SE38Run Report BTCTRNS2

166

7) Go to SM51 :

8) Run Transaction SGEN

Press Continue.

167

Press Continue.

Press Continue.

168

Press Start Job Directly.

169

170

9) Delete Tablespace PSAPEVO700:

171

172

173

4 EHPI Post Upgrade Steps

174

5 EHPI Upgrade Error / Issue Log Excel

175

176

177

178