Solution Manager Upgrade from Solution Manager

7.01 to 7.1

1 Objective.............................................................................................................. 2

2 Notes to be referred:............................................................................................ 2

3 Software Requirements:....................................................................................... 2

4 Hardware Requirements:...................................................................................... 2

5 Checking the Structural Requirements.................................................................3

6 Filling the Download Directory..............................................................................4

7 Starting the Upgrade............................................................................................ 5

7.1 Initialization.................................................................................................. 11

7.2 Extraction..................................................................................................... 12

7.3 Configuration............................................................................................... 20

7.4 Checks......................................................................................................... 47

7.5 Pre-Processing.............................................................................................. 59

7.6 Downtime..................................................................................................... 71

7.7 Post-Processing............................................................................................ 75

7.8 Finalization................................................................................................... 79

8 Post Upgrade activities.................................................................................... 79

8.1 Performing Oracle Specific actions..............................................................79

8.2 Activating the SICF Services.........................................................................80

8.3 Rescheduling the Background Jobs..............................................................82

8.4 SGEN Generation of Loads.........................................................................84

9 Issues Faced....................................................................................................... 85

Problem 1 Component specific Issue during Configuration Roadmap..............85

Problem 2 Port already in use issue in Configuration Roadmap.......................86

 Problem 3 Presence of error summaries in ACTUPG phase in Pre-Processing
Roadmap............................................................................................................ 88

Problem 4 Unresolved requests in buffer ASM issue in Downtime Roadmap. . .89

10 References:...................................................................................................... 89

1 Objective: This guide describes the step by step approach for the Solution
Manager Upgrade from 7.01 to 7.1 on Windows Server 2003 and Oracle 11.2 G.

2 Notes to be referred:
S.No Notes to be referred Notes Description
1 1462137 Information about
upgrading to Solution
Manager 7.1

2 819655 Oracle Database specific

Note for the Upgrade

3 1577909 Supplements to Solution

Manager 7.1

3 Software Requirements:
Source Release - The source release for the Upgrade must be either Solution
Manager 7.0 or Solution Manager 7.01.

4 Hardware Requirements:
File system Space Requirements 20 GB of temporary disk space in the file
system for the Upgrade directory.

Free space in Database At least 60 GB free space in the file system for
the Database.

Database statistics Run the DB Statistics for Oracle prior to and after the
Upgrade.

Making Preparations at the Database Level:

Following Database specific preparations to be carried out.

 Check the value of Parameter shared_pool_size.If the value is lower
than 150 MB, increase it to 400 MB and restart the Database. Refer
SAP Note 556764 for more details.

Log on as user <sid>adm at the OS level. Check the resource quota of

database user SAP<SCHEMA-ID> or SAPSR3.Make sure the resource
quotas are Unlimited.

5 Checking the Structural Requirements

Set the public substitution variable com.sap.cm.share in the SDM
configuration.

Synchronize the Database and SDM repository before starting with the
Upgrade process.
6 Filling the Download Directory
Download all the relevant files for the Upgrade like Enhancement Packages, Support
Pack stacks and Stack Configuration file relevant for the Upgrade.

Download the Upgrade configuration stack and corresponding stack XML file
through Maintenance Optimizer in Solution Manager for the Upgrade. Place
the downloaded files in the Download directory for the Upgrade.

Download the relevant DVDs corresponding to Upgrade from the SWCenter

on SAP Service Marketplace.
 Installations and Upgrades -> My Companys Application Components -> My
Companys Software -> SAP Solution Manager -> SAP Solution Manager 7.1
-> Upgrade -> [OS version] -> [DB version].

7 Starting the Upgrade

Unpack the Upgrade package with the following command

SAPCAR xvf <download directory>\<path>\<Archive>.SAR R E:\z_solm\upg

** The complete path to SOLMANUP should not exceed 30 characters.

To start the Upgrade program, enter the command STARTUP.BAT.

Start the GUI for the upgrade with the command DSUGui.bat.
Specify the host name and port for the connection. Mention host name as
localhost and Port number as default as taken by the tool 4241. Click Log on
to connect to the server.
Click Accept in this screen.
The SOLMANUP tool prompts for admin user and password. Specify the same and
note down the password as it is required in case for restarting the Upgrade from the
point it has stopped.
Choose Next in this step to start the Initialization Process.
7.1 Initialization
Initialization step is completed. Click Next in this step.
7.2 Extraction
Enter the keyword and provide the path to Download Directory and click
continue.
Provide the password for the DDIC user, and OS Specific Password and DB
Password.
Extraction phase is in progress.

