Error when extracting huge table from MSSQL server.

Hi:
Under BI 7
I configured a DB datasouce to retrieve data from a view on MSSQL server.
It runs well when the data amount is below 5 million rows.
When the data volumn is over 5M, the datasouce start failed...
If I use the PREVIEW button in the Datasource maintain page, the system returns
the message:
Unknown error while uploading data from the DB table
Message no. RSDS_ACCESS027.
Does any expert know how to solve this issue?
Thanks a lot!!

Hi Clayton Hung,
I'm facing exactly the same problem with Oracle.Additionally Errors in source system
Message no. RSM340.
Have you found anything?
Cheers Marco
[email protected]

Similar Messages

  • Short dump error when extracting delta records from R/3

    I am working on BW 3.5 and I am facing some short dump error when extracting delta records from the r/3 to BW.
    Below is the error message
    Kindly do the needful ASAP.
    Job started
    Step 001 started (program SBIE0001, variant &0000000024277, user ID BWREMOTE)
    Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
    DATASOURCE = 0ISCM_PAYMENT_01
             Current Values for Selected Profile Parameters               *
    abap/heap_area_nondia......... 2000000000                              *
    abap/heap_area_total.......... 2000000000                              *
    abap/heaplimit................ 40000000                                *
    zcsa/installed_languages...... DE                                      *
    zcsa/system_language.......... E                                       *
    ztta/max_memreq_MB............ 2047                                    *
    ztta/roll_area................ 6500000                                 *
    ztta/roll_extension........... 2000000000                              *
    2,454 LUWs confirmed and 2,454 LUWs to be deleted with function module RSC2_QOUT_CONFIRM_DAT
    ABAP/4 processor: MESSAGE_TYPE_X
    Job cancelled

    Hi,
    I look at the transaction ST22 to see which type of error has given you. Take a look at the notes to correct the error.
    Another option is to look at OSS notes, because the error is giving you a standard extractor.
    Greetings,

  • PL/SQL: numeric or value error when extracting xml file from tables.

    create or replace FUNCTION proc_generate_xml_from_tables(p_directory in varchar2,
    p_areaname in varchar2)
    return integer
    AS
    qryCtx DBMS_XMLGEN.ctxHandle;
    result CLOB;
    clob_len number := 0;
    file_ptr utl_file.file_type;
    oTableName restore_metadata.table_name%type;
    o_filename restore_metadata.table_name%type;
    cursor metadata_restore_list(p_area varchar2) is
    select * from restore_metadata
    where instr(area_name,upper(p_Area)) > 0
    order by degree;
    vtabcount number := 0;
    sql_stmt varchar2(300);
    BEGIN
    dbms_lob.createtemporary(result, true,dbms_lob.session);
    oTableName := upper('MAINT_ACTVS');
    vtabcount := 0;
    sql_stmt := 'select count(*) from ' || oTableName;
    execute immediate sql_stmt into vtabcount;
    o_filename := oTableName || '.xml';
    file_ptr := utl_file.fopen(p_directory,o_filename,'W');
    dbms_output.put_line(oTableName);
    qryCtx := dbms_xmlgen.newcontext('select * from ' || oTableName);
    result := dbms_xmlgen.getxml(qryCtx);
    --dbms_output.put_line(result);
    clob_len := dbms_lob.getlength(result);
    dbms_output.put_line('Length of the clob file' || clob_len);
    utl_file.put_line(file_ptr,result);
    utl_file.fclose(file_ptr);
    dbms_xmlgen.closeContext(qryCtx);
    dbms_lob.freetemporary(result);
    return 0;
    EXCEPTION
    when others THEN
    utl_file.fclose(file_ptr);
    dbms_output.put_line('Table Name into Consideration :- ' || oTableName);
    dbms_output.put_line('Oracle Error Number:- ' || sqlcode || ' Ora Message :- ' || sqlerrm);
    return -1;
    END;
    I am getting the following errors..
    SQL> @temp1.sql
    MAINT_ACTVS
    Length of the clob file34245
    Table Name into Consideration :- MAINT_ACTVS
    Oracle Error Number:- -6502 Ora Message :- ORA-06502: PL/SQL: numeric or value error
    What am I doing wrong here?
    DB version is Oracle 10g
    Edited by: userAtoZ on May 6, 2011 2:55 PM

    >
    My problem lies that my xml file is having data more than 32 K.
    When I write it 32K at a time then it work fine.
    >
    Then break it down.
    l_pos number;
    WHILE (l_pos <= clob_len)
      LOOP
        UTL_FILE.PUT_LINE (file_ptr,DBMS_LOB.SUBSTR ( RESULT , 32767,l_pos));
        l_pos := l_pos + 32767;
      END LOOP;
    utl_file.fclose(file_ptr);
     

  • Error when execute a package from SQL Server Agent

    We have the next problem:
    When we execute a package from a Job of SQL Server agent, it shows the success messege, but reviewing the results, the package didnt do all the tasks.
    When we run it mannually by MSIS the package, it shows the success message and it works fine.
    The workflow of the package is :
    1) Shrink the databases (executing a sql file)
    2) Backup the databases (Back up Database task of MSIS)
    3) Rename the files to .BAK extension (by the Foreach loop container and fyle system task)
    4) Execute command to compress the it (by a .bat)
    5) Move the compress file to another location  (by another Foreach loop)
    Manually run correct, but when is a a SQL AGent Job that execute the package it does only the first 2 steps.
    we are ussing Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64) Jun 17 2011 00:54:03 Copyright (coffee) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) 
    We are using a user with administrator privilegies
    Cheers 

    Can you check if account running package has proper access. You may need to define a proxy account for that.
    See
    http://www.databasejournal.com/features/mssql/article.php/3789881/Proxy-Accounts-in-SQL-Server.htm
    http://gqbi.wordpress.com/2014/01/30/setting-up-a-proxy-account-to-run-sql-server-integration-services-ssis-2012-packages/
    Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

  • Getting run time error when accessing the file from frontend server using F4.....?

    Category               ABAP Programming Error
    Runtime Errors         CONVT_NO_NUMBER
    Except.                CX_SY_CONVERSION_NO_NUMBER
    ABAP Program           ZMM_MIGO_GOODS_ISSUE
    Application Component  Not assigned
    Date and Time          26.05.2014 14:28:30
    Short Text
         "C:\Users\SAP\Desktop\MIGO\MIGO.xlsx" cannot be interpreted as a number
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "ZMM_MIGO_GOODS_ISSUE" had to be terminated because
          it has
         come across a statement that unfortunately cannot be executed.
    Error analysis
         An exception has occurred which is explained in more detail below. The
         exception is assigned to class 'CX_SY_CONVERSION_NO_NUMBER' and was not caught
          in procedure
         "%_SEL_SCREEN_P_FNAME_V" "(FORM)", nor was it propagated by a RAISING clause.
         Since the caller of the procedure could not have anticipated this

    HI CHIRUI,
    I have changed and tried but still i a getting the same thing..
    otherwise please check this i am using some class method i am not getting short dump,but excel file is not getting uploaded.
    REPORT ZMM_MIGO_GOODS_ISSUE NO STANDARD PAGE HEADING.
    DATA : BEGIN OF IT_DATA OCCURS 0,
             ID(10),
             BLDAT(10),                             " Document Date
             BUDAT(10),                             " Posting Date
             REF_DOC_NO(16),                        " Material Slip No
             DEL_NOTE(16),                          " delivery note
             MATNR TYPE MSEG-MATNR,                 " Material Number
             ERFMG(13) TYPE C,                      " Quantity
             BWART TYPE RM07M-BWARTWA,              " Movement Type
             SOBKZ(1),                              " Special Stock
             WERKS TYPE RM07M-WERKS,                " Plant
             LGORT TYPE RM07M-LGORT,                " Storage Location
             PS_POSID TYPE PS_POSID,                " WBS Element
             COST_CENTER TYPE KOSTL,                " cost center
             ORDER TYPE AUFNR,                      " order number
             SERNR TYPE RIPW0-SERNR,                " Serial Number
            END OF IT_DATA,
            BEGIN OF IT_HEAD OCCURS 0,
              ID(10),
              BLDAT(10),                            " Document Date
              BUDAT(10),                            " Posting Date
              REF_DOC_NO(16),                       " Reference document number
              "HEADER_TXT(25),                       " Header Text
              BWART TYPE RM07M-BWARTWA,             " Movement Type
            END OF IT_HEAD,
            BEGIN OF IT_ITEM OCCURS 0,
              ID(10),
              "ID1(10),
              WERKS TYPE RM07M-WERKS,               " Plant
              LGORT TYPE RM07M-LGORT,               " Storage Location
              VAL_TYPE TYPE BWTAR_D,
              MATNR TYPE MSEG-MATNR,                " Material Number
              ERFMG(13) TYPE C,                     " Quantity
              CHARG TYPE MSEG-CHARG,                " Batch
              BWTAR TYPE BWTAR_D,
              PS_POSID TYPE PS_POSID,                 " WBS Element
              ERFME TYPE MSEG-ERFME,                  " Unit
              COST_CENTER TYPE KOSTL,                " cost center
              ORDER TYPE AUFNR,                      " order number
              CUSTOMER TYPE EKUNN,                    " Account Number of Customer
              SERNR TYPE RIPW0-SERNR,                 " Serial Number
              AMOUNT_LC TYPE BAPI_EXBWR,
              SOBKZ(1),
            END OF IT_ITEM,
              HEADER   LIKE BAPI2017_GM_HEAD_01,
              CODE     LIKE BAPI2017_GM_CODE,
              ITEMS    LIKE BAPI2017_GM_ITEM_CREATE OCCURS 0 WITH HEADER LINE,
              SERIAL   LIKE BAPI2017_GM_SERIALNUMBER OCCURS 0 WITH HEADER LINE,
              RETURN   LIKE BAPI2017_GM_HEAD_RET,
              RET      LIKE BAPIRET2 OCCURS 0 WITH HEADER LINE,
              TESTRUN  LIKE BAPI2017_GM_GEN-TESTRUN,
              IT_TAB   TYPE FILETABLE,
              GD_SUBRC TYPE I,
              L_FILE   TYPE RLGRAP-FILENAME,
              IT_RAW   TYPE TRUXS_T_TEXT_DATA,
              COUNT(2) TYPE N,
              TEXT_C(30).
    DATA: DATA     LIKE TABLE OF IT_ITEM WITH HEADER LINE.
    DATA: IT_TEMP  LIKE TABLE OF IT_ITEM WITH HEADER LINE.
    DATA: IT_TEMP1 LIKE TABLE OF IT_ITEM WITH HEADER LINE.
    DATA: IT_ITEM1 LIKE TABLE OF IT_ITEM WITH HEADER LINE.
    SELECTION-SCREEN: BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.
    PARAMETERS : P_FILE TYPE RLGRAP-FILENAME.
    *             p_test AS CHECKBOX.
    SELECTION-SCREEN: END OF BLOCK B1.
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILE.
       CALL METHOD CL_GUI_FRONTEND_SERVICES=>FILE_OPEN_DIALOG
         EXPORTING
           WINDOW_TITLE = 'SELECT FILE'
         CHANGING
           FILE_TABLE   = IT_TAB
           RC           = GD_SUBRC.
       READ TABLE IT_TAB INTO P_FILE INDEX 1.
    START-OF-SELECTION.
       PERFORM GET_EXCEL_DATA.
       PERFORM GET_HEADER_ITEM.
       PERFORM UPDATE_DATA.
    *&      Form  GET_EXCEL_DATA
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM GET_EXCEL_DATA .
       CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
         EXPORTING
           INPUT  = P_FILE
         IMPORTING
           OUTPUT = L_FILE.
       CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
         EXPORTING
           I_LINE_HEADER        = 'X'
           I_TAB_RAW_DATA       = IT_RAW
           I_FILENAME           = L_FILE
         TABLES
           I_TAB_CONVERTED_DATA = IT_DATA
         EXCEPTIONS
           CONVERSION_FAILED    = 1
           OTHERS               = 2.
       IF SY-SUBRC <> 0.
         MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
       ENDIF.
    ENDFORM. " GET_EXCEL_DATA
    *&      Form  GET_HEADER_ITEM
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM GET_HEADER_ITEM .
       DATA : FLAG(1).
       LOOP AT IT_DATA.
         CLEAR FLAG.
         IF IT_DATA-ID IS NOT INITIAL.
           AT NEW ID.
             FLAG = 'X'.
           ENDAT.
         ENDIF.
         IF FLAG = 'X'.
           MOVE-CORRESPONDING IT_DATA TO IT_HEAD.
           APPEND IT_HEAD.
         ENDIF.
         MOVE-CORRESPONDING IT_DATA TO IT_ITEM.
         APPEND IT_ITEM.
       ENDLOOP.
       DATA[] = IT_ITEM[].
       IT_TEMP[] = IT_ITEM[].
       IT_TEMP1[] = IT_ITEM[].
    ENDFORM. " GET_HEADER_ITEM
    *&      Form  UPDATE_DATA
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM UPDATE_DATA .
       DATA : COUNT1(10),
              L_QTY TYPE I,
              DAT(10).
       CONCATENATE SY-DATUM+6(2) '.' SY-DATUM+4(2) '.' SY-DATUM(4) INTO DAT.
       LOOP AT IT_HEAD.
         ON CHANGE OF IT_HEAD-ID.
           CALL FUNCTION 'CONVERT_DATE_TO_INTERNAL'
             EXPORTING
               DATE_EXTERNAL       = IT_HEAD-BUDAT
               ACCEPT_INITIAL_DATE = 'X'
             IMPORTING
               DATE_INTERNAL       = HEADER-PSTNG_DATE.
           IF SY-SUBRC <> 0.
             MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                     WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
           ENDIF.
           CALL FUNCTION 'CONVERT_DATE_TO_INTERNAL'
             EXPORTING
               DATE_EXTERNAL       = IT_HEAD-BLDAT
               ACCEPT_INITIAL_DATE = 'X'
             IMPORTING
               DATE_INTERNAL       = HEADER-DOC_DATE.
           IF SY-SUBRC <> 0.
             MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
           ENDIF.
           MOVE : '2'                TO HEADER-VER_GR_GI_SLIP,
                  'X'                TO HEADER-VER_GR_GI_SLIPX.
    *      IF r1 EQ 'X'.
           MOVE '05' TO CODE-GM_CODE.
           HEADER-REF_DOC_NO = IT_HEAD-REF_DOC_NO.
           "HEADER-HEADER_TXT = IT_HEAD-HEADER_TXT.
    *      ELSEIF r2 EQ 'X'.
    *        MOVE '04' TO code-gm_code.
    *      ELSEIF r3 EQ 'X'.
    *        MOVE '04' TO code-gm_code.
    *      ENDIF.
    *      IF p_test = 'X'.
    *        MOVE 'X' TO testrun.
    *      ENDIF.
         ENDON.
         IT_ITEM1[] = IT_ITEM[].
    *delete it_item[] where werks = '' and id = it_head-id.
         DELETE ADJACENT DUPLICATES FROM IT_ITEM COMPARING ID MATNR.
         LOOP AT IT_ITEM WHERE ID = IT_HEAD-ID.
    *      ON CHANGE OF it_item-id1.
           COUNT1 = COUNT1 + 1.
           CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
             EXPORTING
               INPUT  = IT_ITEM-MATNR
             IMPORTING
               OUTPUT = ITEMS-MATERIAL.
           MOVE : IT_ITEM-WERKS TO ITEMS-PLANT,
                  IT_ITEM-LGORT TO ITEMS-STGE_LOC,
    *             it_item-lgort1 TO items-move_stloc,
                  IT_ITEM-CHARG TO ITEMS-BATCH,
    *            IT_ITEM-VAL_TYPE TO ITEMS-VAL_TYPE,
                  'FRESH' TO ITEMS-VAL_TYPE,
                  IT_HEAD-BWART TO ITEMS-MOVE_TYPE,
                  IT_ITEM-SOBKZ TO ITEMS-SPEC_STOCK,
                  IT_ITEM-ERFMG TO ITEMS-ENTRY_QNT,
                  IT_ITEM-ERFMG TO ITEMS-ENTRY_QNT,
    *            it_item-erfme TO items-entry_uom,
    *            it_item-sgtxt TO items-item_text,
    *            it_item-exbwr TO items-amount_lc,
                  IT_ITEM-PS_POSID TO ITEMS-WBS_ELEM,
                  IT_ITEM-PS_POSID TO ITEMS-VAL_WBS_ELEM,
                  "IT_ITEM-CUSTOMER TO ITEMS-CUSTOMER,
                  IT_ITEM-ERFMG TO L_QTY,
                  IT_ITEM-AMOUNT_LC TO ITEMS-AMOUNT_LC,
                  IT_ITEM-COST_CENTER TO ITEMS-COSTCENTER,
                  IT_ITEM-ORDER TO ITEMS-ORDERID.
    *             items-SPEC_MVMT = 'R'.
           CALL FUNCTION 'CONVERSION_EXIT_ABPSN_INPUT'
             EXPORTING
               INPUT  = ITEMS-WBS_ELEM
             IMPORTING
               OUTPUT = ITEMS-WBS_ELEM.
           CALL FUNCTION 'CONVERSION_EXIT_ABPSN_INPUT'
             EXPORTING
               INPUT  = ITEMS-VAL_WBS_ELEM
             IMPORTING
               OUTPUT = ITEMS-VAL_WBS_ELEM.
    *      CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
    *        EXPORTING
    *          input  = it_item-lifnr
    *        IMPORTING
    *          output = items-vendor.
           APPEND ITEMS.
    *      ENDON.
         ENDLOOP.
         DELETE ADJACENT DUPLICATES FROM IT_TEMP COMPARING ID MATNR.
         DELETE IT_TEMP1 WHERE ID <> IT_HEAD-ID.
         DELETE IT_TEMP WHERE ID <> IT_HEAD-ID.
         DATA: MAT_ITM TYPE MBLPO,
               SERNP TYPE SERAIL.
         MAT_ITM = '0001'.
         LOOP AT IT_TEMP.
           SELECT SINGLE SERNP FROM MARC INTO SERNP WHERE MATNR = IT_TEMP-MATNR.
           IF SERNP IS NOT INITIAL.
             LOOP AT IT_TEMP1 WHERE ID = IT_TEMP-ID AND MATNR = IT_TEMP-MATNR.
    *    MOVE : it_item1-id TO serial-matdoc_itm,
    *     MOVE : mat_itm TO serial-matdoc_itm,
               SERIAL-MATDOC_ITM = MAT_ITM .
               SERIAL-SERIALNO   = IT_TEMP1-SERNR.
               APPEND SERIAL.
               CLEAR IT_ITEM1.
             ENDLOOP.
             MAT_ITM = MAT_ITM + 1.
           ENDIF.
           CLEAR IT_TEMP.
         ENDLOOP.
         CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
           EXPORTING
             GOODSMVT_HEADER       = HEADER
             GOODSMVT_CODE         = CODE
             TESTRUN               = TESTRUN
    *       GOODSMVT_REF_EWM      =
           IMPORTING
             GOODSMVT_HEADRET      = RETURN
    *       MATERIALDOCUMENT      =
    *       MATDOCUMENTYEAR       =
           TABLES
             GOODSMVT_ITEM         = ITEMS
             GOODSMVT_SERIALNUMBER = SERIAL
             RETURN                = RET
    *       GOODSMVT_SERV_PART_DATA =
    *       EXTENSIONIN           =
         CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
           EXPORTING
             WAIT = 'X'
    *   IMPORTING
    *       RETURN        =
         IF NOT RETURN IS INITIAL.
           WRITE :/ 'Material Document Number Generated: ' ,RETURN-MAT_DOC,RETURN-DOC_YEAR.
         ELSE.
           LOOP AT RET.
             WRITE : RET-TYPE,    RET-MESSAGE.
    *      log-index = sy-index.
    *      log-matnr = header-material.
    *      log-message = ret1-message.
    *      APPEND log.
           ENDLOOP.
         ENDIF.
         REFRESH : ITEMS,RET.
         CLEAR : HEADER,RETURN.
         CLEAR: TESTRUN  ,
                RETURN,
                ITEMS[],
                SERIAL[],
                RET[],
                HEADER,
                IT_TEMP[] ,
                IT_TEMP1[].
         IT_TEMP[] = DATA[].
         IT_TEMP1[] = DATA[].
       ENDLOOP.
    ENDFORM. " UPDATE_DATA
    Regards,
    Suresh bheema

  • Error while extracting huge volumes of data from BW

    Hi,
    we see this error while extracting huge volumes of data (apprx 3.4 million and with more no.of columns) and we see this error.
    R3C-151001: |Dataflow DF_SAPSI_SAPSI3131_SAPBW_To_Teradata
    Error calling R/3 to get table data: <RFC Error:
    Key: TSV_TNEW_PAGE_ALLOC_FAILED
    Status: EXCEPTION SYSTEM_FAILURE RAISED
    No more storage space available for extending an internal table.
    >.
    We are not sure if DoP works with source as SAP BW, but when tried with DoP also, we got the same error.
    Will this issue be resolved with an R/3 or ABAP dataflow? Can anyone suggest some possible solutions for this scenario?
    Sri

    The problem is that you've reached the maximum memory configure for your system.
    If this is batch job reconfigure the profile parameter
    abap/heap_area_nondia
    Markus

  • How to extract incremental data from SQL server to oracle tables in ODI

    HI All,
    In my ODI sql server is install.My Source is in SQL server and my target is in Oracle.
    I need to create a interface mapping where i need to extract incremental data from sql server to oracle.
    There is a datetime(with Timestamp) field in sql server .I need to pull incremental data based on dateime.
    Example = tablename.DateTime > (select '1-jan-11' from dual) .....i am using this query but its not woking.the error is Invalid object name"dual".
    We are not going to use Incremental in IKM and LKM.
    Request you to please provide any suggestion ASAP.
    Thanks,
    Lony

    You can do that via Variable.
    In the interface mapping create a filter on Tablename.DateTime
    and put the condition like this
    Tablename.DateTime BETWEEN #VAR and in the variable use this query in refreshing tab with oracle schema
    SELECT max(start_time)||' AND '||max(END_TIME)+1 from audit_table where ETL_JOB_CODE = '20'In the package call the above variable in refresh mode and then interface.
    This way you will pass from the query between and condition date and pass to interface so that SQL Server fetches the data between those too range.
    Note:- You might need to tweak the date format so that SQL Server can understand.
    Hope this helps.

  • Internal error when accessing a table  -

    Hi,
    The program which is running as background was running for last 1 year, last two days the RFC call in the program is dumping.
    In DUMP its showing Internal error when accessing a table
    Error : DBIF_RSQL_SQL_ERROR
    I checed the size of the table its quite huge for the application.
    So there is no issue with table.
    Please advise what causes these sort of error.
    System is ECC 6.0
    With SQL server 8.0
    Regards,
    Thomas

    These are the system log i got it from SM21. For this error logs are as below
    Very High Priority error
    Details Page 2 Line 9 System Log: Local Analysis of onsaprp1                  1
    Time
    Type
    Nr
    Clt
    TCode
    Grp
    N
    Text
    15:43:09
    DIA
    009
    300
    AB
    0
    Run-time error "DBIF_RSQL_INTERNAL_ERROR" occurred
    Run-time error "DBIF_RSQL_INTERNAL_ERROR" occurred
    Details
    Recording at local and central time........................ 11.02.2011 15:43:09
    Task......
    Process
    User......
    Terminal
    Session
    TCode
    Program
    Cl
    Problem cl
    Package
    03084
    Dialog work process No. 009
    TOM
    1
    SAPMSSY1
    T
    Transaction Problem
    SABP
    Further details for this message type
    Module nam
    Line
    Error text
    absapsql
    0786
    HandleRsqlErrors
    Documentation for system log message AB 0 :
    The specified runtime error has occurred in the system.
    Parameter
    abcdefghijklmnopqrstuvwxyz .. DBIF_RSQL_INTERNAL_ERROR
    Technical details
    File
    Offset
    RecFm
    System log type
    Grp
    N
    variable message data
    119
    618840
    l
    Error (Module, Row)
    AB
    0
    HandleRsqlErrors                                    absapsql0786
    High Priority error
    Details Page 2 Line 18 System Log: Local Analysis of onsaprp1                 1
    Time
    Type
    Nr
    Clt
    TCode
    Grp
    N
    Text
    15:44:07
    DIA
    009
    300
    SMEN
    BZ
    Y
    Unexpected return value 8 when calling up
    Unexpected return value 8 when calling up
    Details
    Recording at local and central time........................ 11.02.2011 15:44:07
    Task......
    Process
    User......
    Terminal
    Session
    TCode
    Program
    Cl
    Problem cl
    Package
    03084
    Dialog work process No. 009
    TOM
    om-blr-l
    1
    SMEN
    SAPLSMTR_NAVIGATION
    K
    SAP Web AS Problem
    SBAC
    Further details for this message type
    Module nam
    Line
    Table Name
    Field Name
    dbrepolo
    172
    8
    Documentation for system log message BZ Y :
    When calling a function within the database interface, a return
    value which cannot be processed by the calling function was
    provided.
    Technical details
    File
    Offset
    RecFm
    System log type
    Grp
    N
    variable message data
    120
    11160
    h
    Database Error (Non-SQL)
    BZ
    Y
    8                                                   dbrepolo172
    Edited by: Thomas Paul jr on Feb 14, 2011 6:36 AM
    Edited by: Thomas Paul jr on Feb 14, 2011 6:38 AM

  • Error when extracting data with extractor 2lis_04_matnr - NEED HELP ASAP !!

    Hi experts!
    Got an error when extracting data with extractor 2lis_04_matnr.
    System says (short dump):
    DUMP TEXT START----
    Runtime error:    CONNE_IMPORT_WRONG_COMP_TYPE
    Exception:   CX_SY_IMPORT_MISMATCH_ERROR
    Error when attempting to import object "MC04P_0MAT_TAB".
    The current ABAP program "SAPLMCEX" had to be terminated because one of the statements could not be executed. This is probably due to an error in the ABAP program. When attempting to import data, it was discovered that the data type of the stored data was not the same as that specified in the program.
    An exception occurred. This exception is dealt with in more detail below. The exception, which is assigned to the class 'CX_SY_IMPORT_MISMATCH_ERROR', was neither caught nor passed along using a RAISING clause, in the procedure  "MCEX_BW_LO_API" "(FUNCTION)".                                                                             
    Since the caller of the procedure could not have expected this exception      
    to occur, the running program was terminated.                                
    The reason for the exception is:  When importing the object "MC04P_0MAT_TAB", the component no. 5 in the dataset has a different type from the corresponding component of the target object in the program "SAPLMCEX". <b>The data type is "D" in the dataset, but "C" in the program.</b>
    DUMP TEXT END----
    Please, can someone explain me how to solve it? 
    Really need help ASAP!
    Thanks in advance,
    Jaume
    Message was edited by:
            Jaume Saumell
    Message was edited by:
            Jaume Saumell

    Hi,
    Check this note: 328181
    So you need to delete entries in SM13/LBWQ for application and also detup table content.
    And then refill teh set up table.
    If you are in production clear the entries by running collective run no of times for this application 04.
    With rgds,
    Anil Kumar Sharma .P

  • Problem in Import of Tables from SQL Server.

    Hi Forum,
    I m new to OWB.
    I m facing a prob regarding the import of tables.
    I m importing tables from SQL server through ODBC DB Link..
    It imports the tables fine, but without key constraints..
    Can u tell me, Why? and How can I import that info as well?

    Hi David,
    The things I said are not a fix for this problem.
    If your RCU installation worked, then you do not have to worry about modifying the createfr.sql.
    Edit:
    I've just tracked the problem. It appears that when using the query builder, BI forgets to add the " sign.
    For example:
    This query will give the hyperion error.
    select     "table"."field"
    from     "database.user"."table"
    To correct it write it like this:
    select     "table"."field"
    from     "database"."user"."table"
    Edited by: EBA on Nov 14, 2011 10:21 AM

  • Error ODS activation - sql error when accessing a table.

    Hi,
    sometimes occurs an error by activation ODS. I have proces chain and when is loaded second packet an error occurs. In monitor>>
    -RSMPC 128, datapacket 3 is wrong, with status number 9
    -RSMPC 131
    -RSDRO 108 - communcation error (sql error when accessing a table)
    In sm21>
    -sql error when accessing a table
    -The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was  
    either                                                      caught nor passed along using a RAISING clause, in the procedure <b>"UPDATE_ATAB"</b>   "(FORM)"                                                                    
    Since the caller of the procedure could not have expected this exception     
       to occur, the running program was terminated.                               
      The reason for the exception is:                                             
      The database system recognized that your last operation on the database      
      would have led to a deadlock.                                                
      Therefore, your transaction was rolled back                                  
      to avoid this.                                                                       
      ORACLE always terminates any transaction that would result in deadlock.      
      The other transactions involved in this potential deadlock                   
      are not affected by the termination.
    I have BW 3.5.
    Thank You very much.

    There are a few different scenarios that I can think of where this might come up that all involve what might resulting in parallel (concurrent)processes:
    Loading packets in parallel - that is there are X number of processes loading packets concurrently. This could be set in your IMG settings system wide or in the InfoPackage for just this datasource.   You seem to indicate that you don't have this.
    Database parallel processing - RSAMDIN - ORA_PARALLEL_DEGREE ( there was a different RSADMIN parm for older versions - forget what SP the change came with).
    You have multiple InfoPackages for the datasource, each loading what should be a different range of data, and they run atthe same time.
    You could be loading from two different datasources to the ODS at the same time.
    If any of these are true, I would look at bumping the INITRANS setting up.  Your DBA will probably need to do this for table and its indices.  There is a Note - 831234 that allows you to create a parameter in RSADMIN that will specify a INITRANS value (e.g. 20) rather than using the default. The ODS would need to be activated to pick this new setting up for the table to be altered. 
    You could also look at the Processing settings for the InfoPackage and change to PSA first, then target to see if that helps. 
    Or if you are loading from two different datasources at the same time, you might adjust your schedule so that doesn't happen.
    Pizzaman

  • SM58 : Internal error when accessing a table

    Hi there,
    We have just upgraded from R/3 4.7 to ECC 6.0. After the upgarde we face many "Internal error when accessing a table" in sm58. Is there any table mapping mismatched happened during unicode conversions? How to check the details? Most of the errors are SWW_WI_EXECUTE_INTERNAL_RFC, SWW_WI_CREATE_VIA_EVENT_IBF and etc which are workflow modules.
    can you help?
    Thanks.
    Regards,
    Thava

    Hi
    Have u checked this thread?
    problem in TRFC
    Error while executing Workflow: User is locked.
    /message/5804053#5804053 [original link is broken]
    Regards
    Sridhar Goli

  • ORA-00054 error when loading Oracle table using Data Services

    Hello,
    we are facing ORA-00054 error when loading Oracle table using BO Data services
    (Oracle 10g database, BODS Xi 3.2 SP3)
    Test Job performs
    1- truncate table
    2- load table (tested in standard and bulk load modes)
    Scenario when issue happens is:
    1- Run loading Job
    2- Job end in error for any Oracle data base error
    3- When re-running the same Job, Job fails with following error
         ORA-00054: resource busy and acquire with NOWAIT specified
    It seems after first failure, Oracle session for loading the table stays active and locks the table.
    To be able to rerun the Job, we are forced need to kill Oracle session manually to be able to run the Job again.
    Expected behaviour would be : on error rollback modifications made on table and BODS stops Oracle session in a clean way.
    Can somebody tell me / or point me to any BODS best practice about Oracle error handling to prevent such case?
    Thanks in advance
    Paul-Marie

    the ora-0054 can occure depending how the job failed before. If this occures you will need the DBA to release the lock on the table in question
    Or
           AL_Engine.exe on The server it creates the Lock. Need to Kill Them. Or stop it..
    This Problem Occurs when we select The Bulkloading Option in orclae  We also faced the same issue,Our admin has Killed the session. Then everything alright.

  • Error when determining a number from object BI_TSDTEL and number 01

    Hi BW Experts,
    After Transporting Infosources (Master & Transaction) to BW QA, the transfer rules were not getting activated in QA. The following error message was diaplyed.
    "Error when determining a number from object BI_TSDTEL and number 01
    Object name can only contain characters from syntactical character set
    Object name can only contain characters from syntactical character set
    Data element for InfoObject KOKRS 0CO_AREA could not be created
    Data element for InfoObject KOKRS 0CO_AREA could not be created
    Transfer structure 0IM_FA_IQ_2_SB activated under the name 0IM_FA_IQ_2_SA
    It is not necessary to copy dependent objects for transfer structure 0IM_FA_IQ_2_SA
    Transfer structure 0IM_FA_IQ_2_SA does not exist
    Error RSAR 440 when handling objects with type R3TR ISTS."
    I have gone through the Note: 674818.
    Could someone clear me about BI_TSDTEl, By using this do we need to maintain object intervals manually in all the systems like BW ( Dev & QA ), R/3 (Dev & QA).
    Because  I have not seen the Intervals in R/3 ( Dev & QA) systems.
    please could someone provide Inputs for this.
    Thanks in Advance
    Regards
    SK

    Hi,
    Try to see that transfer structure is existing in the sytem which is connecting in
    the BW quality.
    You need the same to be transported from the development server of R/3 to quality server of R/3.
    Just check if this helps.
    Regards
    Rahul Bindroo

  • Error occurred while downloading files from Administration Server...

    Hi guys,
    If i already have my application deployed and exploded in ../tmp/_WL_user , when I restart the managed server it will try to download again the files from the upload directory in the Administration Servers? (I'm using stage mode).
    Sometimes I got the following error:
    Caused By: java.io.IOException: [DeploymentService:290066]Error occurred while downloading files from Administration Server for deployment request "0". Underlying error is: "null"
    and I already have the war exploded in /tmp/_WL_user
    the staging mode is not only for the first deployment? when i don't have the war exploded in /tmp/_WL_user?
    I've some confusion related to the process or deployment/startup of the managed servers.
    Thanks

    Hi,
    when you get following error * DeploymentService:290066 * then that means
    A service on the machine is preventing the WebLogic Server remote instance from downloading the configuration file. This can be Hosts Intrusion Prevention (HIPS) agents or any other agent causing this issue.
    Disable the agent interfering with the download process to fix this issue.
    Regards,
    Kal

Maybe you are looking for

  • Get Error while update the User defined row table through DSK Code

    Hi experts, I have got an error while updating the user row defined table. Error is - "Invalid row" I have created one master table "@CBF_FARM " and Child table "@CBF_FAR1" First i inserted 5 record in the child table so in my my child table there ar

  • Help needed in configuring alerts in XI

    Hi I have configued an alert category and created a rule and in the container I defined the standard variables          (which start with &SXMS_* )     and also   a few custom variables.but when i raise an exception i am getting two alerts one alert

  • Convert Double To String

    Hello, I have the following method: private String doubleToString(double value, int kommas)      int stringLength;      String mString ="";      String mSubstringSuf ="";      Double dValue = new Double(value);      mString = new String(dValue.toStri

  • OWB RT Log Switches and Parameter

    Good day, all. For various reasons we find ourselves with an OWB data base repository release 10.1 and the target ODS data base release 10.2.0.4. This is an approved configuration within the Oracle Product Matrix. Both sit on the same MS 2003 64-bit

  • Runtime engine clash?

    Anyone know if it's possible to install LV2011 and LV2013 run time engines on the same machine? I want to run some older exes alongside their newer counterparts. Solved! Go to Solution.