Error codes during logon (list) # SAP Basis Adminstrator

 ERROR: 

1:   During an (RFC) logon, the system displays the following text:

"You are not authorized to logon to the target system (error code...)"

with an error code number whose meaning is unclear to you.

2:  You find the following unfamiliar lines in the developer trace file (dev_w..):

DyISigni: client=..., user=..., lang=... , access=..., auth=...

usrexist: effective authentification method: ....

DyISigni: return code=... (see Note 320991)

The extended trace messages (starting from trace level 2, for the "Security" component, you can activate them dynamically using transaction SM50) are available starting from the following kernel versions:

4.6D kernel starting from patch level 141

4.5B kernel starting from patch level 506

Explanation of the Error Codes/Return Codes

0 No error - successful logon

1 Incorrect logon data (client, user name, password)
2 User account is locked
3 Incorrect logon data; for SAPGUI: connection closed
4 Successful logon using virtual user or emergency super user
5 Error when constructing the user buffer (==> possible follow-on error)
6 User exists only in the central user administration (CUA)
7 Invalid user type
8 User account outside validity period
9 SNC name and specified user/client do not match
10 Logon requires SNC (Secure Network Communication)
11 No ABAP user with this SNC name exists in the system
12 ACL entry for SNC-secured server-server link is missing
13 No suitable SAP account found for the SNC name
14 Ambiguous assignment of SNC names to ABAP users
15 Unencrypted SAP GUI connection refused
16 Unencrypted RFC connection refused
20 Logon using logon/assertion ticket is generally deactivated
21 Syntax error in received logon/assertion ticket or reentrance ticket not valid
22 Digital signature check for logon/assertion ticket fails
23 Logon ticket/assertion issuer is not in the ACL table
24 Logon/assertion ticket is no longer valid
25 Assertion ticket receiver is not the addressed recipient
26 Logon/assertion ticket contains no/an empty ABAP user ID
27 Reauthorization check: ticket does not match current user
28 Ticket logon denied by security policy
30 Logon using X.509 certificate is generally deactivated
31 Syntax error in the received X.509 certificate
32 X.509 certificate does not originate from the Internet Transaction Server
34 No suitable ABAP user found for the X.509 certificate
35 Ambiguous assignment of X.509 certificate to ABAP users
36 36 Certificate is older than the date entered as "min. date" (USREXTID)
37 X.509 certificate is not currently valid
41 No suitable ABAP user found for the external ID
42 Ambiguous assignment of external ID to ABAP users
50 Password logon was generally deactivated or denied by security policy
51 Initial password has not been used for too long
52 User does not have a password
53 Password lock active (too many failed logons)
54 Productive password has not been used for too long
60 SPNego logon denied by security policy
61 Invalid SPNego token (syntax)
62 NTLM token received instead of SPNego token
63 Missing/incorrect Kerberos keytab entry
64 Invalid SPNego token (time)
65 SPNego replay attack detected
66 SPNego: Error when creating the SNC name
67 SPNego: No suitable SAP account found for the SNC name
68 SPNego: Ambiguous assignment of SNC names to ABAP users
69 Reauthentication check: SPNego token does not match current user
100 Client does not exist
101 Client is currently locked for logons
102 External WebSocket RFC communication is not allowed (RFC runtime)
103 External WebSocket RFC communication requires alias user (RFC runtime)
104 System is in maintenance mode and locked against logons
110 Tenant was stopped (runlevel STOPPED)
111 Tenant cannot be used generally (runlevel ADMIN)
112 No authorization to log on to the current logon category
120 Server does not allow logon
121 No special rights for logon on this server
300-399 OpenID connect (OIDC) error; see SAP Note 3111813
1001 Password is initial/has expired - interactive change required (RFC/ICF)
1002 Trusted system logon failed (no S_RFCACL authorization)
3000 Reauthorization check: SAML bearer assertion is not compatible with current user
3001 Internal SAML bearer assertion verification error
3002 SAML bearer assertion could not be parsed
3003 SAML bearer assertion was already used (replay)
3004 SAML bearer assertion could not be assigned to a user
3005 Issuer of SAML bearer assertion is not trusted
3006 NameID format of SAML bearer assertion is not supported
3007 Signature of SAML bearer assertion is not valid
3008 SAML bearer assertion is not valid or is no longer valid
3009 SAML is not activated or SAML bearer assertion provider is not activated

Explanations for "access" (access types):

A Dialog logon (SAP GUI)
B Background processing (batch)
C CPIC
F RFC (as of 4.6C: internal RFC)
R RFC (as of 4.6C: external RFC)
I RFC system call (internal SRFC)
S RFC system call ( [external]* SRFC) - *see SAP Note 2590963
U User switch (internal call)
H HTTP
u Restore session (ABAP class CL_USERINFO_DATA_BINDING)
" " API call (such as SUSR_CHECK_LOGON_DATA)
M SMTP authentication (MTA): Password check
P ABAP push channel (APC)/WebSockets
E Establishment of a shared memory area (internal call)
O AutoABAP (internal call)
T Server startup procedure (internal call)
V SAP start service (internal call)
J Java Virtual Machine (internal call)
W BGRFC watchdog (internal call)
G ABAP Resource Manager (internal call)
r RFC via WebSockets (external)
Y TRFC/QRFC/bgRFC (internal)