Enter the DVD Mount points for the required DVD corresponding to Kernel.
Enter DVD path corresponding to Oracle RDBMS client.
Enter DVD path corresponding to Export DVD for product CRM/SOLMAN
Results for Extraction phase. Make note of the manual actions required if any.
Extraction phase is completed. Click Next to proceed to Configuration Phase.
7.3 Configuration
Select High Resource use Archiving off Configuration mode and proceed.
Tool shows the details for the selected configuration. Click Accept Choice and
select Continue.
Download the latest version of SPAM/SAINT update for source release 701 and put it
in the download directory. In this step, SOLMANUP tool offers to update SPAM
version of Current release.
Configuration Roadmap is in progress.
Provide the path for the Language DVDs.
There are no Add-On CDs to be added. Hence, select Continue without adding
CDs and Click continue.
Provide the Stack Configuration XML file downloaded through Maintenance
Optimizer as described in Note 1577909 and click Continue.
SOLMANUP tool shows the following error around SAPK-100AGINCTSPLUG and this
issue is resolved by repeating the phase.

Enter the EHP Keyword as mentioned in Note 1306080 and Click Continue.
As the decision mentioned for the Add-Ons in each case is satisfactory, Click
Continue in this step to proceed.
As the Support pack level offered by the SOLMANUP tool is satisfactory, Click
Continue in this step to proceed.
Support Pack stack for Target release.
The Latest available SPAM update that the tool has detected from the download
directory is pointed out by the tool. This SPAM update can be included now for the
target release of 702.

Click Continue after selecting the SPAM/SAINT update offered by the SOLMANUP
tool.
Dont include any change request in this step and click continue to proceed.
Select None for SPDD transport request and SPAU transport request as there are no
modification adjustment requests to be included and click Continue.
The SOLMANUP wants to use port 3604 for the shadow instance. But, it seems the
port 3604 is already occupied. This is indicated in the results for the Configuration
roadmap as error.
The system is pointing out issue that the port 3604 is currently already in use.
Remove this entry from the Windows services file to resolve this.
Configuration Roadmap is not completed because of the previous failed request.

Once the entry 3604 is removed from the services file, the configuration roadmap
completes successfully and gives the following information for manual actions.
The Configuration roadmap completes successfully for the ABAP stack and prompts
for starting the Configuration roadmap for Java stack.
For the Java part of the Configuration roadmap, enter the OS user credentials for the
<sid>adm user and Click Continue to proceed.
Enter the OS user credentials for the <Sid>adm user and click continue to proceed.
Enter the password for AS Java Administrator (J2EE_ADMIN) and Password for SDM
User and click Continue to proceed.
Specify the password for SAP* user and click Continue.
SOLMANUP tool gives the summary for the system parameters detected during the
Upgrade. After verifying the system parameters mentioned by the Upgrade tool,
Click Continue to proceed in this screen.
The Configuration Roadmap is completed. Click Next to proceed to the Checks
Roadmap.
7.4 Checks
In this roadmap, in the only user interaction involved, the system prompts whether
we want to run the report JOB_RASUVAR1 automatically. This is for saving variants
from the system which shall be restored during a later part of the Upgrade. Select
yes and Click Ok to proceed in this phase. Refer Note 712297 for more details.
At the end of Checks phase, system checks for free space in the Database and
prompts for creating the required Table space PSAP<SID>702 and extend the Table
space PSAPTEMP.Accomplish the same using BRTOOLS and rerun the Checks
Roadmap from the point where it stopped to complete the Checks Roadmap.

BRTOOLS Table Space Creation and Extension

Table space Creation

Start the brspace function for creating PSASASM702 as suggested by tool.

BRSPACE function displayed with the options for entering the inputs
Enter c to continue.

Enter C in this step to continue

Enter C to continue in this screen.

Enter C to continue
Enter C to continue.

Since there is no next data file to specify, enter n in this screen.

BRSPACE Tablespace creation is completed successfully.

BRSPACE Tablespace creation completes successfully.

Table space Extension

Call BRSPACE to extend the Tablespace PSAPTEMP as expected by the SOLMANUP

tool.
BRSPACE displays the different menu options for extending the tablespace.

Enter C to continue from this step.

BRSPACE executes successfully the extension of the Tablespace PSAPTEMP.
Checks Phase is completed.

Click Next in this screen to proceed to Roadmap Pre-Processing.

