Error in DB rollback/SyFlush, return code 016384

[Former Member]

Dear Experts,

We are running on our PRD system our Z report and the session was terminated with the following messages:

SM21:

BZ Y Unexpected return value 1 when calling up DbSlR

BY J Function ROLLBACK on connection R/3 failed

R3 9 Error in DB rollback/SyFlush, return code 016384

Q0 2 Stop Workproc 4, PID 13828220

R4 7 Delete session 001 after error 023

We checked trace file thru SM50:

M Thu Nov 10 10:22:57 2011

M *** WARNING => ThCheckReqInfo: req_info & DP_CANT_HANDLE_REQ

M *** ERROR => ThSysAdmMsg: ThAdmSend [thxxab.c 7598]

M *** WARNING => ThCheckReqInfo: req_info & DP_CANT_HANDLE_REQ

M *** ERROR => ThSysAdmMsg: ThAdmSend [thxxab.c 7598]

M *** WARNING => ThCheckReqInfo: req_info & DP_CANT_HANDLE_REQ

M *** ERROR => ThSysAdmMsg: ThAdmSend [thxxab.c 7598]

M

M Thu Nov 10 10:23:19 2011

M ***LOG US1=> Login, Wrong Password (TRHOFIADM ) [sign.c 4539]

A

A Thu Nov 10 10:54:10 2011

A WP has reached abap/heaplimit = 40894464 bytes

A

A Thu Nov 10 10:55:28 2011

A *** ERROR => User HOTDSBC reached avail. heapsize = 1907 MB: see ST22 [abstor.c 1779]

A *** ERROR => Increase abap/heap_area_total [abstor.c 1780]

A *** ERROR => heap memory WP0: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP1: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP2: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP3: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP4: 1907 MB [abstor.c 1784]

A *** ERROR => heap memory WP5: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP6: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP7: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP8: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP9: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP10: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP11: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP12: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP13: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP14: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP15: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP16: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP17: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP18: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP19: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP20: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP21: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP22: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP23: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP24: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP25: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP26: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP27: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP28: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP29: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP30: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP31: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP32: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP33: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP34: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP35: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP36: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP37: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP38: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP39: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP40: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP41: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP42: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP43: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP44: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP45: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP46: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP47: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP48: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP49: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP50: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP51: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP52: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP53: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP54: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP55: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP56: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP57: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP58: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP59: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP60: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP61: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP62: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP63: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP64: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP65: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP66: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP67: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP68: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP69: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP70: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP71: 0 MB [abstor.c 1784]

A *** ERROR => heap memory WP72: 0 MB [abstor.c 1784]

A

A Thu Nov 10 10:55:29 2011

A TH VERBOSE LEVEL FULL

A ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.

A ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.

A ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.

A ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.

A ** RABAX: level LEV_RX_SAVE_SHMLOCKS entered.

A ** RABAX: level LEV_RX_SAVE_SHMLOCKS completed.

A ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.

A ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.

A ** RABAX: level LEV_RX_ROLLBACK entered.

C *** ERROR => Call to DbSlRollbackDB6 while DBIF already active in DbSlExeReadDB6

[dbsldb6.c 596]

