Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

  Moderators:   

László Herbert

WIKI Space Editor: László Herbert

SCN Topic Spaces: Software Logistics   |    Business Continuity   |   SAP Solution Manager   |   Visualization and Cloud Infrastructure

 

 

Search tips

Use the following search terms: phase name (e.g. START_SHDI_FIRST ) ; error text (e.g. Shadow instance couldn't be started ) ; name of a logfile (e.g. ACTUPG.ELG)

Always verify the most up-to-date procedures by checking the  SUM guide . Always have it on hand while performing the upgrade.

  

Troubleshooting by upgrade roadmaps and phases

 

   Click on the roadmap step

 

  Troubleshooting issues with the SUM UI 

 

  Troubleshooting by upgrade topics

TopicDescription

FAQ

Frequently asked questions related to updates executed by SUM tool

General information

Information about product, NetWeaver and kernel release; Upgrade documents;system dependency; dual stack split.

SUM SL CommonUI

Troubleshooting of SUM start/stop and SL CommonUI related situation

Application related update troubleshooting pages

List of pages containig application specific upgrade troubleshooting ( e.g. BW, Solman)

ADD-ON Handling

Handing addon in MOPZ, Vender Key, IS_SELECT phase

SPDD and SPAU

How to adjust objects? How to handle SPDD/SPAU request?

ACT_UPG phase (DDIC activation)

Handling situations during data dictionary activation in the phase ACT_UPG

PARCONV_UPG

Runtime optimization

Shadow Import phases

Parallel processes, Runtime optimization (uptime)

TABIM phases

Parallel processes, Runtime optimization (downtime)

XPRAS_TRANS XPRAS_UPG and XPRAS_AIMMRG phases

Analysis of eXecution of PRogram After Import phases

SGEN

SAP (ABAP) load generation

Resetting an update

How to reset upgrade/update correctly?

Data loss

Analyzing data loss issue

Starting and stopping instancies

Handling instance start-stop situations during upgrade.

DMO

DMO ( Database migration option )

Glossary

Glossary of SAP system updates executed by SUM

Feedback

Your feedback is very valuable to us. Please take a few moments to complete a simple survey

Disclaimer: Content Accuracy is assured as much as possible. Viewer discretion is advised.

 

 

 

Page: (Un)lock the Standard Instance Page: Accessing operating system (OS) level details from application level at the time of upgrade Page: ADD-ON Handling Page: Application related update troubleshooting pages Page: Database Migration Option for Software Update Manger (DMO) Page: Data Loss after the upgrade Page: FAQ: Frequently asked questions - Background (batch) job processing by SUM Page: FAQ MOPZ Maintenance optimizer Page: FAQ update execution Page: FAQ update planning and preparation Page: FAQ update postprocessing and follow-up activities Page: FAQ updates executed by SUM tool Page: General information Page: Glossary Page: Hanging situation in the last roadmap step in SUM Page: How can I check on which release and SP level a transport request was released Page: ICNV - Incremental Table Conversion Page: Modification Adjustment During Upgrade Page: Notes and KBAs about performance in Upgrades and Enhancement Packages Page: Old exchange tablespace is not empty after update Page: Planning for SAP Upgrade of SAP Netweaver and SAP Business Suite Systems Page: Resetting an update Page: SGEN Page: slcss Page: Software Update Manager (SUM) Page: SPDD in upgrade if Single system mode was selected Page: SUM phases Page: Syntax errors in CHECKS Roadmap Step Page: Table-Content Checks in SUM Page: Troubleshooting in Roadmap step 1 Extraction - Select phase Page: Troubleshooting in Roadmap step 2 Configuration - Select phase Page: Troubleshooting in Roadmap step 3 Checks - Select phase Page: Troubleshooting in Roadmap step 4 Preprocessing - Select phase Page: Troubleshooting in Roadmap step 5.1 Initialization - Select phase Page: Troubleshooting in Roadmap step 5.2 Extraction - Select phase Page: Troubleshooting in Roadmap step 5.3 Configuration - Select phase Page: Troubleshooting in Roadmap step 5.4 Checks - Select phase Page: Troubleshooting in Roadmap step 5.5 Preprocessing - Select phase Page: Troubleshooting in Roadmap step 5.6 Execution - Select phase Page: Troubleshooting in Roadmap step 5.7 Postprocessing - Select phase Page: Troubleshooting in Roadmap step 5.8 Finalization - Select phase or symptom Page: Troubleshooting in Roadmap step 5 Execution - Select phase Page: Troubleshooting in Roadmap step 6 Postprocessing - Select phase Page: Troubleshooting instance start-stop situations during update Page: Troubleshooting Issues with the SUM SL Common UI

10 Comments

  1. cool wiki + great help,  but hard to find this page

    why is this wiki not mentioned in the SUM guide ?

    1. Hello Christoph,

      thank you for your feedback.

      It is good to know, that our work is valuable for customers, especially for you.

      The pages can be found in google and we use references in KBAs also.

      The WIKI is referenced also in the Best practice guide which will be sent to customers who downloaded the SUM too, see offline version herel:

      http://scn.sap.com/community/it-management/alm/software-logistics/blog/2015/05/18/best-practices-for-upgrading-sap-systems

      I am not responsible for the  SUM guide, but I have forwarded your query to the authors.

      Best regards,

      Laszlo

       

       

       

       

      1. maybe you can also submit the links to this wiki+blog to the SAP-SupportTeam of component BC-UPG-TLS-TLA  , because every time i opened a support-ticket to that team, while waiting (not only hours, but several days) for a really helpful solution to SUM-issues, now i have solved that issue, but did not get any response from that support-team yet, the support of that team is very very poor. (sorry to say that) - thanks.

  2. Hi Christoph,

    I have forwarded your feedback to the responsible team.

    You can also provide feedback directly after confirming the incident by filling out the survey.

    I have found a new incident from you and I have taken it. You will get an answer soon. 

    Best regards,

    Laszlo

     

  3. Former Member

    SAP Note 1927413   : data file corrupt in phase MAIN_NEWBAS/TABIM_UPG shows document not released, Could any please update on this.

  4. Hello Madhu, 

    Thank you for your comment, the document was being re-worked, it should now be available.

  5. With SUM 19 SP6 we encounter a problem in Phase PREP_INPUT/DBQUERY_PRE:The password is wrong, SUM states. We have checked the password via sqlplus / brconnect it works. In the first phase of sum where the user has to input ddic password etc. it works fine, afterwards not.

     

    SAPup> Starting subprocess in phase 'PROFREAD' at 20170511140951

      *CENV: BR_ISP=1

        ENV: DBMS_TYPE=ora

        ENV: NLS_LANG=AMERICAN_AMERICA.UTF8

        ENV: ORACLE_HOME=E:\oracle\BD0\12102

        ENV: ORACLE_SID=BD0

        ENV: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC

        ENV: PATH=E:\usr\sap\BD0\DVEBMGS00\exe;E:\oracle\BD0\12102\bin;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\OmniBack\bin\;E:\usr\sap\BD0\SYS\exe\uc\NTAMD64;E:\sapdb\clients\MAXDB\bin;E:\sapdb\clients\MAXDB\pgm;E:\sapdb\programs\bin

        ENV: RSEC_SSFS_DATAPATH=\\server\sapmnt\BD0\SYS\global\security\rsecssfs\data

        ENV: RSEC_SSFS_KEYPATH=\\server\sapmnt\BD0\SYS\global\security\rsecssfs\key

      *CENV: SAPCHECK=T:\Upgrade\SUM\abap\tmp

      *CENV: SAPDATA_HOME=T:\Upgrade\SUM\abap\tmp

        ENV: SAPSYSTEMNAME=BD0

        ENV: dbs_ora_schema=SAPSR3

        ENV: dbs_ora_tnsname=BD0

        ENV: rsdb_ssfs_connect=1

     *DBENV: (auth_shadow_upgrade)

        PWD: T:\Upgrade\SUM\abap\tmp

     

    EXECUTING E:\usr\sap\BD0\DVEBMGS00\exe\brconnect.EXE -u -c -f dbstate -RDB

    BR0801I BRCONNECT 7.40 (29)

    BR0280I BRCONNECT time stamp: 2017-05-11 14:09:51

    BR0262I Enter database user name[/password]:

     

    BR0280I BRCONNECT time stamp: 2017-05-11 14:09:51

    BR0342I Database instance BD0 is started and open

     

    BR0280I BRCONNECT time stamp: 2017-05-11 14:09:51

    BR0802I BRCONNECT completed successfully

     

    #!--------------------------------------------------------------

    #!---- MASKING file "T:\Upgrade\SUM\abap\log\CHKSYSPWD.LOG"

    #!---- TIME: 20170511143015  PHASE: PREP_INPUT/DBQUERY_PRE

    #!--------------------------------------------------------------

     

    SAPup> Starting subprocess in phase 'DBQUERY_PRE' at 20170511142531

      *CENV: BR_ISP=1

        ENV: DBMS_TYPE=ora

        ENV: NLS_LANG=AMERICAN_AMERICA.UTF8

     *DBENV: ORACLE_HOME=T:\Upgrade\SUM\abap\tmp

     *DBENV: ORACLE_SID=BD0

        ENV: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC

        ENV: PATH=T:\Upgrade\SUM\abap\exe;E:\oracle\BD0\12102\bin;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\OmniBack\bin\;E:\usr\sap\BD0\DVEBMGS00\exe;E:\usr\sap\BD0\SYS\exe\uc\NTAMD64;E:\sapdb\clients\MAXDB\bin;E:\sapdb\clients\MAXDB\pgm;E:\sapdb\programs\bin

        ENV: RSEC_SSFS_DATAPATH=\\server\sapmnt\BD0\SYS\global\security\rsecssfs\data

        ENV: RSEC_SSFS_KEYPATH=\\server\sapmnt\BD0\SYS\global\security\rsecssfs\key

      *CENV: SAPCHECK=T:\Upgrade\SUM\abap\tmp

      *CENV: SAPDATA_HOME=T:\Upgrade\SUM\abap\tmp

        ENV: SAPSYSTEMNAME=BD0

     *DBENV: dbs_ora_schema=SAPSR3

        ENV: dbs_ora_tnsname=BD0

        ENV: rsdb_ssfs_connect=1

     *DBENV: (auth_shadow_upgrade)

        PWD: T:\Upgrade\SUM\abap\tmp

     

    EXECUTING T:\Upgrade\SUM\abap\exe\brconnect.EXE -u -c -f dbstate -RDB

    BR0801I BRCONNECT 7.40 (17)

    BR0280I BRCONNECT time stamp: 2017-05-11 14:25:31

    BR0262I Enter database user name[/password]:

    BR0280I BRCONNECT time stamp: 2017-05-11 14:25:31

    BR0301E SQL error -1 at location db_connect-3, SQL statement:

    'CONNECT SYSTEM/*******@BD0'

    Error while trying to retrieve text for error ORA-00001

    BR0310E Connect to database instance BD0 failed

     

    BR0280I BRCONNECT time stamp: 2017-05-11 14:25:31

    BR0804I BRCONNECT terminated with errors

    SAPup> Process with PID 5760 terminated with status 3 at 20170511142531!

     

    In the first run the Oracle_Home is set correctly, in the second not. Can someone help me solve the issue?

    Kind Regards,

    Michae

    1. Hi Michael,

      I would recommend to post this query on the SAP Cummunity

      https://answers.sap.com/questions/ask.html

      and enter Primary tag Oracle Database.

      It is the best place for communicate with others and get answers.

      Best regards,

      Laszlo

  6. Very well structured. Great source of information. 

    Thank you

  7. Hi Alexander,

    it's really good to know that our work delight customers.

     

    Best regards,

    Laszlo