This document deals with the planning of SPS Upgrade for BW System

Please provide your feedback

Pre-requisites

   Create filesystem /usr/sap/<SID>/SUM with 30 GB space with sidadm:sapsys as owner and permission as 777 .

   Add 70 GB in /oracle

   Update sudo master list on <host> , reuxeuuz1150 and add below Command /usr/bin/chmod -R 777 /usr/sap/<SID>/SUM and /software/IBMUPG/*/*/*/saphostexec -install

   Create user sapadm with primanry group as sapsys and homes directory as /export/home/sapadm on <host>

   Install SAP hostagent on <host>

   Change permission of sapuxuserchk at all location on server <host>

   Open ilink port for 4239 , 4240 , 4241 on host <host>

   Install latest 720 Kernal

   Upgrade ST-A/PI component to 1Q*

   Install java6 on <host>

Manual SPS Preparation

   Generate XML in Solman

   Download Software

   Upload Software

   Take offline backup of <SID> system

   Update database stats

   Check ‘NLS_NCHAR_CHARACTERSET’

   Check shared_pool_size and ‘shared_pool_reserved_size’

   Check dba_sys_privs for scheman ID

   Check/Change the operation modes

   Use transaction SM51 to check hostname

   Check Number of Update/Dialog/Background Work Process and increase if requried

   configure the OS user authentication

   Check/Change STMS configuration

   Check the tp and R3trans version

   Refresh and Check Missing tables and indexes (db02)

Check the DB13 calendar entries. Delete all entries in period of upgrade.

SUM Tool Uptime activities

   Log on to the host on which the primary application server instance is running as user waiadm

   Unpack the Software Update Manager package with the following command:SAPCAR –xvf < download directory > / < path > / < Archive > .SAR -R /usr/sap/ < sapsid >

   To start the Software Update Manager, enter the command / < update directory > /STARTUP ” guistart=on “

   Select target roadmap step

      Enter a user name and a password for the administrator role

      Enter the password for the waiadm user and choose Next

   Confirm target roadmap step

      Enter the keyword and confirm target roadmap step

      In the Stack File or Directory field, specify the path to the stack configuration XML file.

   Extraction roadmap step

      Enter the password for user DDIC

      Enter the path for SAP Cryptographic Library

      SAP Note Implementation which appears in the list

   Configuration roadmap step

      Choose preconfiguration mode as Standard (archiving off during downtime)

      Enter password for Oracle User SYSTEM

      Enter Batch Configuration and Upgrade Processes parameter

      Check the software packages that are defined in the stack configuration file

Add SPDD Transport Request if any

      SPAM version check

      Enter shadow instance Numbers

      Checks roadmap step

      Check the results of System Check

      Evaluating results of Preparation steps

      Check the value of the parameter rdisp/bufrefmode in DEFAULT.PFL

   Preprocessing roadmap step

      Release the repairs and requests containing objects locked by SAP

      Confirm the locking of ABAP workbench on all SAP Instances

      Modification adjustment and activation

      Remaining pre-processing task

Business Rampdown

Reschedule the batch jobs bt btctrns1

Check the batch job from SM37. If any active wait for sometime and after that cancel it after discussing with client

check sm35 in progress entries

Take the backup of sum directory

check unreleased transport

Lock all user except Upgrade team

clean invalid temp tables

check any update sm13

check backup DB13

Check and adjust operation modes (RZ04)

Update pre upgrade ASU activities

Disable DB archivelog mode

   BW Pre-activities

       Clean BW Queues

       Process all the entries in the Inbound and Outbound queue( SMQ1, SMQ2 ) at ECC side

       Clean up RSA7 Delta queue at ECC side.

      Stop the BW Process chains

      Check all inconsistant Info Objects

      Delete temporary BI database objects

      Check for invalid temp tables and delete if any

      Check PSA Consistency if required

      Repair Master Data

      Check if all Transfer and Update Rules are active.

      Make sure that all requests in the Data targets are active and available for reporting

      Background jobs scheduling

      Check for active ODS

      Ensure all ODS data load requests have been activated

      Transaction RSRV : Analysis of BI objects

      Check that M Tables are Empty (ODS Tables)

      Check for active Info Cubes

      Execute Program if any Infocubes,ODS,Transfer structure inactive

      Execute few BW reports and take screen shot for data validation

       Check the unreleased transport request.

       Check the update from SM13(Global view). Delete it after discussing with client

      No change of operation mode is defined on the primary application server instance during the update

   Check the DB13 calendar entries. Delete all entries in period of upgrade.

   Perform Pre-Upgrade data validation

   Take backup of upgrade directory and DB backup

   Stop saposcol and saprouter if running

   Stop OS level Jobs

   Stop Application servers

SUM Tool Downtime activities

   Click on Action Completed in Last screen of Preprocessing phase

   Click on Next to Start Downtime phase

   Continue with downtime Phase

   Continue with postprocessing phase

   Continue with Finalization phase

Basis Post Activities

   Run Stats Update

   Check the Unused Indexes and Tables after DB02 refresh

   Check Tables TAORA,IAORA and TSORA for correct tabart and tablespace mapping

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

  1. Rajarshi Chatterjee

    feed back is…certainly a very good document. You can do an instant revision of the entire upgrade process by taking a glance at it.

    Just some thoughts,

    1. Update queues in SM13 should be cleared before starting the update only else it will throw error in the checks phase.

    2. you won’t need to stop the application servers. once the ‘preprocessing’ stage ends as soon as you press next the SUm will bring down the instances one after another.

    I’ve some questions. Just for knowledge. Can you please explain the significance of the below points?

    1. Check shared_pool_size and ‘shared_pool_reserved_size’

    2. Check the value of the parameter rdisp/bufrefmode in DEFAULT.PFL

    3. Update database stats.

    Thanking You.

    (0) 

Leave a Reply