Solution Manager 7.2 SP 08 Upgrade and Migration Using SUM DMO Approach – III-B – Upgrade+Migration – ABAP Stack

Solution Manager 7.2 SP 08 Upgrade and Migration Using SUM DMO Approach – III-B – Upgrade+Migration – ABAP Stack

 

This blog is the continuation of the previous blog , please find the below link for the same

Solution Manager 7.2 SP 08 Upgrade and Migration Using SUM DMO Approach – III -A– Upgrade+Migration – ABAP Stack

In the previous blog , configuration phase successfully completed and now this blog continues with Checks Phase  of SUM tool.

Click on unprocessed Items

Check the file ORATBSXT.LST

Create table space PSAPSR3740X of 70 GB using commands listed in the file ORATBSXT.LST

Above requirement changes as per your Database size and version of your landscape.

After adding space to table space PSAPSR3740X  click next and proceed further.

here the Check Phase comes to end and next we enter the Preprocessing Phase

Check the log file RSVBCHCK.ELG

As pe rthe note 1705774

Go to tcode SM13 and delete the update records as shown below

Now Repeat phase MAIN_INIT/JOB_RSVBCHCK2

It locks the environment , no transports can be imported to system

Next

Release above transports and proceed further.

MAIN_SHDRUN/DDIC_UPG: DDIC import of all SAP packages and of SPDD results

Logon to the shadow instance as user DDIC in client 000 on server illinsapsm2 instance 05

• Create user – XXX (copy of DDIC)
• Now login with new user and run SPDD transaction on shadow instance.
• you can access shadow system: sapgui <hostname> <Instance No>

Capture the SPDD changes in a transport and proceed further

After SPDD changes, click Next

Manually activated view AICTPLNSTAMAXCOL by login on to SAP system through SE11

MAIN_SHDIMP:SHADOW_IMPORT_UPG: this phase imports upgrade and language data in to new tables

MAIN_SHDIMP:SHADOW_IMPORT_INC: This phase imports included Add-on’s and support packages into shadow tables and the new tables.

• Check Successful Backup
• Disable Backup Script from the crontab
• Sum tool automatically Suspend the Jobs

Now the actual downtime begins, click Next and we enter Execution Phase

To resolve above error, please refer note 1705774 – Error in phases MAIN_SWITCH/JOB_RSVBCHCK2 or MAIN_SWITCH/JOB_RSVBCHCK_D; Checks after phase MAIN_INIT/JOB_RSVBCHCK* were negative.

F8(execute), Select all and click delete ,Now select Repeat phase and click next.

Here the downtime comes to an end i.e execution phase completed and next we enter into

Post processing Phase

Cross check the Note 1908075, and component BI_CONT is not the valid component for this note. Click Next

Check the log file PHASES.ELG

As per the note 2381785

2381785 – Creation of column view for “0BCTCOMP” failed in phase RUN_CUBE_CALC_VIEW_CREATE

Resolution

The InfoObject 0BCTCOMP is obsolete and is no longer delivered by SAP (no D version as of BW Release 7.30). If you do not use 0BCTCOMP, it can be deleted. After this, you can repeat the phase in SUM.

Go to tcode- RSD1 and delete InfoObject 0BCTCOMP as shown below.

Now again repeat the phase, it gave error as below

A3EERSDD_HDB_INDEX 000 “EC:2048’column store error: fail to create” “scenario: [34011] Inconsistent calculation” “model;scenario -> MetadataProvider” ” ”

A3EERSDD_HDB_INDEX 003 Creation of column view for “0CCMPVRT” failed

A3EERSDD_HDB_INDEX 003 Creation of column view for “0CCMPCURR” failed

A3EERSDD_HDB_INDEX 003 Creation of column view for “0CCMPDATA” failed

A3EERSDD_HDB_INDEX 003 Creation of column view for “0UIMPDATA” failed

A3EERSDD_HDB_INDEX 003 Creation of column view for “0UIM_MON” failed