Explanations for "auth" (authentication types):

P Password-based authentication

T Logon ticket

t Assertion ticket

X Certificate-based logon (X.509, https)

S SNC (Secure Network Communication)

R Internal RFC or trusted system RFC

A Internal call via background processing, for example

E External authentication (PAS, SAML, ...)

U Inverse user switch (ABAP class CL_USER_POC)

s HTTP security session

2 SAML2

1 SAML1

o OAuth2

N SPNego

a APC session (WebSockets)

B SAML bearer

r Reentrance ticket

D OIDC logon

d OIDC bearer

List: CPIC error codes in SAP Systems # SAP Basis Administrator

 This note concerns error analysis in the network environment and CPIC return codes in particular.
The meaning of the return code numeric values is unclear.

  CPIC return codes (not SAP-specific)

  CM_OK                          0
  CM_ALLOCATE_FAILURE_NO_RETRY  1
  CM_ALLOCATE_FAILURE_RETRY      2
  CM_CONVERSATION_TYPE_MISMATCH  3
  CM_SECURITY_NOT_VALID          6
  CM_SYNC_LVL_NOT_SUPPORTED_PGM  8
  CM_TPN_NOT_RECOGNIZED          9
  CM_TP_NOT_AVAILABLE_NO_RETRY  10
  CM_TP_NOT_AVAILABLE_RETRY    11
  CM_DEALLOCATED_ABEND          17
  CM_DEALLOCATED_NORMAL        18
  CM_PARAMETER_ERROR            19
  CM_PRODUCT_SPECIFIC_ERROR    20
  CM_PROGRAM_ERROR_NO_TRUNC    21
  CM_PROGRAM_ERROR_PURGING      22
  CM_PROGRAM_ERROR_TRUNC        23
  CM_PROGRAM_PARAMETER_CHECK    24
  CM_PROGRAM_STATE_CHECK        25
  CM_RESOURCE_FAILURE_NO_RETRY  26
  CM_RESOURCE_FAILURE_RETRY    27
  CM_UNSUCCESSFUL              28
  CM_OPERATION_INCOMPLETE      35
  CM_SYSTEM_EVENT               36

