SAP DBTech JDBC: [258]: insufficient privilege: Not authorized - SAP HANA

Dear All,
We are getting the below error when we tried to call procedure ART_PROC using the SYSTEM user in SAP HANA Studio,
Could not execute 'call "TESTECC"."ART_PROC"'
SAP DBTech JDBC: [258]: insufficient privilege: Not authorized
Kindly provide your suggestions on the same.
Thanks
Arun R

Hello Arun,
Firstly it is **not** recommended to use SYSTEM for anything other than management tasks.
My Assumptions
* the procedure ART_PROC was not created by the SYSTEM user
Solution : you need to give EXECUTE privileges on the procedure to SYSTEM
How: Only the user who created the procedure or who has been give grant privilege can give the EXECUTE privilege. SYSTEM cannot give itself this privilege
For the Grant command check out sec 1.8.6.17 of the http://help.sap.com/hana/SAP_HANA_SQL_Script_Reference_en.pdf
OR
in the HANA Studio
in the System tab expand the system with the log in user as the owner/grantor of the privilege
here you will see a node called Security.
Right-click and choose 'Find User/Role'
Type System in the search dialog that opens - double click on SYSTEM user displayed below
System user opens up - Navigate to Object Privileges tab
here using the green '+' button  search for ART_PROC and then on the right side tick the 'Execute' checkbox
click on save.
Warm regards
aadi

