ID” 2200882. Mss: Additional Information - Software Update Manager 1.0 SP16 Version 2 Validity: 24.02.2016 - active Language English (Mester) Header Data ReleasedOn 24.02.2016 080432 Release Status Released for Customer Component —_BC._DBMSS Miciosott SAL Sever Other Components BC-UPG-RDM README: Upgrade Supplements Priority Recommendations (Additonal fo Category Workaround of missing funcionalty ‘Symptom Information for al lifecycle management procedures supported by SUM SP16 (Sofware Update Manager SP16) on MS SQL Server. Other Terms: ‘SUM, upgrade, update, opi, enhancement package instalation, SP, support package instalation, MS SQL Server, MSS Reason and Prerequisites Enfor in procedures supported by SUM SP16 ‘Solution ‘This note contains information about MS SQL Server specific problems. [tis constantly updated. Therefore, make sure that you always read it immediately before the upgiade. Contents 1 Important General iniormation 2 Correction tthe Guides, 3. Preparing the EHP 4 Problems During the Preparation '5 Problems During the instalation @ Problems After the Instalaton 7 Poslsteps required after SUM Date [Section |Description 2eiMai/i2 [2 __|schema/user mismatch 2QiAp110 |[3__|SQLCMD must be instaled 19INovoe|3___[MAIN_NEWBASITABIM_POST oiAug10|3 tf execdbscript OtiMar12 [3 | Setting endronment variables O1iMarr12 |4 [Phase MSSCONCHECK falls 28ian/10 |S [Problem with SNOTE siSepi08|5 | UPGRADE/DEPLOYMENT_BASED_UPGRADE/START_J2EE_DEPL 17idu09 [5 [SQL Server deadlocks 1IFobi10|5__|UPGRADE;DEPLOYMENT_BASED_UPGRADE/START J2EE_DEPL 2a/Apr10 |S ___|Abap runtime ecrors 2ikdani11 |S [Phase PARMVNT_SHD fails. Zikunt |S |Phase START-I2EE-DUAL-STACK fall 1OApII2|5 [Phase EXCHANGE_MSS_JDBC_DRIVER 12/Sep/14|5 [OSL call failed for MSSUPGGETREL in phase PREP_PRE_CHECKINITPUT_PRE| 30/Mayii1 6 __|ST22 may show cuntime errors ‘oaiiul12 [7 |mssjdbc folder missingin B0/Sep15|7 __ [SQL Server Windows service is not started + important Genera intormation«+ Please read SAP Note 62988 to find out the minimal SQL Sarver patch levels required for executing the SUM tool Before you slat the SUM tool, make sure thatthe erwironment varable auh_shadow_upgrade is nol set inthe erwronment, (No such ‘erwvronment variable should est, neither in stem nor in user envaronmert) Furthermore, do not set any environment variables (¢¢.auth_shadow_uparade, __) manually during the upgrade procedure unless you are ‘explicitely insirucied to do 50, (Aso do not mistake inlormatonal messages ike Emaronment vanable 15 nol set as a request set the variable) Start release 700, ABAPIABAP-JAVA: ‘the general basis SP level of your source system is lower than SP 16, the SAP EHP! tool changes the class CL_SQL_METADATA_MSS of your (productive) source system during the update procedure by patching this single class to the level of SP 17_ This should not damage your system buts the only way to guarartee a successil construction of your shadow system, which is needed forthe update procedure + Start release 7 0x, ABAP/ABAP-Java: wien updating an SAP system based on 70 you might encounter problems in phase PARMVNT_SHD because indexes are generated with SOL syntax ofincompatible SOL Server version ‘AS workaround, proceed as described in SAP note 1551087, 2, Correction to the Gulges 3. Preparing he EPH! ‘26Marchi2012 ABAPIABAPSIAVA, SQL Servet 2005 o higher: Make sure that there is no schema/user mismatch of your SAP ABAP system. Check this by executing the SQL query use select schema_id'"), user_id(') via SOL Sarver Management Stucio (replace by the lowercase sapsystemname) ihe returned values are differen, you have a schema/user misinalch. In this case please proceed as described in note 108037 to repair ‘is mismatch |fthe mismatch is not cortected, in phase TABSPC_PREP wrong (100 huga) tables are chosen for cloning. Ths wil later lead to extremly ong runiimes forthe phases MAIN_SHDIMP/SUBMOD CP2SHD/TP_ACTION_CP2STAB and MAIN_SWITCHITP_ACTION_CP2STRIG. See note 1656672 for futher explahations. 23/Apriv2010 ABAPIABAPHIAVA: ‘SQLCMD must be instalied on the central instance host as a prerequisite for any update (ENP instalation) of an SAP system running on SQL Server 2005 and higher. Especialy in case of a distnbuted SAP system (|e. database instance and central instance are not running onthe: Same host), SQLCMD might not be installed when folowing the SAP instalauon documertaton. SQLCMD Is part of the "Feature Pack for Microsoft SQL Server" and can be downloaded at hitps aww microsoft com/downloadideails aspx7id=18748 (for SQL Server 2006) ~ install Instructions » Microsoft SQL Server 2005 Command Line Query Utility hitps aww microsoft comidownloadidetalls aspx7id-~30440 (for SAL Server 2008) > Install Instructions » Microsoh® SQL Server® 2008 R2 Command Line Unites hips. saww. microsoft. comidownloadidetails.aspx7id=29005 (for SQL 2012)- instal Instructions -» Microsoft® SOL Server® 2012 Command Line Utlties hitps aww. microsoft. comidownloadidetails.aspx?id=26433 (for SQL 2014) You can check whether SQLCMD 1s installed by caling the folowing command from the command tine sajemd 7 ‘SQLCMD shows the version atthe beginning ofthe output, e.g. Version 9.00.4035.00 NT AMD64, |fsqicma can stil nat be found, check ithe palh to soicind (usualy %ProgramPiles*%é\Microsoft SQL Serveri -adm's environment ine phase should run through ‘5 Problems During the instalation + 2alJanuary/2010 Target release 70x, ARAP- Extraction SQL Server is on release 2008 or higher During the implementation of SAP notes via SNOTE, you might encounter runtime error DBIE_RSQL_SOL_ERROR in ABAP program SAPLSEMFB, include program LSEMFBUO7, function CLM_CWB_NOTE_FUNC_SAVE The faling statement is: 30000002 insert progdir from wa_progdir. “The database error text is: 30000002 "Mictosofl[SQL Server Native Client 10 0{SQL Server|Cannot insert the value NULL into column MAXLINELN, table REPOSRC;, column does not allow nuls. INSERT fails “To sole this problem, praceed as descnbed in SAP note 1377270. Then repeat he note application. 08/Septemberi08 ‘Targel release 701, ABAP+JAVA, Phase UPGRADE/DEPLOYMENT_BASED_UPGRADEISTART_J2EE_DEPL ‘Yourmight get the folowing error "Could not start AS Java instance with name J2EE and number ofthe standard system, ‘To soe the problem, do the folowing = Change tothe EHPLairectory"\SYSiexe\' contain entries like 3 ETP399 CREATE 3 ETP309 INDEX /BOBF/OBM_NCAT-CTK] ON [/BOBFIOBM_NCAT-] 3 ETP399 ([NODE_CAT_KEYI) 3 ETP399 WITH PAD_INDEX = OFF 3ETP309 2WETPO00 10:36:59. Retcode 1: error in DDL statement for ‘IBOBFIOBM_NCAT" - repeat DEETP345 10:37 11: Retcode 1: SQL error"156 {Microsof[SGL Native ClienSQL Serverncorrect syntax near the keyword "OFF DDL statement for NBOBFIOBM_NCAT Proceed as described in SAP note 1551067. 21/June!2014 ABAPHIAVA, SUM phase START J2EE-DUAL-STACK falls Start of Java instance fails because the SSL service cant be started. ‘This!s caused by a problem on the dalabase level. Because of outdated statisics @ bad access planis taken fora select on UME_STRINGS. Therefore, this select and he assaciated tread in the application server gets Blocked, To solve the problem, proceed as follows Slap the applicabon server, ~ Staft SOL Server Management Stu ‘open a query window, and executeUundate statistics SAPSID=DB UME_STRINGS WITH FULLSCAN (ahere is the SAP system ID). ~ Start he application server “Repeat the SUM-phase 1 12 AVA During the execution of the JDBC driver exchange procedure for SAP systems based on SAP NetWeaver 7.0 (and alts Enhancernt Packages), the driver exchange execition (phase EXCHANGE_MSS_JDBC_DRIVER) may end during the instance bootstrap with te folowing exception cam sap engine bootstrap. SynchrorizationException: Database initialization failed! Check database props! Proceed as described in SAP note 1700482. + 1a'Sepi2014 (OSOL cal failed for MSSUPGGETREL in phase PREP_PRE_CHECKINTPUT_PRE |fyou folowed SAP Noie 965908 to use SQL Server Dafabase Mirronng and changed the environment variable MSSQL_SERVER forthe