SICK: SAP Initial Inconsistency Check



Share this article :

Transaction code sick is to determine inconsistencies in the system. When logging on to the system for the first time, you need to trigger a consistency check manually. The function is then called automatically whenever you start the system or an application server.

SICK: SAP Initial Inconsistency Check

1. The initial consistency check determines whether:

• The release number in an SAP kernel matches the release number stored in the database system.
• The character set specified in the SAP kernel matches the character set specified in the database system.

Note:

• Transaction code SICK is same with the transaction code SM28.

Tags:

Related posts

SAP License Installation
RBDLSMAP_RESET: Reset/Remove Table Entries after BDLS
Create Oracle Control File for SAP System Refresh
BPC Transport: Environment status not offline; cannot export/import transport request
© 2018 ITsiti. All Rights Reserved
Powered by KEEM