Gateway error codes

  CPIC_ERROR                    221 Error in the CPIC interface
  CANT_GET_MEMORY              222 Memory bottleneck
  NI_READ_FAILED                223 Network read error
  NI_WRITE_FAILED              224 Network write error
  INVALID_REQUEST              225 Invalid request
  NOT_YET_CONNECTED            226 Not yet connected
  GW_WP_DIED                    227 Gateway process died
  SHM_READ_FAILED              228 Shared memory problem (read)
  SHM_WRITE_FAILED              229 Shared memory problem (write)
  NO_MORE_LU                    230 No available LU
  NO_MORE_WP                    231 No available gateway process
  CANT_START_WORKPROCESS        232 Error when starting the gateway process
  WRONG_COMM_TYPE              233 Wrong communication type
  CONNECT_FAILED                234 Connection setup failed
  COMM_TABLE_ERROR              235 Error in comm. table
  GW_CONNECT_FAILED            236 No connection to the gateway
  GW_DISCONNECTED              237 Connection to the gateway disconnected
  WRITE_TO_GW_FAILED            238 Error with GW comm. (write)
  READ_FROM_GW_FAILED          239 Error with GW comm. (read)
  INVALID_LEN                  240 Invalid length
  INVALID_ENVIRONMENT           241 Invalid environment
  GW_TIMEOUT                    242 Timeout
  GW_CONNECT_TO_R3              243 Error when setting up R/3 connection
  SYSTEM_DISCONNECTED          244 Partner disconnected connection
  MEM_OVERFLOW                  245 Memory overflow
  WRONG_APPCHDR_VERSION         246 Incorrect APPC header version
  GW_APPC_SERVER_DOWN          247 Loc. gateway not started
  TXCOM_TABLE_FAILED            248 Error when accessing TXCOM
  COMM_TABLE_OVERFLOW           249 Comm. table full
  C_NO_MEM                      450 No memory
  C_NO_SIDE_INFO                451 No SIDE INFO entry
  C_TP_START                    452 TP-START failed
  C_NO_INIT                    453 No initialization
  C_GETLU                      454 "getlu" failed
  C_SIGNAL                      455 "signal" failed
  C_TIMEOUT                    456 Timeout when establishing connection
  C_ALLC                        457 CMALLC failed
  C_SEND                        458 CMSEND failed
  C_PREPARE                    459 Prepare-To-Receive failed
  C_FLUSH                      460 CMFLUS failed
  C_RECEIVE                    461 CMRCV failed
  C_NO_ARGUMENT                462 Missing argument
  C_GET_ALLOCATE                463 "get_allocate" failed
  C_DEAL                        464 CMDEAL failed
  C_TP_END                      465 TP-END failed
  C_MAX_CONV                    466 Max. number conv. reached
  C_SNAOPEN                    467 "snaopen" failed
  C_SNACTL                      468 "snactl" failed
  C_NO_FLUSH                    469 No flush in IBM environment
  C_SNACLSE                    470 "snaclse" failed
  C_STATE_CHECK                471 Status error
  C_NO_SIDE_INFO_ENTRY          472 No side info entry
  C_NO_CONV                    473 No conversation
  C_MANUAL_CANCELD              474 Connection manually cancelled
  C_AUTO_CANCELD                475 Connection automatically cancelled
  C_NO_PARTNER                  476 No partner found
  C_CONFIRM                    477 Confirm failed
  C_CONFIRMED                  478 Confirmed failed
  C_NO_HOST_IN_SIDE_INFO        479 GWHOST not in side info entry
  C_NO_SERV_IN_SIDE_INFO        480 GWSERV not in side info entry
  C_NO_PROT_IN_SIDE_INFO        481 PROTOCOL not in side info entry
  C_NO_LU_IN_SIDE_INFO          482 LU not in side info entry
  C_NO_TP_IN_SIDE_INFO          483 TP not in side info entry
  C_NO_GATEWAY_CONNECTION       484 No connection to the gateway
  C_GETHOSTNAME                485 gethostname failed
  C_NO_SAP_CMACCP              486 SAP_CMACCP not executed
  C_NO_PROGRAM_NAME_ARG         487 Program not in arg. list
  C_NO_HOST_ARG                488 Host not in arg. list
  C_NO_SERV_ARG                489 Service not in arg. list
  C_NO_CONVID_ARG              490 Conv. ID not in arg. list
  C_ILLEGAL_PARAMETER           491 Illegal parameter
  C_LU62CVCT                    492 LU62CVCT failed
  C_LU62ATTACH                  493 LU62ATTCH failed
  C_NO_CONV_TABLE              494 No conv. table
  C_ILL_CONV_TABLE              495 Incorrect conv. table
  C_ILL_MOD_VALUES              496 Invalid conv. modification
  C_NIHOSTTOADDR                497 NiHostToAddr failed
  C_NIADDRTOHOST                498 NiAddrToHost failed
  C_THOST_FAILED                499 Reading table THOST failed
  INVALID_MODE                  630 Invalid mode number received
  MAX_NO_OF_GATEWAYS            631 Max. no. of gateways reached
  MISSING_LU_SPEC              632 No LU specified
  MAX_CPIC_CLIENTS              633 Max. no. of clients reached
  BAD_TPNAME                    634 Invalid TP name
  FORK_FAILED                  635 Fork failed
  BAD_NI_HANDLE                636 Invalid NI handle
  REXEC_FAILED                  637 rexec failed
  TP_START_FAILED              638 Starting the TPs failed
  NI_DG_SEND_FAILED            639 NiDgSend failed
  INTERNAL_ERROR                640 Internal error
  GW_HOST_UNKNOWN              664 Gateway host unknown
  GW_SERVICE_UNKNOWN            665 Gateway service unknown
  GW_NI_ERROR                  666 NI error
  GW_EXEC_FAILED                667 exec failed
  R2_RESTARTED                  668 R/2 restarted
  SYM_DEST_TOO_LONG            669 Symb. destination too long
  NO_MORE_SIDE_INFO_ENTRY       670 No more side info entries
  R3_LOGIN_FAILED              672 R/3 Login failed
  IMS_ERROR_PURGING            673 IMS error purging
  PENDING_TERM_OUTPUT          674 Timeout of reg. programs
  GW_SECURITY_ERROR            676 TP not registered
  GW_TIMEOUT_REG_PRGM          677 Timeout of registered program
  TP_REGISTERED                678 TP is registered
  TP_NOTREGISTERED              679 TP not registered
  TP_REG_SECU_ERROR            720 Security violation for reg. prgrms
  GW_SNC_DISABLED              721 SNC deactivated
  GW_SNC_REQUIRED              722 SNC required
  GW_SNC_NAME_NOT_SET           723 SNC name not defined
  GW_SNC_NAME_NO_DEFAULT        724 Default SNC name not permitted
  GW_SNC_PROT_NOT_SUPP          725 Log does not support SNC
  GW_R3_NOT_CONNECTED          726 No local R/3 system
  GW_SNC_REQUIRED_FOR_LU_TP     727 SNC required
  CONV_ID_NOT_FOUND            728 Conversation ID not found
  GW_SNC_SECURE_PORT            729 Comm. must make SNC
  GW_SNC_START_EXT_DIS          730 Start of ext. Program deactivated
  GW_SHUTDOWN                  731 Gateway was shut down
  GW_REM_PRGM_DISABLED          732 No external programs
  GW_STOLEN_CONVID              733 Conversation ID does not fit
  GW_NET_CONV_ERROR             734 Net Conv Error
  GW_MONITOR_DISABLED           735 Monitor not active
  GW_DUPLICATE_CVID            736 Conv. ID not unique
  GW_CONNECT_TIMEOUT            737 Timeout of connection setup to remote system
  GW_REQ_TO_DP_FAILED          738 Request could not be transferred to the dispatcher
  GW_CLIENT_ALREADY_DISC        739 Connection partner has already disconnected the connection
  GW_NO_HOST_IN_ROUTE           740 No hosts contained in route
