Presales Asset of the Week: Predictive Analytics with SAP HANA

To our SAP Partners: watch this demo http://bit.ly/UhJOok showcasing how business analysts and data scientists can take advantage of predictive analytics in big data scenarios. It also highlights how developers can embed the predictive analytics capabilities of SAP HANA into custom business solutions.
Predictive Analytics with SAP HANA allows customers and partners to:
- Make smarter & faster decisions with real-time insights
- Accelerate key business processes with rapid analysis and reporting
- Invent new business models and processes by leveraging innovative solutions

To get enabled on SAP HANA, please access the SAP HANA Resource Library in the SAP PartnerEdge Portal (need S-User).

Similar Messages

  • Error message is 'The Request Error : 400' with SAP Download Manager

    Hello,
    The authorization object SWDOWNLOAD (download software) is assigned to the My user ID.
    But I could not download below that file.
    SAP_ABA 710 (4~8)
    SAP_BASIS 710 (4~8)
    PI_BASIS 2006_1_710 (4~8)
    SAP_BW 710 (4~8)
    Error message is 'The Request Error : 400' with SAP Download Manager
    I logged on to SAP Service Marketplace, software download area /swdc.
    I have created objects in the download basket and have received approvals (->Maintenance-Optimizer) where required.
    I start the SAP Download Manager and the objects from the download basket are visible in the object list of the program window.
    After I choose "Objects for Download", the system starts the download.
    In the info-line (in the lower part of the window), the system displays the message 'Processing object...' and then 'The request failed: 400'.

    Hello,
    In these cases the following things should be checked:
    1.- Please be sure that you are using the latest Donwload Manager version
    2.- S-User and password should be active
    3.- Specify the proxy. Please refer to SAP Note 155954
    4.- It might be that you are not licensed for the product you want to download.
    If the checkings above are correct and the problem is still alive, I would recommend you to open an SAP customer message under component XX-SER-SAPSMP-SDM providing the following information:
    1.- The exactly software product name and package or stack number you try to download.
    2.- Attach to the message the results of the trace file generated as per note 574885:
    574885 - Download Manager: Generate trace file for analysis
    I hope this helps you.
    Regards,
    Blanca

  • An issue using the COM components supplied with SAP GUI 6.2 or 6.4

    We are having an issue using the COM components supplied with SAP GUI 6.2 or 6.4.  We used to have SAP 4.6c and now we have 5.0.  When we were on 4.6c, we used these COM components to logon and execute RFC calls and we had much success.  Now that we are on 5.0, we can’t seem to instance any SAP functions that have something to do with SAP Workflow.  We have experienced this problem when using VB6 or .NET, but our existing code that always worked is in VB 6.0.
    SAP Components used:
    o     SAP Logon Control
    o     SAP Function Control
    o     Librfc32.dll
    o     Other supporting C DLLs and/or COM object supplied with the SAP GUI installation.
    For example, if we want to call the RFC ARCHIV_CONNECTION_INSERT, this code fails in VB6 when the “Set objworkflow = objFuncCtrl.Add(strFunction)” line of code executes.  Instead of returning an instance of the object ARCHIV_CONNECTION_INSERT function, no object is created.  In 6.2, SAP raises no errors, but the object we are trying to create is still “Nothing”.  If we use 6.4, SAP raises an error “SAP data type not supported” via a message box and then the object is still = Nothing.  Interestingly enough, the 6.2 GUI COM controls don’t display the error dialog.  The message box that is shown comes from the SAP Function COM Object "SAP.Functions" (wdtfuncs.ocx).
    Now, what is interesting is if we use the same code to call a standard function or custom function that doesn’t have anything to do with SAP Workflow, then the code works fine.  Again, all of our code used to work just fine on an SAP 4.6 system.
    Here is the code that fails:
        'SAP Logon control - object for creating connections to an SAP system
        Dim objSAPLogonCtrl As Object
        'SAP connection object
        Dim objConnection As Object
        'Object that will represent the SAP function called
        Dim objSAP As Object
        'SAP function control object - object factory for creating other SAP function objects
        Dim objFuncCtrl As Object
        'Create instance of an SAP logon conrol
        Set objSAPLogonCtrl = CreateObject("SAP.Logoncontrol.1")
        'Create a connection object
        Set objConnection = objSAPLogonCtrl.NewConnection
        'Define connecion parameters
        objConnection.ApplicationServer = "sapvm"
        objConnection.SystemNumber = "00"
        objConnection.Client = "800"
        objConnection.User = "iissap"
        objConnection.Password = "tstadm"
        objConnection.Language = "E"
        objConnection.TraceLevel = 10
        'call the logon method of the connection object
        If objConnection.Logon(0, True) = False Then
            MsgBox Error
            Exit Sub
        End If
        'Create an instance of the SAP Function control object
        Set objFuncCtrl = CreateObject("SAP.Functions")
        'Set the function control connection object
        Set objFuncCtrl.Connection = objConnection
        'Function name to be generated and called
        Dim strFunction As String
        strFunction = <b>"ARCHIV_PROCESS_RFCINPUT"</b>
        'Create an instance of the function defined in strFunction
        Set objworkflow = objFuncCtrl.Add(strFunction)
        If objworkflow Is Nothing Then
            MsgBox "Could not create object " & strFunction
        Else
            MsgBox strFunction & " object created."
        End If
    If anyone has seen anything like this or has any ideas, please help!
    Mike and Hameed
    <b></b>

    Hi,
    documentation on the Scripting API is available at ftp://ftp.sap.com/pub/sapgui/win/640/scripting/docs/
    This API is a replacement of the existing, obsolete COM interfaces.
    Best regards,
    Christian

  • Which is the MYSQL version compatible with SAP PI 7.0

    Dear friends,
    can any body tell me which is the MYSQL version compatible with SAP PI 7.0,  i m getting the below error , some body told me, may be the MYSQL version is not compatible with PI 7.0
    Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Error when attempting to get processing resources: com.sap.aii.af.service.util.concurrent.ResourcePoolException: Unable to create new pooled resource: DriverManagerException: Cannot establish connection to URL 'jdbc:mysql://192.168.51.50:3306/stagingdb': SAPClassNotFoundException: com.mysql.jdbc.Driver
    rgds
    mojib

    Hi
    if the interface was running fine and suddenly stop working ...and as per the error log u have pasted here ....99% chances are due to connection problem ...check whether TCP/IP connection for port 1433 is working finr or not ,,....do Xi system is able to make the telnet from SQL server or not...may be any firewall get enable ..........
    just check with this blog also .....same thing happensa with me once also fora client .....
    (/people/charu.agarwal/blog/2009/07/02/problems-faced-while-connecting-to-sql-server-using-jdbc-adapter-in-pi)
    Regards
    Abhishek

  • Understanding of the table level information from SAP HANA Studio

    Hello Gurus,
    Need some clarification from following information provided by SAP HANA Studio.
    I have a table REGIONS and the contents are as follows:
    REGION_ID REGION_NAME
    11      Europe
    12      Americas
    13      Asia
    44      Middle East and Africa
    15      Australia
    6      Africa
    The Runtime Information about the table is as follows:
    Image# 1
    Image# 2
    Image# 3
    Total size in KB show in Image#2 and 3 are not matching. Why?
    Total size in KB show in Image#2 and Total Memory Consumption are not matching. Why?
    The values of Memory consumption in Main Storage and Delta Storage are not matching in Image# 1 and Image# 2. Why?
    Estimated Maximum Memory Consumption (Image# 1) and Estimated Maximum Size (Image# 2) are matching.
    Why the Loaded column Image# 2 is showing the value ‘PARTIALLY’. The table has just 6 rows and still partially loaded? Why?
    What is the significance of column Loaded in Image# 2 and 3 ?
    Thanks,
    Shirish.

    Have a look on this
    Playing with SAP HANA
    That presentation should help you to answer the questions yourself
    Regards,
    Krishna Tangudu

  • Gain a competitive edge with SAP HANA certification

    Please see the following blog:
    http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/27492
    Regards,
    Marc
    SAP Customer Solution Adoption (CSA)
    Edited by: Marc Bernard on Nov 29, 2011 11:59 AM

    Hey Vitaly,
    1) It's a private training course provided with SAP HANA access. Also, the trainer is supposedly the first person to be certified in HANA in Southeast Asia (he currently works in Singapore). The link is below:
    http://www.eknazar.com/houston/ekClassifieds/product_desc.php?id=422617&al=1
    I don't think they are affiliated with SAP, but I should ask. The reason I preferred this training is it was 5 day training with 1 month access to SAP HANA, and little cheaper cost. The training SAP provided was only 2 day class - felt it would be too overwhelming (and I don't think they give HANA access besides maybe 2 days)
    2) Money is gone? So $1,300 down the drain if you fail? Jeez. Is there a way to just pay for taking the test rather than paying for the training also?

  • DBLINK truncation with SAP HANA db

    Hi - I have Oracle 11g installed in my Windows laptop and dblink connected to SAP's HANA database via ODBC using the HANA odbc driver. My NVARCHAR data in HANA is being truncated in half. I am working thru sqlplus. Same result in SQL developer client tool. The VARCHAR data is ok. I created three Oracle instances with the only difference being the NLS_CHARACTERSET & NLS_NCHAR_CHARACTERSET values. I have three SIDS: orcl, orulu, and orclutf8. All with the same result. My gateway settings for each are all the same. I started testing with SID orcl and once I found that out I decided to create orclu and orclutf8. In our Unix boxes, we have orcl and orclu settings and those are behaving the same (we use unixodbc.org as the mgr).
    I provided orclutf8 gateway .ora file and the orclut8 system info below.
    Symptoms/Info:
    The character set of HANA db is AL32UTF8.
    The HANA db table contains NVARCHAR and have Unicode values (eg: em dash, even Chinese char). NVARCHAR columns gets cut in half as shown in sqlplus (same in sql developer).
    For the half that do show up, the actual Unicode character shows up in sqlplus as either unprintable character or upside down question mark or a \u character. This is ok coz no abends therefore data gets process and let my customers deal with the non-converted data – it is ok with them.
    Since all SIDs are behaving the same way, I provided you information for orclutf8: initdwutf.ora, the system info, and the trace file. Of all things that SHOULD work, it is the one with the exact character set to HANA.
    I have two tables in HANA with the same number of columns and rows. Only difference is NVARCHAR versus VARCHAR.There are three columns with 3, 20, and 150 length.
    I took a Oracle trace when selecting from each table and compared them both. I pasted a picture at the bottom. The left side is the VARCHAR and right side NVARCHAR. You can see the HANA odbc driver report a truncation issue on line 209 but I do not see this error in sqlplus. I have a SAP incident open on this.
    Is there something in the Oracle side that can be tried? For example, in the trace compare picture, the VARCHAR trace shows that is doubled the data size for each column from 3, 20, and 150 to 6, 40, and 300. In the NVARCHAR it did not.
    SID: orcl
                    SELECT value$ FROM sys.props$ WHERE name = 'NLS_CHARACTERSET’;
                    WE8MSWIN1252
                    SELECT value$ FROM sys.props$ WHERE name = 'NLS_NCHAR_CHARACTERSET’;
                    AL16UTF16
    SID: orclu
                    SELECT value$ FROM sys.props$ WHERE name = 'NLS_CHARACTERSET’;
                    AL32UTF8
                   SELECT value$ FROM sys.props$ WHERE name = 'NLS_NCHAR_CHARACTERSET’;
                    AL16UTF16
    SID: orclutf8
                    SELECT value$ FROM sys.props$ WHERE name = 'NLS_CHARACTERSET’;
                    AL32UTF8
                   SELECT value$ FROM sys.props$ WHERE name = 'NLS_NCHAR_CHARACTERSET’;
                    UTF8
    initdw7utf.ora:
    # This is a sample agent init file that contains the HS parameters that are
    # needed for the Database Gateway for ODBC
    # HS init parameters
    #HS_FDS_CONNECT_INFO = <odbc data_source_name>
    HS_FDS_CONNECT_INFO = HANADW7
    HS_FDS_TRACE_LEVEL=DEBUG
    #HS_LANGUAGE=AL32UTF8
    HS_LANGUAGE=AMERICAN_AMERICA.AL32UTF8
    HS_FDS_REMOTE_DB_CHARSET=AL32UTF8
    # Environment variables required for the non-Oracle system
    #set <envvar>=<value>
    SELECT * FROM sys.props$:
    DICT.BASE       2
    DEFAULT_TEMP_TABLESPACE           TEMP
    DEFAULT_PERMANENT_TABLESPACE            USERS
    DEFAULT_EDITION       ORA$BASE
    Flashback Timestamp TimeZone            GMT
    TDE_MASTER_KEY_ID
    DST_UPGRADE_STATE            NONE
    DST_PRIMARY_TT_VERSION    11
    DST_SECONDARY_TT_VERSION          0
    DEFAULT_TBS_TYPE   SMALLFILE
    NLS_LANGUAGE          AMERICAN
    NLS_TERRITORY          AMERICA
    NLS_CURRENCY          $
    NLS_ISO_CURRENCY   AMERICA
    NLS_NUMERIC_CHARACTERS  .,
    NLS_CHARACTERSET  AL32UTF8
    NLS_CALENDAR          GREGORIAN
    NLS_DATE_FORMAT    DD-MON-RR
    NLS_DATE_LANGUAGE            AMERICAN
    NLS_SORT       BINARY
    NLS_TIME_FORMAT     HH.MI.SSXFF AM
    NLS_TIMESTAMP_FORMAT      DD-MON-RR HH.MI.SSXFF AM
    NLS_TIME_TZ_FORMAT            HH.MI.SSXFF AM TZR
    NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZR
    NLS_DUAL_CURRENCY            $
    NLS_COMP      BINARY
    NLS_LENGTH_SEMANTICS       BYTE
    NLS_NCHAR_CONV_EXCP       FALSE
    NLS_NCHAR_CHARACTERSET UTF8
    NLS_RDBMS_VERSION            11.2.0.1.0
    GLOBAL_DB_NAME     ORCLUTF8
    EXPORT_VIEWS_VERSION      8
    WORKLOAD_CAPTURE_MODE           
    WORKLOAD_REPLAY_MODE  
    NO_USERID_VERIFIER_SALT   57505D68AFECC3BCECE484A1C42CC8CE
    DBTIMEZONE   00:00

    1) When I tried HS_KEEP_REMOTE_COLUMN_SIZE=LOCAL the nvarchar select statement still truncated and displayed them in sqlplus.
    For the varchar select statement, it just error'ed out in sqlplus.
    ERROR:
    ORA-28562: Heterogeneous Services data truncation error
    ORA-02063: preceding line from DEVUTF8
    no rows selected
    I commented out the HS_KEEP_REMOTE_COLUMN_SIZE=LOCAL for now.
    2) For the nvarchar select statement, I do not get an error messages via sqlplus. I get the records displayed truncated in half they should be. A native odbc error do show up in the Oracle Trace file. I think that comes from the HANA odbc driver. It is line 209 of the picture in my original thread.
    3) DESCRIBE commands output below:
    SQL> desc ESBA_DB.ZTESTSAP@DEVUTF8 - THIS IS THE NVARCHAR TABLE. The sizes match what is in HANA db.
    Name                                      Null?    Type
    MANDT                                     NOT NULL NVARCHAR2(3)
    NAME                                      NOT NULL NVARCHAR2(20)
    NAME_150                                  NOT NULL NVARCHAR2(150)
    SQL> desc PTAN.ZTESTSAP_VC@DEVUTF8 - THIS IS THE VARCHAR TABLE.The sizes do not match what is in HANA db.
    Name                                      Null?    Type
    MANDT                                              VARCHAR2(1)
    NAME                                               VARCHAR2(6)
    NAME150                                            VARCHAR2(50)
    4) Below is the gateway trace. I included from the first occurence of hgodscr and all the way to the end of it. You can see the HANA odbc driver truncation.
    Entered hgodscr, cursor id 1 at 2014/10/02-11:15:41
    Allocate hoada @ 03705518
    Entered hgopcda at 2014/10/02-11:15:41
    Column:1(M): dtype:-9 (WVARCHAR), prc/scl:3/0, nullbl:1, octet:3, sign:1, radix:0
    Exiting hgopcda, rc=0 at 2014/10/02-11:15:41
    Entered hgopcda at 2014/10/02-11:15:41
    Column:2(N): dtype:-9 (WVARCHAR), prc/scl:20/0, nullbl:1, octet:20, sign:1, radix:0
    Exiting hgopcda, rc=0 at 2014/10/02-11:15:41
    Entered hgopcda at 2014/10/02-11:15:41
    Column:3(N): dtype:-9 (WVARCHAR), prc/scl:150/0, nullbl:1, octet:150, sign:1, radix:0
    Exiting hgopcda, rc=0 at 2014/10/02-11:15:41
    hgodscr, line 910: Printing hoada @ 03705518
    MAX:3, ACTUAL:3, BRC:100, WHT=5 (SELECT_LIST)
    hoadaMOD bit-values found (0x40:TREAT_AS_NCHAR)
    DTY         NULL-OK  LEN  MAXBUFLEN   PR/SC  CST IND MOD NAME
    12 VARCHAR Y          3          3 128/  3 1000   0  40 MANDT
    12 VARCHAR Y         20         20 128/ 20 1000   0  40 NAME
    12 VARCHAR Y        150        150 128/150 1000   0  40 NAME_150
    Exiting hgodscr, rc=0 at 2014/10/02-11:15:41
    Entered hgoftch, cursor id 1 at 2014/10/02-11:15:41
    hgoftch, line 130: Printing hoada @ 03705518
    MAX:3, ACTUAL:3, BRC:100, WHT=5 (SELECT_LIST)
    hoadaMOD bit-values found (0x40:TREAT_AS_NCHAR)
    DTY         NULL-OK  LEN  MAXBUFLEN   PR/SC  CST IND MOD NAME
    12 VARCHAR Y          3          3 128/  3 1000   0  40 MANDT
    12 VARCHAR Y         20         20 128/ 20 1000   0  40 NAME
    12 VARCHAR Y        150        150 128/150 1000   0  40 NAME_150
    Performing delayed open.
    SQLBindCol: column 1, cdatatype: -8, bflsz: 6
    SQLBindCol: column 2, cdatatype: -8, bflsz: 22
    SQLBindCol: column 3, cdatatype: -8, bflsz: 152
    Entered hgopoer at 2014/10/02-11:15:41
    hgopoer, line 233: got native error 0 and sqlstate 01004; message follows...
    [SAP AG][LIBODBCHDB32 DLL] Data truncated {01004}[SAP AG][LIBODBCHDB32 DLL] Data truncated {01004}[SAP AG][LIBODBCHDB32 DLL] Data truncated {01004}[SAP AG][LIBODBCHDB32 DLL] Data truncated {01004}[SAP AG][LIBODBCHDB32 DLL] Data truncated {01004}
    Exiting hgopoer, rc=0 at 2014/10/02-11:15:41
    hgoftch, line 740: calling SQLFetch got sqlstate 01004
    SQLFetch: row: 1, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 1, column 1, bflsz: 6,  bflar: 6, (bfl: 3, mbl: 3)
    SQLFetch: row: 1, column 2, bflsz: 22, bflar: 6
    SQLFetch: row: 1, column 2, bflsz: 22,  bflar: 6, (bfl: 20, mbl: 20)
    SQLFetch: row: 1, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 1, column 3, bflsz: 152,  bflar: 0, (bfl: 150, mbl: 150)
    SQLFetch: row: 2, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 2, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 2, column 2, bflsz: 22, bflar: 12
    SQLFetch: row: 2, column 2, bflsz: 22,  bflar: 12, (bfl: 0, mbl: 20)
    SQLFetch: row: 2, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 2, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 3, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 3, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 3, column 2, bflsz: 22, bflar: 8
    SQLFetch: row: 3, column 2, bflsz: 22,  bflar: 8, (bfl: 0, mbl: 20)
    SQLFetch: row: 3, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 3, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 4, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 4, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 4, column 2, bflsz: 22, bflar: 6
    SQLFetch: row: 4, column 2, bflsz: 22,  bflar: 6, (bfl: 0, mbl: 20)
    SQLFetch: row: 4, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 4, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 5, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 5, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 5, column 2, bflsz: 22, bflar: 12
    SQLFetch: row: 5, column 2, bflsz: 22,  bflar: 12, (bfl: 0, mbl: 20)
    SQLFetch: row: 5, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 5, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 6, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 6, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 6, column 2, bflsz: 22, bflar: 8
    SQLFetch: row: 6, column 2, bflsz: 22,  bflar: 8, (bfl: 0, mbl: 20)
    SQLFetch: row: 6, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 6, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 7, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 7, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 7, column 2, bflsz: 22, bflar: 6
    SQLFetch: row: 7, column 2, bflsz: 22,  bflar: 6, (bfl: 0, mbl: 20)
    SQLFetch: row: 7, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 7, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 8, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 8, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 8, column 2, bflsz: 22, bflar: 12
    SQLFetch: row: 8, column 2, bflsz: 22,  bflar: 12, (bfl: 0, mbl: 20)
    SQLFetch: row: 8, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 8, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 9, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 9, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 9, column 2, bflsz: 22, bflar: 8
    SQLFetch: row: 9, column 2, bflsz: 22,  bflar: 8, (bfl: 0, mbl: 20)
    SQLFetch: row: 9, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 9, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 10, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 10, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 10, column 2, bflsz: 22, bflar: 6
    SQLFetch: row: 10, column 2, bflsz: 22,  bflar: 6, (bfl: 0, mbl: 20)
    SQLFetch: row: 10, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 10, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 11, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 11, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 11, column 2, bflsz: 22, bflar: 12
    SQLFetch: row: 11, column 2, bflsz: 22,  bflar: 12, (bfl: 0, mbl: 20)
    SQLFetch: row: 11, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 11, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 12, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 12, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 12, column 2, bflsz: 22, bflar: 8
    SQLFetch: row: 12, column 2, bflsz: 22,  bflar: 8, (bfl: 0, mbl: 20)
    SQLFetch: row: 12, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 12, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 13, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 13, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 13, column 2, bflsz: 22, bflar: 6
    SQLFetch: row: 13, column 2, bflsz: 22,  bflar: 6, (bfl: 0, mbl: 20)
    SQLFetch: row: 13, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 13, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 14, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 14, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 14, column 2, bflsz: 22, bflar: 12
    SQLFetch: row: 14, column 2, bflsz: 22,  bflar: 12, (bfl: 0, mbl: 20)
    SQLFetch: row: 14, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 14, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 15, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 15, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 15, column 2, bflsz: 22, bflar: 40
    SQLFetch: row: 15, column 2, bflsz: 22,  bflar: 40, (bfl: 0, mbl: 20)
    SQLFetch: row: 15, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 15, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 16, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 16, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 16, column 2, bflsz: 22, bflar: 8
    SQLFetch: row: 16, column 2, bflsz: 22,  bflar: 8, (bfl: 0, mbl: 20)
    SQLFetch: row: 16, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 16, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 17, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 17, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 17, column 2, bflsz: 22, bflar: 32
    SQLFetch: row: 17, column 2, bflsz: 22,  bflar: 32, (bfl: 0, mbl: 20)
    SQLFetch: row: 17, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 17, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 18, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 18, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 18, column 2, bflsz: 22, bflar: 40
    SQLFetch: row: 18, column 2, bflsz: 22,  bflar: 40, (bfl: 0, mbl: 20)
    SQLFetch: row: 18, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 18, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 19, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 19, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 19, column 2, bflsz: 22, bflar: 12
    SQLFetch: row: 19, column 2, bflsz: 22,  bflar: 12, (bfl: 0, mbl: 20)
    SQLFetch: row: 19, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 19, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 20, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 20, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 20, column 2, bflsz: 22, bflar: 2
    SQLFetch: row: 20, column 2, bflsz: 22,  bflar: 2, (bfl: 0, mbl: 20)
    SQLFetch: row: 20, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 20, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 21, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 21, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 21, column 2, bflsz: 22, bflar: 2
    SQLFetch: row: 21, column 2, bflsz: 22,  bflar: 2, (bfl: 0, mbl: 20)
    SQLFetch: row: 21, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 21, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 22, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 22, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 22, column 2, bflsz: 22, bflar: 6
    SQLFetch: row: 22, column 2, bflsz: 22,  bflar: 6, (bfl: 0, mbl: 20)
    SQLFetch: row: 22, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 22, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 23, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 23, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 23, column 2, bflsz: 22, bflar: 12
    SQLFetch: row: 23, column 2, bflsz: 22,  bflar: 12, (bfl: 0, mbl: 20)
    SQLFetch: row: 23, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 23, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 24, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 24, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 24, column 2, bflsz: 22, bflar: 40
    SQLFetch: row: 24, column 2, bflsz: 22,  bflar: 40, (bfl: 0, mbl: 20)
    SQLFetch: row: 24, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 24, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 25, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 25, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 25, column 2, bflsz: 22, bflar: 8
    SQLFetch: row: 25, column 2, bflsz: 22,  bflar: 8, (bfl: 0, mbl: 20)
    SQLFetch: row: 25, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 25, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 26, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 26, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 26, column 2, bflsz: 22, bflar: 32
    SQLFetch: row: 26, column 2, bflsz: 22,  bflar: 32, (bfl: 0, mbl: 20)
    SQLFetch: row: 26, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 26, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 27, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 27, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 27, column 2, bflsz: 22, bflar: 40
    SQLFetch: row: 27, column 2, bflsz: 22,  bflar: 40, (bfl: 0, mbl: 20)
    SQLFetch: row: 27, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 27, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 28, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 28, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 28, column 2, bflsz: 22, bflar: 12
    SQLFetch: row: 28, column 2, bflsz: 22,  bflar: 12, (bfl: 0, mbl: 20)
    SQLFetch: row: 28, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 28, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 29, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 29, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 29, column 2, bflsz: 22, bflar: 2
    SQLFetch: row: 29, column 2, bflsz: 22,  bflar: 2, (bfl: 0, mbl: 20)
    SQLFetch: row: 29, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 29, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 30, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 30, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 30, column 2, bflsz: 22, bflar: 2
    SQLFetch: row: 30, column 2, bflsz: 22,  bflar: 2, (bfl: 0, mbl: 20)
    SQLFetch: row: 30, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 30, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 31, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 31, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 31, column 2, bflsz: 22, bflar: 6
    SQLFetch: row: 31, column 2, bflsz: 22,  bflar: 6, (bfl: 0, mbl: 20)
    SQLFetch: row: 31, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 31, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 32, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 32, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 32, column 2, bflsz: 22, bflar: 12
    SQLFetch: row: 32, column 2, bflsz: 22,  bflar: 12, (bfl: 0, mbl: 20)
    SQLFetch: row: 32, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 32, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 33, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 33, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 33, column 2, bflsz: 22, bflar: 8
    SQLFetch: row: 33, column 2, bflsz: 22,  bflar: 8, (bfl: 0, mbl: 20)
    SQLFetch: row: 33, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 33, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 34, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 34, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 34, column 2, bflsz: 22, bflar: 6
    SQLFetch: row: 34, column 2, bflsz: 22,  bflar: 6, (bfl: 0, mbl: 20)
    SQLFetch: row: 34, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 34, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 35, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 35, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 35, column 2, bflsz: 22, bflar: 12
    SQLFetch: row: 35, column 2, bflsz: 22,  bflar: 12, (bfl: 0, mbl: 20)
    SQLFetch: row: 35, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 35, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 36, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 36, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 36, column 2, bflsz: 22, bflar: 8
    SQLFetch: row: 36, column 2, bflsz: 22,  bflar: 8, (bfl: 0, mbl: 20)
    SQLFetch: row: 36, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 36, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 37, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 37, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 37, column 2, bflsz: 22, bflar: 6
    SQLFetch: row: 37, column 2, bflsz: 22,  bflar: 6, (bfl: 0, mbl: 20)
    SQLFetch: row: 37, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 37, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 38, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 38, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 38, column 2, bflsz: 22, bflar: 12
    SQLFetch: row: 38, column 2, bflsz: 22,  bflar: 12, (bfl: 0, mbl: 20)
    SQLFetch: row: 38, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 38, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 39, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 39, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 39, column 2, bflsz: 22, bflar: 8
    SQLFetch: row: 39, column 2, bflsz: 22,  bflar: 8, (bfl: 0, mbl: 20)
    SQLFetch: row: 39, column 3, bflsz: 152, bflar: 0
    SQLFetch: row: 39, column 3, bflsz: 152,  bflar: 0, (bfl: 0, mbl: 150)
    SQLFetch: row: 40, column 1, bflsz: 6, bflar: 6
    SQLFetch: row: 40, column 1, bflsz: 6,  bflar: 6, (bfl: 0, mbl: 3)
    SQLFetch: row: 40, column 2, bflsz: 22, bflar: 38
    SQLFetch: row: 40, column 2, bflsz: 22,  bflar: 38, (bfl: 0, mbl: 20)
    SQLFetch: row: 40, column 3, bflsz: 152, bflar: 298
    SQLFetch: row: 40, column 3, bflsz: 152,  bflar: 298, (bfl: 0, mbl: 150)
    40 rows fetched
    Exiting hgoftch, rc=0 at 2014/10/02-11:15:42 with error ptr FILE:hgoftch.c LINE:740 ID:Fetch resultset data
    Entered hgoftch, cursor id 1 at 2014/10/02-11:15:42
    hgoftch, line 130: Printing hoada @ 03705518
    MAX:3, ACTUAL:3, BRC:40, WHT=5 (SELECT_LIST)
    hoadaMOD bit-values found (0x40:TREAT_AS_NCHAR)
    DTY         NULL-OK  LEN  MAXBUFLEN   PR/SC  CST IND MOD NAME
    12 VARCHAR Y          4          3 128/  3 1000   0  40 MANDT
    12 VARCHAR Y          6         20 128/ 20 1000   0  40 NAME
    12 VARCHAR Y          0        150 128/150 1000   0  40 NAME_150
    0 rows fetched
    Exiting hgoftch, rc=1403 at 2014/10/02-11:15:42
    Entered hgoclse, cursor id 1 at 2014/10/02-11:15:46
    Exiting hgoclse, rc=0 at 2014/10/02-11:15:46
    Entered hgodafr, cursor id 1 at 2014/10/02-11:15:46
    Free hoada @ 03705518
    Exiting hgodafr, rc=0 at 2014/10/02-11:15:46
    Entered hgocomm at 2014/10/02-11:15:46
    keepinfo:0, tflag:1
       00: 4F52434C 55544638 2E376265 35343664  [ORCLUTF8.7be546d]
       10: 392E312E 32362E36 3630               [9.1.26.660]
                     tbid (len 23) is ...
       00: 4F52434C 55544638 5B312E32 362E3636  [ORCLUTF8[1.26.66]
       10: 305D5B31 2E345D                      [0][1.4]]
    cmt(0):
    Entered hgocpctx at 2014/10/02-11:15:46
    Exiting hgocpctx, rc=0 at 2014/10/02-11:15:46
    Exiting hgocomm, rc=0 at 2014/10/02-11:15:46
    Entered hgolgof at 2014/10/02-11:15:46
    tflag:1
    Exiting hgolgof, rc=0 at 2014/10/02-11:15:46
    Entered hgoexit at 2014/10/02-11:15:46
    Exiting hgoexit, rc=0

  • License problems with SAP-HANA developer at CloudShare

    Hello everyone,
    after connecting to the HANA Instance with HANA Studio (local and in the CloudShare instance) and adding the new System HDB   the System is marked with a red 'X' displayinng the message "System locked; license invalid or expired".
    Under Properties->License I have seen License Type invalid, Dates undefined.
    After that I requested with the Hardware key a new license as described in http://scn.sap.com/docs/DOC-31036 I first deleted the old key and installed the new key. I got the pop-up message "License key has been installed successffully", but nothing changed. I restarted the Service and Studio and tried again. Again nothing changed.
    What more can I do ??
    Thanks, Gerd

    Hello everyone,
    after connecting to the HANA Instance with HANA Studio (local and in the CloudShare instance) and adding the new System HDB   the System is marked with a red 'X' displayinng the message "System locked; license invalid or expired".
    Under Properties->License I have seen License Type invalid, Dates undefined.
    After that I requested with the Hardware key a new license as described in http://scn.sap.com/docs/DOC-31036 I first deleted the old key and installed the new key. I got the pop-up message "License key has been installed successffully", but nothing changed. I restarted the Service and Studio and tried again. Again nothing changed.
    What more can I do ??
    Thanks, Gerd

  • How do I get access to Mobile documents admin console login with SAP HANA Cloud cockpit?

    Hi All,
    I am trying to launch SAP Mobile Documents from my trail version of SAP HANA Cloud.
    The Help link which I had followed  via link:
    https://help.hana.ondemand.com/help/frameset.htm?dc618538d97610148155d97dcd123c24.html#concept_0B49F10346C94249845EC16364FFF66D_76
    In SAP Cloud HANA Cockpit Using the link available in Authorization>Authorization Management
    I had created an user assigned to a Group, and Group has been assigned to a  Role ODP-OPERATOR,
    Next step, when I am trying to assign a token, I could not able find a token. How to get a token from here?
    My intention of creating user, group, role and token is for getting access to Mobile documents admin console.
    However I have also tried to access the mobile documents admin console via link
    https://smd-p1886950994trial.hana.ondemand.com/mcm/admin
    When I browse the above link, It shows HTTP 503 the requested service is not currently available.
    I am not sure, How to get access Mobile documents Admin page from here
    Could someone clarify on this please?
    Regards,
    Saravanan.R

    Hi,
    I have managed find an answer from this link SAP Mobile Documents on SAP HANA Cloud saying, SAP Mobile documents trial is not available in SAP HANA Cloud cockpit.
    Regards,
    Saravanan.R

  • Connect SAP HANA Studio with SAP HANA One Instance Reg 70

    Hello,
    i have already create an instance and set all passworts in Management One Console.
    If i want to add a new system in Hana studio a got an error message: "Database connection is not available"
    SAPControl request failed. Cannot retrieve JDBC connection for: ...
    com.sap.ndb.studio.jdbc.JDBCConnectionStatus: Database connection is not available. See error log for more details.
      at com.sap.ndb.studio.jdbc.JDBCPlugin.createConnection(JDBCPlugin.java:295)
      at com.sap.ndb.studio.navigator.operations.SAPSystemObjectUpdate.executeTryJDBC(SAPSystemObjectUpdate.java:238)
      at com.sap.ndb.studio.navigator.operations.SAPSystemObjectUpdate.execute(SAPSystemObjectUpdate.java:84)
      at com.sap.ndb.studio.navigator.operations.UpdateSAPSystemOperation.execute(UpdateSAPSystemOperation.java:70)
      at com.sap.ndb.studio.datamodel.controler.DataModelOperation.execute(DataModelOperation.java:67)
      at com.sap.ndb.studio.datamodel.controler.DataModelOperationQueue$DataModelOperationThread.run(DataModelOperationQueue.java:99)
    Caused by: com.sap.db.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: Cannot connect to jdbc:sap://xxx.eu-west-1.compute.amazonaws.com:30015 [Cannot connect to host exxx4.eu-west-1.compute.amazonaws.com:30015 [Connection timed out: connect], -813.].
      at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.createException(SQLExceptionSapDB.java:219)
      at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.createException(SQLExceptionSapDB.java:203)
      at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.generateDatabaseException(SQLExceptionSapDB.java:186)
      at com.sap.db.jdbc.Driver.connect(Driver.java:238)
      at com.sap.ndb.studio.jdbc.JDBCPlugin$3.run(JDBCPlugin.java:590)
    I must add, that i test it in the firm's intranet. So we have diverse firewalls. What firewall settings has our IT department change, for enabling the database connection?
    Hope you can help me.
    CT

    Not related to UI Development Toolkit for HTML Developer Center.  Moved to SAP HANA Developer Center community.
    Regards, Mike (Moderator)

  • Cannot use SAP HANA Studio with SAP HANA One Instance

    Hello together,
    i try to make some tests in the SAP HANA environment. But i got the following error message each time:
    An internal error occurred during: "Updating system 'HDB' ...".
    java.lang.NullPointerException
      at com.sap.ndb.studio.datamodel.manager.SAPSystemState.isThereAtLeastOneIndexserverProcessWithStateColor(SAPSystemState.java:44)
      at com.sap.ndb.studio.navigator.operations.SAPSystemObjectUpdate.execute(SAPSystemObjectUpdate.java:76)
      at com.sap.ndb.studio.navigator.operations.UpdateSAPSystemOperation.execute(UpdateSAPSystemOperation.java:70)
      at com.sap.ndb.studio.datamodel.controler.DataModelOperationJob.run(DataModelOperationJob.java:70)
      at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
    I often read about different SAP HANA One and SAP HANA Studio versions.
    Following information about the versions:
    Studio: Version: 1.0.52
    Hana One Instance 52.1
    What could be the reason for getting this error message? I hope you can help me.
    Thanks in advance.
    CT

    Hi Nicky,
    As per my knowledge, there is no separate licensing required for HANA studio. License for HANA d/b or Enterprise HANA license is sufficient.
    Installation of HANA studio will not ask for any licenses.
    Regards,
    Suma

  • Wk 8 - Video of the week: Improving speed with a B...

    Hi Everyone
    This weeks video shows you how to fit a BT Accelerator.  Extension wiring around your home can affect your broadband speed. Fitting a BT Accelerator (which you may also have heard called an iPlate) can really help improve it.
    To view our other videos, visit our YouTube Channel.
    Thx
    Kerry
    Retired BTCare Community Manager - StephanieG and SeanD are your new Community Managers
    If you like a post, or want to say thanks for a helpful answer, please click on the Ratings star on the left-hand side of the post.
    If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.

    I came across a facility to check on reported faultsb at https://www.bt.com/consumerFaultTracking/secure/faults/tracking.do?pageId=5&reload=true
    so I tried it out to find only the last fault (Sept 14th) - it took ages to load BT's speedchecket and eventually after running it the speed was 0.62mb - so it had obviously speeded up by then. last week on one occasion it was running at 0.22mbits and earlier that day I had 0.0mbits - however the fact it gave me a result at all suggests it was more than that (perhaps the software was "too ashamed" to say what it really was!). If so the software is more intelligent tan most of the people at the call centre.
    The thing is since switching to BT I get around 0.7-0.8mb but when I complain it sometimes goes up to 1 or 1.1mb but within 24 hours it drops to 0.8 and after another 24 hours bottoms out at 0.6-0.7 once more. On several occasions BT has sent out engineers, and it seems the "fault"  is around 700m of cable - that is, 700m down the road there is a 4mbits service but at my roadside connection point the speed is around 1mbit (on a good day, just after BT resets the kit at the exchange). I have madee a dozen calls this year - but only the last one (2 weeks ago) is shown on the tracking service - and that was closed a week ago - there are no details it just saus "closed").
    All BT did wes reset the exchange equipment on the day I called - as the speed went up to 1m as usual and as I predicted it was down to 0.6 again 2 days later. BT recons that they are providing me with 1mb speed and that is all they are obliged to do. but that is like a Reliant Robin dealer saying he can prove the car will run at 50mph and goes to the top of a gradient turns the car around, gets the needle up to 51mph going down the hill and then says - see it will do more than 50. Rubbish service is rubbish service.
    R

  • Find the idoc segment link with Sap Table

    Dear Abaers,
    I am new to Idoc. i have one Idoc (Orders01) for creating sales order.
    I had seen the t-codes WE 30 and WE 60 to know the field description.
    The fielddescription shows names like name1 name2 ort01 etc.
    i want to know what are the db tables involved for that particular idoc segment.
    Thanks in Advance,
    Arati

    Hi Arati,
    to get the description name:
    WE30 transaction and check the segments name available.
    With the segment name, go to WE31 and check the fields used and column 'Data element'.
    Double-click in data element (or inform in se11), you have the description value of the field.
    About the tables involved:
    Click in 'Where use list' os this data element.

  • Powershell: using the WMI or CIM with SAP/Oracle

    This post may seem familiar but we all know SAP is a middleware for a enterprise and it's database. 
    Does this application have any way to interface with powershell possibly through get-wmiObjects or some similar command that can interface faster than logging in to SAP's slow and cumbersome interface?

    This is available:
    https://social.technet.microsoft.com/Forums/en-US/9e85fbef-3ecc-46dd-b0a3-d59e2742c262/announcing-general-availability-of-powershell-connector-and-release-candidate-of-generic-sql-and-sap?forum=ilm2
    SAP Support forums for PowerShell:
    http://scn.sap.com/community/windows
    ¯\_(ツ)_/¯

  • Is using Sybase Rep Server with SAP HANA a possibility?

    We have a customer has system that they are already using Sybase Replication Server.  They are asking to add HANA and BusinessObjects BI Platform as a sidecar, to there system and remove the Java applications they are using for reporting.  They are wondering if they can use Sybase Rep server to move the data into Hana instead of SLT.

    If you have a SAP Business Suite system then SLT is the recommended approach since carries  out a application level replication of sorts. However, for non SAP Business Suite systems you do have the option to use Sybase Replication Server for HANA. Ask your customer to speak to their SAP Account Manager and she/he will be able to advice them on the option.
    Have a look at the link below for pointers:Replicating data to HANA using SAP Sybase Replication Server.

Maybe you are looking for

  • I downloaded photoshops 30 day trial but every time i open it it just says adobe photoshop cc 2014 has stopped working

    but it only gives me a option to close the program if you could help me to get this working that would be very helpful.

  • Report skips first entry in resultSet

    I have an application with four different reports that can work with the same resultset.  Three of them are fine, but for some reason the fourth always skips the first record returned by the resultset. The reports have 2 columns, and are formatted to

  • Insert Pages in VB Script

    Hi I need a coding for insert a page in a document in VB script. Is this possible. For adding pages i will use the above code. myInDesign.Documents.Item(1).Pages.Add But i want to insert a page in between the document. Sajeev

  • Pre-populate CS4 installer serial number

    Ive used the Adobe Create Suite 4 Deployment Toolkit to create a silent installer for Photoshop. While this will be useful for unattended installations, I am also looking for a way to control a manual installation, filling in the serial number for th

  • How to Achieve this Typical Requirement

    Hi All, I have a requirement in the following way.is it Possible to achieve? lets take user with user-id(SSO environment) <b>ABC</b> ,maintained in MS AD under domain name say "<b>SAP.com</b>" We are going to migrate this domain into another domain s