HANA Hierarchy consumption in BOBI

Hi Frzz,
Currently we have created some hierarchies in SAP HANA. And i would like to consume those views in BOBI. Could you please let me know what are the supporting reports (Webi,Crystal,Dashboard, Explorer etc ) that i can consume my HANA hierarchies.
Best Regards,
Krishna.

Hi Krishna,
As far as i know hierarchies created in HANA studio can be only consumed in the reporting tool which can understand MDX i.e Excel or SAP BO Analysis Office
Other Reporting tools like WebI may not be able to consume though.
PS: i tried doing this in the earlier versions and hit this road block. Hoping some one who is able to consume the hierarchies in BO or withsome update w.r.t road plan of this action item will reply here.
Regards,
Krishna Tangudu

Similar Messages

BW data model and impacts to HANA memory consumption

Hi All,
As I consider how to create BW models where HANA is the DB for a BW application, it makes sense moving the reporting target from Cubes to DSOs. Now the next logical progression of thought is that the DSO should store the lowest granularity of data(document level). So a consolidated data model that reports on cross functional data would combine sales, inventory and purchasing data all being stored at document level. In this scenario:
Will a single report execution that requires data from all 3 DSOs use more memory vs the 3 DSOs aggregated say at site/day/material?Lower Granularity Data = Higher Memory Consumption per report execution
I'm thinking that more memory is required to aggregate the data in HANA before sending to BW. Is aggregation still necessary to manage execution memory usage?
Regards,
Dae Jin

Let me rephrase.
I got an EarlyWatch that said my dimensions on one of cube were too big. I ran SAP_INFOCUBE_DESIGNS in SE38 in my development box and that confirmed it.
So, I redesigned the cube, reactivated it and reloaded it. I then ran SAP_INFOCUBE_DESIGNS again. The cube doesn't even show up on it. I suspect I have to trigger something in BW to make it populate for that cube. How do I make that happen manually?
Thanks.
Dave

Html diashow

