Expand +



Tip: 19 guidelines for avoiding common pitfalls during your next SAP NetWeaver BW upgrade project

by The Tip Doctor

April 26, 2010

The Tip Doctor, Insider Learning Network

This tip is just 1 of the tips from the session "17 tips and tricks to dramatically reduce your SAP NetWeaver Business Warehouse upgrade timeline," from SAP NetWeaver/BI and Portals 2010.

A good project plan should be updated throughout the upgrade process and include all issues that you have hit, how you resolved them, and which group was involved in fixing the issue. These best practices will help you avoid some of the most common pitfalls along the way:

1. Don’t forget to open the clients up for change (Client 000)

2. During table conversion, you may run out of space. Make sure your temporary tablespace is at least 20GB.

3. You can create a new temporary tablespace and then remove it after the upgrade if your space is constrained.

4. Follow all database upgrade instructions from the upgrade guides

          a. Run statistics after the upgrade

          b. Table conversion can be done while logged into the shadow system using transaction SE14

            ;         i. With DB2, you can compress tables in V9 if space is an issue

          c. Update all parameters for the database to help performance; use the correct SAP Notes for your version

5. Update SAP ABAP parameters for new version

6. Update SAP applications server profiles with new values

7. Make sure the permissions are set correctly on all your upgrade directories and /usr/sap and /sapmnt

8. In your current executable directory, make sure you have write authority on all programs

9. All activities such as SAP BW object changes, and SAP BW query changes, should stop before starting the PREPARE

10. Install new client software for database on application servers if necessary

11. Make sure there are no loads running during the upgrade

12. Before installing plug-ins, make sure you have loaded all data from source system

          a. Check SMQ1 and SMQ2

13. After upgrade, activate all source system connections again to make sure there is nothing inactive from the upgrade

14. Make sure you have the latest R3trans, TP, and SPAM/SAINT version for your current SAP version

15. Tune your database to the best of your ability before you start the upgrade. A well-tuned database will help speed up the upgrade.

16. Make sure you have enough log space if you are doing the upgrade with logging turned on

          a. Automate the cleanup job to keep the file system from filling up

          b. Log space will use approx 18G up to step DOWNCONF_TRANS

          c. Log space will use approx 22G til the end of the upgrade

17. Clean up old profiles in the profiles directory. These may cause problems. Delete all but the current profile or move them to another directory.

18. Verify that the SAP BW system and source system ports are active in WE20

19. Your loads are now controlled by the qRFC monitor. Transaction SMQS. Make sure you set the “Max. Conn” to the recommend value for your business warehouse and source systems.

For more information on the SAP NetWeaver/BI and Portals conference, visit

An email has been sent to:

More from SAPinsider


Please log in to post a comment.

No comments have been submitted on this article. Be the first to comment!