7.5 Pre-Processing
Enter the keyword for BI_CONT from the Note 1558363 and click Ok to proceed.
Enter the keyword for DMIS from the Note 1468391 and click Ok to proceed.
The SOLMANUP tool checks for Open repairs and prompts if there are any
transport requests which have not been released and hence the objects are still
locked under them.
Release the mentioned transport requests and select Check again for Open
transports.
The SOLMANUP tool prompts for the development environment to be locked now.
The tool also gives the opportunity to lock the development environment at a later
point of time. Hence, select Lock Later and Click Continue.
The SOLMANUP tool again prompts for the development environment to be locked.
Select Lock now and click Continue to proceed.
In this step, SPDD Repository modifications can be included. Since, no repository
modifications are applicable select Adjustments made, Continue with Procedure.
In this step, the SOLMANUP tool is throwing an error in ACT_UPG phase.
Select Accept non-severe errors and repeat phase MAIN_SHDRUN/ACT_UPG to
resolve this issue.
The Pre-Processing roadmap is completed. Select Actions Completed and click
Continue to proceed.
Take complete offline DB Backup of Database, File system backup of /usr/sap/<sid>
and Upgrade directory.
Select Backup Completed to proceed in this screen.

Pre-processing roadmap is completed and Click Next in this screen to proceed.

7.6 Downtime
Repeat the phase at this stage from the point where it has stopped to resolve the
issue.
Downtime Roadmap is running.
Downtime roadmap is completed and the tool is prompting to take Backup at the DB
level.

Make full DB Backup of Database and file system backup of /usr/sap/<SID>. Select
Actions Completed and click Continue to proceed.
The downtime roadmap is completed.Click Continue to proceed.
7.7 Post-Processing
Select Adjustments completed and click Continue to proceed.
Clicks continue in this screen to send the Upgrade evaluation form later.
The upgrade tool shows that the Upgrade is completed. Clicks continue to proceed
from this screen.
Click Exit to exit from the Upgrade tool.
7.8 Finalization
The system shows that the Upgrade is completed. Click Ok to exit from the tool.

8 Post Upgrade activities

The following activities need to be carried out before making use of upgraded
system for productive use.

8.1 Performing Oracle Specific actions

Execute the SQL Script sapdba_role.sql again after the Upgrade.To perform this,

Log on as user <sid>adm at the windows OS level.

Start the SQL script with

o cd %ORACLE_HOME%/database

o copy <DRIVE>:\usr\sap\<SAPSID>\SYS\exe\run\sapdba_role.sql
 o sapdba_role.sqlsqlplus /nolog @sapdba_role <SAPSCHEMA-ID>

8.2 Activating the SICF Services

The upgrade program disables services of the ICF during the upgrade for security
reasons.

In this case, when logging into SICF, we find that service webgui is disabled.
From SICF, right click on the disabled webgui service and activate the same.
8.3 Rescheduling the Background Jobs
Log on to client 000 as user DDIC.

The Background Jobs had been stopped during the Upgrade. The Background Jobs
need to be rescheduled.
On executing the report, we get the success message that the jobs which had been
descheduled due to Upgrade have been rescheduled.
8.4 SGEN Generation of Loads
Schedule SGEN Generation of Loads during the off-peak hours

Goto T.code SGEN and select the option Regenerate after an SAP System
Upgrade. SGEN shall be running for a long period of time. Disable the Archive logs
before running the SGEN as SGEN process shall be writing lot of archive logs.
Once SGEN Process completes, Archive logs can be enabled again.

9 Issues Faced

Problem 1 Component specific Issue during Configuration

Roadmap
Error when creating co-file for Transport request SAPK-100AGINCTSPLUG
Solution This issue is resolved by repeating the phase.

Problem 2 Port already in use issue in Configuration Roadmap

SOLMANUP Tool indicates that Port is already in use and hence cannot be used by
SOLMANUP tool for shadow instance as output for Configuration Roadmap.
SOLMANUP tool indicates Port 3604 is already in use and hence requires the
same to be freed up so that the port 3604 can be used for running the shadow
instance.

Solution The issue is resolved by removing the entry for port 3604 from
services file and rerunning the checks phase.
Problem 3 Presence of error summaries in ACTUPG phase in
Pre-Processing Roadmap.
SOLMANUP tool indicates that it has Detected 72 error summaries in ACTUPG.ELG in
Pre-Processing Roadmap.

Solution - Select Accept non-severe errors and repeat phase

MAIN_SHDRUN/ACT_UPG to resolve this issue.
Problem 4 Unresolved requests in buffer ASM issue in
Downtime Roadmap
SOLMANUP tool indicates it has detected unresolved requests in buffer of ASM.

Solution This issue is resolved by repeating the phase from the point where it
stopped.

10 References:
From SAP service Market place, http://service.sap.com, Upgrade Master guide
for Solution Manager upgrade from 7.01 to 7.1
 From SAP Service Market place, http://service.sap.com, Upgrade guide for
Solution Manager Upgrade from 7.01 to 7.1