Bw On Hana Documentation And Troubleshooting.docx

BW on HANA Documentation & Troubleshooting  

https://wiki.scn.sap.com/wiki/display/SAPHANA/BW+on+HANA+Documentation+and+Troubleshooting Created by Des Gallagher, last modified on Jan 19, 2016 Go to start of metadata

Purpose The Purpose of this page is to collect all BW on HANA relevant information and also provide technical detail on common issues and how to troubleshoot known problems.

BW on HANA Sizing If you want to do the sizing for an existing BW system on any DataBase that you want to migrate to HANA use the latest version of the report /SDF/HANA_BW_SIZING from the SAP note1736976 Sizing Report for BW on HANA. If you start a Greenfield implementation you should use the SAP QuickSizer in this case. Please go to http://service.sap.com/quicksizer for further details. Using SAP QuickSizer, you will get information on both the SAP HANA In-Memory Database and the SAP NetWeaver BW application server. For an existing Enterprise data warehouse solution where there is no existing ABAP application server for BW you can use the sizing scripts from the note 1637145 SAP BW on HANA: Sizing SAP In-Memory Database.

BW on HANA Installation and upgrade guides: You can find the relevant guides here: http://help.sap.de/nw74#section7

BW on HANA Migration: Before doing the upgrade and migration apart from referring to the upgrade and migration guides please also read carefully the information in the SAP First Guidance document at the link below, together with the standard documentation this should provide all the necessary information you need to successfully migrate BW on any SAP supported database to BW on HANA: http://scn.sap.com/docs/DOC-7856 In general DMO is the recommended tool for the BW on HANA Migration, please see the documentation on the tool at the link below which includes information on how to optimize the BW on HANA Migration performance: http://scn.sap.com/community/bw-hana/blog/2015/03/17/dmo-optimizing-system-downtime If you do not use DMO as upgrade of the BW system is not required before migration please refer to the information at the SCN links below for the General steps to follow for the BW on HANA Migration using the Software provisioning manager tool: http://scn.sap.com/community/bw-hana/blog/2014/10/22/bw-on-hana-scaleout-migration-part-1-preparation-checklist-andknown-issues http://scn.sap.com/community/bw-hana/blog/2014/10/22/bw-on-hana-scaleout-migration-part-2-migration-process-andissues-encountered http://scn.sap.com/community/bw-hana/blog/2014/10/22/bw-on-hana-scaleout-migration-part-3-post-migration-activities-andissues-encountered

Common Questions: I want to migrate to BW on HANA where can I find further information on technical requirements? A good starting point is the information in the following note: 1600929 - SAP BW powered by SAP HANA DB: Information

Troubleshooting, issues and reported problems POST Migration: Issue: Unwanted Secondary Indexes still exist in transaction DB02 after BW on HANA Migration, they can be found in DB02 under 'Unknown objects in ABAP Dictionary' and sub heading 'DB Indexes' :

Solution: Follow the KBA 2077953 - How to remove unwanted secondary Indexes after a BW on HANA Database migration to remove these secondary Indexes. Issue: Delta merge for large BW table fails, you see the HANA Alert 29 in HANA Studio. Solution: Use the symptom part of the KBA 2211729 - Not enough memory to execute delta merge, HANA Alert 29 Size of delta storage of column-store tables to confirm that you have followed the standard troubleshooting steps to free up enough memory for the delta merge. If this does not work please follow the Resolution section of the KBA to work around the problem. Issue: After the BW on HANA Migration I do not see the expected performance improvement in my BW queries. What can I do? Solution: There is often the expectation that after a BW on HANA migration from another database that all BW queries should be much faster. Of course if the query was slow already before database migration to HANA due to some calculations happening on the BW application server and these calculations cannot be pushed down to HANA DB then HANA cannot help for these use cases without a redesign of the BW Query. The Query run time component that we can expect to see significantly improved with HANA is the database time, this is the Event ID 9000 (Data Manager Time) in the BW Query run time statistics. To trouble shoot the problem and determine if the problem is HANA Database related or not please follow the information in the Knowledge based article How to determine if a BW on HANA query performance problem is HANA database related. In the Knowledge based article Push down of BW OLAP functionalities to SAP HANA you find the current list of OLAP related data intensive operations that are pushed down from BW application server to the HANA Database. Issue: I am executing the BW on HANA Post migration report RS_BW_POST_MIGRATION and it fails with error. What can I do to troubleshoot the problem? Solution: 1: Check that you execute the report in the background with the variant SAP&POSTMGRHDB. 2: If you still get errors check the application log (transaction SLG1) for the time the report failed to find the relevant error messages and the step that the report failed on. In the majority of cases the report fails on the step Create calc views cubes/infoobjects and the relevant calculation view cannot be created. In most case the calculation views cannot be created for the following infoobjects: Creation of column view for 0PRODUCT failed Creation of column view for 0GN_CAT_PUR failed Creation of column view for 0BCTCOMP failed Creation of column view for 0GN_CAT_SAL failed Creation of column view for 0GN_COMPANY failed Creation of column view for 0GN_VENDOR failed The errors for infoobject 0BCTCOMP can be ignored if you don't use this content object. It has no D version in the system after BW release 730 so is obsolete. Please see the relevant part of the1695112 - Activities in BW after migrating to the SAP HANA database below: " 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. Otherwise the TXTTAB field value and the CHKTAB field value can be deleted for 0BCTCOMP in the table RSDIOBJFIX using transaction SE16. After this you can open the InfoObject 0BCTCOMP in InfoObject maintenance (RSD1) and you can deselect the short text field. You can then save and activate the InfoObject. "

For the remaining error messages: Creation of column view for 0GN_CAT_SAL failed Creation of column view for 0GN_COMPANY failed Creation of column view for 0GN_VENDOR failed Creation of column view for 0PRODUCT failed Creation of column view for 0GN_CAT_PUR failed Often the reason why the above column views cannot be created is that they are dependent on the info object 0GN_BWBEOTY which has a missing master data read class in the active version (it is available in the content version of the info object you can check this in RSD1 transaction under the tab master data/texts): The Solution is to install from BW content the info object 0GN_BWBEOTY and then the active version should have the master data read class and you should then be able to execute RS_BW_POST_MIGRATION and create the HANA views successfully for 0GN_* objects given above. Please note that you may need to Install the BW objects from content again without flagging the match or copy option, in this case any changes that you have made to the standard object will be overwritten:

If it is not clear from SLG1 what is the name of the info object that has the problem on HANA, (as in the above case the info object was 0GN_BWBEOTY) if you check the Index server trace file for the time that you get the error in SLG1 you should be able to find the name of the problem info object. In this example the following error message could be found in the Index server trace: Index creation addViewAttribute error: [2030] Adding view attribute 0GN_BWBEOTY_TSH: field TXTSH not exist in table SAPABAP1:RSBWBEOTYPTen at ptime/query/plan_executor/trex_wrapper/trex_wrapper_body/trex_joinindex.cc:280.



    



Follow SCN Contact Us



SAP Help Portal Privacy



Terms of Use



Legal Disclosure



Copyright

No labels