To resolve above error, follow below note

2453312 – Creation of column view for 0CCMVRKF failed (Error 2.048 has occurred in the BWA/SAP HANA)

Resolution: Install the InfoCube 0CCMVRKF and execute report RSDDB_LOGINDEX_CREATE

Now select Multi Providers (0CCMPVRT,0CCMPCURR,0UIMPDATA,0CCMPDATA,0UIM_MON) and install one by one

Once installation completed for these multiproviders 0CCMPVRT, 0CCMPCURR, 0UIMPDATA, 0CCMPDATA, 0UIM_MON

->Execute report RSDDB_LOGINDEX_CREATE for above multiproviders one by one, it creates column view of type ICF for objects 0CCMPVRT, 0CCMPCURR, 0UIMPDATA, 0CCMPDATA, 0UIM_MON and also activates it.

For example I have shown for object 0CCMPVRT

Now Repeat Phase, Next

I performed SPAU changes after completion of upgrade and make sure SPAU changes are  completed within 14 days.

Click Next

To resolve above error , follow note

2428343 – RUN_RSDB02CK_END_DMO – Secondary index “/BIC/E****” / “/BIC/F****” does not exist in the database

Cause

This issue occurs due to superfluous BW Aggregates found in the system.

These BW aggregates, being superfluous on HANA systems can be removed from the system. It occurs in systems which are not BW systems but source for a BW system or the systems where the BW configuration is incorrect.

DMO checks if the system is BW in the phase PREP_CONFIGURATION/DETBWMODE. if the configuration is faulty or if DMO is not able to detect whether or not its a BW system, it asks for user input.

If the system is BW, DMO runs a phase RUN_AGGREGATE_DROP which drops these BW Aggregates and the error doesn’t occur. For Non-BW systems, this phase does not run and so the Aggregates are found in the system resulting in error.

Resolution

Please always use the latest SUM version to avoid running into known issues. Since these BW Aggregates are superfluous on HANA systems, They can be removed in order to proceed.

To remove them, proceed with the following steps

• Start report RS_BW_POST_MIGRATION in the system
• Select task 10 (Task 10: Drop aggregates) in the options
• Execute
• Once the report finishes successfully, repeat the phase in SUM

If the issue will occur after the mentioned steps, follow the instructions from KBA 2268610 – Aggregate tables or indexes are missing in the data dictionary

• Uncheck all boxes and select only task 10 (Task 10: Drop aggregates) in the options

Non again repeat phase, click Next

Again gave same error,execute report SAP_INFOCUBE_INDEXES_REPAIR(this report repairs secondary indexes) , after this again execute SUM, again it gave error.

Now ignore the phase and click next

Click Next

After the successful completion of an upgrade via Software Update Manager (SUM) tool, you can also view the UPGANA.XML file for the upgrade analysis.

NOTE: UPGANA.XML has replaced ProcessOverview.html

• The UPGANA.XML file can exist in either:
  • ../SUM/abap/htdoc/UPGANA.XML for SUM 1.0
  • ../SUM/abap/doc/analysis/UPGANA.XML for SUM 2.0

->You can also view the UPGANA.XML file in the notepad for the upgrade analysis  in the following way

1. In the SUM directory under /abap/htdoc or /abap/doc/analysis you will find the log file UPGANA.XML
2. You can copy this file and the UpgAnalysis.xsl file to a local directory and view this XML file through a browser window.

Note: When you run the SUM with near Zero Downtime Maintenance (nZDM) on a test system, you can use the figures provided by this XML to forecast your next run in production environment.

To view the UPGANA.XML file in the readable format,you can use XML Notepad software.

Refer to the SUM guide appendix SUM Analysis for further information. You can find the SUM guide here

In the next blog , I have explained post steps for ABAP system, please follow the below link for the same

Solution Manager 7.2 SP 08 Upgrade and Migration Using SUM DMO Approach – IV – Post Steps – ABAP Stack