Skip to Content
avatar image
Former Member

DBSQL_ALLOCATION_FAILED error in S4HANA 1610

Hello Experts,

Our S4HANA 1610 system is facing following ABAP dump continuously.

DBSQL_ALLOCATION_FAILED

I did checked the profile parameters as per OSS Note

2399990 - How-To: Analyzing ABAP Short Dumps in SAP HANA Environments

But The profile check is green with no errors.

Even the memory consumption is very low when DB error occured

Memory consumption
Roll.... 0
EM...... 0
Heap.... 1686720
Page.... 0
MM used. 979888
MM free. 703128

Following are the system details

SAP Release..... 751
SAP Basis level 0000

SAP kernel.......749
Created on....... Dec 9 2016 08:57:39
Created at....... Linux GNU SLES-11 x86_64 cc4.8.5 use-pr161208
Database version SQLDBC 2.00.080.1493752021
Patch level....... 100
Patch text.......

Database............. HDB 1.0
SAP database version. 749

##########################################################

ABAP DUMP pasted Below

Category Resource bottleneck
Runtime Errors DBSQL_ALLOCATION_FAILED
Date and Time 26.04.2018 02:40:52
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Short Text |
| A memory allocation request could not be complied with. |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|What happened? |
| Resource bottleneck |
| |
| Program "SAPMSSY2" had to be terminated because a capacity limit has been |
| reached. |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|What can I do? |
| Note which actions and entries caused the error to occur. |
| |
| Consult your SAP administrator. |
| |
| Using transaction ST22 for ABAP dump analysis, you can view, manage, |
| and retain termination messages for longer periods. |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Error analysis |
| The SQL runtime environment wanted to request 4096 bytes of memory. This |
| amount of memory was not available however. |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|How to correct the error |
| If the error occurs in a non-modfied SAP program, you might be able to |
| find a solution in the SAP Notes system. If you have access to the SAP |
| Notes system, check there first using the following keywords: |
| |
| "DBSQL_ALLOCATION_FAILED" |
| "SAPMSSY2" bzw. SAPMSSY2 |
| "%_START_JOB" |
| If you cannot solve the problem yourself, please send the following |
| information to SAP: |
| |
| 1. This description of the problem (short dump) |
| To do this, choose System -> List -> Save -> Local File (unconverted) |
| on the screen you are in now. |
| |
| 2. A suitable system log |
| To do this, call the system log in transaction SM21. Restrict the time |
| interval to ten minutes before the short dump and five minutes after |
| it. In the display, choose System -> List -> Save -> Local File |
| (unconverted). |
| |
| 3. If these are programs of your own, or modified SAP programs: Source |
| code of these programs |
| To do this, choose More Utilities -> Upload/Download -> Download in |
| the Editor. |
| |
| 4. Details regarding the conditions under which the error occurred or |
| which actions and input caused the error. |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|System environment |
| SAP Release..... 751 |
| SAP Basis level 0000 |
| |
| Application server... MRSFIN1610 |
| Instance name....... MRSFIN1610_MS4_01 |
| Network address...... 10.3.91.193 |
| Operating system... Linux |
| Release.............. 3.0.101-77-default |
| Hardware type....... x86_64 |
| Character length..... 16 Bits |
| Pointer length........ 64 Bits |
| Work process number... 11 |
| ABAP load version.... 2217 |
| Shortdump setting. full |
| |
| Database server... mrsfin1610 |
| Database type..... HDB |
| Database name..... MS4 |
| Database user ID SAPABAP1 |
| |
| Terminal.......... |
| |
| Character set C |
| |
| SAP kernel.......749 |
| Created on....... Dec 9 2016 08:57:39 |
| Created at....... Linux GNU SLES-11 x86_64 cc4.8.5 use-pr161208 |
| Database version SQLDBC 2.00.080.1493752021 |
| Patch level....... 100 |
| Patch text....... |
| |
| Database............. HDB 1.0 |
| SAP database version. 749 |
| Operating system... Linux |
| |
| Memory consumption |
| Roll.... 0 |
| EM...... 0 |
| Heap.... 1686720 |
| Page.... 0 |
| MM used. 979888 |
| MM free. 703128 |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|User and Transaction |
| Client................. 100 |
| User.................. SAPSYS |
| Language key.......... E |
| Transaction......... |
| Transaction ID...... 59DE69F8F2D800B0E005ACEF7185C59C |
| |
| EPP whole context ID...... |
| EPP connection ID........ |
| EPP call counter......... 0 |
| |
| Program.............. SAPMSSY2 |
| Screen.............. SAPMSSY2 4005 |
| Screen line.......... 4 |
| Active debugger..... "none" |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Information on where terminated |
| The termination occurred in ABAP program or include "SAPMSSY2", in |
| "%_START_JOB". The |
| main program was "SAPMSSY2". |
| |
| In the source code, the termination point is in line 6027 of program or |
| include "SAPMSSY2". |
| Program "SAPMSSY2" was started as a background job. |
| |
| Job name....... SAP_POC_PROCESS_EVENT_QUEUES |
| Job initiator.. DDIC |
| Job number...... 02395100 |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Source Code Extract |
----------------------------------------------------------------------------------------------------
|Line |SourceCde |
----------------------------------------------------------------------------------------------------
| 5997| space space |
| 5998| space space |
| 5999| space space. |
| 6000| ELSE. |
| 6001|* Laufzeitwerte des Jobs ermitteln |
| 6002| CALL FUNCTION 'GET_JOB_RUNTIME_INFO' |
| 6003| IMPORTING |
| 6004| external_program_active = curr_xpgflag |
| 6005| jobcount = curr_jobcount |
| 6006| jobname = curr_jobname |
| 6007| stepcount = curr_stepcount |
| 6008| EXCEPTIONS |
| 6009| no_runtime_info = 1 |
| 6010| OTHERS = 99. |
| 6011| |
| 6012| IF sy-subrc <> 0. |
| 6013| |
| 6014| cant_process_data = sy-subrc. |
| 6015| SHIFT cant_process_data LEFT DELETING LEADING space. |
| 6016| CONCATENATE 'retrieval of runtime info failed:' cant_process_data |
| 6017| INTO cant_process_data SEPARATED BY space. "#EC NOTEXT |
| 6018| IF trace_level > btc_trace_level0. |
| 6019| CALL 'WriteTrace' |
| 6020| ID 'CALL' FIELD btc_obj_job_start |
| 6021| ID 'PAR1' FIELD cant_process_data. |
| 6022| ENDIF. |
| 6023| MESSAGE a801(bt). |
| 6024| |
| 6025| ELSE. |
| 6026| |
|>>>>>| SELECT SINGLE * FROM tbtco |
| 6028| WHERE jobname = curr_jobname AND |
| 6029| jobcount = curr_jobcount. |
| 6030| |
| 6031| IF sy-subrc <> 0. |
| 6032|* Job ist nicht gefunden |
| 6033| IF trace_level > btc_trace_level0. |
| 6034| PERFORM trc_message |
| 6035| USING |
| 6036| btc_obj_job_start |
| 6037| 'job not found' "#EC NOTEXT |
| 6038| 'job will be aborted' "#EC NOTEXT |
| 6039| space space space. |
| 6040| |
| 6041| cant_process_data = curr_jobname. |
| 6042| |
| 6043| CALL 'C_WRITE_SYSLOG_ENTRY' |
| 6044| ID 'TYP' FIELD ' ' |
| 6045| ID 'KEY' FIELD tbs_cant_process_job |
| 6046| ID 'DATA' FIELD no_data. |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Contents of system fields |
----------------------------------------------------------------------------------------------------
|Name |Val. |
----------------------------------------------------------------------------------------------------
|SY-SUBRC|0 |
|SY-INDEX|0 |
|SY-TABIX|1 |
|SY-DBCNT|0 |
|SY-FDPOS|36 |
|SY-LSIND|0 |
|SY-PAGNO|0 |
|SY-LINNO|1 |
|SY-COLNO|1 |
|SY-PFKEY| |
|SY-UCOMM| |
|SY-TITLE|ABAP Job Control, ABAP Job Runtime Environment |
|SY-MSGTY| |
|SY-MSGID| |
|SY-MSGNO|000 |
|SY-MSGV1| |
|SY-MSGV2| |
|SY-MSGV3| |
|SY-MSGV4| |
|SY-MODNO|0 |
|SY-DATUM|20180426 |
|SY-UZEIT|024051 |
|SY-XPROG|%NEWSTEP |
|SY-XFORM| |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Active Calls/Events |
----------------------------------------------------------------------------------------------------
|No. Ty. Program Include Line |
| Name |
----------------------------------------------------------------------------------------------------
| 1 MODULE (PAI) SAPMSSY2 SAPMSSY2 6027 |
| %_START_JOB |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Chosen Variables |
----------------------------------------------------------------------------------------------------
|Name |
| Val. |
----------------------------------------------------------------------------------------------------
|No. 1 Ty. MODULE (PAI) |
|Name %_START_JOB |
----------------------------------------------------------------------------------------------------
|CANT_PROCESS_DATA |
| |
| 22222222222222222222222222222222 |
| 00000000000000000000000000000000 |
| 00000000000000000000000000000000 |
| 00000000000000000000000000000000 |
| 2000200020002000200020002000200020002000200020002000200020002000200020002000200020002000200020|
|AD_ALRT_OPERATION |
| 11 |
| 0000 |
| B000 |
| 0B000000 |
|TRACE_LEVEL |
| 0 |
| 0000 |
| 0000 |
| 00000000 |
|SY-XPROG |
| %NEWSTEP |
| 2445554522222222222222222222222222222222 |
| 5E57345000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 25004E0045005700530054004500500020002000200020002000200020002000200020002000200020002000200020|
|RC_RZL_STR_SET_FAILED |
| 212 |
| D000 |
| 4000 |
| D4000000 |
|BTC_OBJ_JOB_START |
| JOBSTART |
| 44455455222222222222222222222222 |
| AF234124000000000000000000000000 |
| 00000000000000000000000000000000 |
| 00000000000000000000000000000000 |
| 4A004F0042005300540041005200540020002000200020002000200020002000200020002000200020002000200020|
|SY-REPID |
| SAPMSSY2 |
| 5454555322222222222222222222222222222222 |
| 310D339200000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 5300410050004D00530053005900320020002000200020002000200020002000200020002000200020002000200020|
|SY-MSGID |
| |
| 22222222222222222222 |
| 00000000000000000000 |
| 00000000000000000000 |
| 00000000000000000000 |
| 20002000200020002000200020002000200020002000200020002000200020002000200020002000 |
|AL_MONIDEF_PRES_NODE_ASG_MTE |
| 1 |
| 3 |
| 1 |
| 0 |
| 0 |
| 3100 |
|BTC_END_OF_MONTH |
| 02 |
| 33 |
| 02 |
| 00 |
| 00 |
| 30003200 |
|SPACE |
| |
| 2 |
| 0 |
| 0 |
| 0 |
| 2000 |
|SY-MSGNO |
| 000 |
| 333 |
| 000 |
| 000 |
| 000 |
| 300030003000 |
|AL_RULE_SEMANTIC_ERROR |
| S |
| 5 |
| 3 |
| 0 |
| 0 |
| 5300 |
|SY-MSGV1 |
| |
| 22222222222222222222222222222222222222222222222222 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| 2000200020002000200020002000200020002000200020002000200020002000200020002000200020002000200020|
|SY-MSGV2 |
| |
| 22222222222222222222222222222222222222222222222222 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| 2000200020002000200020002000200020002000200020002000200020002000200020002000200020002000200020|
|SY-MSGV3 |
| |
| 22222222222222222222222222222222222222222222222222 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| 2000200020002000200020002000200020002000200020002000200020002000200020002000200020002000200020|
|SY-MSGV4 |
| |
| 22222222222222222222222222222222222222222222222222 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| 2000200020002000200020002000200020002000200020002000200020002000200020002000200020002000200020|
|RC_CANT_CONVERT_FDATE |
| 504 |
| F000 |
| 8100 |
| F8010000 |
|CURR_JOBNAME |
| SAP_POC_PROCESS_EVENT_QUEUES |
| 54555445554445554544555545452222 |
| 310F0F3F02F3533F565E4F1555530000 |
| 00000000000000000000000000000000 |
| 00000000000000000000000000000000 |
| 5300410050005F0050004F0043005F00500052004F0043004500530053005F004500560045004E0054005F00510055|
|CURR_JOBCOUNT |
| 02395100 |
| 33333333 |
| 02395100 |
| 00000000 |
| 00000000 |
| 30003200330039003500310030003000 |
|TBTCO |
| ##|
| 2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222200|
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000|
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000|
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000|
| 2000200020002000200020002000200020002000200020002000200020002000200020002000200020002000200020|
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Application Calls |
----------------------------------------------------------------------------------------------------
|Index|Calls |
----------------------------------------------------------------------------------------------------
| 1|background job SAP_POC_PROCESS_EVENT_QUEUES 02395100 |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Internal notes |
| The termination was triggered in function "ab_jsqln" of the SAP kernel, in |
| line 2600 of module "//bas/749_STACK/src/krn/abap/runt/absapsqln.cpp#1". |
| The internal operation just processed is "SQLN". |
| Internal mode started at 20180426024051. |
| Exception "Exception N3dbi4base20ExceptionOutOfMemoryE occurred." was caught. |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Active Calls in SAP Kernel |
----------------------------------------------------------------------------------------------------
|Lines of C sStack in kernel (structure different on each platform) |
----------------------------------------------------------------------------------------------------
|dw.sapMS4_D01[S](LinStackBacktrace+0xa9)[0x64accd] |
|dw.sapMS4_D01[S](LinStack+0x3e)[0x64dc39] |
|dw.sapMS4_D01[S](CTrcStack2+0x4b)[0x649a92] |
|dw.sapMS4_D01[S](rabax(char16_t const*, char16_t const*, int, char16_t const*, void const*)+0x12b4|
|dw.sapMS4_D01[S](ab_jsqln()+0x1fc6)[0x2279976] |
|dw.sapMS4_D01[S](ab_extri()+0x1b8)[0x1c57788] |
|dw.sapMS4_D01[S](ab_xevent(char16_t const*)+0x23)[0x1cb0883] |
|dw.sapMS4_D01[S](ab_dstep+0xf6)[0x1c53676] |
|dw.sapMS4_D01[S](dynpmcal(DINFDUMY*, STPDUMMY*)+0x4cb)[0x1c3aa5b] |
|dw.sapMS4_D01[S](dynppai0(DINFDUMY*)+0x2b2)[0x22f2242] |
|dw.sapMS4_D01[S](dynprctl(DINFDUMY*)+0x1e5)[0x1c3bb55] |
|dw.sapMS4_D01[S](dynpen00+0x3e0)[0x1c32d10] |
|dw.sapMS4_D01[S](ThrtCallAbapVm+0xc2)[0x1c22a62] |
|dw.sapMS4_D01[S](ThStart()+0x1863)[0x4efe76] |
|dw.sapMS4_D01[S](DpMain+0x395)[0x2282655] |
|libc.so.6[S](__libc_start_main+0xe6)[0x7f3f0f76ec36] |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Database Interface Information |
----------------------------------------------------------------------------------------------------
|B|1|DBSQL: Could not allocate 4096 bytes [ $Id: //bas/749_STACK/src/krn/include/dbi/base/dbi_exc_b|
|B|1|Exception N3dbi4base20ExceptionOutOfMemoryE (Code: 1001) thrown at @(#) $Id: //bas/749_STACK/s|
|B|1|DBSQL: Could not allocate 4096 bytes [ $Id: //bas/749_STACK/src/krn/include/dbi/base/dbi_exc_b|
|B|1|No exception callstack available, printing current stack ... [ $Id: //bas/749_STACK/src/krn/db|
----------------------------------------------------------------------------------------------------

##########################################################Operating system... Linux

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Apr 26 at 09:15 AM

    Hello Dnyandev,

    this does not look like an memory allocation failure originating from the HANA database layer. Rather, this looks like a memory request could not be fulfilled on SAP ABAP AS side. I suppose the NetWeaver Community would be the right one for this issue.

    BR, Bojan

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Bojan,

      I have added additional tags to address Netweaver community.

      Thanks,

      Dnyandev Kondekar

  • May 02 at 01:55 PM

    SAP Note 1999997 - FAQ: SAP HANA Memory says (point 29), that the root cause for this issue might be low memory at client side. That would explain why the memory usage in HANA is low when the issue occurs.

    As recommended in the note, please check the ulimit settings as well as general memory configuration. Is there any free RAM when the dump is created?

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Bartosz,

      Following are the ulimits set. The RAM is 100 GB free on constant basis. The eror is occurring for SAPSYS user.

      [1]ulimit -Ha
      core file size (blocks, -c) unlimited
      data seg size (kbytes, -d) unlimited
      scheduling priority (-e) 0
      file size (blocks, -f) unlimited
      pending signals (-i) 1971806
      max locked memory (kbytes, -l) 256
      max memory size (kbytes, -m) unlimited
      open files (-n) 1048576
      pipe size (512 bytes, -p) 8
      POSIX message queues (bytes, -q) 819200
      real-time priority (-r) 0
      stack size (kbytes, -s) unlimited
      cpu time (seconds, -t) unlimited
      max user processes (-u) 1971806
      virtual memory (kbytes, -v) unlimited
      file locks (-x) unlimited

      Thanks,

      Dnyandev

  • May 08 at 03:17 PM

    Hello Dnyandev Kondekar,

    Can you please check memory parameter shown as below and try to increase and try again?

    -Yogesh

    Add comment
    10|10000 characters needed characters exceeded