Similar Messages

  • SAP DBTech JDBC: [258]: insufficient privilege: Not authorized

    I am using SAP HANA Cloud Trial; I created Analytic View based on two table dimension table and fact table, I can display content from both tables, but I can not display data preview from my Analytic View, getting authorization message;SAP DBTech JDBC: [258]: insufficient privilege: Not authorized.

    Hi,
    Please post this issue under SAP HANA Cloud Platform space. The platform experts should be able to help with that.
    Regards,
    Ifat.

  • SAP HANA security issue: SAP DBTech JDBC: [258]

    Hello experts,
    I am trying SAP HANA security features by playing out with a test user (MYTESTUSER) I've previously created. This is the permissions detail I've granted to the mentioned user:
    Granted Roles:
    PUBLIC
    Object Privileges:
    _SYS_BIC : SELECT
    _SYS_REPO : EXECUTE, SELECT
    REPOSITORY_REST (SYS): EXECUTE
    MYSCHEMA : SELECT (Contains source tables for views)
    Package Privileges:
    TEST.MYTEST (Package containing my views)
    Analytic Privileges:
    AP_MYTEST : Contains all my views and a couple restrictions over an attribute.
    What do I expect?: when logging on as MYTESTUSER it should be able to deploy the different folders in SAP HANA Studio, dive into "Content" folder, and even more: reach the package TEST.MYTEST, once there by selecting "Calculation Views" folder then being able to open CV_MYTEST calc view (which was already added into AP_MYTEST shown above).
    What happens as is?: Running as MYTESTUSER I am able to reach the calc view, when opened it is able for view only (its design). When pushing over the button "Open in Data Preview Editor" it trhows me the error:
    Cannot get the data provider outline
    SAP DBTech JDBC: [258]: insufficient privilege: insufficient privilege: Not authorized at ptime/query/checker/query_check.cc:2418
    What is expected?: Running as MYTESTUSER "Open in Data Preview Editor" feature must return and show adequate data from calculated view.
    In consequence:
    What does this error ("Not authorized at ptime/query/checker/query_check.cc:2418") specifically means and how to start addressing it?
    I'm unable to determine what is crashing or in what point it doesn't work. Any clues?
    I've also realized that there's no way out to perform some kind of trace (at least in an easy-known-fashion). Could you also advice? it would be quite important to be able to detect what are specifically the missing authorizations for a performed action. (kinda SU53 in SAP)
    Any clues or advices are welcome. Thanks a lot in advance,
    Bernardo

    Hi Bernardo,
    Can you check whether _SYS_REPO has SELECT access on your schema. Open _SYS_REPO user and check whether your schema is listed under objects privileges or not. If not run the below query.
    GRANT SELECT ON SCHEMA <schema_name> TO _SYS_REPO WITH GRANT OPTION.
    if it doesn't work try to give SELECT and EXECUTE access on both _SYS_BI and _SYS_BIC to your schema and check. And also but default your should have all the privileges on your schema.
    Regards,
    Venkat N.

  • Access database view from JPA to HANA database, JDBC: [258]: insufficient privilege:

    My java application is delopyed on neo.ondemand.com and use the hana database on cloud also, we use eclipselink
    the jpa persistence configuration:
    <property name="eclipselink.target-database" value="com.sap.persistence.platform.database.HDBPlatform"/>
    here i do not specify any user or password to access the database, i think hana JDBC somehow hide the user information when java application and hana database both are on the cloud.
    for the tables created by JPA itself, access if fine.
    now i have created a view via Hana studio, though database tunnel using account  dXXXXXXsapdev
    i have an JPA entity, and i am trying to access the view from java application, it reports error:
    Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.3.2.v20111125-r10461): org.eclipse.persistence.exceptions.DatabaseException Internal Exception: com.sap.db.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: [258]: insufficient privilege:
    I do not know which database user is used by JPA to access the view, how can i grant the database rights on the view so that "native java application on cloud" can
    access the database schema (or view created though database tunnel )
    any comment is welcomed.

    Hi,
    Please post this issue under SAP HANA Cloud Platform space. The platform experts should be able to help with that.
    Regards,
    Ifat.

  • Insufficient privilege: Not authorized at ptime/query/checker/query_check.cc on hdbsequence

    Hi All,
    I am currently trying to create a table (TOPIC) and a sequence (SEQ_TOPIC_ID) in HCP, and a XSJS service on top of it to insert a entry to the table.
    In my XS project, I placed a TOPIC.hdbtable and SEQ_TOPIC_ID.hdbsequence in it. Both table and sequence are generated correctly in my trial account schema in the hana db.
    Then,in order to grant the access to the table and sequence , I also placed a file model_access.hdbrole in the project folder.
    The content looks like follow:
    role i065831trial.bubuwork.TopicCenter::model_access {
        application privilege: i065831trial.bubuwork.TopicCenter::Basic;
        sql object i065831trial.bubuwork.TopicCenter::TOPIC : SELECT,INSERT;
        sql object i065831trial.bubuwork.TopicCenter::SEQ_TOPIC_ID : SELECT, DROP;
    The issue is, when I call the XSJS service from the web url, I will facing below error:
    Error while executing query: [dberror(Connection.prepareStatement): 258 - insufficient privilege: Not authorized at ptime/query/checker/query_check.cc:2547]
    the role has been granted to my account, and I am able to insert to the table TOPIC without sequence with above role setting, but If I try to read the SEQ_TOPIC_ID, an insufficient privilege will shown up.
    My question is: Is following line correct to grant the privilege to a role for sequence ? It does not seem to work for sequence  !
    sql object i065831trial.bubuwork.TopicCenter::SEQ_TOPIC_ID : SELECT, DROP;
    Thanks very much!

    Thanks Thomas for your reply, firstly I tried to embed my sequence in the insert SQL, as the problem happened. I pulled out the sequence into a single query string, like blow:
    var select_topic_next_val = "select \"i065831trial.bubuwork.TopicCenter::SEQ_TOPIC_ID\".nextval as seqid from dummy";
    function close(closables) {
        var closable; 
        var i; 
        for (i = 0; i < closables.length; i++) { 
                  closable = closables[i]; 
                  if(closable) { 
                            closable.close(); 
    function insertTopic(xargs){
        var connection = $.db.getConnection(); 
        var statement = null;
        var resultSet = null;
        try{
            //get next sequence id
            statement = connection.prepareStatement(select_topic_next_val);
            resultSet = statement.executeQuery();
            while(resultSet.next()){
                var seqId = resultSet.getString(1);
                break;
    //        statement = connection.prepareStatement(insert_topic_sql);
    //        statement.setString(1,seqId);
    //        statement.setString(2,xargs.owner);
    //        statement.setString(3,xargs.approver);
    //        statement.setString(4,xargs.name);
    //        statement.setString(5,xargs.status);
    //        statement.setString(6,xargs.description);
    //        //statement.setTimestamp(6,xargs.lastModify);
    //        statement.setTimestamp(7,null);
    //        statement.setDate(8,xargs.begda);
    //        statement.setDate(9,xargs.endda);
    //        statement.setString(10,xargs.keyword);
    //        statement.executeUpdate();
        }finally { 
            close([resultSet, statement, connection]); 

  • AMDP syntax call to external procedure: "SQLScript message: insufficient privilege: Not authorized"

    I am getting the message "SQLScript message: insufficient privilege: Not authorized" in the syntax check in SE24 for an AMDP call to an external procedure which is not located in the default schema (located in schema MYSCHEMA).
    With DB_DBUSER & DB_DBSCHEMA I have confirmed the default user and schema to both be SAPHANAABAP.
    In HANA Studio the owner of schema MYSCHEMA has granted the following privileges:
    grant debug  on schema MYSCHEMA to SAPHANAABAP;
    grant select on schema MYSCHEMA to SAPHANAABAP;
    grant update on schema MYSCHEMA to SAPHANAABAP;
    grant delete on schema MYSCHEMA to SAPHANAABAP;
    grant insert on schema MYSCHEMA to SAPHANAABAP;
    grant attach debugger to SAPHANAABAP;
    What is the missing piece in this puzzle?

    Thanks

  • AMDP call to Procedure: "SQLScript message: insufficient privilege: Not authorized"

    Hi!
    the syntax check in SE24 reports an error in line 1 in method MY_HANA_PROCEDURE (pls see first screenshot below). If I remove the call to procedure ZTEST in line 247 the syntax check is successfull. Development in SE24 is performed by user ABAPDEVELOPER whilst the procedure ZTEST has been created by user HANADEVELOPER which has been assigned the schema (the procedure is not in schema HANADEVELOPER) to which the procedure belongs the procedure being called (ZTEST) to the 'Object Privileges' (pls see second screenshot below).
    Any ideas out there?

    Hi,
    please check if all necessary authorizations have been granted to SAP<SID> using report RS_AMDP_SICK.
    Is the procedure you want to execute in the catalog, i.e. "_SYS_BIC" schema? Otherwise, you will have to grant the necessary authorizations to SAPHANAABAP (the DB user) for the schema.
    Best,
    Jasmin

  • ObjectIsClosedException: SAP DBTech JDBC: Object is closed

    Hi everybody,
    i try to insert data via jdbc in a loop (a Thread) with a PreparedStatement.
    the first insertion is successful - but all following inserts are not because of
    ObjectIsClosedException (see jdbc-traces)
    I do not close the PrepearedStatement or the Connection.
    What is the cause of the "[T166].close()" (see trace #2) ???
    the Problem is with a call DBROC ({call INSERTEVENTENTRY(?,?,?,?,?,?,?,?,?,?,?,?,?,?)}, too!!
    Thanks for your help!
    Matthias
    (MaxDB is running on SuSE Linux 11.1)
    JDBC-Trace: #1
    ===========================
    ClassLoader: sun.misc.Launcher$AppClassLoader at 1a16869
    package com.sap.dbtech.jdbc, MaxDB JDBC Driver, SAP AG, 7.6.06 Build 002-000-008-537 (Make-Version: 7.7.06 Build 009-121-202-944) on Java 1.6.0_10
    Thread a8c488 main Timestamp: 2009-05-15 13:06:58.792
    new Connection 'jdbc:sapdb://xxxxxxxxxxEVENTDB'
    user=eventhist
    password=***
    connectiontrace=/home/ighjhgj/workspace/EventLogger/jd...
    Reject GSS Authentication - password is not empty
    com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[T141][ParseID 000002440000090154000000]
    Thread 1431340 Thread-3 Timestamp: 2009-05-15 13:07:41.02
    com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[T141][ParseID 000002440000090154000000].setTimestamp (1, 2009-05-15 12:39:12.175)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[T141][ParseID 000002440000090154000000].setShort (2, 2)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[T141][ParseID 000002440000090154000000].setShort (3, 0)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[T141][ParseID 000002440000090154000000].setShort (4, -1)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[T141][ParseID 000002440000090154000000].setString (5, Biologie 2)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[T141][ParseID 000002440000090154000000].setString (6, 01GD61)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[T141][ParseID 000002440000090154000000].setString (7, aus)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[T141][ParseID 000002440000090154000000].setString (8, Nährstoffpumpe Gaswäsche)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[T141][ParseID 000002440000090154000000].setString (9, null)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[T141][ParseID 000002440000090154000000].setString (10, null)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[T141][ParseID 000002440000090154000000].setString (11, null)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[T141][ParseID 000002440000090154000000].setString (12, null)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[T141][ParseID 000002440000090154000000].setString (13, null)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[T141][ParseID 000002440000090154000000].setString (14, null)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[T141][ParseID 000002440000090154000000].executeUpdate ()
    new RTEException: -708 Timeout
    whereAmIjava.lang.Throwable
         at com.sap.dbtech.util.Tracer.whereAmI(Tracer.java:328)
         at com.sap.dbtech.rte.comm.RTEException. 0
    com.sap.dbtech.jdbc.ConnectionSapDB at 166aa18[T142].commit ()
    com.sap.dbtech.jdbc.ConnectionSapDB at 166aa18[T142].close ()
    com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[closed][ParseID 000002450000060154000000].setTimestamp (1, 2009-05-15 13:07:35.886)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[closed][ParseID 000002450000060154000000].setShort (2, 1)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[closed][ParseID 000002450000060154000000].setShort (3, 1)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[closed][ParseID 000002450000060154000000].setShort (4, 1)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[closed][ParseID 000002450000060154000000].setString (5, Biologie 2)
    <-!
    Timestamp: 2009-05-15 13:07:41.111com.sap.dbtech.jdbc.exceptions.ObjectIsClosedException: SAP DBTech JDBC: Object is closed.
         at com.sap.dbtech.jdbc.ConnectionItem.assertOpen(ConnectionItem.java:53)
         at com.sap.dbtech.jdbc.CallableStatementSapDB.setString(CallableStatementSapDB.java:2191)
         at com.sap.dbtech.jdbc.trace.log.PreparedStatement.setString(PreparedStatement.java:704)
         at com.sap.dbtech.jdbc.trace.PreparedStatement.setString(PreparedStatement.java:336)
         at de.pkv.eventlogger.handler.EventLogEntryDAO.insertEventLogEntry(EventLogEntryDAO.java:141)
         at de.pkv.eventlogger.handler.DBhistoryOutputHandler.run(DBhistoryOutputHandler.java:50)
         at java.lang.Thread.run(Thread.java:619)
    com.sap.dbtech.jdbc.ConnectionSapDB at 166aa18.close ()
    com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[closed][ParseID 000002450000060154000000].setTimestamp (1, 2009-05-15 13:07:36.046)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[closed][ParseID 000002450000060154000000].setShort (2, 2)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[closed][ParseID 000002450000060154000000].setShort (3, 0)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[closed][ParseID 000002450000060154000000].setShort (4, -1)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[closed][ParseID 000002450000060154000000].setString (5, Biologie 2)
    <-!
    Timestamp: 2009-05-15 13:07:41.119com.sap.dbtech.jdbc.exceptions.ObjectIsClosedException: SAP DBTech JDBC: Object is closed.
         at com.sap.dbtech.jdbc.ConnectionItem.assertOpen(ConnectionItem.java:53)
         at com.sap.dbtech.jdbc.CallableStatementSapDB.setString(CallableStatementSapDB.java:2191)
         at com.sap.dbtech.jdbc.trace.log.PreparedStatement.setString(PreparedStatement.java:704)
         at com.sap.dbtech.jdbc.trace.PreparedStatement.setString(PreparedStatement.java:336)
         at de.pkv.eventlogger.handler.EventLogEntryDAO.insertEventLogEntry(EventLogEntryDAO.java:141)
         at de.pkv.eventlogger.handler.DBhistoryOutputHandler.run(DBhistoryOutputHandler.java:50)
         at java.lang.Thread.run(Thread.java:619)
    JDBC-Trace: #2
    ===========================
    ClassLoader: sun.misc.Launcher$AppClassLoader at 1a16869
    package com.sap.dbtech.jdbc, MaxDB JDBC Driver, SAP AG, 7.6.06 Build 002-000-008-537 (Make-Version: 7.7.06 Build 009-121-202-944) on Java 1.6.0_10
    Thread a8c488 main Timestamp: 2009-05-15 22:48:58.594
    new Connection 'jdbc:sapdb://xxxxxxx/EVENTDB'
    user=eventhist
    password=***
    connectiontrace=/home/mlbbl/workspace/EventLogger/jd...
    Reject GSS Authentication - password is not empty
    com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[T166][ParseID 0000026800000a0212003c00]
    Thread e45076 Thread-3 Timestamp: 2009-05-15 22:49:15.555
    com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[T166][ParseID 0000026800000a0212003c00].setTimestamp (1, 2009-05-15 22:48:26.031)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[T166][ParseID 0000026800000a0212003c00].setShort (2, 6)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[T166][ParseID 0000026800000a0212003c00].setShort (3, 0)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[T166][ParseID 0000026800000a0212003c00].setShort (4, -1)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[T166][ParseID 0000026800000a0212003c00].setString (5, KM2 Konstt)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[T166][ParseID 0000026800000a0212003c00].setString (6, null)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[T166][ParseID 0000026800000a0212003c00].setString (7, null)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[T166][ParseID 0000026800000a0212003c00].setString (8, null)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[T166][ParseID 0000026800000a0212003c00].setString (9, null)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[T166][ParseID 0000026800000a0212003c00].setString (10, KM2)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[T166][ParseID 0000026800000a0212003c00].setString (11, DCT1_XDC8:0)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[T166][ParseID 0000026800000a0212003c00].setString (12, S24VD20.ACK)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[T166][ParseID 0000026800000a0212003c00].setString (13, null)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[T166][ParseID 0000026800000a0212003c00].setString (14, null)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[T166][ParseID 0000026800000a0212003c00].execute ()
    => false
    com.sap.dbtech.jdbc.ConnectionSapDB at 166aa18[T166].close ()
    com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[closed][ParseID 0000026800000a0212003c00].setTimestamp (1, 2009-05-15 22:48:26.021)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[closed][ParseID 0000026800000a0212003c00].setShort (2, 1)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[closed][ParseID 0000026800000a0212003c00].setShort (3, 1)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[closed][ParseID 0000026800000a0212003c00].setShort (4, 1)
    com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[closed][ParseID 0000026800000a0212003c00].setString (5, KM2 Konstt)
    <-!
    Timestamp: 2009-05-15 22:49:15.692com.sap.dbtech.jdbc.exceptions.ObjectIsClosedException: SAP DBTech JDBC: Object is closed.
         at com.sap.dbtech.jdbc.ConnectionItem.assertOpen(ConnectionItem.java:53)
         at com.sap.dbtech.jdbc.CallableStatementSapDB.setString(CallableStatementSapDB.java:2191)
         at com.sap.dbtech.jdbc.trace.log.CallableStatement.setString(CallableStatement.java:2888)
         at com.sap.dbtech.jdbc.trace.CallableStatement.setString(CallableStatement.java:1050)
         at de.pkv.eventlogger.handler.EventLogEntryDAO.callInsertEventLogEntry(EventLogEntryDAO.java:150)
         at de.pkv.eventlogger.handler.DBhistoryOutputHandler.run(DBhistoryOutputHandler.java:52)
         at java.lang.Thread.run(Thread.java:619)

    it was the wrong place for a finally-statement in run()-Method:
         public void run() {
             while (true) { // do forever
                 try {
                   entry = this.theQueue.take(); // wait, if empty
                   if (DEBUG) System.out.println(name + ": try to take from queue: " + entry);
                   if (DEBUG) System.out.println(name + ": EventLogEntry: " + entry.toString());
                   // do the work: insert into Database:
                       success = dao.insertEventLogEntry(entry);     // insert new Entry (Prep.Statement)
                       //success = dao.callInsertEventLogEntry(entry);     // insert new Entry (call db_proc)
                 if (DEBUG) System.out.println(name + ": Insert new LogEntry. Success: " + success);
                   // Thread.sleep(10);
                   //Thread.yield();
                 } catch (InterruptedException e) {
                     System.err.println(name + ": Error in Thread.sleep()");
                   e.printStackTrace();
                 } catch (Exception e) {                       
                     System.err.println(name + ": Error: " + e.getMessage());
                 } // catch
          //       finally {
          //            if (con != null) {
          //                    try {
          //                         con.close();
          //                    } catch (SQLException e) {
          //                         // TODO Auto-generated catch block
          //                         e.printStackTrace();
          //               } // if con
          //       } // finally
               } // while
         } // run     
    regards
    Matthias

  • SAP DBTech JDBC: [259] (at 26): invalid table name:  Could not find table/view RS_POOL_CLUSTER_TABLES in schema SYSTEM: line 1 col 27 (at pos 26)

    Hi Gurus,
    I am trying to load a HANA column table using the import function and get the following error even though the mappings from the file to the table are 1:1.
    I get the following errors:
    Error 1: SAP DBTech JDBC: Result set is positioned before first row.
    Error 2: SAP DBTech JDBC: [259] (at 26): invalid table name:  Could not find table/view RS_POOL_CLUSTER_TABLES in schema SYSTEM: line 1 col 27 (at pos 26)
    With the following stack trace:
    com.sap.db.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: [259] (at 26): invalid table name:  Could not find table/view RS_POOL_CLUSTER_TABLES in schema SYSTEM: line 1 col 27 (at pos 26)
      at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.createException(SQLExceptionSapDB.java:334)
      at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.generateDatabaseException(SQLExceptionSapDB.java:165)
      at com.sap.db.jdbc.packet.ReplyPacket.buildExceptionChain(ReplyPacket.java:100)
      at com.sap.db.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:1141)
      at com.sap.db.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:888)
      at com.sap.db.jdbc.StatementSapDB.sendCommand(StatementSapDB.java:929)
      at com.sap.db.jdbc.StatementSapDB.sendSQL(StatementSapDB.java:978)
      at com.sap.db.jdbc.StatementSapDB.execute(StatementSapDB.java:256)
      at com.sap.db.jdbc.StatementSapDB.executeQuery(StatementSapDB.java:401)
      at com.sap.db.jdbc.trace.Statement.executeQuery(Statement.java:131)
      at com.sap.ndb.studio.bi.dataprovisioning.util.DBUtil.getPoolTables(DBUtil.java:200)
      at com.sap.ndb.studio.bi.dataprovisioning.util.DBUtil.getTablesToHide(DBUtil.java:188)
      at com.sap.ndb.studio.bi.filedataupload.ui.wizards.pages.SelectTableDialog.createDialogArea(SelectTableDialog.java:108)
      at org.eclipse.jface.dialogs.Dialog.createContents(Dialog.java:775)
      at org.eclipse.jface.window.Window.create(Window.java:432)
      at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104)
      at com.sap.ndb.studio.bi.filedataupload.ui.wizards.pages.SelectTableDialog.create(SelectTableDialog.java:186)
      at com.sap.ndb.studio.bi.filedataupload.ui.wizards.pages.ImportFileSelectionWizardPage$14.widgetSelected(ImportFileSelectionWizardPage.java:779)
      at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
      at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
      at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1057)
      at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4170)
      at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759)
      at org.eclipse.jface.window.Window.runEventLoop(Window.java:826)
      at org.eclipse.jface.window.Window.open(Window.java:802)
      at org.eclipse.ui.internal.handlers.WizardHandler$Import.executeHandler(WizardHandler.java:152)
      at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:279)
      at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)
      at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
      at sun.reflect.GeneratedMethodAccessor33.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
      at java.lang.reflect.Method.invoke(Unknown Source)
      at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
      at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243)
      at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224)
      at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
      at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167)
      at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
      at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
      at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
      at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:420)
      at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
      at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
      at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
      at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
      at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
      at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1057)
      at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4170)
      at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759)
      at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
      at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
      at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
      at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
      at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
      at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
      at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
      at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
      at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
      at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
      at java.lang.reflect.Method.invoke(Unknown Source)
      at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
      at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
      at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
      at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
    I'm sure many of you have come across this before. Any help will be much appreciated.
    Thanks in advance

    Hello Akhtar,
    Have you tryed to delete the heador row from your file?
    I received the same error when loading a csv file, but when I delete the heador row it worked.
    Best Regards,
    Juliana Genova

  • SAP DBTech JDBC: [260] Error

    Hi,
    We have installed a SAP HANA 80. I'm created a simple table with two fields (field01, field02) and then created an analytic view for testing. I activated without any errors. But when I click preview data it gives the error below. Also when I try to connect via Lumira, (I'm able to see the analytic view in lumira) while retrieving the data it gives the error below agian.
    I have no field named ORDER. Any ideas?
    Thanks.
    SAP DBTech JDBC: [260]: invalid column name: invalid column name: ORDER: line 1 col 3934 (at pos 3933) at ptime/query/checker/check_expr.cc:846

    How do I see the query formed? I just right click on the Analytic View and click "Preview Data"
    I installed also HANA Studio 80 (which was before 70). Now I still receive the same error but there is this detail:
    MDX SELECT * FROM BIMC_DIMENSION_VIEW WHERE CUBE_NAME = 'DENEME2' AND CATALOG_NAME = 'Trendbox'
    An exception stack trace is not available.
    When I execute the statement seperately I get the error:
    Could not execute 'MDX SELECT * FROM BIMC_DIMENSION_VIEW WHERE CUBE_NAME = 'DENEME2' AND CATALOG_NAME = 'Trendbox'' in 195 ms 217 µs .
    SAP DBTech JDBC: [260]: invalid column name: invalid column name: ORDER: line 1 col 3934 (at pos 3933) at ptime/query/checker/check_expr.cc:846

  • SAP DBTech JDBC: [4]: cannot allocate enough memory: Out of memory

    Hello,
    I am currently experiencing this error when making request to the Hana database via jdbc : SAP DBTech JDBC: [4]: cannot allocate enough memory: Out of memory
    I guess I am running out of space, so I wanted to delete some data from unused tables. The problem is that I cannot connect with Studio anymore "Error when connecting to system".
    Is there another way to delete data from some tables when getting this particular error ?
    Does anyone experienced such a situation ?
    Thank you,
    Benoît

    Hi Benoit,
    Please plan to migrate to the latest version from Rev 38 before 1 year license expires in Rev 38 in Oct 2013. You need to export your content and import in the latest version.
    As you are aware, a lot of bugs are fixed between Rev 38 and the newer releases along with new SPS5 features  and HANA One is adding new web based management features in each HANA One release which does not need SSH to stop|start HANA as it can be done in browser starting in Rev 52 (check out The specified item was not found.for additional info). Please stay tuned for the upcoming version which will have additional management features to manage your instance.
    Thanks,
    Swapan

  • Having problems with com.sap.dbtech.jdbc.DriverSapDB

    Hi all,
    I'm using webdynpro and i need to connect to a db.
    the line below throghs the Exception
    the line above throghs an Exception ClassNotFoundException
    Class.forName("com.sap.dbtech.jdbc.DriverSapDB");
    I have imported thre jar sapDB.jar what else can i do?
    I want to connect to an sql DB via java and i stack.
    need your help,
    Yoav
    Message was edited by: Yoav Toussia Cohen

    Hi Yoav,
    I belive you put the database access codes in your Web Dynpro's implementation. In this case you need to have your JDBC driver deployed as shared library to the server. You also need to define the Library Reference in your Web Dynpro's project properties.
    However, this is not a good approach and Web Dynpro never intends for business process development. You should have an EJB wrapped your database access. Then import this EJB as a model in Web Dynpro to preserve the MVC separation. Always remember Web Dynpro is an UI development tool and not for business process.
    Regards,
    Marc

  • ORA-01031: insufficient privileges - NOT TRUE

    Oracle: 10.2.0.2.0
    Os: Solaris 10 (10/08 s10x_u6wos_07b X86)
    When I try to connect to db with sqlplus and not indicating SID it connets OK.
    -bash-3.00$ sqlplus sys/qaz123 as sysdba
    SQL*Plus: Release 10.2.0.2.0 - Production on Wed Jun 2 00:53:34 2010
    Copyright (c) 1982, 2005, Oracle.  All Rights Reserved.
    Connected to:
    Oracle Database 10g Release 10.2.0.2.0 - Production
    SQL>...but if I indicate SID name it returns me error: ORA-01031: insufficient privileges
    -bash-3.00$ sqlplus sys/qaz123@eric1 as sysdba
    SQL*Plus: Release 10.2.0.2.0 - Production on Wed Jun 2 00:44:13 2010
    Copyright (c) 1982, 2005, Oracle.  All Rights Reserved.
    ERROR:
    ORA-01031: insufficient privilegesSo it cant be insufficient privileges because, as u all see above, sys is able to connect. So whats wrong ?
    Edited by: user639256 on Jun 1, 2010 3:57 PM

    Hi Hemant,
    You didn't specify SID, you specified the TNS connection. A SYS (SYSDBA) connection via TNS is a REMOTE_LOGIN that requires additional configuration -- viz REMOTE_LOGIN_PASSWORDFILE.
    Please lookup the documentation.
    Hemant K Chitaleare sure this is true for connecting on local server?
    SQL> conn / as sysdba
    Connected.
    SQL> show parameter remote
    NAME                                 TYPE        VALUE
    remote_archive_enable                string      true
    remote_dependencies_mode             string      TIMESTAMP
    remote_listener                      string
    remote_login_passwordfile            string      EXCLUSIVE
    remote_os_authent                    boolean     FALSE
    remote_os_roles                      boolean     FALSE
    SQL> conn sys/oracle@orcl as sysdba
    Connected.
    SQL> alter system set remote_login_passwordfile=none;
    alter system set remote_login_passwordfile=none
    ERROR at line 1:
    ORA-02095: specified initialization parameter cannot be modified
    SQL> alter system set remote_login_passwordfile=none scope=spfile;
    System altered.
    SQL> startup force
    ORACLE instance started.
    Total System Global Area 1073741824 bytes
    Fixed Size                  1253124 bytes
    Variable Size             251658492 bytes
    Database Buffers          813694976 bytes
    Redo Buffers                7135232 bytes
    Database mounted.
    Database opened.
    SQL> show parameter remote
    NAME                                 TYPE        VALUE
    remote_archive_enable                string      true
    remote_dependencies_mode             string      TIMESTAMP
    remote_listener                      string
    remote_login_passwordfile            string      NONE
    remote_os_authent                    boolean     FALSE
    remote_os_roles                      boolean     FALSE
    SQL> conn sys/oracle@orcl as sysdba
    Connected.
    SQL> conn sys/oracle@navneet as sysdba
    Connected.
    SQL>Regards

  • Unable to locate SAP Tutor 2.2 as in Note 1071313 - SAP Tutor Windows

    Hi all,
    I wanted to download SAP Tutor 2.2. Note 1071313 - SAP Tutor Windows Vista Compatibiity guides me to:
    SAP Tutor 2.2 is released for customers and can be downloaded from the following path:
    service.sap.com/swdc-> Download -> Installations and Upgrades -> Entry by Application Group -> SAP Application Components -> SAP TUTOR -> SAP Tutor 2.2
    But I am unable to find the file. It seems to have been moved. Any ideas?
    Thanks
    Ibrahim

    Hi,
    Go through below URL
    http://help.sap.com/bp_autov1600/Auto_DE/html/index.htm
    select business information-demo offering, here you will find SAP tutor
    Thanks
    chidambaram

  • Issuer of sso ticket is not authorized SAP gui logon

    Hello,
    Would you please brief me how to enable SSO between two ABAP systems for NWBC.
    We are not able to browse from source system to target system in NWBC, a logon prompt of second system is displayed for each browser session.
    What I did.
    Certified the server certificates with CA.
    Imported the certificate CA into ABAP and browser as well.
    Exchanged the certificates of both systems to each other strust store.
    RFC connections between those two ABAP systems are working fine , without logon prompts.
    HTTPS is working fine in browser without prompting for any certificate.
    After examining the trace using fiddler debugger,
    MYSAPSSO2 cookie is created and the same is being passed on to next system.
    It seems /its/webgui is not able to decrypt/receive this mysapsso2 cookie.
    SSL Server standard is certified by root CA in both abap systems and the root CA is added to strust store.
    ACL list is maintained for each in both systems.
    Issue has been resolved. ACL list is client dependent. So,  entries are maintained in the desired client.
    Now, no more logon prompt .

    Hi Michael,
    Thanks for you rhelp
    But this is not the problem.
    We found something strange in two environments.
    In BW Development (this is OK), the certified in ACL is showing:
    BWD 200 CN=BWD, OU=I0020274560, OU=SAP Web AS, O=SAP Trust Community, C=DE
    In BW Quality (isn´t OK), the certified in ACL is showing:
    BWQ 300 CN=BWQ  (only this)
    Can be this the problem? If yes, how can I solve?
    Thanks
    Carlos

Maybe you are looking for