Short dump DBIF_RSQL_INTERNAL_ERROR

[mohitsahu]

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

[Former Member]

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

[former_member182657]

Could you share SM21 logs also.

Regards,

Gaurav

[mohitsahu]

Here is SM21 logs:

1. When calling a function within the database interface, a return

value which cannot be processed by the calling function was

provided.

2. A short dump was generated for the specified program termination.

You can analyze this short dump in the system log evaluation by

selecting this line or evaluating Table SNAP (Transaction ST22).

3.

The transaction has been terminated.  This may be caused by a

termination message from the application (MESSAGE Axxx) or by an

error detected by the SAP System due to which it makes no sense to

proceed with the transaction.  The actual reason for the termination

is indicated by the T100 message and the parameters.

Additional documentation for message 00                  671

Internal session terminated with a runtime error (see ST22)

No documentation exists for message 00671

I checked also the dev trace file but did just get

ABAP Program RBDLPUTL                                .

Source RBDLPUTL                                 Line 17.

Error Code DBIF_RSQL_INTERNAL_ERROR.

Module  $Id: //bas/720_REL/src/krn/runt/absapsql.c#20 $ SAP.

Function ab_HandleRsqlErrors Line 724.

** RABAX: level LEV_RX_STDERR completed.

** RABAX: level LEV_RX_RFC_ERROR entered.

** RABAX: level LEV_RX_RFC_ERROR completed.

** RABAX: level LEV_RX_RFC_CLOSE entered.

** RABAX: level LEV_RX_RFC_CLOSE completed.

** RABAX: level LEV_RX_IMC_ERROR entered.

** RABAX: level LEV_RX_IMC_ERROR completed.

** RABAX: level LEV_RX_DATASET_CLOSE entered.

** RABAX: level LEV_RX_DATASET_CLOSE completed.

** RABAX: level LEV_RX_ERROR_SAVE entered.

** RABAX: level LEV_RX_ERROR_SAVE completed.

** RABAX: level LEV_RX_ERROR_TPDA entered.

** RABAX: level LEV_RX_ERROR_TPDA completed.

** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.

** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.

** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.

** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.

** RABAX: level LEV_RX_END entered.

** RABAX: level LEV_RX_END completed.

** RABAX: end no http/smtp

** RABAX: end RX_BTCHLOG RX_VBLOG

Internal error when accessing a table..

Regards,

Mohit

[srinivasan_vinayagam]

Hi Mohit,

SE11 ->Table BDLFUNCMAP - Display Table -> Utilities -> Database Object -> Display

You can see the which column contains length 12.

Test it by passing with field length 23 or to change the data length or change the field length value in Data element level 23 or above.

Regards,

V Srinivasan

[mohitsahu]

Hello Srinivasan,

As i stated earlier, this error occurred yesterday with the character length. I thought of changing the size but waited to see if the job will get cancelled again or not.

But today it was cancelled with some other reason.

I dont think this time changing the char size will bring any change as this is SAP standard job and nothing was changed in the report and parameter. as well

Regards,

Mohit

[former_member838366]

Can you share the new reason too?

Regards,

Praveen

[mohitsahu]

Hello Praveen,

I shared the logs of the latest problem occurred.

Regards,

Mohit

[Sriram2009]

Hi Mohit

If possible do the full restart and then check the same background job

BR

[mohitsahu]

Hello SS,

I can not take restart of the production system without having solid reason behind it. Moreover the job is related to SDCCN i think, so i dont think i will get restart approval.

Regards,

Mohit

[srinivasan_vinayagam]

Hi Mohit,

Yes this issue related to SDCCN.

Regards,

V Srinivasan

[mohitsahu]

Hello Srinivasan,

This job is getting failed in both the CRM and ECC prod system.

Regards,

Mohit

[srinivasan_vinayagam]

Hi Mohit,

Scheduled EWA from SDCCN as per note 207223.

Note 581692 - Apparently inconsistent job data - incorrect stepcount

Note 1272015 - Jobs with empty job names or job count

Note 37104 - Error analysis: Background processing system

Check above notes.

Regards,

V Srinivasan

[former_member182657]

Could you share the complete dump from ST22.

Regards,

Gaurav

[mohitsahu]

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

[former_member182657]

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) DATA...

Regards,

Gaurav

[mohitsahu]

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