cancel
Showing results for 
Search instead for 
Did you mean: 

Is SQL Server 2005 RTM supported with kernel 721?

Former Member
0 Kudos

Hi, Gurus:

We are trying to upgrade the kernel of a customer from their current release (700 SP 254) to the newer release 721.

Their platform is:

OS: Microsoft(R) Windows(R) Server 2003 Enterprise x64 5.2.3790 ServicePack 2 Build 3790

DB: MS SQL Server 2005 - 9.00.1399.06 (X64) # RTM Enterprise Edition

SAP_BASIS+SAP_ABA: Release 700 SP22

According to the PAM, kernel 720 and 721 (not the EXT versions, though) should support this platform, however, when we upgrade the kernel

following the instructions of note "1713986 - Installation of kernel 721(EXT)" a runtime error START_CALL_SICK occurs. The error message states:

"DB release MSSQL 09.00.1399.06 is not supported with this kernel (721)"

Kernel 720 has the same problem (we have tried latest SAPEXE and disp+work packages available in the marketplace).

According to http://support.microsoft.com/kb/321185, build 1399 stands for SQL Server 2005 RTM.

If we take a look to this dump and any other dump of a SAP system for any of our customers running an 720/721 kernel (even those using SQL Server 2012) you can see the line:

Database............. "MSSQL 9.00.2047 or higher"

According to http://support.microsoft.com/kb/321185 build 2047 stands for SQL Server 2005 Service Pack 1.

Since running SICK/SM28 executes report RSICC000 which, in turn, calls Cfunction SAPICC, that is an internal C function coded inside the kernel.

We suspect that when kernel 720 was compiled, the SQL 2005 release was set to 9.00.2047 instead of 9.00.1399, but we don't know whether this

was an error or it was done on purpose, requiring SP1 to be installed on the database in order to run kernel 720/721.

We have checked SAP Note 1716826 - Usage of the downward compatible kernel 721 (EXT) (and related 1728283, 1744209, 1467086 and 1636252) butthe only statement is:

"The SAP kernel 721 is intended for Microsoft SQL Server 2005 and higher"

, without any reference about the SP level/build level.

Have you found this problem before?

Any advice will be appreciated.

Best Regards,

José

Accepted Solutions (1)

Accepted Solutions (1)

divyanshu_srivastava3
Active Contributor
0 Kudos
We suspect that when kernel 720 was compiled, the SQL 2005 release was set to 9.00.2047 instead of 9.00.1399, but we don't know whether this

That is why you have new kernel patches.

Let me check on this, I will get back to you.

Regards

Former Member
0 Kudos

Thanks for your answer.

We have tried both kernel 720 and 721 with the latest patches available (namely SAP Kernel 721 patch level 325 released on 2014-09-19) and the error is exactly the same.

Regards,

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi Jose,

I believe you should goto SQLServer 2005 Service Pack 1 - 9.00.2047.

RTM are base releases and should be updated.

As a work around, you can play with the registry value from where this is picking the database version, make it what this is looking for, but that is not a solution.

So, you have to get upto SP1 or higher, infact best time to rub you hands and update your database.

Regards

Sriram2009
Active Contributor
0 Kudos

Hi Jose

Before you are get in to new kernel upgrade either MS Sql 2005 latest service pack  refer the SAP Note for Service pack 62988 - Service packs for MS SQL Server


Regards

Sriram

Sriram2009
Active Contributor
0 Kudos

Hi Jose

Follow the steps for install the new kernel release either 720 or 721 as mention in the SAP Notes

1636252 - Installing a 7.20 kernel in SAP Web AS 7.00/7.01/7.10/7.11


1713986 - Installation of kernel 721 (EXT)


BR

SS

Former Member
0 Kudos

Thanks for your reply:

I agree DB should be upgraded, but it is out of the scope of the project unless I can find evidence (SAP OSS Note/instalation guide/Help document) that RTM is not supported by 721 kernel. I opened this thread hoping to find such evidence.

I will try to change the registry value only to check whether the problem is DB release alone and not any other cause (Basis SP, for example).

Do you know where does the check look for DB patch level? I have always assumed that it is stored in the internal resource database and it is accessed through DBSL with an stored procedure.

I know for sure that key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\Setup\PatchLevel does not affect the DB Release seen by SAP.

Regards,

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi Jose,

That is just to check. As wrote before, this is not a solution.

Also, for version query, I refer this note.

http://service.sap.com/sap/support/notes/1402538

Regards

Sriram2009
Active Contributor
0 Kudos

Hi Jose

RTM - is very beginning release of MS Sql 2005, after you are updated the service pack it will be normal version of MS Sql 2005. Kindly refer the link you can find the more information about MS Sql version

Microsoft SQL Server Version List

BR

SS

Former Member
0 Kudos

Hello:

Indeed, note "62988 - Service packs for MS SQL Server" v78 states clearly:

You must implement at least the following SQL Server version:

                                                                                                                                                                                                                                                                                                                                                  

SQL Server:Minimum Version
SQL Server 201211.0.3393
SQL Server 2008 R210.50.1702
SQL Server 200810.00.2531 (2)
SQL Server 20059.00.3042 (**) (1)
SQL Server 20008.00.2039 (*)
SQL Server 77.00.1063

But since it does not mention any kernel release restriction, I didn't linked this information to the kernel change. It is not that SQL Server 2005 RTM is not supported with kernel 721, SQL Server 2005 RTM is not supported at all. It's just that kernel 700 SP 254 doesn't enforce the compliance whereas kernel 721 SP 325 does.

I hope this information is useful for you folks for planning future kernel updates.

Thank you very much and kind regards,

José

Answers (0)