Skip to Content
author's profile photo Former Member
Former Member

Short dump DBIF_RSQL_INTERNAL_ERROR

Hello All,

We are facing the error in background job AUTO_SESSION_MANAGER failure. yesterday it was cancelled because of the below error

ORA-12899:Value too Large for column "USER.TABLENAME.OBJECT"(actual:23,maximum: 12) DATABASE

ERROR: 12899

and today the error is

An internal error in the database interface occurred during access to

the data of table "BDLFUNCMAP".

Do anyone has any idea?

Regards,

Mohit

Add a comment
10|10000 characters needed characters exceeded

Related questions

4 Answers

  • Posted on Dec 16, 2014 at 08:47 AM

    Hi Mohit,

    ORA-12899:Value too Large for column "USER.TABLENAME.OBJECT"(actual:23,maximum: 12) DATABASE

    ERROR: 12899

    Follow SAP Note 1203259 - ORA-12899:Value too Large for column "USER.TABLENAME.OBJECT"(actual:241,maximum: 240) DATABASE ERROR: 12899(UX0051)

    Regards,

    Gaurav

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hello Gaurav,

      I already checked this note. But the problem is this is SAP standard program and as i stated today the error occurred for this time is different from previous problem.

      Regards,

      Mohit

  • Posted on Dec 16, 2014 at 09:10 AM

    Could you share the complete dump from ST22.

    Regards,

    Gaurav

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hello Gaurav,

      Here is the log

      Runtime Errors DBIF_RSQL_INTERNAL_ERROR

      Date and Time 15.12.2014 20:00:34

      Short text

      Internal error when accessing a table.

      What happened?

      The current ABAP/4 program terminated due to

      an internal error in the database interface.


      What can you do?

      Note which actions and input led to the error.

      For further help in handling the problem, contact your SAP administrator

      .

      You can use the ABAP dump analysis transaction ST22 to view and manage

      termination messages, in particular for long term reference.

      Error analysis

      An internal error in the database interface occurred during access to

      the data of table "BDLFUNCMAP".

      The situation points to an internal error in the SAP software

      or to an incorrect status of the respective work process.

      For further analysis the SAP system log should be examined

      (transaction SM21).

      For a precise analysis of the error, you should supply

      documents with as many details as possible.

      How to correct the error

      Start the work process involved and repeat the action that lead to the

      error.

      If the error position is in a program that you can change, you can try

      to create preliminary solution: Reformulate the database command by

      varying the properties such as individual record access instead of

      input/output via internal tables, the structure of the selection

      conditions (WHERE clause), nested SELECT loops instead of FOR ALL

      ENTRIES and other such variations.

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

      Check the entries in the developer trace of the work process involved

      (transaction ST11).

      If the error occures in a non-modified SAP program, you may be able to

      find an interim solution in an SAP Note.

      If you have access to SAP Notes, carry out a search with the following

      keywords:

      "DBIF_RSQL_INTERNAL_ERROR" " "

      "RBDLPUTL" or "RBDLPUTL"

      "START-OF-SELECTION"

      If you cannot solve the problem yourself and want to send an error

      notification to SAP, include the following information:

      1. The description of the current problem (short dump)

      To save the description, choose "System->List->Save->Local File

      (Unconverted)".

      2. Corresponding system log

      Display the system log by calling transaction SM21.

      Restrict the time interval to 10 minutes before and five minutes

      after the short dump. Then choose "System->List->Save->Local File

      (Unconverted)".

      3. If the problem occurs in a problem of your own or a modified SAP

      program: The source code of the program

      In the editor, choose "Utilities->More

      Utilities->Upload/Download->Download".

      4. Details about the conditions under which the error occurred or which

      actions and input led to the error.

      em environment

      SAP-Release 701

      Application server... "sapcrmpd"

      Network address...... "192.168."

      Operating system..... "Linux"

      Release.............. "2.6.32-279.el6.x86_6"

      Hardware type........ "x86_64"

      Character length.... 16 Bits

      Pointer length....... 64 Bits

      Work process number.. 45

      Shortdump setting.... "full"

      Database server... "sap-prod-4"

      Database type..... "ORACLE"

      Database name..... "DC1"

      Database user ID.. "SAPxcA"

      Terminal.......... " "

      Char.set.... "C"

      SAP kernel....... 720

      created (date)... "Apr 21 2012 01:40:08"

      create on........ "Linux GNU SLES-9 x86_64 cc4.1.2 use-pr120412"

      Database version. "OCI_102, 10.2.0.5.0, V3, default"

      Patch level. 215

      Patch text.. " "

      Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"

      SAP database version. 720

      Operating system..... "Linux 2.6, Linux 3"

      Memory consumption

      Roll.... 1217168

      EM...... 0

      Heap.... 0

      Page.... 24576

      MM Used. 1119136

      MM Free. 77368

      User and Transaction

      Client.............. 100

      User................ "D-BS"

      Language key........ "E"

      Transaction......... " "

      Transactions ID..... "548FE61017CF3B94E1000000C0A8896B"

      Program............. "RBDLPUTL"

      Screen.............. "SAPMSSY0 1000"

      Screen line......... 6

      Information on where terminated

      Termination occurred in the ABAP program "RBDLPUTL" - in "START-OF-SELECTION".

      The main program was "RBDLPUTL ".

      In the source code you have the termination point in line 17

      of the (Include) program "RBDLPUTL".

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

      Job Name....... "AUTO_SESSION_MANAGER"

      Job Initiator.. "D-BS"

      Job Number..... 20002502

      Source Code Extract

      Line SourceCde

      1 report RBDLPUTL.

      2 * Dynamically generated

      3 Tables: bdl_clustl.

      4 Tables: bdl_gener.

      5 data: to_be_sent like bdlfuvers-to_be_sent.

      6 data: begin of bdl_table occurs 20.

      7 include structure BDLFUNCMAP.

      8 data: end of bdl_table.

      9 tables:BDLFUNCMAP.

      10 tables:bdl2trans.

      11 import bdl_table from database bdl_clustl(DB) id 'Dapcrmprod'.

      12 if sy-subrc = 0.

      13 Loop at bdl_table.

      14 if bdl_table-status = 'D'.

      15 delete BDLFUNCMAP from bdl_table.

      16 else.

      >>>>> modify BDLFUNCMAP from bdl_table.

      18 endif.

      19 endloop.

      20 if sy-subrc = 0.

      21 update bdl2trans set sapnet_chg ='20141125150650'

      22 where sapnetbdl ='BDLFUNCMAP' .

      23 Commit work.

      24 endif.

      25 endif.

      Regards,

      Mohit

  • Posted on Dec 16, 2014 at 09:23 AM

    Could you share SM21 logs also.

    Regards,

    Gaurav

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 16, 2014 at 03:47 PM

    can you try to update the DBSL patch level and check it.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.