SAP——BWP跑数报错：2020-03-27 BWP报错：The memory quest for 4056 bytes could not be for com

2020年3月27日 2071点热度 1人点赞 0条评论

一、BWP跑数失败，提示

二、报错信息-见附件：

三、分析原因：

从报错看，BW系统的缓存和扩展内存已全部耗尽，导致申请4K的内存都不可以，具体调整优化措施如下：

1、建议调整前对BWP系统进行数据备份；

2、数据备份成功后，选择业务不忙时段（如晚间），按照以下建议对SAP参数进行尝试性修改：

1）按照建议，以事务码rz10修改以下参数，测试程序是否可用；

BW系统总体可用内存有45G，而扩展内存值均为默认的4G，因此建议加大以下三个参数

ztta/roll_extension = 8000000000

ztta/roll_extension_dia = 8000000000

ztta/roll_extension_nondia = 8000000000

2）如果可用则修改结束，重启SAP BW；------此处是代表修改参数对程序运行有效果；

3）重启后以事务码rz11检查参数是否已经修改，并测试运行程序；

4）如果测试成功，代表参数生效且程序运行正常；

------以上代表此问题被修改完毕，后期随着业务数据量的增加等因素，SAP参数可能还需要做相应的修改，可参照SAP系统报错的建议或者与我们及时联系，谢谢。

四、解决方法：

调整参数：

ztta/roll_extension = 8000000000

ztta/roll_extension_dia = 8000000000

ztta/roll_extension_nondia = 8000000000

附件：

类别 Resource Shortage

运行时错误 SYSTEM_NO_ROLL

日期和时间 25.03.2020 15:31:57

----------------------------------------------------------------------------------------------------

|短文本 |

| The memory request for 4056 bytes could not be complied with. |

----------------------------------------------------------------------------------------------------

|发生了什么？ |

| Each transaction requires some main memory space to process application |

| data. If the operating system does not have any more memory, the |

| transaction is terminated. |

----------------------------------------------------------------------------------------------------

|您可以做什么？ |

| Try to find out (using specific data selection for example) whether the |

| transaction will run with less main memory. |

| |

| If the problem is due to a temporary bottleneck, run the transaction |

| again. |

| |

| If the error persists, ask your system administrator to check the |

| following profile parameters: |

| |

| o ztta/roll_area (1.000.000 - 15.000.000) classic roll area |

| per user and internal session o ztta/roll_extension (10.000.000 |

| - 500.000.000) available memory/user in extended memory |

| EM o ztta/max_memreq_MB maximum size of an individual memory request |

| (in MB) o abap/heap_area_total (100.000.000 - 1.500.000.000) |

| available memory (malloc) for all users of an application server. If |

| several background processes are running on one server, temporary |

| bottlenecks can occur. Of course, the amount of memory (in bytes) must |

| also be available on the machine (main memory or file system swap). |

| Caution: |

| The operating system must be set up so that there is also enough memory |

| for each process. Usually, the maximum address space is too small. |

| Ask your hardware manufacturer or your competence center about this. |

| |

| o abap/heap_area_dia: (10.000.000 - 1.000.000.000) |

| restriction of the memory that can be allocated to the heap with malloc |

| per dialog process. |

| |

| Parameter for background processes: |

| |

| o abap/heap_area_nondia: (10.000.000 - 1.000.000.000) |

| restriction of the memory that can be allocated to the heap with malloc |

| per background process. |

| |

| Other memory-relevant parameters are: |

| |

| o em/initial_size_MB: (35 - 1200) |

| Extended memory area from which all users of an application server can |

| meet their memory needs. |

| |

| o abap/shared_objects_size_MB: |

| Size of the shared memory area that can be used to save shared objects |

| area instances. This memory area is global for all users of the |

| application server. |

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

----------------------------------------------------------------------------------------------------

|错误分析 |

| More main memory area was requested. |

| The total available space has already been assigned however. Possible |

| causes: |

| - A large number of (large) internal tables |

| - A large number of (large) programs active |

| - Deep nesting of subroutines with large amounts of local data |

----------------------------------------------------------------------------------------------------

|如何更正此错误 |

| Perform an analysis to find out whether this request makes sense or |

| whether a program error has occurred. Pay particular attention to the |

| internal table entries listed below. |

| The amount of memory (in bytes) used at termination time was: |

| |

| Roll area...................... 0 |

| Extended memory (EM) 4002840608 |

| Assigned memory (HEAP) 2027969408 |

| Short area..................... |

| Paging area.................... 81920 |

| Maximum address space.......... 18446744073709551615 |

| 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: |

| |

| "SYSTEM_NO_ROLL" |

| "????????????????????????????????????????" bzw. |

| " " |

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

----------------------------------------------------------------------------------------------------

|系统环境 |

| SAP Release..... |

| SAP Basis level 0008 |

| |

| Application server... YCZBBWPRD |

| Network address...... 172.18.1.18 |

| Operating system... Linux |

| Release.............. 3.0.76-0.11-default |

| Hardware type....... x86_64 |

| Character length..... 16 Bits |

| Pointer length........ 64 Bits |

| Work process number... 13 |

| Shortdump setting. full |

| |

| Database server... hanabw |

| Database type..... HDB |

| Database name..... BWP |

| Database user ID SAPBWP |

| |

| Terminal.......... WIN-VUMMMIT2B9J |

| |

| Character set C |

| |

| SAP kernel....... 742 |

| Created on....... Sep 2 2014 15:05:39 |

| Created at....... Linux GNU SLES-11 x86_64 cc4.3.4 use-pr140815 |

| Database version SQLDBC 1.00.60.0379371 |

| Patch level....... 17 |

| Patch text....... |

| |

| Database............. HDB 1.0 |