Hi,
I've built a fullscreen-html-diashow (landscape) with hype for usage in dps apps for iPad which can easily be adapted as kind of framework.
Navigation by swiping left or right, buttons, simple tapp on image or tapping one of the thumnails. Caption for each picture. Simple optical control of length and actual position.
onlinesample: http://www.aachener-zeitung.de/zva/karlo/fullScreenSlideShow_iPad_landscape/fullScreenSlid eShow_iPad_landscape.html?
(won't work in firefox as target is mainly the dps-app, best viewed online with actual safari)
hypefile here:
http://hype.desk.com/customer/portal/questions/5802848-fullscreen-diashow-adobe-dps-app
framework (export):
https://dl.dropboxusercontent.com/u/11350320/fullScreenDiaShow_iPad_landscape.zip
Usage: Just insert your captions to the div: <div id="outsideCaptionsContainer" style="display:none"> of the htmlfile exactly as provided in the sample. copy your jpg's (named 1.jpg to xx.jpg, sizes / constrains 1024*768 and bigger) to the folder. ready.
Each caption needs to have a corresponding file and vise versa ...
Feel free to use – Hope it'll work as expected
Hans-Gerd Claßen

Hello Bob,
thx for response
only thing needing internetconnection is the googlefont, but should fallback to systemfont offline ...
Of course it's necessary to embed it within a objectstate and switchoffbutton to get out of fullscreen ...
Tested with ios7.1 – works offline here without any problem ...
Hans

Hierarchy on HANA Calculation View with Optional Input Parameters Fails

Hi,
Has anyone succeeded in building a hierarchy on top of a calculation view with optional input parameters, where an input parameter is not filled?
The original requirement came from the wish to create a parent child hierarchy on a calculation view that was copied into the customer space from a HANA Live Financial Statement query view, but I have found the following when creating a simple level hierarchy on a calculation view that consumes one table. The Calculation View has one Input Parameter where the 'mandatory' box is unchecked.
Calculation view reads ECC table FAGLFLEXT
Simple level based hierarchy on fields PRCTR, RACCT and SEGMENT
Input parameter is used as a filter for PRCTR with logic ("EMPTY" = '$$P_PROFITCTR$$' or "PRCTR" = '$$P_PROFITCTR$$')
When I run the view I see the following behaviour in HANA Studio and Analysis for Excel
Before building the hierarchy I could run the view with or without the Input Parameter
After building the hierarchy I can run the view with the Input Parameter filled, but it fails when the Input Parameter is not filled.
Error message is "error: search table error: [2426] missing placeholder; missing value for mandatory parameter P_PROFITCTR"
P_PROFITCTR is not a mandatory parameter, but the selection for the hierarchy view thinks it should be. I don't find any notes around this issue, so I don't think it's version related, however the version I have used for this test is 1.00.70.
It's a shame we can't currently build the hierarchy as the parent child relationship is provided in HANA Live view NewGLFinancialStatementQuery.
Thanks,
Ken

Hi Ken,
We have been facing similar issue. We have even tried to set default value and as optional parameter. View still fails to create hierarchy (we are not using HANA live). As mentioned on page 97 of HANA modelling guide input parameter is mandatory from engine point of view. Hierarchy is generated as column view during the initial activation of calculation view and therefore expect a value by caller.
This seems to be a product error. Some one from HANA development team should explain this issue in detail. I would expect someone like Thomas Jung reply to us.
At the moment, we cant use input parameter for date prompt which gives us calendar popup feature for date selection. Hierarchies just don't work with input parameter. We are missing something.
Regards
Angad

HANA level based Hierarchy is not displaying in AOLAP

Hi all,
I have created a level based Hierarchy in HANA which I have been able to display in Excel using a HANA MDX Provider connection:
However when I try to use the Hierarchy in Analysis for OLAP I am unable to see it, instead the dimensions are flat:
I have used an OLAP connection to HANA which otherwise appears to be working correctly.
We are on SAP BusinessObjects BI Platform 4.1 Support Pack 1 Version: 14.1.1.1036. and HANA 1.00.69.01.386065.
If anyone can help it would be greatly appreciated.
Regards,
Steve Willis.

Hi Stephen,
This should be possible. In my environment, I'm able to access both the flat and hierarchical presentations for a dimension, if I expand the dimension in the tree (see screenshot). I have noticed that the flat presentation is the default. However, if I expand and drag the appropriate hierarchy, I am seeing the hierarchy in the crosstab.
Are you able to expand the dimension and access the hierarchy?
Best regards,
Philip

Problem creating standard ECC Parent-Child Hierarchy in HANA

Hi all -
I've been trying to get a hierarchy to work on the front end of a stand alone HANA system using profit center hierarchy data from SETLEAF / SETNODE tables from ECC. Here is how my test hierarchy looks:
Following another post I found around here, I created an attribute view and filtered SETNAME to 'TST_HANA'.
The resulting data when connected to my attribute view caused an error that there was no root node, so I manually inserted the last row shown here (where PCA_PARENT = SETNAME and PCA_CHILD = SUBSETNAME):
Finally, I created my parent-child hierarchy in the attribute view and connected that view to my data foundation in the analytic view via left-outer join between Profit Center and VALFROM. However, when I go to connect to my view via MDX in excel, I get the following message:
"Hierarchy create error: Multiple parents not allowed for hierarchy node TST_ND1" Clearly from the data, there aren't multiple parents for TST_ND1. It's already a pain that to use a standard hierarchy I have to manually insert a root node, but that doesn't even seem to fix the problem.
Can anyone suggest how to fix this to get a standard profit center hierarchy working?
Thank you!
AZ

Hi,
According to me, Hierarchy level will work fine in ms excel for all analytical, calculation view using MDX Provider..
Do you have any composite primary key or composite foreign key in the tables....
r u getting correct level hierarchy output in Hana studio... plz check with all types of permutation possible.if u r getting correct output in analytical view w.r.t hana but fails to get in Ms excel..
please create Calculation view of that.. & then check the output in ms-excel..
Thanks,

How to find out memory consumption for table in HANA without load it into memory

Hi,
To determine the memory consumption for a table in HANA, you can query table M_CS_TABLES, however, it requires load table into memory first, I just wonder if there has another table store memory consumption information for all HANA tables regardless it load into memory or not. Below is screenshot for one of table in my system, since that table is partially loaded into memory, "Total Memory Consumption (KB):" tell me the memory consumption of the portion load into memory, what I am looking for is something like "Estimated Maximun Memory Consumption (KB)" which provides me total memory consumption for that table including portion doesn't load into memory, of course I can use this Esitmated information, but consider I have close to thousand tables in my HANA system already, it's not pratical to check tables one by one.
Thanks,
Xiaogang.

Hi Xiaogang,
Estimated Memory Size that you see in the Table Run time Information - same is available in M_CS_TABLES also
If you don't get the size of any Table in M_CS_TABLES View, then the same will also not be available in Runtime information of the Table
Even if tables are not loaded into memory, you can get the Estimated Size, just try running the query with filter LOADED = 'NO'
Regards,
Vivek

Cost Center Assessment to Cost Hierarchy based on Actual Consumption error

Assessment is set up:
SENDER: Cost Center: Overhead Expenses (values in expense accounts)
RECEIVER: Top Node of Cost Object Hierarchy (material consumption has been posted to two objects - related account has value and quantity fields)
Segment is set up:
Sender Rules: Posted Amounts
Share:100%
Actual value origin
Receiving tracing factor:
Receiver rule: Variable Portions
Var. portion type: Actual Consumption
No Scaling
Assumption is that "Var. portion type: Actual Consumptions" means the quantity in the consumption account on the receiver from the inventory posting. Is this true?
Edited by: Chris Gibson on Apr 13, 2010 11:56 PM

Hi dear Ajay, thank you for your answer.
first, I understand the difference between KSUB and KSU5, in the defined scenario, we have both. planned values, become actual with the MEC activities. business definition.
regarding the cycle, I have setup assessment cost element so we can get all planned lines posted as 1.
On sender tab I have only the cost center. no cost element defined.
receiver its cost center.
furthermore, i've not setup allocation structure, so all cost elements should be allow, there is no restriction on this.
the only difference is: planned costs which their origin is already an assessment are not being assessed again.
I can show you the print screens with cycles setup if it helps
best regards
MF

Hana BOBI dashboard exposed as odata service

I am planning for a business case where I need to get the dashboard output as Odata service which can be consumed by WEBIDE from HCP for SAPUI5 development. Please guide me how i can do that

This leads to the folloing error: Invalid value: not supported type conversion.
The post is splitted as Ctrl+V blocks the editor....
Calling URL:
leads to:

Creation of Universe based on Hana OLAP connection

I have to create a universe in IDT 4.1 sp2 based on SAP HANA OLAP
connection ?
How can i access SAP HANA view which was created using OLAP connection in Business objects Explorer? It does not allow creating Universe on top of SAP HANA OLAP connection and gives an error
SAP Business Objects query and reporting applications can directly connect to OLAP SAP HANA connections. No universe is required, only a published OLAP SAP HANA connection.
Thanks

Hi Jyothy,
Refer the below link on how to create universe on Analytic View/Calculation View using relation connection in IDT
http://www.sapanalyticsguru.com/index.php/sap-bobi/31-universe-creation-on-hana-view-using-information-design-tool

Text node in the Charac Hierarchy sums up

Hi,
I am working on IP.
I had created an hierarchy for a specific consumption data with the top node as a text node, which should appear only once in the report.
But when i use the Input ready query, the system shows multiple rows of the text node for every new characteristic values in the nodes below this node.
How do i avoid the text node being displayed multiple times?
Thanks in advance,
regards,
Sriram

Hi Jacky,
Yes i have text nodes for more than one set of characteristics.
Level 1A
    Level 2
        Char1 A
        Char1 B
Level 1B
        Char1 C
        Char1 D
        Char1 E
These characteristic also have an attribute characteristic. Hence, in the Input ready query it displays as follows;
Level 1A
    Level 2          Char2 A
    Level 2          Char2 B
        Char1 A    Char2 A
        Char1 B    Char2 B
Is there a way to avoid the "Char2" in the text nodes.
Thank in advance for the solution,
regards,
Sriram

PSA no deletion SAP BW on HANA Rev 61

Hi,
PSAs are not getting deleted for some of the datasources due to error loads and multiple runs. System is SAP BW on HANA Rev 61.
The previous job failure was not corrected and the subsequent job was started based on the process chain schedule and that one as well failed. This has happened 2 times. Now the PSA table says it has duplicate entries and it is not dropping when we try to delete manually or through program.
Whenever we try to delete the PSA, the SAPLSDB2 program runs and is stuck in SM51. St22 error log says
SQL error "-10807" while accessing table "/BIC/B0000674001".
65        l_s_data TYPE /BIC/B0000674001.
66 *---1363526 Increasing the security to check the number of records inserted in PSA table
67 *---is actually equal to data in l_t_data or p_t_data.
68 DATA: l_rollback TYPE rs_bool,
69        l_count TYPE i.
70 l_rollback = RS_C_FALSE.
71 *---1363526
72
73 APPEND LINES OF p_t_data TO l_t_data.
74
75 CLEAR: l_s_data.
76 l_s_data-partno = p_partno.
77
78 MODIFY        l_t_data
79 FROM          l_s_data
80 TRANSPORTING partno
81 WHERE        request = p_requestid.
82
83
>>> INSERT      /BIC/B0000674001
85 FROM TABLE l_t_data
86 ACCEPTING DUPLICATE KEYS.
87 *---1363526
88 DESCRIBE TABLE l_t_data LINES l_count.
89 IF l_count NE sy-dbcnt.
90    l_rollback = RS_C_TRUE.
91 ENDIF.
92 *---1363526
Category              ABAP Server Resource Shortage
Runtime Errors        DBIF_RSQL_SQL_ERROR
Except.                CX_SY_OPEN_SQL_DB
Date and Time          10.08.2014 11:28:01
|Short text                                                                                        |
|    SQL error "-10807" while accessing table "/BIC/B0000674001".                                  |
|What happened?                                                                                    |
|    Database error text: "System call 'recv' failed, rc=145:Connection timed out"                |
|What can you do?                                                                                  |
|    Please make a note of the actions and input which caused the error.                          |
|    -                                                                                            |
|                                                                                                  |
|    To resolve the problem, contact your                                                          |
|    SAP system administrator.                                                                    |
|                                                                                                  |
|    Using transaction ST22 for ABAP dump analysis you can see and                                |
|    administrate termination messages and retain them for longer periods.                        |
|    Please make a note of the actions and input which caused the error.                          |
|    -                                                                                            |
|                                                                                                  |
|    To resolve the problem, contact your                                                          |
|    SAP system administrator.                                                                    |
|                                                                                                  |
|    Using transaction ST22 for ABAP dump analysis you can see and                                |
|    administrate termination messages and retain them for longer periods.                        |
|Error analysis                                                                                    |
|    An exception occurred that is explained in detail below.                                      |
|    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught                |
|    in                                                                                          |
|    procedure "INSERT_ODS" "(FORM)", nor was it propagated by a RAISING clause.                  |
|    Since the caller of the procedure could not have anticipated that the                        |
|    exception would occur, the current program is terminated.                                    |
|    The reason for the exception is:                                                              |
|    Database error text: "System call 'recv' failed, rc=145:Connection timed out"                |
|How to correct the error                                                                          |
|    Internal call code.........: "[RSQL/INSR//BIC/B0000674001 ]"                                  |
|    Please check the entries in the system log (Transaction SM21).                                |
|    You may able to find an interim solution to the problem                                      |
|    in the SAP note system. If you have access to the note system yourself,                      |
|    please use the following search criteria:                                                    |
|                                                                                                  |
|        "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"                                                |
|        "GP4PWAW7JG4VX23SSK75NF4776C" bzw. "GP4PWAW7JG4VX23SSK75NF4776C"                          |
|        "INSERT_ODS"                                                                              |
|    If you cannot solve the problem yourself, please send the                                    |
|    following documents to SAP:                                                                  |
|                                                                                                  |
|    1. A hard copy print describing the problem (short dump).                                    |
|      To obtain this, select "System->List->Save->Local File (unconverted)"                      |
|      on the current screen.                                                                    |
|                                                                                                  |
|    2. A suitable hardcopy printout of the system log.                                            |
|      To obtain this, call the system log with Transaction SM21                                  |
|      and set the time interval to 10 minutes before and 5 minutes after                        |
|      the short dump. In the display choose "System->List->Save->                                |
|      Local File (unconverted)"                                                                  |
|                                                                                                  |
|    3. If the programs are your own programs or modified SAP programs,                            |
|      supply the source code.                                                                    |
|      To do this, choose "More Utilities->Upload/Download->Download" in the                      |
|      Editor.                                                                                    |
|                                                                                                  |
|    4. Details regarding the conditions under which the error occurred                            |
|      or which actions and input led to the error.                                              |
|    You may able to find an interim solution to the problem                                      |
|    in the SAP note system. If you have access to the note system yourself,                      |
|    please use the following search criteria:                                                    |
|                                                                                                  |
|        "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"                                                |
|        "GP4PWAW7JG4VX23SSK75NF4776C" bzw. "GP4PWAW7JG4VX23SSK75NF4776C"                          |
|        "INSERT_ODS"                                                                              |
|    If you cannot solve the problem yourself, please send the                                    |
|    following documents to SAP:                                                                  |
|                                                                                                  |
|    1. A hard copy print describing the problem (short dump).                                    |
|      To obtain this, select "System->List->Save->Local File (unconverted)"                      |
|      on the current screen.                                                                    |
|                                                                                                  |
|    2. A suitable hardcopy printout of the system log.                                            |
|      To obtain this, call the system log with Transaction SM21                                  |
|      and set the time interval to 10 minutes before and 5 minutes after                        |
|      the short dump. In the display choose "System->List->Save->                                |
|      Local File (unconverted)"                                                                  |
|                                                                                                  |
|    3. If the programs are your own programs or modified SAP programs,                            |
|      supply the source code.                                                                    |
|      To do this, choose "More Utilities->Upload/Download->Download" in the                      |
|      Editor.                                                                                    |
|                                                                                                  |
|    4. Details regarding the conditions under which the error occurred                            |
|      or which actions and input led to the error.                                              |
|    The exception must either be prevented, caught within proedure                                |
|    "INSERT_ODS" "(FORM)", or its possible occurrence must be declared in the                    |
|    RAISING clause of the procedure.                                                              |
|    To prevent the exception, note the following:                                                |
|System environment                                                                                |
|    SAP Release..... 730                                                                          |
|    SAP Basis Level. 0006                                                                        |
|                                                                                                  |
|    Application server... "pkghnp"                                                                |
|    Network address...... "10.83.240.20"                                                          |
|    Operating system..... "SunOS"                                                                |
|    Release.............. "5.10"                                                                  |
|    Hardware type........ "sun4u"                                                                |
|    Character length.... 16 Bits                                                                  |
|    Pointer length....... 64 Bits                                                                |
|    Work process number.. 4                                                                      |
|    Shortdump setting.... "full"                                                                  |
|                                                                                                  |
|    Database server... "vsyexhann01"                                                              |
|    Database type..... "HDB"                                                                      |
|    Database name..... "HNP"                                                                      |
|    Database user ID.. "SAPHNP"                                                                  |
|                                                                                                  |
|    Terminal.......... " "                                                                        |
|                                                                                                  |
|    Char.set.... "C"                                                                              |
|                                                                                                  |
|    SAP kernel....... 720                                                                        |
|    created (date)... "Mar 21 2012 09:58:29"                                                      |
|    create on........ "SunOS 5.10 Generic_141444-09 sun4us"                                      |
|    Database version. "SQLDBC 1.00.61.0380109 "                                                  |
|                                                                                                  |
|    Patch level. 201                                                                              |
|    Patch text.. " "                                                                              |
|                                                                                                  |
|    Database............. "HDB 1.0"                                                              |
|    SAP database version. 720                                                                    |
|    Operating system..... "SunOS 5.10, SunOS 5.11"                                                |
|                                                                                                  |
|    Memory consumption                                                                            |
|    Roll.... 0                                                                                    |
|    EM...... 100555392                                                                            |
|    Heap.... 0                                                                                    |
|    Page.... 0                                                                                    |
|    MM Used. 75424248                                                                            |
|    MM Free. 25123904                                                                            |
|User and Transaction                                                                              |
|    Client.............. 330                                                                      |
|    User................ "BIREMOTE"                                                              |
|    Language key........ "E"                                                                      |
|    Transaction......... " "                                                                      |
|    Transaction ID...... "53E66CC9405502F9E10000000A53F03E"                                      |
|                                                                                                  |
|    EPP Whole Context ID.... "CEED21FC7C3EC04FA3C0D0912FE05A37"                                  |
|    EPP Connection ID....... 00000000000000000000000000000000                                    |
|    EPP Caller Counter...... 0                                                                    |
|                                                                                                  |
|    Program............. "GP4PWAW7JG4VX23SSK75NF4776C"                                            |
|    Screen.............. "SAPMSSY1 3004"                                                          |
|    Screen Line......... 2                                                                        |
|    Debugger Active..... "none"                                                                  |
|Server-Side Connection Information                                                                |
|    Information on caller of Remote Function Call (RFC):                                          |
|    System.............. "SP1"                                                                    |
|    Installation number " "                                                                      |
|    Database release... 620                                                                      |
|    Kernel release...... 640                                                                      |
|    Connection type 3 (2=R/2, 3=ABAP system, E=external, R=reg. external)                        |
|    Call type.......... "synchronous and transactional type T (emode 0, imode 0)"                |
|    Inbound TID.........." "                                                                      |
|    Inbound queue name..." "                                                                      |
|    Outbound TID........."0A53F03E141153E6C6641A65"                                              |
|    Outbound queue name.." "                                                                      |
|                                                                                                  |
|    Client#............. 330                                                                      |
|    User................."BIWREMOTE"                                                              |
|    Transaction......... " "                                                                      |
|    Call program........."SAPLERFC"                                                              |
|    Function module "ARFC_DEST_SHIP"                                                              |
|    Call destination.. "HNP330"                                                                  |
|    Source server....... "pkgapp2_SP1_03"                                                        |
|    Source IP address "10.83.240.59"                                                              |
|                                                                                                  |
|    Additional information on RFC logon:                                                          |
|    Trusted relationship." "                                                                      |
|    Logon return code....0                                                                        |
|    Trusted teturn code..0                                                                        |
|                                                                                                  |
|    Note:                                                                                        |
|    - For Releases < 4.0, information on the RFC caller is not available.                        |
|    - The installation number is provided from Release > 700                                      |
|    Transaction......... " "                                                                      |
|    Call Program........."SAPLERFC"                                                              |
|    Function Module..... "ARFC_DEST_SHIP"                                                        |
|    Call Destination.... "HNP330"                                                                |
|    Source Server....... "pkgapp2_SP1_03"                                                        |
|    Source IP Address... "10.83.240.59"                                                          |
|                                                                                                  |
|    Additional information on RFC logon:                                                          |
|    Trusted Relationship " "                                                                      |
|    Logon Return Code... 0                                                                        |
|    Trusted Return Code. 0                                                                        |
|                                                                                                  |
|    Note:                                                                                        |
|    - For Releases < 4.0, information on the RFC caller not available.                            |
|    - The installation number is available from caller Release > 700                              |
|Information on where terminated                                                                  |
|    Termination occurred in the ABAP program "GP4PWAW7JG4VX23SSK75NF4776C" - in                  |
|    "INSERT_ODS".                                                                                |
|    The main program was "SAPMSSY1 ".                                                            |
|                                                                                                  |
|    In the source code you have the termination point in line 84                                  |
|    of the (Include) program "GP4PWAW7JG4VX23SSK75NF4776C".                                      |
|    The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in                  |
|    procedure "INSERT_ODS" "(FORM)", but it was neither handled locally nor                      |
|    declared                                                                                    |
|    in the RAISING clause of its signature.                                                      |
|                                                                                                  |
|    The procedure is in program "GP4PWAW7JG4VX23SSK75NF4776C "; its source code                  |
|    begins in line                                                                              |
|    23 of the (Include program "GP4PWAW7JG4VX23SSK75NF4776C ".                                    |
|Source Code Extract                                                                              |
|Line |SourceCde                                                                                  |
| 54|* leave further processing because data is not consistent                                  |
| 55|                                                                                            |
| 56| IF l_inconsistency_found = rs_c_true.                                                    |
| 57|    p_subrc = 77.                                                                          |
| 58|    EXIT.                                                                                  |
| 59| ENDIF.                                                                                    |
| 60|                                                                                            |
| 61|                                                                                            |
| 62|                                                                                            |
| 63|                                                                                            |
| 64| DATA: l_t_data TYPE ty_t_data,                                                            |
| 65|        l_s_data TYPE /BIC/B0000674001.                                                    |
| 66|*---1363526 Increasing the security to check the number of records inserted in PSA table    |
| 67|*---is actually equal to data in l_t_data or p_t_data.                                      |
| 68| DATA: l_rollback TYPE rs_bool,                                                            |
| 69|        l_count TYPE i.                                                                    |
| 70| l_rollback = RS_C_FALSE.                                                                  |
| 71|*---1363526                                                                                |
| 72|                                                                                            |
| 73| APPEND LINES OF p_t_data TO l_t_data.                                                    |
| 74|                                                                                            |
| 75| CLEAR: l_s_data.                                                                          |
| 76| l_s_data-partno = p_partno.                                                              |
| 77|                                                                                            |
| 78| MODIFY        l_t_data                                                                    |
| 79| FROM          l_s_data                                                                    |
| 80| TRANSPORTING partno                                                                      |
| 81| WHERE        request = p_requestid.                                                      |
| 82|                                                                                            |
| 83|                                                                                            |
|>>>>>| INSERT      /BIC/B0000674001                                                              |
| 85| FROM TABLE l_t_data                                                                      |
| 86| ACCEPTING DUPLICATE KEYS.                                                                |
| 87|*---1363526                                                                                |
| 88| DESCRIBE TABLE l_t_data LINES l_count.                                                    |
| 89| IF l_count NE sy-dbcnt.                                                                  |
| 90|    l_rollback = RS_C_TRUE.                                                                |
| 91| ENDIF.                                                                                    |
| 92|*---1363526                                                                                |
| 93|                                                                                            |
| 94|                                                                                            |
| 95|*---1363526                                                                                |
| 96| IF sy-subrc NE 0 OR l_rollback = RS_C_TRUE.                                              |
| 97|* Insert not successful - rollback changes                                                |
| 98|    CALL FUNCTION 'DB_ROLLBACK'.                                                            |
| 99|*---1363526                                                                                |
| 100|    p_subrc = 13.                                                                          |
| 101| ENDIF.                                                                                    |
| 102|                                                                                            |
| 103|ENDFORM.                    "INSERT_ODS                                                    |
|    isShmLockId = 0                                                                              |
|    isUsed      = 1                                                                              |
|    isCtfyAble = 1                                                                              |
|    hasScndKeys = 0                                                                              |
|    hasRowId    = 0                                                                              |
|    scndKeysOutdated = 0                                                                          |
|    scndUniKeysOutdated = 0                                                                      |
|    ----- Shareable Table Header Data -----                                                      |
|    tabi        = 0xFFFFFFF1DD5E8E58                                                            |
|    pgHook      = 0x0000000000000000                                                            |
|    idxPtr      = 0x0000000000000000                                                            |
|    id          = 11    (0x0000000B)                                                            |
|    shmTabhSet = 0x0000000000000000                                                            |
|    refCount    = 0    (0x00000000)                                                            |
|    tstRefCount = 0    (0x00000000)                                                            |
|    lineAdmin    = 4    (0x00000004)                                                            |
|    lineAlloc    = 4    (0x00000004)                                                            |
|    shmVersId    = 0    (0x00000000)                                                            |
|    shmRefCount = 1    (0x00000001)                                                            |
|    rowId        = 18446744073709551615                                                          |
|    scndKeyAdmin = 0x0000000000000000                                                            |
|    0A53F03E141153E6C6641A65HNP330                          00000001SENDED RSAR_TRFC_DATA_RECEIVE|
|    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000|
|    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000|
|    3433433433333343433334334453332222222222222222222222222233333333544444225545555445445455444454|
|    0153603514115356366411658E0330000000000000000000000000000000000135E454002312F4263F4141F2535965|
|    0030004100350033004600300033004500310034003100310035003300450036004300360036003400310041003600|
|PROG                                                                                              |
|    SAPLERFC                                                                                      |
|    0000000000000000000000000000000000000000                                                      |
|    0000000000000000000000000000000000000000                                                      |
|    5454454422222222222222222222222222222222                                                      |
|    310C526300000000000000000000000000000000                                                      |
|    005300410050004C004500520046004300200020002000200020002000200020002000200020002000200020002000|
|%_DUMMY$$                                                                                        |
|                                                                                                  |
|    0000                                                                                          |
|    0000                                                                                          |
|    2222                                                                                          |
|    0000                                                                                          |
|    0020002000200020                                                                              |
|NUMBER_OF_FUNCTION_MODULES                                                                        |
|    1                                                                                            |
|    0000                                                                                          |
|    0001                                                                                          |
|    00000001                                                                                      |
|SUPPORTABILITY_INFO-DEBUG_CONTEXT_ID                                                              |
|                                                                                                  |
|    0000000000000000000000000000000000000000                                                      |
|    0000000000000000000000000000000000000000                                                      |
|    2222222222222222222222222222222222222222                                                      |
|    0000000000000000000000000000000000000000                                                      |
|    0020002000200020002000200020002000200020002000200020002000200020002000200020002000200020002000|
|SPACE                                                                                            |
|                                                                                                  |
|    0                                                                                            |
|    0                                                                                            |
|    2                                                                                            |
|    0                                                                                            |
|    0020                                                                                          |
|SCREEN                                                                                            |
|                                                                                                  |
|    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000|
|    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000|
|    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222|
|    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000|
|    0020002000200020002000200020002000200020002000200020002000200020002000200020002000200020002000|
|No.      4 Ty.          FUNCTION                                                                |
|Name ARFC_DEST_SHIP                                                                              |
|SENDER_ID                                                                                        |
|    pkgapp2_SP1_03                                                                                |
|    00000000000000000000000000000000                                                              |
|    00000000000000000000000000000000                                                              |
|    76667735553533222222222222222222                                                              |
|    0B71002F301F03000000000000000000                                                              |
|    0070006B00670061007000700032005F005300500031005F0030003300200020002000200020002000200020002000|
|SUPPORTABILITY_INFO                                                                              |
|    ########                                        ## #                                        |
|    000000000000000000000000000000000000000000000000000000                                        |
|    000000000000000000000000000000000000000000000000000000                                        |
|    000000002222222222222222222222222222222222222222002220                                        |
|    000000000000000000000000000000000000000000000000000000                                        |
|    0000000000000000000000000000000000200020002000200020002000200020002000200020002000200020002000|
|UNIT_ID                                                                                          |
|    ################

Hi Siddartha,
That option is not working.
Thanks

After upgrading HANA from rev. 69.1 to rev.72 OOM errors occure during HDB startup

Hello,
we upgraded our HANA scale out system from rev. 69.1 to rev. 72.
~4 hours after the upgrade our HDB crashed with OOM errors on the master indexserver.
Since than we are trying to start it back up and face OOM errors during startup in the index rebuild phase:
The errors clearly state the HANA runs out of allocatable memory for Pool/IndexRebuildAllocator during startup.
It looks like HANA requires more memory during this phase compared to rev. 69.1
Our Master node has 512GB of physical memory and the Allocation limit is set to 95% of this (default).
Here is what we read from our logs during startup:
[3331]{-1}[-1/-1] 2014-03-24 01:35:36.735498 i Service_Startup ptime_master_start.cc(00719) : Rebuilding system indexes.
[3331]{-1}[-1/-1] 2014-03-24 01:35:37.236971 i Service_Startup ptime_master_start.cc(00733) : Rebuilding system indexes done.
[3331]{-1}[-1/-1] 2014-03-24 01:35:37.237002 i Service_Startup ptime_master_start.cc(00735) : Rebuilding indexes.
[3331]{-1}[-1/-1] 2014-03-24 01:35:37.244660 i Service_Startup IndexManager_rebuild.cc(00478) : Number of indexes: 2837
[3331]{-1}[-1/-1] 2014-03-24 01:35:37.245606 i Service_Startup IndexManager_rebuild.cc(00580) : Number of JobEx indexes: 2798
[3367]{-1}[9/-1] 2014-03-24 01:36:33.729391 w ResMan           ResourceContainer.cpp(01300) : Information about shrink at 24.03.2014 01:28:46 000 Mon:
Reason for shrink: Precharge for big block allocation. User size: 6269307200
ShrinkCaller
[4123]{-1}[9/-1] 2014-03-24 01:36:42.465154 w Memory           PoolAllocator.cpp(01060) : Out of memory for Pool/IndexRebuildAllocator, size 48B, flags 0x0
[4123]{-1}[9/-1] 2014-03-24 01:36:42.465168 e Memory           ReportMemoryProblems.cpp(00733) : OUT OF MEMORY occurred.
[3538]{-1}[9/-1] 2014-03-24 01:36:42.465164 w Memory           PoolAllocator.cpp(01060) : Out of memory for Pool/IndexRebuildAllocator, size 48B, flags 0x0
[3538]{-1}[9/-1] 2014-03-24 01:36:42.465177 e Memory           ReportMemoryProblems.cpp(00733) : OUT OF MEMORY occurred.
[4123]{-1}[9/-1] 2014-03-24 01:36:42.465168 e Memory           ReportMemoryProblems.cpp(00733) : Failed to allocate 48 byte.
[3538]{-1}[9/-1] 2014-03-24 01:36:42.465177 e Memory           ReportMemoryProblems.cpp(00733) : Failed to allocate 48 byte.
[4123]{-1}[9/-1] 2014-03-24 01:36:42.465168 e Memory           ReportMemoryProblems.cpp(00733) : Current callstack:
[3538]{-1}[9/-1] 2014-03-24 01:36:42.465177 e Memory           ReportMemoryProblems.cpp(00733) : Current callstack:
[3562]{-1}[9/-1] 2014-03-24 01:36:42.465245 w Memory           PoolAllocator.cpp(01060) : Out of memory for Pool/IndexRebuildAllocator, size 48B, flags 0x0
[3562]{-1}[9/-1] 2014-03-24 01:36:42.465256 e Memory           ReportMemoryProblems.cpp(00733) : OUT OF MEMORY occurred.
GLOBAL_ALLOCATION_LIMIT (GAL) = 520645177866b (484.88gb), SHARED_MEMORY = 243742983024b (227gb), CODE_SIZE = 6919073792b (6.44gb)
PID=2987 (hdbnameserver), PAL=487793667686, AB=1596952576, UA=0, U=1415644701, FSL=0
PID=3196 (hdbcompileserve), PAL=487793667686, AB=447041536, UA=0, U=356200477, FSL=0
PID=3193 (hdbpreprocessor), PAL=487793667686, AB=416477184, UA=0, U=292814063, FSL=0
PID=3254 (hdbstatisticsse), PAL=54199296409, AB=1040187392, UA=0, U=862081043, FSL=0
PID=3257 (hdbxsengine), PAL=487793667686, AB=1100451840, UA=0, U=907234077, FSL=0
PID=3251 (hdbindexserver), PAL=487793667686, AB=265382010522, UA=0, U=218447843045, FSL=0
Total allocated memory= 520645177866b (484.88gb)
Total used memory     = 472943874222b (440.46gb)
Sum AB                = 269983121050
Sum Used              = 222281817406
Heap memory fragmentation: 9
Top allocators (ordered descending by inclusive_size_in_use).
1: /                                                                       218448756093b (203.44gb)
2: Pool                                                                    214254480696b (199.53gb)
3: Pool/IndexRebuildAllocator                                              196297409104b (182.81gb)
4: Pool/PersistenceManager                                                 9920106968b (9.23gb)
5: Pool/PersistenceManager/PersistentSpace(0)                              9779577952b (9.10gb)
6: Pool/PersistenceManager/PersistentSpace(0)/RowStoreLPA                  9473884512b (8.82gb)
7: Pool/ResourceContainer                                                  2852314824b (2.65gb)
8: AllocateOnlyAllocator-unlimited                                         2832931544b (2.63gb)
9: Pool/malloc                                                             2660566632b (2.47gb)
10: Pool/malloc/libhdbrskernel.so                                           2467813288b (2.29gb)
11: Pool/RowEngine                                                          2284285840b (2.12gb)
12: AllocateOnlyAllocator-unlimited/FLA-UL<3145728,1>/MemoryMapLevel2Blocks 2135949312b (1.98gb)
13: AllocateOnlyAllocator-unlimited/FLA-UL<3145728,1>                       2135949312b (1.98gb)
14: Pool/RowEngine/CpbTree                                                  1417842512b (1.32gb)
15: AllocateOnlyAllocator-limited                                           1184520640b (1.10gb)
16: AllocateOnlyAllocator-limited/ResourceHeader                            1184517680b (1.10gb)
17: Pool/RowEngine/LockTable                                                536881408b (512mb)
18: AllocateOnlyAllocator-unlimited/FLA-UL<120,256>/BigBlockInfoAllocator   360752520b (344.04mb)
19: AllocateOnlyAllocator-unlimited/FLA-UL<120,256>                         360752520b (344.04mb)
20: Pool/PersistenceManager/PersistentSpace(0)/RowStoreConverter            239921680b (228.80mb)
Top allocators (ordered descending by exclusive_size_in_use).
1: Pool/IndexRebuildAllocator                                               196297409104b (182.81gb)
2: Pool/PersistenceManager/PersistentSpace(0)/RowStoreLPA                   9473884512b (8.82gb)
3: Pool/ResourceContainer                                                   2852314824b (2.65gb)
4: Pool/malloc/libhdbrskernel.so                                            2467813288b (2.29gb)
5: AllocateOnlyAllocator-unlimited/FLA-UL<3145728,1>/MemoryMapLevel2Blocks 2135949312b (1.98gb)
6: Pool/RowEngine/CpbTree                                                   1417842512b (1.32gb)
7: AllocateOnlyAllocator-limited/ResourceHeader                             1184517680b (1.10gb)
8: Pool/RowEngine/LockTable                                                 536881408b (512mb)
9: AllocateOnlyAllocator-unlimited/FLA-UL<120,256>/BigBlockInfoAllocator    360752520b (344.04mb)
10: Pool/PersistenceManager/PersistentSpace(0)/RowStoreConverter/ConvPage    239075328b (228mb)
11: Pool/RowEngine/Internal                                                  205837824b (196.30mb)
12: StackAllocator                                                           176672768b (168.48mb)
13: AllocateOnlyAllocator-unlimited/FLA-UL<48,128>/FreeBigBlockInfoAllocator 144301008b (137.61mb)
14: Pool/RowEngine/Transaction                                               103391528b (98.60mb)
15: Pool/malloc/libhdbexpression.so                                          90507984b (86.31mb)
16: Pool/malloc/libhdbbasement.so                                            90380472b (86.19mb)
17: AllocateOnlyAllocator-unlimited/ReserveForUndoAndCleanupExec             84029440b (80.13mb)
18: AllocateOnlyAllocator-unlimited/ReserveForOnlineCleanup                  84029440b (80.13mb)
19: Pool/Statistics                                                          83825720b (79.94mb)
20: Pool/PersistenceManager/ContainerNameDirectory                           59182968b (56.44mb)
In order to fix this bottleneck, we first need to get HDB started, but how?
Is there a way to aviod that row store tables are being loaded during startup? (this would allow enough memory for the index rebuild)
Is there a way to skip the index rebuild during startup?
Can we increase the allocation limit to more than 95% of the physical memory? (e.g. we could configure swap space to be utilized, just to get over the edge of this during the startup in order to bring our HDB back up and work on reducing the memory requirement on the master index server)
Kind Regards
Florian Wittmann
ps. we also have a call with SAP.

To update everyone who runs into the same issue during startup of HANA, here is the solution that has worked for us. But I highly recommend to have such an approach reviewed by SAP service before I you perform this!
For us the only chance left to bring HANA up was to configure swap space on the master node. (We configured 20GB...we could not know how much memory it would need during the startup to get passed the index rebuild, so that was just a guess that turned out to be just enough for us to get passed that memory peak during the startup phase).
After that we adjusted the custom parameter file /sapmnt/<SID>/global/hdb/custom/config/global.ini
and maintained a global_allocation_limit that we manually calculated as (512GB physical mem. + 20GB swap mem.)/0.95
e.g.
[memorymanager]
global_allocation_limit=517530
Than we started HANA up again and made use of the page file during the index rebuild in the startup phase...of course this dramatically slows down the startup...well you do an index reorg using swap space...but after 1hour we got passed the index rebuild and memory utilization went down again. (With this error we learned that HANA has a significantly higher memory consumption during startup and the upgrade from SP 6 to SP 7 must have even increased this slightly, since we managed to startup our HANA db before upgrading without this issue, but it was not the root cause!)
Now that we had HANA back up, we investigated memory consuming indices together with SAP, and with the help of below query, we identified row store table RSMONMESS to hold 25GB of 2ndary indices!
select table_name, round((sum(index_size)) / 1024 / 1024, 2) as
SIZE_IN_MB, count(*) as number_of_indexes from M_RS_INDEXES group by
table_name order by SIZE_IN_MB desc
Before droping 2ndary indices:
TABLE_NAME;SIZE_IN_MB;NUMBER_OF_INDEXES
RSMONMESS;30.883,8;6
drop index SAP<SID>."RSMONMESS~AXX";
drop index SAP<SID>."RSMONMESS~TIM";
drop index SAP<SID>."RSMONMESS~AU1";
drop index SAP<SID>."RSMONMESS~RID";
drop index SAP<SID>."RSMONMESS~AXY";
After drop:
TABLE_NAME;SIZE_IN_MB;NUMBER_OF_INDEXES
RSMONMESS;5.708,43;1
With that change we reset our custom parameter on global_allocation_limit and went back to the default (95% of main physical mem.), removed the swap file and started up HANA again...and during this startup we managed to stay in our global_allocation_limit and bring HANA back up again!

Problems in creating RLANG stored procedure in HANA studio

Hi,
While I am creating a stored procedure (using .hdbprocedure file) in HANA studio with language as RLANG, I am getting an error message like this: "It is not supported to use another language than sqlscript".
I have the following setting configured.
HANA System -> Administration -> Configuration ->indexserver.ini -> repository -> sqlscript_mode = UNSECURE
Any clues will be appreciated.
Best Regards
Surya

HI Raj,
This happens even for the empty procedure as following
PROCEDURE "IDMANALYTICS_OPER"."idmanalytics.hana.db.hdbprocedures::MC_ROLEMINING_CLUSTERING_R" ( )
LANGUAGE RLANG
SQL SECURITY INVOKER
READS SQL DATA AS
BEGIN
Write your procedure logic
END;
The procedure that I wanted to write is following.
PROCEDURE MC_ROLEMINING_CLUSTERING_R(IN rolemining_input "_SYS_BIC"."idmanalytics.hana.db.views/MC_ROLEMINING_VINPUT",
IN params "IDMANALYTICS_DB"."idmanalytics.hana.db.hdbtables::MC_ROLEMINING_PARAMETER",
OUT result MC_ROLEMINING_CLUSTERS_TYPE,
OUT result_hierarchy MC_ROLEMINING_HIERARCHY_TYPE,
OUT result_userorder MC_ROLEMINING_USERORDER_TYPE
LANGUAGE RLANG AS
BEGIN
noofclusters <- params$INT_VALUE[1];
simindex <- params$DOUBLE_VALUE[2];
distancemethod="jaccard"
clusteringmethod="complete"
usercol <- rolemining_input$USER_ID
privcol <- rolemining_input$PRIV_ID
#--generate user-permission matrix from user-permission table
uptable <- data.frame(users = usercol, privileges = privcol)
uniqueusers <- sort(unique(uptable$users))
uniqueprivileges <- sort(unique(uptable$privileges))
upmatrixdata <- vector()
index <- 0
for(i in uniqueusers )
for(j in uniqueprivileges) {
row_to_find <- data.frame(users=i, privileges = j)
if(duplicated(rbind(uptable, row_to_find))[nrow(uptable)+1]){
upmatrixdata <- append(upmatrixdata, 1, after = index)
else {
upmatrixdata <- append(upmatrixdata, 0, after = index)
index <- index +1
upmatrix <- matrix(
upmatrixdata ,
nrow = length(uniqueusers),
ncol = length(uniqueprivileges),
byrow = TRUE,
          dimnames = list(
          uniqueusers,
              uniqueprivileges
#--apply hierarchical clustersing
require(vegan)
distance<-vegdist(upmatrix,method=distancemethod)
clusters<-hclust(distance,method=clusteringmethod)
#--fill clusters for given h and k
if(noofclusters > 0){
userclusters<-cutree(clusters,k=noofclusters)
tempresult <- as.data.frame(userclusters)
result <- data.frame(USER_ID=row.names(tempresult), CLUSTER_ID=tempresult$userclusters)
if(noofclusters <= 0 & simindex >= 0){
userclusters<-cutree(clusters,h=simindex)
tempresult <- as.data.frame(userclusters)
result <- data.frame(USER_ID=row.names(tempresult), CLUSTER_ID=tempresult$userclusters)
#--fill role hierarchy
clusters_merge <- as.data.frame(clusters$merge)
clusters_height <- clusters$height
clusters_order <- clusters$order
result_hierarchy <- data.frame(HEIGHT=clusters_height, V1=clusters_merge$V1, V2=clusters_merge$V2)
#--fill user order
clusters_order <- clusters$order
result_userorder <- data.frame(USERORDER=clusters_order)
END;

"While trying to invoke the method com.sap.ip.bi.bics.dataaccess consumer.queryview.hierarchy.iqqvDrillPathElement.getCharacteristics Type ()of an object loaded from local variable 'pathElement' (WIS 00000)"

Hi Gurus,
   We are using BOBI 4.1 and we have created a webI report and while refreshing the report, we are facing the below error first time. After we close the error message and if we refresh again, its working fine. I have found one note (1724168 - Hierarchy error when refreshing a Web Intelligence document) stated that its a bug in 4.0 and its resolved in 4.1. But still am facing the same error in 4.1. Kindly help me to resolve the issue. Anyone input is highly appreciated.
Thanking you in anticipation.
Obinna.

Dear Henry,
   Please find my inputs below.
What SP are you on? --------- BOBI 4.1 SP2
what does your webi query look like -   are you selecting a full hierarchy ? ------- No
are you filtering your dataset at runtime using input variables / parameters? -------Yes. We have used formula variable at BW level and I have hard cored its value at BO side in different queries (same report) by giving different value for each query.
Is your APS / DSL_Bridge properly up-sized on the BIPlatform? what's the Xmx value in the command line? --------- Xmx4G
Does your administrator monitor anything unusual in the BW SM66/ST05/ST22 ? -------- Everything is working fine in BW system side.
How high mem usage seen task manager / PIDs on the BIPlatform? -------- Everything is normal (Total RAM Size 24 GB)

HANA Hierarchy consumption in BOBI

Similar Messages

Maybe you are looking for