..GW_ROUTE_CONNECT_DIS          741 Route already disconnected (no longer used)
  GW_CONN_IS_FREE              742 Connection already released
  GW_CONN_IS_DISC              743 Connection disconnected
  GW_REQBLK_ADM_ERROR           744 Error in request processing
  GW_BUFINFO_ERROR              745 Error in buffer handling
  GW_HDLINFO_ERROR              746 Error in network handling
  TP_REG_NOREG_ERROR            747 Number of registrations exceeded for this program
  TP_REG_ACCESS_DENIED          748 Access to registered server denied
  GW_PARAM_NOT_FOUND            749 Parameter could not be found
  GW_PRXY_ACCESS_DENIED         750 Gateway must not be used as a proxy
  GW_ACCEPT_TIMEOUT            751 Timeout when logging on (gw/accept_timeout)
  GW_WRONG_SERVER              752 not connected to the gateway
  C_NO_SIDE_INFO_GW            760 No side info file
  C_RECEIVE_WITH_PAR            761 CMRCV failed
  C_NO_SNC_LIB_ARG              762 SNC library not in arg. list
  C_NO_SNC_NAME_ARG            763 SNC name not in argument list
  C_SNC_INV_HANDLE              764 SNC invalid handle
  C_SNC_DISABLED                765 SNC deactivated
  C_SNC_ERROR                  766 General SNC error
  C_SNC_MODE_ON                767 SNC required
  C_SNC_NOT_AVAILABLE           768 SNC not available
  C_ILLEGAL_PARAMETER2          769 Invalid parameter
  C_AREA_TOO_SMALL              770 Memory area too small
  C_SNC_INV_STATE              771 Invalid SNC status
  C_RETURN_CODES                772 Error numbers
  C_REG_STATE_CHECK            773 Status violation during registration
  C_CPICTERR                    774 Error text for error number
  C_NO_SYMDEST                  775 No symbolic destination
  C_FUNCTION_NOT_SUPPORTED      776 Function not supported
  C_NET_CONV_ERROR              777 Conversion error when reading or writing data
  C_SIDEINFO_DISABLED          778 Access to side info file deactivated
  C_TIMEOUT_BLOCK              779 Timeout for blocking network call
  C_FAILOVER_ERROR              780 Error when communicating with failover software
  C_PROXY_ERROR                781 Error when communicating with the proxy server
  C_MPI_ERROR                  782 Error when communicating with memory pipes (Mpi)
  C_MTX_ERROR                  783 Error with lock management (mutex)
  C_CS_ERROR                    784 Error with lock management (critical section)

FAQ: SAP HANA Native Storage Extension (NSE)

1: How can I activate NSE?

NSE can be activated via DDL commands on the desired tables. There are no additional configuration steps needed.

2. I have activated NSE for a database object but want to revert my changes. How can I achieve this?

Changes to database objects can be reverted by setting the load granularity to default.

ALTER TABLE "<table_name>" DEFAULT LOADABLE;

Adding the option CASCADE allows to overwrite all modifications on the below layers:

ALTER TABLE "<table_name>" DEFAULT LOADABLE CASCADE;

 

3. Where do I find information about buffer cache usage?

Information on the buffer cache usage such as hit ratio and size can be obtained in the following locations:

• M_BUFFER_CACHE_STATISTICS
• M_BUFFER_CACHE_POOL_STATISTICS
• SQL: "HANA_NSE_BufferCache" (SAP Note 1969700)
• M_SQL_PLAN_CACHE (starting SAP HANA 2.0 SPS07, columns *_BUFFER_CACHE_IO_READ_SIZE, *_BUFFER_CACHE_PAGE_MISS_COUNT and *_BUFFER_CACHE_PAGE_HIT_COUNT)
• SQL: "HANA_SQL_SQLCache_2.00.070+" (SAP Note 1969700)

4. How can I calculate the memory consumption of NSE enabled tables?

As explained in question #1, pages of NSE tables, when loaded into memory, are loaded into the buffer cache. Some helper structures for the columns are still loaded into the main store area of HANA and reside there until the column is unloaded.
After reading an NSE table, its non-pageable area will be loaded to the main store memory, while the pageable area will be loaded into the buffer cache. If, just after this read, you check the memory consumption for the table, the value will be the sum of main store memory and the memory occupied in the buffer cache. Keeping in mind the nature of the Buffer Cache, you will understand that the allocation in the buffer cache is transient. As soon as another NSE table is read, those pages loaded into the buffer cache may be displaced in a least-recently used fashion. Or they may stay there for longer, if there is enough space in the buffer cache to accommodate both tables. Given the transient characteristic of the pages loaded into the buffer cache, for the purpose of determining memory savings brought by NSE, this memory area should not be considered for the definition of the total memory allocated by the NSE table.

SQL: "HANA_Tables_ColumnStore_TableSize_2.00.030+" (SAP Note 1969700) reports the NSE-related memory consumption in column PAGED_GB.

5. Where is the buffer cache located?

The buffer cache is stored in the heap allocator Pool/CS/BufferPage. The allocator always resides in DRAM. This also applies to systems using PMEM or Fast Restart Option.

6. How does the buffer cache behave during memory pressure?

The NSE Buffer cache is not unloaded as part of shrink operations. As a result, the memory used by the NSE cache cannot be released and be reused by other components in case the database runs out of memory.

To avoid memory issues, the buffer cache should be configured with a reasonable size depending on the size of tables located in NSE.

7. How to handle NSE advisor recommendations to move columns like $trexexternalkey$ or $AWKEY_REFDOC$GJAHR$?

