2444016 - START_CALL_SICK occurs after migration | SAP Knowledge Base Article

SAP Knowledge Base Articles - preview

2444016 - START_CALL_SICK occurs after migration


A new SAP system (based on Netweaver) is firstly installed. Then, another database's backup is used to restore this newly installed system. After restoring,  dump D020_SNC_CHECK_EXTID occurs when logging on to the system by SAP GUI.

The following errors shows in developer trace file:

 "FASTFIRSTROW" is not a recognized table hints option. If it is intended as a parameter to a table-valued function or to the CHANGETABLE function, ensure that your database compatibility mode is set to 90.
 Incorrect syntax near the keyword 'with'. If this statement is a common table expression, an xmlnamespaces clause or a change tracking context clause, the previous statement must be terminated with a semicolon.
 C Error 99 (dbcode 321) in StartSelect
 C StartSelect: stmt of NULL_STMTID
 C EXEC sap_check_if_sick
 A *** ERROR => Can't execute sap_check_if_sick [sapicc.c 1327]



Netweaver systems based on Microsoft SQL Server 2005 or higher.


SAP NetWeaver 7.0


D020_SNC_CHECK_EXTID, sap_check_if_sick, START_CALL_SICK, SAPMSYST , KBA , BC-DB-MSS , SQL Server in SAP NetWeaver Products , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.