When exploring log files, we found the following message:
20210910/020052.101 - 37 U00009907 Memory dump '(BINDPAR: 1)' (Address='n/a', Length='000004')
20210910/020052.102 - 37 00000000 0000076C >...l<
20210910/020052.102 - 37 >1900<
20210910/020052.102 - 37 U00009907 Memory dump '(BINDPAR: 2)' (Address='n/a', Length='000004')
20210910/020052.103 - 37 00000000 00000770 >...p<
20210910/020052.103 - 37 >1904<
Is there a way to explain the "Memory dump" message?
This a normal message that can be ignored. It is displayed when a Time Critical DB call longer than 2 seconds is reporting which bind parameters where used.
You will see that each time "U00009907 Memory dump '(BINDPAR: %n)' is followed by a bind parameter 2 lines below between >%b<
The fact that it mentions "Memory dump" is confusing but there is no Forced Trace.
Release : 12.3
Component : JWP / JCP
The following message structure in the JWP/JCP logs should be ignored:
U00009907 Memory dump '(BINDPAR: %n)'
There is NO memory dump, the JWP/JCP is only reporting the bind parameters of Time Critical DB call.
In the example below a bind parameters (1078186886) is passed for the parameter AUSR_AH_Idnr. This is particular for the Time Critical calls in Java processes.
47 - 20210902/115703.851 - 50 U00009907 Memory dump '(BINDPAR: 1)' (Address='n/a', Length='000004')
47 - 20210902/115703.851 - 50 00000000 4043D386 >@CÓ.<
47 - 20210902/115703.851 - 50 >1078186886<
47 - 20210902/115703.866 - 50 U00003525 UCUDB: ===> 'SELECT AUSR_CAdr,AUSR_Tz_Sess,AUSR_Tz_Oh,AUSR_NameDept,AUSR_Lang,AUSR_Client,AUSR_OH_Idnr,AUSR_AH_Idnr,AUSR_Ewonly,AUSR_Meldopt,AUSR_Aclmsg,AUSR_Srv_Adm,AUSR_Sysmsg,AUSR_RemoteId FROM AUSR WHERE AUSR_AH_Idnr = ?'
47 - 20210902/115703.898 - 50 U00003434 Server routine 'FlushUserAction/USER_UPD' required '0' minutes and '9' seconds for processing.