$trexexternalkey$ or $AWKEY_REFDOC$GJAHR$ are internal columns (SAP Note 1986747) that refer to the primary key respectively a multi-column index/concat attribute. Indexes can be moved to NSE as well.

a) identify index name:

SELECT SCHEMA_NAME, TABLE_NAME, INDEX_NAME, INDEX_TYPE, CONSTRAINT FROM INDEXES WHERE TABLE_NAME = '<table_name>';

b) change the index load granularity

ALTER INDEX "<schema>"."<index_name>" PAGE LOADABLE;example: ALTER INDEX "PLAYGROUND"."_SYS_TREE_CS_#170484_#0_#P0" PAGE LOADABLE;

 

8. How can I get information on the impact of NSE on query performance?

Starting SAP HANA 2.0 SPS07 monitoring view M_SQL_PLAN_CACHE contains several additional columns  that provide deeper insight on NSE usage during query execution (*_BUFFER_CACHE_IO_READ_SIZE, *_BUFFER_CACHE_PAGE_MISS_COUNT and *_BUFFER_CACHE_PAGE_HIT_COUNT).

The following sql commands in SAP Note 1969700 exist to support the investigation:

• SQL: "HANA_SQL_SQLCache_2.00.070+" 
• SQL: "HANA_SQL_SQLCache_TopLists_2.00.070+" 

9. Does DDIC support NSE?

Since S/4 HANA 2021, DDIC supports load unit settings "Page Preferred" and "Page Enforced". Depending on the S/4 HANA release, these settings can change.
The current configuration can either be checked via SE11 -> "Technical Settings" -> "DB-Specific Properties".
Alternatively, you can query the details directly in DBACOCKPIT via the following SQL:

select
    t.TABLE_NAME, t.LOAD_UNIT HDB_LOAD_UNIT,
    CASE WHEN d.LOAD_UNIT = 'P' THEN 'Page Preferred'
      WHEN d.LOAD_UNIT = 'Q' THEN 'Page Enforced' END DDIC_LOAD_UNIT
FROM
    TABLES t full outer join DD09L d ON t.table_name = d.tabname
WHERE
    (t.LOAD_UNIT = 'PAGE' OR d.LOAD_UNIT IN ('P', 'Q')) AND t.SCHEMA_NAME LIKE 'SAP%';

For further details on DDIC integration, please see SAP Note 2973243.

10. When are DDIC load unit settings applied and what happens if an upgrade changes the DDIC load unit?

Whether load unit settings are applied automatically depends on the scenario:

1. When converting from anyDB to SAP S/4 HANA, the DDIC load unit is applied in the course of the migration, tables with "page preferred" and "page enforced" are created using NSE.
2. A fresh installation of S/4 HANA 2021+ is performed. The DDIC load unit is applied directly during installation.
3. A conversion from Suite on HANA to S/4 HANA or a S/4 HANA upgrade does not enforce DDIC load unit settings. In this scenario only exchange tables are created with the new settings. The load unit setting of existing tables will be preserved. Only a change to "Page Enforced" will result in a load unit change on the database. Other SAP_BASIS objects with load unit "Page Preferred" such as BALDAT, CDPOS, and EDID4 stay as is and will not be automatically changed.

11. Do I need additional disk space when using NSE?

During conversion to page loadable, the persistence structures are rewritten for optimal usage with NSE. In most cases, this does not change the total amount of disk space needed. However, in rare cases tables, partitions, and columns that are converted to NSE may see an increased disk usage up to 80 %. Some column data types (like TIMESTAMP, DATE, CHAR, VARCHAR and NVARCHAR) do not support all possible dictionary compressions if columns are stored as page loadable.

12. Is the buffer cache preloading data after a system restart just like the normal column store does?

No, the buffer cache will be empty after restart and only be populated on demand.

Note: 

Please refer to the SAP note to get full details. 

2799997 - FAQ: SAP HANA Native Storage Extension (NSE)

what is SAP HANA Native Storage Extention? #Data Archiving

SAP HANA 2 SPS 04 provides a new feature called SAP HANA Native Storage Extension (NSE). NSE is a disk-based extension to the in-memory COLUMN STORE in SAP HANA. Instead of loading a whole column, only the needed pages are loaded into the buffer cache when accessing the data.

SAP HANA Native Storage Extension (NSE) is a general-purpose, built-in warm data store in SAP HANA that lets you manage less-frequently accessed data without fully loading it into memory. It integrates disk-based or flash-drive-based database technology with the SAP HANA in-memory database for an improved price-performance ratio. 

SAP HANA offers various software solutions to manage multi-temperature data (hot, warm, and cold), such as DRAMs for hot data and SAP HANA Extension Nodes, SAP HANA dynamic tiering for warm data, and SAP HANA Cold Data Tiering for cold data. 

Hot data is used to store mission-critical data for real-time processing and analytics. It is retained continuously in SAP HANA memory for fast performance and is located in the highest performance (and highest TCO) storage. 

Warm data is primarily used to store mostly read-only data that need not be accessed frequently. The data need not reside continuously in SAP HANA memory, but is still managed as a unified part of the SAP HANA database ― transactionally consistent with hot data, and participating in SAP HANA backup and system replication operations, and is stored in lower cost stores within SAP HANA. 

Cold data is used to store read-only data, with very infrequent access requirements. You manage cold data separately from the SAP HANA database, but you can still access it from SAP HANA using SAP HANA’s data federation capabilities. This image shows the difference between standard HANA in-memory storage and the storage offered with NSE:

The capacity of a standard SAP HANA database is equal to the amount of hot data in memory. However, the capacity of a SAP HANA database with NSE is the amount of hot data in memory plus the amount of warm data on disk.

Since growth in data volume results in increased hardware costs, the ability to decouple data location from a fixed storage location (layer) is one of the key themes of a multi-temperature data storage strategy.

NSE is integrated with other SAP HANA functional layers, such as query optimizer, query execution engine, column store, and persistence layers. Key highlights of NSE are:

• A substantial increase in SAP HANA data capacity, with good performance for high-data volumes.
• The ability to co-exist with the SAP HANA in-memory column store, preserving SAP HANA memory performance.
• An enhancement of existing in-market paging capabilities by supporting compression, dictionary support, and partitioning.
• An intelligent buffer cache that manages memory pages in SAP HANA native storage extension column store tables.
• The ability to monitor and manage buffer cache statistics via system views.
• The ability to support any SAP HANA application.
• A simple system landscape with high scalability that covers a large spectrum of data sizes.
• An advisor that collects object access statistics and provides column store object load unit recommendations.

 

How to check SAP Application log Statistics with help of Program "SBAL_STATISTICS" ? # SAP Basis Administrator

To check SAP Application log statistics you can use the program "SBAL_STATISTICS," you can utilize the reporting capabilities it provides for analyzing and obtaining detailed statistical information about application logs generated by various applications within SAP. This program serves as a useful tool for effectively monitoring and managing log entries.

Based on the findings from the SBAL_STATISTICS report, administrators may decide to clean up old logs, adjust logging levels, or take corrective actions on applications based on the insights derived from the statistics of application logs.

Accessing the Program

You can access the program through Tcode "SA38", as shown below

Click on execute and select the statistic collection option as per requirement. 

STATISTIC COLLECTIONS

TIME CREATION: 

get the number of logs for every month in a year, how many logs are in each month

CLIENTS :

get the number of logs for every client, how many logs are in each client

OBJECTS, Subobject, messages :

detailed overview based on OBJECT and SUBOBJECT of logs

columns:

• OBJECT, SUBOJECT (defined in TCODE SLG0)
• MIN DATE - the oldest creation date ( highlighted field is older than 180 days)
• MAX DATE - the latest creation date ( highlighted field is older than 180 days)
• Logs Cnt - number of logs
• MsgCnt All - number of messages
• MsgCnt E, W, I, S, A - number of message with type Error, Warning, Information, Success, Cancel
• reached exp date - number of logs they reached expiry date and can be deleted via option SLG2 - only logs that have reached their expiration date
• and can be deleted - number of logs can be deleted via option SLG2 - And logs that can be deleted before the expiration date
• cannot be deleted - number of logs cannot be deleted via option SLG2 - Non-deletable logs (display only). Such logs can be deleted only be the application that created the logs.
• never expire - number of logs that expity date is set to 31/12/9999
• % - number of % logs in current client.

USERS: 

get the number of logs for every user

PROGRAMS: 

get the number of logs for the program

TCODE: 

get the number of logs for TCODE

EXPIRATION DATE: 

get the number of logs for each option of Expiration Date (SLG2)

- Only logs that have reached their expiration date

- And logs that can be deleted before the expiration date

- Non-deletable logs (display only)

RELID data, BALDAT: 

get number records with different RELID in BALDAT

Statistic logs

to view data select Option and click on Execute. 

You can view log details under Details as shown below.

Documents referred : 2524124 - Application log Statistics

Data Management Guide forSAP Business Suite

How to Switch HANA alerts off/on with SQL Statement ?

 we can switch off the underlying alert checker, so it no longer runs automatically or you can switch it back on again using the following methods:

• HANA 1.0 SPS12

• HANA 2.0 SPS00 and higher

If you need to disable or enable these alerts in batch (more than one at once), the easy way is to manipulate STATISTICS_SCHEDULE (_SYS_STATISTICS).
STATISTICS_SCHEDULE Table (Embedded Statistics Service)
Statistics schedule per host. This view contains information only for the last 7 days.
 

Caution
If you switch off alerts, you may not be warned about potentially critical situations in your system.
Be careful when modifying data on SYSTEM_STATISTICS through SQL Script.

For example: You want to disable all the schedules for the alerts shown in both HANA Cockpit > Configure Alerts / HANA studio > Alerts. Run the following statement:

UPDATE _SYS_STATISTICS.STATISTICS_SCHEDULE SET "STATUS" = 'Inactive' where "ID" between 1 and 710

In case you want to activate them back to the original schedule, you can run the following statement:

UPDATE _SYS_STATISTICS.STATISTICS_SCHEDULE SET "STATUS" = 'Idle' where "ID" between 1 and 710

You can build your own scripts and procedures for this purpose. For example, to save the current status of the alerts to restore later or to just disable a few alerts for a given maintenance window.

 

How to check Web dispatcher version in web ? #Sap Basis Administrator

To check the version of SAP Web Dispatcher using various methods, users can log into the SAP operating system and execute specific commands or access the web interface.​ These methods ensure accurate identification of the version currently in use.

1. Command Line Method

