SAP Note 460268 - Could not find stored procedure

Note 1152240 - Setting Up Microsoft SQL Server 2008 (R2)

Header

Version / Date 83 / 2013-01-14

Priority Recommendations/additional info

Category Special development

Primary Component BC-DB-MSS Microsoft SQL Server

Secondary Components

Summary

Symptom

This SAP note provides information about the following:

Setting up and running SQL Server 2008 or SQL Server 2008 R2 for an SAP system

Upgrading SQL Server 2000 or SQL Server 2005 to SQL Server 2008 (R2).

Upgrading SQL Server 2008 to SQL Server 2008 R2.

In this note, SQL Server 2008 (R2) - with (R2) written in parentheses - means that the information applies to both SQL Server 2008 and SQL Server 2008 R2.

Reason and Prerequisites Always download the latest version of this note since it contains important and up-to-date information.

When using SQL Server 2008 (R2) with your SAP system, you must follow the instructions of the guide:"Upgrade to and Installation of SQL Server 2008 in an SAP Environment".You can download the guide from SAP Service Marketplace at:http://service.sap.com/instguides -> Database Upgrades -> MS SQL Server.For practical reasons, we call this guide "Upgrade and Installation Guide" in this SAP note.

RDBMS media for SQL Server 2008 (R2):You normally obtain the SQL Server 2008 (R2) RDBMS media as part of the installation package from SAP. However, you can also download it at:http://service.sap.com/swdc -> Installations and Upgrades -> A-Z index -> <first letter of your product> -> <your product version>If your SAP product was initially not released for SQL Server 2008 (R2), you might not not find it there. In this case, use the material number of the SQL Server 2008 (R2) RDBMS media and search for it. For more information about the material number, see SAP note 1144459.

For all SAP systems running on SQL Server 2008 (R2), apply at least the following patch levels of the DBSL library. Otherwise, serious problems occur in transports, upgrades and EHP installations.The minimum patch levels are:

- Kernel Release 7.00 ------> 188

- Kernel Release 7.01 ------> 23

- Kernel Release 7.10 ------> 132

- Kernel Release 7.11 ------> 16

- Kernel Release 7.20 ------> no restriction

For more information, about how to download kernel patches, see SAP note 19466.

To run your SAP J2EE system based on SAP NetWeaver 7.0 (or 7.0 EHP1, 7.0 EHP2) on SQL Server 2008 (R2), your system must run with the "Microsoft SQL Server JDBC Driver" version 1.2.  Use the instructions in SAP note 639702 to check your JDBC driver version and

SAP Note 460268 - Could not find stored procedure

Summary

apply SAP note 1145221 to replace your DataDirect JDBC driver by the "Microsoft SQL Server JDBC Driver" or

apply SAP note 639702 to patch your "Microsoft SQL Server JDBC Driver" to version 1.2.

For the installation or system copy of a high-availability SAP  system on Windows Server 2008 (R2), make sure that you follow the  Windows Server 2008 (R2) steps specified in the High Availability  section of the installation guide, and in SAP note 1490337.

Before you plan to install or upgrade your SAP system on SQL Server, read SAP note 1076022, which informs about the supported SAP and SQL Server 2008 (R2) release combinations.

For a BI system, read the following BI-specific notes before you use SQL Server 2008 (R2):

- 1126568: Enable star join optimization with SQL Server 2008 (R2)

- 991014: Vardecimal compression/row compression for BI on SQL Server

SolutionCONTENT:

       I    INSTALLING AN SAP SYSTEM ON SQL SERVER 2008 (R2)       II   SYSTEM COPY ON SQL SERVER 2008 (R2)       III  SAP UPGRADE AND SAP EHP INSTALLATION ON SQL SERVER 2008(R2)       IV   CREATING A MODIFIED INSTALLATION MASTER DVD       V    TROUBLESHOOTING       VI   FREQUENTLY ASKED QUESTIONS

I    INSTALLING AN SAP NETWEAVER SYSTEM ON SQL SERVER 2008 (R2):

Installing SAP Netweaver CE 7.2 systemsInstall SAP Netweaver CE 7.2 systems as described in the installation guide.

Installing SAP systems based on SAP Netweaver 7.1 EHP1 (7.11)If you have a Java system, proceed as described in the installation guide for your SAP product.

