Здравствуйте! Появилась вот такая ошибка после переезда на 64bit систему.

Динамическая ошибка START_CALL_SICK
Дата и время 05.12.2008 09:05:22
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|КрТекст |
| Database inconsistency: Start Transaction SICK. |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Что произошло? |
| 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. |
| - |
| |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Что Вы можете сделать? |
| 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. |
| |
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Анализ ошибки |
| The error probably occurred when installing the |
| R/3 system. |
| Error message of the error that appeared first: |
| "DB CHECK Wrong long datatypes. Perform SQL2005 after upgrade steps. Please see |
| note 126973". |
----------------------------------------------------------------------------------------------------

Информация о месте прерывания |
| The termination occurred in the ABAP program "SAPMSYST" in |
| "D020_SNC_CHECK_EXTID". |
| The main program was "SAPMSYST ". |
| |
| The termination occurred in line 1765 of the source code of the (Include) |
| program "SAPMSYST" |
| of the source code of program "SAPMSYST" (when calling the editor 17650).

ошибка вроде как появилась после того как я исправил ошибку COMPURE_INT_TIMES_OVERFLOW.

В продуктиве пока её не исправлял и проблем с SICK нет.

У меня данный дамп появлялся после того, как подправил параметры памяти и рабочие процессы отваливались из-за нехватки памяти. Запусти транзакцию SICK, посмотри, что она напишет.

DB CHECK Wrong long datatypes. Perform SQL2005 after upgrade steps. Please see note 126973


Severe problems were detected during initial system check.
Please, do not use that system before fixing these problems.

Нота 126973 по данной ошибке ссылается на ноту 799058. Смотрите...

это я знаю. как я понял надо выполнить пункт III из этой ноты.


If you use SAP NetWeaver 2004s (7.0) or higher, there is an SAPinst option to perform migration steps. Only use this option, if the basis release of your source system is also 7.0.

For basis releases 4.6C, 6.20 or 6.40 perform the following steps:

1. Apply all available SAP basis support packages for your release.
2. Shut down the SAP system.
3. For ABAP systems with basis release 6.40 or earlier: Drop SAP stored procedures in the database with the stored procedure "sap_droproc" as described in section II above.
4. Make sure that the source server and database collations are set to SQL_Latin1_General_CP850_BIN2. For more information about how to check and change this, see SAP note 600027.
5. Detach the SAP database from the source server using sp_detach_db (or use the Enterprise Manager).
6. Install a new instance of Microsoft SQL Server 2005 on your target system. In some cases you will use the same physical server. This is the case, for example, when changing from a 32-bit SQL server 2000 to a 64-bit SQL server 2005 on the same host. In this case you can uninstall SQL Server 2000 and then install SQL Server 2005 with the same instance name.
Use the SQL4SAP.vbs script for the installation, if possible. If not, make sure that you select the collation option:
"Binary order based on code point comparison, for use with the 850 (Multilingual) Character Set."
7. If you migrate to a new physical server you must install a new SAP instance on that server that matches your source system release. If your system stays on the same server, this step is not necessary.
8. If the source and target server are different, you have to copy the database files of your database from your source server to the target server and attach them to your SQL Server 2005 database either with sp_attach_db or the SQL Server Management Studio for SQL Server 2005. The target database may be created under a different name, which is normally the same as the target system ID.
9. Download the zipfile that includes the SAP tools for MS SQL Server from SAP Service Marketplace. Extract it to a local (empty) folder on the central instance server. Run sapinst.exe, and choose "Database Copy". This option performs the required post-upgrade steps for all SAP products running on SQL Server 2005.
It is not necessary to run any other option, in particular do not run the "Schema Conversion" option for 4.6C systems. It is recommended to still run 4.6C systems under the 'dbo' schema.
10. Apply the latest kernel and dbsl_lib patches from SAP Service Marketplace for your release before you start the SAP system. SAP 4.6C systems must use the 4.6D executables and SAP 6.20 systems running with SQL Server 2005 must use the 6.40 executables. This is required for all application servers. Also install the Microsoft runtime DLLs as described in SAP note 684106.
11. If you use a Java system, update the JDBC driver as described in SAP note 639702.
12. Start the SAP system.
13. Execute the following commands in the SQL Server 2005 Management Studio (connect with a db administrator login):
----------------------------------------------
use <SID> -- where <SID> is your SAP database
go
EXEC sp_updatestats
go
----------------------------------------------
It takes some time to replace the old SQL Server 2000 index statistics with new SQL Server 2005 statistics. You can run this while the SAP system is online.


Я переехал одного сервера на другой. с sql 2000 на sql 2005.

пункт 1 пропускаю.
3 пункт выполнил.
4 у меня collation SQL_Latin1_General_CP850_BIN2.
5,6,7,8 пункты вополнял ещё при установке.
9 пункт предлагают всё сделать через Database copy?
10 - надо скачать последний kernel и lib_dbsl?
11 - Java я не использую.
13 пункт уже делал отдельно без предварительных шагов.

не помогло.

Попробуйте внимательно почитать пункт 9. Там говорится, что надо скачать zip-файл, разархивировать его в чистую директорию и запустить оттуда sapinst.exe и он выполнит пост-апгрейдные действия. т.е. он не предлагает заново скопировать систему...
ЗЫ: я никогда не имел дела с серверами на MS SQL, так что могу подсказывать только на уровне логики...

только вот что за zip файл надо скачать? sap tools? что то на маркетплэйсе найти не могу его.

Нота 683447
===
You can download the latest version of the SAP Tools for MS SQL Server from SAP Service Marketplace at: service.sap.com/msplatforms -> SQL Server.
===

большое спасибо. всё получилось)