One effective way to check the Web Dispatcher version is by executing the command sapwebdisp -v in the command prompt after logging in as the administrative user13. This command will display the version information directly, ensuring that you are aware of what is currently operational.

2. Accessing the Work Directory

Another method involves navigating to the "work" directory of the Central Instance (CI), typically located at /usr/sap/SID/DV*/work, where you can open the file named dev_desp. The first line of this file will indicate the release version of the Web Dispatcher being used.

3. Using the Web Admin Interface

For those preferring a graphical user interface, one can check the version through the SAP Web Dispatcher admin URL. By clicking on “Release information” within the Web Dispatcher administrative interface, it should display the current version.

 4. Monitoring Through Administration Tools

Additionally, administrators can monitor the SAP Web Dispatcher version and its status using command line programs like icmon. This method provides a continuous report on the current state of the Web Dispatcher46.

5. Verifying via Process Information

Lastly, confirming the Web Dispatcher version can also be achieved by checking system-level processes. Using the command ps -ef | <searchRefSen indexList="30,60" order="4" >grep webdisp can reveal which Web Dispatcher instance is running, including its kernel version in use</searchRefSen>.

  

Menu Functions - Administration of Work Processes in SM50 #SAP Basis Administrator

System Administration in SM50

The most important administration tasks are listed for reference below:

Managing Work Processes

• Terminate ABAP Program
• Debug ABAP Program
• Display Active Processes
• Display Details of a User
• Display Details of a Process
• Delete Session
• Terminate Process (With or Without Core)
• Start Process After Error/Termination Automatically
• Cancel Request Processing
• Display System-Wide Process List
• Reset Terminations
• Reset the Info Area

Trace Functions / Analysis

• Create Snapshot
• Snapshot Administration
• Write C Stack
• Manage Dispatcher Trace File
• Display Trace File
• Download Trace File
• Change Trace Components
• Configure Trace File Display
• Reset Trace File

  

Note: To use these functions, you first need to select at least one work process.

•  Cancel a process:

Administration  Process  Cancel  With Core/Without Core

The work process is terminated at operating system level. The Dispatcher starts a new work process with a new PID (provided you have configured the system appropriately) “Start Process After Error/Termination Automatically”). You can create a core file when the process is terminated for analyzing later. You can display the core file in transaction .RZ11

• Start Process After Error/Termination Automatically:

Administration  Process  Restart After Error   Yes/No.

If a process is terminated due to an error, it can be restarted automatically. The default is Yes.

• Debug a running ABAP program.

Administration  Program  Debugging

This function can only be executed if you have selected a work process in which an ABAP program is currently running. You can find the report name in the Active Program column. Note that you need “debug and replace authorization”, which is controlled by authorization object S_DEVELOP together with OBJTYPE 0 DEBUG and ACTVT = 02

• Terminate a running ABAP program:

Administration  Program  Cancel

This function can only be executed if you have selected a work process in which an ABAP program is currently running. You can find the report name in the Active Program column. If a program is terminated, a short dump is generated.

• Deleting an ABAP session:

Administration  Delete Session

You can delete the running ABAP session without having to close the work process.

• Display system-wide process list:

Goto  System-Wide List (or icon: . )

You can switch to the system-wide process list from the process overview of an individual instance.

With the icon you can also go to the system-wide process list.

• Display details of a process:—

Goto  Process Information (or icon: .)

Here you can display detailed information on memory statistics, database statistics, SQL statements, runtime, application, and specific attributes of the process.

• Display details of a user:

Goto  User Info

You can display information on the user here. To manage users go to the User Overview (transaction SM04).

In the process overview, you cannot be sure that a user session you want to terminate or delete is still active in the work process that you have chosen. You could therefore unintentionally affect another user's session.

• Reset Terminations:

List  Reset  Failures.

This counter is displayed in the column overview in column Failures (Work Process Failures). It specifies how often the work process has been restarted because of an error or a manual restart.

• Reset information area:

List  Reset  Info Area.

Resetting the info area is useful if, for example, dynamic work processes have been added or removed in the meantime.

 

What is the use of SAP Web Dispatcher in SAP Landscape?

 #use of SAP Web Dispatcher in SAP Landscape

#SAP Web Dispatcher functionality in SAP systems

The SAP Web Dispatcher serves as a pivotal component within the SAP landscape, primarily acting as a reverse proxy that optimizes the flow of HTTP(S) requests. Its key functions include load balancing across application servers, enhancing security features, and acting as an intermediary between clients and the SAP system.

1. Acting as an Intermediary

The SAP Web Dispatcher functions as a bridge between the internet and the SAP system, efficiently forwarding incoming HTTP(S) requests to the appropriate application servers while returning backend responses to clients127. This role is crucial for ensuring that requests are managed effectively within the SAP architecture.

2. Load Balancing

One of the primary uses of the SAP Web Dispatcher is to balance the load across multiple application servers in the SAP landscape. It ensures an even distribution of incoming requests, thereby optimizing resource utilization and preventing any single server from becoming overwhelmed48. The dispatcher employs various algorithms, including dynamic load balancing, to assess capacity and allocate requests accordingly8.

3. Enhancing Security

The SAP Web Dispatcher significantly enhances security by enforcing the use of HTTPS for secure connections and allowing URL filtering to restrict access to sensitive areas of the system8. It also manages SSL configurations, facilitating secure communications and protecting critical data from potential threats48.