If you have an ABAP or ABAP+Java system, perform the following steps after you have finished the installation:

Patch your runtime libraries as described in SAP note 684106.

Apply the latest DBSL patch.

Installing SAP systems based on SAP NetWeaver 7.1 When SAP Netweaver 7.1 was originally released, SQL Server 2008 (R2) was not available and not supported by SAP. Therefore, you cannot use the installation DVDs that you received from SAP or downloaded from SAP Service Marketplace to install your SAP system on SQL Server 2008 (R2).

If you have a Java system, you have to use a modified Installation Master DVD. For more information, see section "IV Creating a modified Installation Master DVD".

If you have an ABAP or ABAP+Java system, you initially have to install on SQL Server 2005 and then upgrade to SQL Server 2008 (R2).Proceed as follows:

a) Install your SAP system on SQL Server 2005.

b) Apply the required SAP_BASIS and SAP_BW support packages.

c) Patch your runtime libraries as described in SAP note 684106.

d) Apply at least the SAP kernel patch defined at "Reason and Prerequisites".

SAP Note 460268 - Could not find stored procedure

Summary

e) Upgrade the database release to SQL Server 2008 (R2) as described in the "Upgrade and Installation Guide".

Installing SAP systems based on SAP Netweaver 7.0 (including all EhPs)Install SAP systems based on SAP Netweaver 7.0 by using SWPM 1.0 SP1 or higher. For more details see SAP note 1680045.Always read the current SL Toolset release note (e.g. SAP note 1716219for SL Toolset SPS06) for more information how to find the download location for the SL Toolset software.Media:

Use the kernel/Java media defined in SAP note 1680045.

Use ABAP export DVDs of the original shipment.

                       

                       

II   SYSTEM COPY ON SQL Server 2008 (R2):

Copying SAP Netweaver CE 7.2 systemsCopy your SAP Netweaver CE 7.2 systems as described in the system copy guide for your SAP Netweaver CE 7.2 system.

Copying SAP systems based on SAP NetWeaver 7.1 EHP1 If you have a Java system, copy your Java system as described in the system copy guide for your SAP system.

If you have an ABAP or ABAP+Java system, you have to perform the following additional steps:

Patch your runtime libraries as described in SAP note 684106.

Use a modified Kernel DVDFor more information about how to create a modified kernel DVD, see SAP note 1480785.

Copying SAP systems based on SAP NetWeaver 7.1 If you want to perform a system copy of an SAP system that is based on SAP NetWeaver 7.10 on SQL Server 2008 (R2), you cannot use the Installation Master DVD that you received from SAP or downloaded from SAP Service Marketplace (SMP). Instead, you have to do the following:

Use a modified Installation Master DVDFor more information, see section "IV Creating a modified Installation Master DVD".

           If you have an ABAP or ABAP+Java system - in addition to using the modified Installation Master DVD - the following have to be done:

Patch your runtime libraries as described in SAP note 684106

Use a modified Kernel DVDFor more information about how to create a modified kernel DVD, see SAP note 1480785.

Copying SAP systems based on SAP Netweaver 7.0 (including all EhPs)Copy your SAP system using SWPM 1.0 SP1 or higher.For more information see SAP note 1680045.Always read the current SL Toolset release note (e.g. SAP note 1716219for SL Toolset SPS06) for more information how to find the download location for the SL Toolset software.Media:

SAP Note 460268 - Could not find stored procedure

Summary

Use the kernel media defined in SAP note 1680045.

IMPORTANT:After the successful system copy procedure of SAP system in SQL Server 2008 (R2), configure the SQL Server system  as described in SAP Note 1237682.

ABAP/ABAP+JAVA: Before performing a system copy of your SAP system, make sure that you have applied the required Basis SP level defined in SAP note 1076022.

III   SAP UPGRADE AND SAP EHP INSTALLATION ON SQL SERVER 2008 (R2)

This procedure applies to both:

Upgrades to SAP systems based on SAP Netweaver 7.1 EHP1

EHP installations to SAP systems based on SAP Netweaver 7.0 EHP1 or SAP Netweaver 7.1 EHP1

Perform the following steps before you start the upgrade or the EHP installation:

