realloc failed because of memory limit(rec_type=PF_RFC_CLIENT_STAT, internal_max_rec_no=1280

[former_member217468]

Hi ,

we had an issue today on our ECC system 742 patch 325 , where a batch job was on hold for couple of hours and the work process trace had the following , has anyone seen this before

M Mon May 23 19:34:03 2016

M  *** WARNING => PfRecSave: realloc failed because of memory limit(rec_type=PF_RFC_CLIENT_STAT, internal_max_rec_no=1280). [pfxxstat.c   9036]

M  {root-id=005056B325D61ED688991E36955C80FB}_{conn-id=00000000000000000000000000000000}_0

M 

M Mon May 23 19:34:07 2016

M  *** WARNING => PfRecSave: realloc failed because of memory limit(rec_type=PF_RFC_CLIENT_STAT, internal_max_rec_no=1280). [pfxxstat.c   9036]

M  {root-id=005056B325D61ED688991E36955C80FB}_{conn-id=00000000000000000000000000000000}_0

C 

Thx / Jonu

[feng_shi]

Hi Jonu,

"batch job was on hold" means the job was waiting something.

work process trace below just means that the max size of a kernel statistic entry limit reached when kernel was trying to save the RFC kernel statistic.

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

M  *** WARNING => PfRecSave: realloc failed because of memory limit(rec_type=PF_RFC_CLIENT_STAT, internal_max_rec_no=1280)

it was just a warning, harmless, which was not the root cause why batch job was on hold.

here, probably, the job on hold was waiting for RFC response.

Thanks and best regards,

Shi