4. Flexibility and Configuration

The dispatcher offers configurability, allowing it to be tailored to specific SAP landscapes, including ABAP and Java systems8. It can be deployed in front of multiple SAP systems, which is beneficial for organizations that require centralized traffic management48.

5. Caching and Performance Improvement

Additionally, the SAP Web Dispatcher can act as a web cache, which helps improve response times by storing frequently accessed content and reducing the load on application servers4. This feature enhances overall system performance and contributes to quicker response times for end-users.

​In summary, the SAP Web Dispatcher plays a vital role in managing HTTP(S) traffic, load balancing, and enhancing security within the SAP landscape, making it essential for optimizing system performance and reliability.

 

 

SAP Web Dispatcher: Release, Installation, Patches, Documentation

# Know which version is supported for your scenario and where to find the software.

# Find the online documentation of SAP Web Dispatcher.

 About SAP Web Dispatcher

SAP Web Dispatcher is a load balancer and reverse proxy that can be used with different web application server backends:

• SAP NetWeaver Application Server ABAP
• SAP NetWeaver Application Server Java
• SAP HANA XS, both in the "Classic" and "Advanced" flavor
• Any web server

Note: HANA XS Classic and HANA XS Advanced come with an internal Web Dispatcher of version 7.53. This note does not apply to this internal HANA Web Dispatcher. It cannot be used as a load balancer or reverse proxy for other systems. It is not possible to upgrade the Web Dispatcher version inside these products.

Selecting a SAP Web Dispatcher Version

SAP Web Dispatcher version 7.93 is recommended for most deployments.

SAP Web Dispatcher is downward compatible; the newest SAP Web Dispatcher can be used with all older backend systems.

If the recommended version is not supported on your operating system then pick the highest SAP Web Dispatcher version that is supported. See section Supported Operating Systems below.

We recommend the SAP Web Dispatcher version to be greater or equal to the kernel version of your backend system. The patch level is not relevant. If you have to use a SAP Web Dispatcher version that is lower than the kernel of your backend system some features of the AS ABAP may not be not available.

We recommend using the most current SAP Web Dispatcher patch level. There is no concept of "stack kernel" in SAP Web Dispatcher.

 

Additional notes:

• For details on SAP Web Dispatcher versions, corresponding product versions, release notes, incompatible changes, maintenance schedule and documentation,
• Incompatible changes: 
• There are no incompatible changes in SAP Web Dispatcher 7.89 and 7.85 with respect to 7.81.
• SAP Web Dispatcher 7.81 contains some slightly incompatible changes of configuration parameters with respect to version 7.77. See the section "Upgrade to the current version from earlier versions" below for details.
• SAP Web Dispatcher 7.73 and 7.77 contain some slightly incompatible changes of configuration parameters with respect to version 7.53. See the section "Upgrade to the current version from earlier versions" below for details.

• Supported operating systems: The latest SAP Web Dispatcher supports the operating systems Linux on x86 and PPC LE, Windows and AIX. If you have to deploy SAP Web Dispatcher on another operating system then use the highest version that supports that operating system. See the section "Supported Operating Systems for SAP Web Dispatcher Versions".

• Unicode: The Unicode SAP Web Dispatcher supports both Unicode and non-Unicode backend systems.

• The Product Availability Matrix (PAM) of some older SAP products lists outdated versions of SAP Web Dispatcher (e.g. for SAP NetWeaver). Please disregard such information of the PAM and follow the recommendation of this note instead.

Updating SAP Web Dispatcher

We generally recommend using the SAP Web Dispatcher with the most current patch level of the used version. The update is done simply by exchanging the executables. You may update SAP Web Dispatcher to the latest patch level of the currently installed version or to a different version. There is no automated upgrade procedure for SAP Web Dispatcher.

Online Documentation for the SAP Web Dispatcher

Navigate to http://help.sap.com

-> Enter "ABAP Platform and SAP NetWeaver" into the search field
-> Select the first link
-> Select the desired version
-> Application Server ABAP Infrastructure 
-> Components of Application Server ABAP
-> SAP Web Dispatcher

 

 SAP Web Dispatcher Versions, Corresponding Product Versions, Release Notes, Maintenance Schedule and Documentation

SAP Web Dispatcher is always delivered as part of another SAP product. The SAP Web Dispatcher release notes are part of that product. The following table helps you identify the corresponding product and release notes. SAP Web Dispatcher release notes are found under the topic "Application Server Infrastructure".

This table indicates which minimum version of SAP Web Dispatcher to use with a certain SAP product version. For details see section "Selecting a SAP Web Dispatcher Version" above.

The maintenance schedule of the SAP Web Dispatcher is identical with the SAP Kernel. The maintenance end dates can be read from the notes referenced in the table below. The other information in the notes regarding which kernel can be used with which S/4HANA or NetWeaver release cannot be applied to SAP Web Dispatcher. See section "Selecting a SAP Web Dispatcher Version" above.

The release notes for both BC-CST-WDP and BC-CST-IC are relevant for SAP Web Dispatcher unless the feature explicitly applies only to Internet Connection manager (ICM).

 

Profile Parameter Changes (*)

 

Reference document : 

908097 - SAP Web Dispatcher: Release, Installation, Patches, Documentation

Administration of Application Server ABAP