Skip to Content
avatar image
Former Member

Short dumps while doing selective deletions

Hello Gurus,

This is pretty urgent. I apprcite if you guys can help me out here.

Iam doing selective deletion at cube level by compnay code(50 values),plant(65 values) and material(200 values).

I an getting short dumps with DBIF_DSQL2_SQL_ERROR/ CX_SY_NATIVE_SQL_ERROR.

On ODS objects with same selection as above, I am getting Short dumps with RAISE_EXCEPTION.

Is this someting related to system issues tha tI need to contact BASIS or something else.

Please suggest.

Regards,

Suman

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • avatar image
    Former Member
    May 26, 2006 at 05:13 PM

    Hello Simmi,

    Please check OSS note 455281.

    *********************************************************

    Symptom

    During the selective deletion of data from an InfoCube the system generates a dump with ABAP runtime error DBIF_DSQL2_SQL_ERROR and Oracle error number ORA-03113.

    The termination occurs in an ABAP/4 program with a name like "GP74CA15T7AG7JHBFD47W20UV4Q", that means in a generated program.

    Additional key words

    Selective deletion, delete, delete facts, DELETE_FACTS, RSDRD, ORA-03113, DBIF_DSQL2_SQL_ERROR

    Cause and prerequisites

    During the deletion from the InfoCube the system determines how many records the cube contains and how many of these are supposed to be deleted.

    During the count the system uses the bitmap-indexes created on the cube. The access of these can fail in Oracle 8.1.6 and that results in the error above.

    Solution

    Because Oracle does not support Oracle Releases 8.0.6 and 8.1.6 anymore since the end of October, you must upgrade to the newest Oracle Release 8.1.7 to correct the error.

    A workaround is to delete the bitmap indexes (Admin Workbench, Cube administration, tab title Performance), to execute the deletion and then to set up the indexes again.

    *********************************************************

    Regards,

    Praveen

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    May 26, 2006 at 07:44 PM

    Praveen,

    Thanks for the immediat update. I will have to see hw applicable is the note. We are not on Oracle. We have MS-SQL database. This the dump description,

    Runtime Errors DBIF_DSQL2_SQL_ERROR

    Exception CX_SY_NATIVE_SQL_ERROR

    Occurred on 26.05.2006 at 07:54:46

    SQL error 257 occurred when executing EXEC SQL.

    What happened?

    The error occurred in the current database connection "DEFAULT".

    Error analysis

    An exception occurred. This exception is dealt with in more detail below

    . The exception, which is assigned to the class 'CX_SY_NATIVE_SQL_ERROR', w

    neither

    caught nor passed along using a RAISING clause, in the procedure

    "MSSQL_CREATE_TABLE_AS_SELECT" "(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:

    How to correct the error

    The exception must either be prevented, caught within the procedure

    "MSSQL_CREATE_TABLE_AS_SELECT"

    "(FORM)", or declared in the procedure's RAISING clause.

    To prevent the exception, note the following:

    Database error text........: "Implicit conversion from data type ntext to

    varchar is not allowed. Use the CONVERT function to run this query."

    Triggering SQL statement...: " ? ? ? RK"

    Internal call code.........: "[DBDS/NEW DSQL]"

    Please check the entries in the system log (Transaction SM21).

    You may able to find an interim solution to the problem

    in the SAP note system. If you have access to the note system yourself,

    use the following search criteria:

    -


    "DBIF_DSQL2_SQL_ERROR" CX_SY_NATIVE_SQL_ERRORC

    "RSDD_MSSQL_GENERAL_UTILS " or "RSDD_MSSQL_GENERAL_UTILS "

    "MSSQL_CREATE_TABLE_AS_SELECT"

    -


    -


    Information on where terminated

    The termination occurred in the ABAP program "RSDD_MSSQL_GENERAL_UTILS " in

    "MSSQL_CREATE_TABLE_AS_SELECT".

    The main program was "GPBFHED11JH0TLT3NYP110SO4MW ".

    The termination occurred in line 291 of the source code of the (Include)

    program "RSDD_MSSQL_GENERAL_UTILS "

    of the source code of program "RSDD_MSSQL_GENERAL_UTILS " (when calling the

    editor 2910).

    The program "RSDD_MSSQL_GENERAL_UTILS " was started as a background job.

    Processing was terminated because the exception "CX_SY_NATIVE_SQL_ERROR"

    occurred in the

    procedure "MSSQL_CREATE_TABLE_AS_SELECT" "(FORM)" but was not handled locally

    not declared in the

    RAISING clause of the procedure.

    The procedure is in the program "RSDD_MSSQL_GENERAL_UTILS ". Its source code

    starts in line 269

    of the (Include) program "RSDD_MSSQL_GENERAL_UTILS ".

    Internal notes

    The termination occurred in the function "DsqlErrorHandler" of the SAP

    Basis System, specifically in line 1994 of the module

    "//bas/620/src/krn/runt/abexsql.c#10".

    The internal operation just processed is "DSQL".

    The internal session was started at 20060526075445.

    Internal call code.........: "[DBDS/NEW DSQL]"

    An exception occurred. This exception is dealt with in more detail below

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hello Simmi,

      Please chceck note 743519.

      *******************************************************

      Symptom

      During request deletion in BW MSSQL error 107 occurs:

      The column prefix 'DIM' does not match with a table name or

      alias name used in the query.

      Error happens after BW 3.0B SP16 or later was applied.

      Other terms

      EXEC SQL

      DBIF_DSQL2_SQL_ERROR

      CX_SY_NATIVE_SQL_ERROR

      sap_atomic_BW_create_like

      Reason and Prerequisites

      Generic coding was adapted in a way that made one of the generated

      statements incompatible to MSSQL server during request deletion.

      This causes the MS SQLServer error 107.

      Solution

      The source code of BW stored procedure was changed accordingly.

      The change is available in BW 3.0B SP 22.

      ********************************************************

      Regards,

      Praveen

  • avatar image
    Former Member
    May 26, 2006 at 11:42 PM

    Hi Suman,

    Most of the cases the above short dump is due to the memory issue in the system. You can resolve it by reducing the selection for the selective deletion. Ex: If it is a fiscal year try it by splitting it into months... It should work.

    Thanks

    Srikanth.

    Add comment
    10|10000 characters needed characters exceeded