B ***LOG BZY=> unexpected return code 1 calling DbSlRollba [dbcon#11 @ 3127] [dbcon 3127 ]

B ***LOG BYJ=> database function ROLLBACK for connection R/3 failed [dbcon#11 @ 3130] [dbcon 3130 ]

B *** ERROR => DISTRIBUTED_TA_FAILED:

[dbcon.c 1694]

B 000: name = R/3, con_id = 000000000, state = ACTIVE , tx = NO , hc = NO , perm = YES,

B reco = NO , frco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO

M ***LOG R39=> ThIRollBack, db_rollback ( 016384) [thxxhead.c 13737]

M in_ThErrHandle: 1

M *** ERROR => ThIRollBack: db_rollback (step 4, th_errno 18, action 2, level 1) [thxxhead.c 10633]

M ThResetEmMagic: reset em magic for T213/M0/I1

M

M Info for wp 4

M

M pid = 13828220

M severity = 0

M status = 0

M stat = WP_RUN

M waiting_for = NO_WAITING

M reqtype = DP_RQ_DIAWP

M act_reqtype = DP_RQ_DIAWP

M rq_info = 0

M tid = 213

M mode = 0

M len = 8

M rq_id = 44991

M rq_source = FROM_WP_CA

M last_tid = 213

M last_mode = 0

M semaphore = 0

M act_cs_count = 0

M csTrack = 0

M csTrackRwExcl = 0

M csTrackRwShrd = 0

M mode_cleaned_counter = 0

M control_flag = 1000000

M int_checked_resource(RFC) = 0

M *****************************************************************************

M *

M * LOCATION SAP-Server tstprd02_P01_80 on host tstprd02 (wp 4)

M * ERROR ThIRollBack: db_rollback

M *

M * TIME Thu Nov 10 10:55:29 2011

M * RELEASE 700

M * COMPONENT Taskhandler

M * VERSION 1

M * RC 18

M * MODULE thxxhead.c

M * LINE 10853

M * COUNTER 7322

M *

M *****************************************************************************

M

M PfStatDisconnect: disconnect statistics

M Entering TH_CALLHOOKS

M ThCallHooks: call hook >SAP-Trace buffer write< for event BEFORE_DUMP

M TrThHookFunc: called for WP dump

M TrStopTrace: switch off Trace for this WP

M TrFlushTrace: flush the trace buffer to file

M ThGetTransId2: got trans id (spa) >4EBB13BB438B0B40E10080000A42000E< (32)

M TrSaveFile: file can be kept (12211979/16777216 Bytes)

M TrIResetErrorAction: reset all errors for action 0

M TrWriteBuffer: 152 Bytes for block buffer

M TrBuffFlush: wrote 149347 Bytes of buffer to file

M TrWriteBuffer: 72 Bytes of block trailer

M TrIResetErrorAction: reset all errors for action 1

M TrFiICheckIndex: check index SAP-Trace tracefile list at 7000003d030b820

M TrFiICheckIndex: check record in slot 0

M TrFiICheckIndex: check record in slot 1

M TrFiICheckIndex: check record in slot 2

.

.

.

.

.

.

.

C *** ERROR => Call to DbSlDisconnectDB6 while DBIF already active in DbSlExeReadDB6

Please advise.

We are on AIX 6.1 DB297FP3

Regards,

Rudi

[Former Member]

Hi,

* ERROR => ThSysAdmMsg: ThAdmSend [thxxab.c 7598] M M Thu Nov 10 10:23:19 2011 M ***LOG US1=> Login, Wrong Password (TRHOFIADM ) [sign.c 4539] A A Thu Nov 10 10:54:10 2011 A WP has reached abap/heaplimit = 40894464 bytes A A Thu Nov 10 10:55:28 2011 A *** ERROR => User HOTDSBC reached avail. heapsize = 1907 MB: see ST22 [abstor.c 1779] A *** ERROR => Increase abap/heap_area_total [abstor.c 1780] A *** ERROR => heap memory WP0: 0 MB [abstor.c 1784] A *** ERROR => heap memory WP1: 0 MB [abstor.c 1784] A *** 

It seems that your SAP buffer parameters pertaining to heap memory are not perfectly tuned to match you program requirement.

Consider modifying values of following SAP buffer parameters using tcode RZ10

abap/heap_area_dia

abap/heap_area_nondia

abap/heap_area_total

Hope this helps.

Regards,

Deepak Kori

[Former Member]

Hi Deepakkori and SAP Database,

Thanks for your reply, i also have the same perception with you at first regarding heap memory error mentioned, however this error occurred when select only 10 days data selection but there's no error occurred when i select 1 month data selection which is larger space needed, the report showed up successfully.

Anyway, the heap memory settings are as follow:

abap/heap_area_dia 2000683008

abap/heap_area_nondia 2000683008

abap/heap_area_total 2000683008

Any idea?

Regards,

Rudi

[Former Member]

Hi,

You should not set these parameters as SAP has introduced zero memory management in which its no more required to set these parameters. What is your OS and DB version ?

Thanks

Sunny

[Former Member]

Hi Sunny,

We use AIX 6.1and DB2 9.7 FP3

Regards,

Rudi

[Former Member]

Hi Rudi,

Try to modify the parameters as shown below. Take R3 restart and check out the results.

In case you excute the program in foreground :

======================================

abap/heap_area_dia 6000683008

abap/heap_area_nondia 2000683008

abap/heap_area_total 8000683008

In case you execute the program in background

======================================

abap/heap_area_dia 2000683008

abap/heap_area_nondia 6000683008

abap/heap_area_total 8000683008

Hope this resolves your issue.

Regards,

Deepak Kori

[Former Member]

Hi Deepak Kori,

Thanks for your suggestion, we consider to have a down time since this is a productive system.

Regards,

Rudi

[Former Member]

I will suggest you check the st22 for the relevant error show the dump error + the point the program stopped to the abaper to see if he has insight in this problem. then check the db2diag.log at the time the error happened to find more regarding the error.

[Former Member]

Hi Henry,

There's no warning nor error message in db2diag.log and i also have pasted st22 error dump in the above.

Regards,

Rudi

[former_member189725]

The problem clearly seems to be an issue with heap memory and the SAP session terminates as the fetch from the database extends the internal table which actually exhauts the heap memory limit for the dialog work process thus leaving no more memory available to the process.

Please make sure you have enough extended memory allocated (em/total_size_mb)and use the special extended memory implementation in AIX.

An SAP work process should not use heap memory normally as 64 bit platforms has practically no restriction on the value of extended memory to be set. The use of heap memory which actually ties up a work process to work on behalf of only 1 user context should generally be avoided . When you run the application which gives the dump, please check ST02 to see how much of extended memory is being utilized . If there is a huge consumption of memory make sure you ask the developer to recheck the code to see if there can be any lesser volume of fetch into internal tables in the memory.

Edited by: Ratnajit Dey on Nov 17, 2011 6:31 PM

[Former Member]

Seems a heap memory problem, could you check the sap profile parameters and db parameters as well, using dbm cfg and db cfg

Thanks