| SAP database version. 742 |

| Operating system... Linux 2.6, Linux 3 |

| |

| Memory consumption |

| Roll.... 0 |

| EM...... 4002840608 |

| Heap.... 2027969408 |

| Page.... 81920 |

| MM used. 0 |

| MM free. 0 |

----------------------------------------------------------------------------------------------------

|用户和事务 |

| Client................. 001 |

| User.................. SYSADMING |

| Language key.......... 1 |

| Transaction......... |

| Transaction ID...... 5E7A3A96F28F2255E1000000AC120112 |

| |

| EPP whole context ID...... 000C29A154F41EEA9BCCEBF98246717B |

| EPP connection ID........ 00000000000000000000000000000000 |

| EPP call counter......... 0 |

| |

| Program.............. ???????????????????????????????????????? |

| Screen.............. |

| Screen line.......... 0 |

| Active debugger..... "none" |

----------------------------------------------------------------------------------------------------

|关于在何处终止的信息 |

----------------------------------------------------------------------------------------------------

|系统字段的内容 |

----------------------------------------------------------------------------------------------------

|名称 |评估 |

----------------------------------------------------------------------------------------------------

|SY-SUBRC|0 |

|SY-INDEX|2 |

|SY-TABIX|1 |

|SY-DBCNT|1 |

|SY-FDPOS|0 |

|SY-LSIND|0 |

|SY-PAGNO|0 |

|SY-LINNO|1 |

|SY-COLNO|1 |

|SY-PFKEY|200D |

|SY-UCOMM|EXECUTE |

|SY-TITLE|显示数据传输流程 |

|SY-MSGTY|E |

|SY-MSGID|MC |

|SY-MSGNO|602 |

|SY-MSGV1|SYSADMING |

|SY-MSGV2|E_BW_DTP |

|SY-MSGV3|SYSADMING |

|SY-MSGV4| |

|SY-MODNO|0 |

|SY-DATUM|20200325 |

|SY-UZEIT|153036 |

|SY-XPROG|SAPMSSY1 |

|SY-XFORM|XAB_WFLUSH |

----------------------------------------------------------------------------------------------------

|内部注释 |

| The termination was triggered in function "dyGetDummyDynpro" of the SAP |

| kernel, in |

| line 2283 of module "//bas/742_REL/src/krn/dynp/dybas.c#3". |

| The internal operation just processed is " ". |

| Internal mode started at "##############". |

----------------------------------------------------------------------------------------------------

|SAP 内核中的活动调用 |

----------------------------------------------------------------------------------------------------

|内核中 C 堆栈的行（结构因各平台而异） |

----------------------------------------------------------------------------------------------------

|dw.sapBWP_DVEBMGS00[S](LinStackBacktrace+0x8c)[0x62f7e9] |

|dw.sapBWP_DVEBMGS00[S](LinStack+0x35)[0x633830] |

|dw.sapBWP_DVEBMGS00[S](CTrcStack2+0x4e)[0x62f5ac] |

|dw.sapBWP_DVEBMGS00[S](rabax_CStackSave()+0xcf)[0x777c15] |

|dw.sapBWP_DVEBMGS00[S](ab_rabax+0x285c)[0x77f4cf] |

|dw.sapBWP_DVEBMGS00[S](dyGetDummyDynpro(unsigned char, unsigned char)+0xd8)[0x1a209b8] |

|dw.sapBWP_DVEBMGS00[S](init_imode_spa()+0x3af)[0x19e6b6f] |

|dw.sapBWP_DVEBMGS00[S](dynpinrl()+0xb5)[0x19e7035] |

|dw.sapBWP_DVEBMGS00[S](dy_cdiag+0x54b)[0x19fc5eb] |

|dw.sapBWP_DVEBMGS00[S](ab_sdialog+0x149)[0x1b05069] |

|dw.sapBWP_DVEBMGS00[S](ab_RabaxDialog()+0xaf)[0x777361] |

|dw.sapBWP_DVEBMGS00[S](ab_extri()+0x10a)[0x17284ea] |

|dw.sapBWP_DVEBMGS00[S](ab_xevent(char16_t const*)+0x35)[0x1760605] |

|dw.sapBWP_DVEBMGS00[S](ab_dstep+0x139)[0x1724349] |

|dw.sapBWP_DVEBMGS00[S](dynpmcal(DINFDUMY*, STPDUMMY*)+0x2ca)[0x16f018a] |

|dw.sapBWP_DVEBMGS00[S](dynppai0(DINFDUMY*)+0x28e)[0x16f0d2e] |

|dw.sapBWP_DVEBMGS00[S](dynprctl(DINFDUMY*)+0x173)[0x19f7b73] |

|dw.sapBWP_DVEBMGS00[S](dynpen00+0x364)[0x19ea2d4] |

|dw.sapBWP_DVEBMGS00[S](ThrtCallAbapVm+0xcb)[0x19b964b] |

|dw.sapBWP_DVEBMGS00[S](ThHandleRequest(REQUEST_BUF*, unsigned char)+0x17a)[0x197e61a] |

|dw.sapBWP_DVEBMGS00[S](TskhLoop()+0x6f)[0x197e9cf] |

|dw.sapBWP_DVEBMGS00[S](ThStart()+0x263)[0x4e6bb3] |

|dw.sapBWP_DVEBMGS00[S](DpMain+0x38d)[0x191544d] |

|libc.so.6[S](__libc_start_main+0xe6)[0x7f7d88376c36] |

----------------------------------------------------------------------------------------------------

本作品采用知识共享署名 4.0 国际许可协议进行许可

SAP——BWP跑数报错：2020-03-27 BWP报错：The memory quest for 4056 bytes could not be for com

文章评论