Database inconsistency: Start Transaction SICK.

[Former Member]

Hi,

I just finished doing a system copy using the R3load procedure, after the copy i am getting the following error upon logon, does anyone know how to correct the error. The system in 4.7 and the database is MS SQL 2000

Database inconsistency: Start Transaction SICK.

What happened?

The current program had to be terminated because of an

error when installing the R/3 System.

The error occurred when initializing the R/3 System.

-

What can you do?

Please call the Transaction SICK. The list generated here

contains an installation error.

Make a note of the actions and input which caused the error.

To resolve the problem, contact your SAP system administrator.

You can use transaction ST22 (ABAP Dump Analysis) to view and administer

termination messages, especially those beyond their normal deletion

date.

Error analysis

The error probably occurred when installing the

R/3 system.

Error message of the error that appeared first:

"Can't execute sap_check_if_sick".

How to correct the error

Report the error to the group responsible for installing your

R/3 System.

You may able to find an interim solution to the problem

in the SAP note system. If you have access to the note system yourself,

use the following search criteria:

"START_CALL_SICK" C

"SAPMSYST " or "SAPMSYST "

"D020_SNC_CHECK_EXTID"

[Former Member]

Hi Juan,

there are a lot of sp procedures and tables that are missing in the database how do i go about recreating these. i have recreated some of the sp procedures using the MSSPROCS report

[JPReyes]

Hi Trevor,

Check the kernel version, try installing the latest kernel for that SAP version/OS/DB,

Also check that MS Loopback Adapter,

Regards

Juan

Please reward with points if helpful