SAP HANA – rename system, part 1/2
SAP HANA system can be renamed by changing the system identifiers, like host names, SID and instance number. Below You find information how to do this…
Read MoreSAP Security Notes Summary – December 2021
Traditionally once a month I’ll publish review all SAP security notes and news that were released in a given month. SAP Security Notes contain SAP’s expert advice regarding important action items and patches to ensure the security of your systems.
Read More
SAP – CVE-2021-44228 Apache Log4j Vulnerability
SAP continues to investigate the remote code execution vulnerability (CVE-2021-44228) related to Apache Log4j disclosed on Dec 10, 2021. SAP encourages customers to update to the latest version of Log4j, where applicable. Check regularly updated detailed information in SAP site – here. Additional information about vulnerability in HANA XS and AS Java Core Components.
Read MoreSAP HANA – Prefetch timed out error
When You run a replication task or an activity of large tables in HANA Smart Data Integration sometimes You receive below error:
[119944]{352621}[136/-1] 2021-XX-09 09:55:04.182041 e MonitorView DPAdapterLocationsMonitor.cc(00196) : Request for adapters' configuration for agent : 'AGENT_NAME' failed with error :
[115205]{350872}[146/-1] 2021-XX-09 09:57:05.163932 i TraceContext TraceContext.cpp(01269) : UserName=USERNAME, ApplicationUserName=USERNAME, ApplicationName=sap.hana.im.dp.monitor.jobs::scheduleTask, ApplicationSource=sap.hana.im.dp.monitor.jobs:ScheduleObject.xsjs::doScheduleObject, StatementHash=b04ef094eb43b5643057befc019e3123, StatementExecutionID=844438624279623
[115205]{350872}[146/-1] 2021-XX-09 09:57:05.163917 e DPAdapterManager AdapterManager.cpp(04668) : ::sendMessage: Prefetch timed out.
[115205]{350872}[146/-1] 2021-XX-09 09:57:05.164020 e FedTrace DPAdapterAccess.cpp(02401) : DPAdapterAccess::ExecuteQuery: failed with error: Prefetch timed out.
Read More
SAP PO – How to enable a handling of large messages in the Messaging System
You have to remeber. Concurrent processing of large messaging in the messaging system queue could lead to out of memory errors due to heap being exhausted. A message is considered to be #large# if it exceeds the threshold for large messages. In order to be processed, the message must have a specific number of permits (the number of permits is the message size divided by the threshold).
Read More