1. Make sure that your SAP system runs at least on the dbsl-patch level defined at "Reason and Prerequisites" above.

2. Provide a patched SAP kernel for your target system as follows:Download from SAP Service Marketplace the latest kernel SAPEXE_<patch>-<xxxxxx>.SAR and SAPEXEDB_<patch>-<xxxxxx>.SAR for your source release and for your target release to the download directory (<your download directory>) that you use for your SAP upgrade/EHPI.

IV   CREATING A MODIFIED INSTALLATION MASTER DVD

a) Copy the SAP NetWeaver Installation Master DVD to a <Local_Directory>.

b) Download the control.xml file for your SAP system that is attached to this note and extract it.

For SAP Netweaver 7.1 based systems, download control_710.zip

For SAP Netweaver CE 7.1 systems, download control_710_CE.zip

c) Change to the  <Local_Directory> where you have copied the SAP NetWeaver Installation Master DVD.

d) Replace the control.xml file with the downloaded one.

e) The control.xml file is located in the following directory on the installation Master DVD

For SAP Netweaver 7.1 based systems, you find it in:<Local_Directory>\DATA_UNITS\<platform>\NW07\WEBAS\IND

For SAP Netweaver CE 7.1 systems, you find it in:<Local_Directory>\DATA_UNITS\<platform>\CE71\WEBAS\IND

V   TROUBLESHOOTING

Problem: During a system copy of a SAP NetWeaver 7.0 SR3 based system, the execution of procedures fails, usually when executing procedure sap_z_collector. This is due to the fact that you copy a system of basis 7.00 but at a support package level that does not support SQL Server 2008 (R2).

Solution: Apply at least basis support package level 14 on the source system, and then repeat the system copy procedure.

Problem: By default, the SQL Server 2008 failover cluster is installed with Kerberos authentication on both Windows Server 2003 and

SAP Note 460268 - Could not find stored procedure

Summary

Windows Server 2008. On Windows Server 2003, after the SQL Server 2008 failover cluster installation has completed successfully, the SQL Server 2008 cluster group fails to start if the Kerberos authentication is not used in your active directory domain.

Solution: To bring the SQL Server group online, perform the following steps in your system:

a) In the Cluster Administrator tool, right-click the resource "SQL Network Name" and select "Properties".

b) Select the "Parameters" tab.

c) Disable the "Enable Kerberos Authentication flag".

d) Start the SQL Server Group resources in the order "SQL Network Name", 'SQL Server", and "SQL Server Agent".

VI. FREQUENTLY ASKED QUESTIONS

1. How to apply SQL Server 2008 (R2) service packs to failover cluster.

a) Download the Service packs and Cumulative updates for SQL Server 2008 (R2)

b) First apply the Service Pack and Cumulative updates to the Passive Node ( Note: The node where SQL Server currently not running is referred as Passive Node)

c) Move the SQL Server Group to the node that was updated with service packs.

d) Verify that all SQL Server resources are online on the currently active node.(Note: The node where SQL Server currently running is referred as Active Node)

e) If SAP system is already installed, start the SAP system and make sure you can connect to the SAP system.

f) Now install the Service packs and Cumulative updates to the current Passive Node.

g) Make sure you can failover the SQL Server Group to the updated node.

h) If SAP system is already installed, start the SAP system and make sure you can connect to the SAP system.

Affected Releases

Software Component Release From Release To Release And subsequent

SAP_BASIS 70 700 702

SAP_BASIS 71 710 720

Related Notes

1496520 SQL Server: Sick message after homogeneous system copy

1490337 High Availability SAP System on Windows Server 2008 (R2)

1427804 RSDU_TABLE_TRUNC_PARTITION_MSS -ALTER TABLE SWITCH failed

1377270 NOT NULL-columns missing defaults

1291861 SICK message: Wrong long datatypes

1260968 COPYTOSHADOW: R3trans loses reports

1161733 SQL Server: SAP EHPI for SAP NetWeaver 7.0

1145221 JDBC driver exchange to Microsoft JDBC Driver

1144459 SAP Installation Media and SQL4SAP for SQL Server 2008 (R2)

1141630 RSDU_TABLE_TRUNC_PARTITION_MSS -ALTER TABLE SWITCH