Following two software archives are required for the switch to the SAP JVM 4 ( SAP Note: 1555341). • SAPJVMSWITCH.SAR. (Path: SAP Service Market Place ->SAP Technology Components ->SAP JVM 4.1 ->SAP JVM SWITCH TOOL 1.0 ->Support Package Patches ->->and download the.

UpdateStar is compatible with Windows platforms. UpdateStar has been tested to meet all of the technical requirements to be compatible with Windows 10, 8.1, Windows 8, Windows 7, Windows Vista, Windows Server 2003, 2008, and Windows XP, 32 bit and 64 bit editions. Simply double-click the downloaded file to install it. UpdateStar Free and UpdateStar Premium come with the same installer. UpdateStar includes such as English, German, French, Italian, Hungarian, Russian and. You can choose your language settings from within the program.

Note 1299009 central note upgrade systems on sap net weaver 7 0 ehp 2 • 1. Page 1 of 14 SAP Note 1299009 - Central Note: Upgrade Systems on SAP NetWeaver 7.0 EHP 2 Note Language: English Version: 25 Validity: Valid Since Summary Symptom Upgrade to SAP Systems based on SAP NetWeaver 7.0 including SAP enhancement package 2. Other terms Upgrade, SAP NetWeaver 7.0 EHP2, central Note Reason and Prerequisites * Solution This is the central Note for upgrades to SAP systems based on SAP NetWeaver 7.0 including enhancement package 2. ---------------------------------------------------------------------- CONTENTS Part A: Upgrade Notes and Keywords Part B: New Upgrade Program Release and Version Part C: Correction Package for the Upgrade Program Part D: General Problems / Information on all Upgrades..I/. Upgrade Keyword..II/. Important General Information..III/.

Corrections to the Guide..IV/. Errors on the CD-ROM..V/.

Preparing the Upgrade..VI/. Problems During the Upgrade Phases..VII/. Problems After the Upgrade..VIII/. Chronological Summary ______________________________________________________________ __ ______________________________________________________________ __ Part A: Upgrades Notes and Keywords For more information on the upgrade of your specific application and the current keyword, see one of the following Notes: SAP NetWeaver 7.0 EhP2.Note 1299008 SAP CRM...Note 1341978 SAP ERP...Note 1341975 • Page 2 of 14 SAP Note 1299009 - Central Note: Upgrade Systems on SAP NetWeaver 7.0 EHP 2 SAP SCM...Note 1341981 SAP SRM...Note 1448239 Database...... Note number ______________________________________________________________________ SAP MaxDB...... 817463 IBM DB2 for i......1168235 IBM DB2 for Linux, UNIX, and Windows...

819876 IBM DB2 for z/OS...... 815202 MS SQL Server...... 825146 Oracle....... 819655 ______________________________________________________________ __ ______________________________________________________________ __ Part B: New Upgrade Program Release and Version Before you start the upgrade program, check if there is a new release and version of SAPup. The current SAPup release is: SAPup version lmt_001 1.

To determine the currently used SAPup release and version, 2. Proceed as follows: - UNIX: Go to /abap/bin and call './SAPup -V'. Under UNIX, you have to enter the ABAP upgrade directory to allow SAPup to use the correct OS libraries.

- Windows: Go to abapbin and call '.SAPup.exe -V'. - IBM i: ADDLIBLE SAPup UPGDIR() PARMLIST(' -V') 3. SAPup displays the following message: This is SAPup version lmt_001, patch level. To download SAPup from SAP Service Marketplace go to com/patches. Select Browse our Download Catalog ->Additional Components ->Upgrade Tools ->SAPUP UNICODE ->SAPUP 7.02 UNICODE ->->SAPUPLMT001 archive. Caution: Always use the Unicode SAPup release and version regardless of your SAP system being Unicode or non-Unicode!

• Page 3 of 14 SAP Note 1299009 - Central Note: Upgrade Systems on SAP NetWeaver 7.0 EHP 2 Unpack the archive to a temporary location. In roadmap step 'Extraction', the upgrade program asks you to specify the path to the new SAPup. To get a list of all patches contained in a specific SAPup, call SAPup -V ______________________________________________________________ __ ______________________________________________________________ __ Part C: Correction Package for the Upgrade Program Before the upgrade, it is VITAL that you apply the correction package for the upgrade program, if available. The correction package is provided as SAR archive that you must integrate into the upgrade.

Each SAR archive is valid for only one product (= exactly one delivered DVD set). The upgrade control program displays the correct name of the correction package you have to apply. The SAR archives are available at the following SAP Service Marketplace area: ->Browse our Download Catalog ->Additional Components ->Upgrade Tools ->Corrections for Upgrade ->CORRECTIONS FOR UPGRADE 7.02 ->#OS independent There are two packages, one for ABAP and one for Java: ABAP Package Name: FIX_NW702.UPG Java Package Name: FIX_J_BS7I2010.UPG Comments: o Caution: All products (SAP NetWeaver 7.0 EHP2 and all products based on it) use the same correction package. O The archive names on SAP Service Marketplace have a slightly different naming convention: The prefix 'FIX_' ist not displayed. In addition, they have an extension representing the patchlevel and - an 8 digit number. Thes extension varies with each patchlevel of the archive. O Some products are known under different names and can be used differently.

For example, NW-AS 7.00 which is part of Netweaver 04s is the successor product to WEB-AS as well as to the BW product family. However, there is only one correction package regardless of the use of the system. • Page 4 of 14 SAP Note 1299009 - Central Note: Upgrade Systems on SAP NetWeaver 7.0 EHP 2 Integration into the upgrade 4. Download the correction package for your product. Store the SAR archive in the main upgrade directory. Unpack the SAR archive using 'SAPCAR -xvf.SAR' You will get two files, one of them is.UPG, the other one contains a history of changes. During the KEY_CHK phase, the upgrade program searches the upgrade directory for the correct correction package.

If it is successful, the package is automatically integrated into the upgrade. If the upgrade program does not find a valid package, it displays a user dialog requesting that you place the correction package in the upgrade directory. You can use 'Retry' to repeat the search. The UPG archive contains data files and cofiles for the transport requests and the corresponding buffer files (ABAP upgrade only), and control files of the upgrade. The corrections to the ABAP tools of the source release are imported in the TOOLIMP4_FIX, TOOLIMP6_FIX phases (provided these exist), while the corrections for the shadow system are imported in the SHD_FIX_IMP phase. The transport requests are imported automatically. Region Hack Samsung Bd C6500 Remote.

You must not import requests into the system manually! The corrections to the J2EE upgrade program and control files are included automatically and the program is restarted to make the changes become active. ______________________________________________________________ __ ______________________________________________________________ __ Part D: General Problems / Information on all Upgrades I/ Upgrade keyword ---------------------------------------------------------------------- For the upgrade keyword, see the relevant product-specific Note listed in part A of this Note. ---------------------------------------------------------------------- II/ Important General Information • Page 5 of 14 SAP Note 1299009 - Central Note: Upgrade Systems on SAP NetWeaver 7.0 EHP 2 ------------------------------------------- Windows only: Execute program R3dllins.exe The 6.40 kernel is compiled with the new version of MS compiler and requires additional libraries for operation. To prevent problems during and after the upgrade, you must execute program R3dllins.exe on your central host, all application hosts, and on the remote shadow host, if you are planning to use one.

You can find the program on the Upgrade Master CD in the NTI386NTPATCHfolder. It must be executed before you start the upgrade program and directly from the NTPATCH folder (it can be shared). Copying and executing the program will not work! ------------------------------------------------- LSMW now part of SAP_BASIS As of SAP Web AS 6.20, LSMW is part of SAP_BASIS. If you are using LSMW and your source release is based on SAP Web AS 6.10 or lower, do not implement LSMW after the upgrade. For more information, see SAP Note 673066. ------------------------------------------------- MSCS Configuration: Split the ABAP Central Instance In an MSCS configuration, you must split the ABAP central instance into the ABAP central instance (ASCS) and central instance, as described in SAP Note 1011190, if one of the following cases apply: o You have upgraded your SAP NetWeaver '04 ABAP only system to SAP NetWeaver 7.0 ABAP o You have upgraded your SAP NetWeaver '04 ABAP only system to SAP NetWeaver 7.0 ABAP, and now want to install a Java Add-In.

The split must done before the Java Add-In installation. The split is required for the use of the enqueue replication server. If you run an MSCS configuration without enqueue replication server, which is the traditional MSCS configuration (where the clustered central instance runs the message server and enqueue work process), you will loose the enqueue lock table during a failover. The enqueue replication server configuration prevents this loss. If you want to migrate an ABAP+Java system that is already upgraded to SAP NetWeaver 7.0 to the new configuration with enqueue replication server you must perform a homogeneous system copy.

--------------------------------------------------------------------- III/ Corrections to the Guides ------------------------------------------------- Upgrade Guides with regard to Business Intelligence ABAP The note 447341, which is in the list of SAP Notes for the Upgrade and mentioned in the chapter 'BW: Converting Inconsistent Characteristic Values with a Conversion Routine', is only relevant for the upgrade from BW version 2.0 to 3.0. If the BW start release is 3.0 or higher, this note has to be ignored. --------------------------------------------------- Manual Start of ASCS and ERS Instance (Phase REQ_ASCS_START) • Page 6 of 14 SAP Note 1299009 - Central Note: Upgrade Systems on SAP NetWeaver 7.0 EHP 2 When you update the SAP kernel on the host with the ASCS instance, also run program 'cleanipc'. For more information about this program, see SAP Note 1195961. ------------------------------------------ ------------------------------------------------- Starting the Upgrade Program It is no longer required to specify the jce_policy_zip option when starting the upgrade program. --------------------------------------------------------------------- IV/.

Errors on the CD-ROM --------------------------------------------------------------------- V/ Preparing the Upgrade ------------------------------------------------ LINUX systems: Pay attention to correct kernel for the upgrade If You want to upgrade an SAP system with LINUX, and you are asked to replace the kernel before the upgrade, make sure that you do not use the 7.20 EXT kernel. Install the normal 7.20 kernel instead. The 7.20 EXT kernel can be used optionally, provided that the requirements are fullfilled. For further information, see SAP note 1563102. ------------------------------------------------- Avoing Error with the 'DB_STORAGE_GET' Module>When you include SAP NetWeaver 7.0 EHP2 Support Package 4 into the upgrade, than implement SAP Note 1470501 afterwards to avoid an error with the 'DB_STORAGE_GET' module. -------------------------------------------------- Preventing long runtime of SUSR_AFTER_IMP_PROFILE During the upgrade, the after-import method SUSR_AFTER_IMP_PROFILE can have a long runtime, and there may be a longer system downtime as a result. For information about how to prevent long runtimes of this method, see SAP Note 821496.

--------------------------------------------------- Avoiding Loss of Customer Objects In very rare cases, customer objects can get lost during the upgrade. You can check in a program whether your system is affected.

If so, you have to apply a correction after the roadmap step 'Extraction' and before roadmap step 'Configuration'. For more information about the program to check and the correction, see SAP Note 1462709. -------------------------------------------------- Preventing Unrequired Table Conversion • Page 7 of 14 SAP Note 1299009 - Central Note: Upgrade Systems on SAP NetWeaver 7.0 EHP 2 For SAP systems with a Support Package stack level lower than 7.1 SPS 08implement SAP Note 1283197. This prevents the unnecessary conversion of cluster tables. ----------------------- -------------------------- For Source Releases SAP R/3 4.6C and SAP R/3 4.6D Only: Prevent Lossof your BSVV objects during the upgrade If are upgrading your SAP system with the source SAP R/3 4.6C or SAP R/3 4.6D and have created customer-defined objects such as R3TR BSVV Z* before the upgrade, you might lose parts of your BSVV objects during the upgrade. To solve this issue, proceed as described in SAP Note 1432102 prior to starting the upgrade.

----------------------------------------- ------------------------------------------------ Parameter for the Central Syslog rslg/collect* There may be conflicts with parameter values for the central syslog 'rslg/collect*' of the default profile. If the parameters are set with 39 and 40, you must change them to 14 and 15.

Make sure that the ports are not used by other applications. If so, choose some other number. For more information, see Note 1069225. ------------------------------------------------- Source Release on Kernel 6.40 with SuSE SLES 9 IA64 / RedHat 4.0 IA64 If you are using the above combination on your source release and have set environment variable LD_ASSUME_KERNEL 2.4.21 according to SAP Note 797084, proceed as follows: Before you start the upgrade, you need to delete the environment variable LD_ASSUME_KERNEL 2.4.21 and deactivate component icman by setting the following instance profile entry: rdisp/start_icman=false Restart the system. After the upgrade, delete the instance profile entry again. -------------------------------------------------- Back up customer-specific entries in table EDIFCT If you have maintained customer-specific entries in table EDIFCT, they may get lost during the upgrade.

Download Free Madness Project Nexus Hacked All Levels there. If you do not want to lose these entries, export them before the upgrade and reimport them after the upgrade. For more information, see Note 865142. ------------------------------------------------- Windows only: Last profile text line must end with line feedback Check that the last text line in all profiles ends with a line feedback.To check this, open a profile file with a text editor, go down with the cursor and ensure that the last line is empty. Otherwise there could be problems in the KX_SWITCH phase as some tools will not be able to handlethe profiles properly. ------------------------------------------------- Windows only: Stop SAP MMC during the upgrade downtime Make sure that SAP MMC is not running during the upgrade downtime. Otherwise, the files in the kernel directory will be in use and the phase KX_SWITCH is not executed successfully.

• Page 8 of 14 SAP Note 1299009 - Central Note: Upgrade Systems on SAP NetWeaver 7.0 EHP 2 ------------------------------------------------- Windows only: Comment out parameter DIR_SERVER_ORAHOME Check the default profile of your system. If you find the parameter DIR_SERVER_ORAHOME, comment it out.

Otherwise the phase KX_SWITCH is not executed successfully. ----------------------------------------------------------------------- VI/ Problems During the Upgrade Phases ----------------------------------------------- SAP JVM 6.1.00.6 Error at Startup When you run the startup script, the upgrade GUI fails to initialize. The problem is caused by an OS notification for a segmentation error, bus error, or an illegal instruction error - either of which causes the SAP JVM to terminate and the upgrade tool to hang.

This issue occurs on 64-bit systems running Solaris 11, but might also occur on other UNIX-based operating systems. For the solution of the issue, see SAP Note 1708424. ------------------------------------------------ Use of Back- and Next-Button during upgrade procedure If you restart the upgrade procedure choosing 'Back' repeatedly and 'Next' again, then stop and restart the SL Controller first prior to choosing 'Next', in order to properly reset the internal status of the SUM tool. Otherwise an error might occur, for example during the execution of the GETSYNC_INFO_FINISHED phase. --------------------------------------------------- SPS06 included in Upgrade: Error in Preprocessing / Phase RUN_RSDB02CK_END If you include Support Package SAP_ABA 702 06 into the upgrade, the following error can occur: Checks after phase MAIN_POSTP/RUN_RSDB02CK_END were negative! Last error code set: Batch Job RSDB02CK Failed: Error(s) were found in the log(s), accumulated in 'RSDB02CK.ELG'. In the log file, the following error message exists: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ DB02 consistency check ERRORS and RETURN CODE in RSDB02EN.QO1 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2EETG033 Table 'TASYB' does not exist in the database You can ignore this error.

If you include a lower or higher Support Package into the upgrade, the error does not occur. ----------------------------------------------- Phase IS_SELECT An error in the IS_SELECT phase can erroneously lead to the deletion of the add-on.

In the following situation, the error can occur: The add-on has the status 'KEEP'. When you choose 'Continue' a message informs you that 'KEEP' is not valid and the status is set to 'UNDECIDED'. • Page 9 of 14 SAP Note 1299009 - Central Note: Upgrade Systems on SAP NetWeaver 7.0 EHP 2 You select another option, for example, 'Keep with vendor key'. When you then choose 'Back' and run the Configuration roadmap stepa second time, you no longer get the message that 'KEEP' is not possible and you cannot choose another option. Although the status of the add-on is then still 'KEEP', the add-on will be deleted.

To solve the problem, reset the upgrade completely by choosing 'Back' several times. Then, start the upgrade from scratch. --------------------------------------------------- Phase PARCONV_UPG During the upgrade, the phase PARCONV_UPG can fail with an error during the creation of secondary indexes. In the conversion log files of the form NCONV.

The following error is reported: Index ' ' could not be created completely in the database To solve this problem, repeat the phase. To avoid the error in advance include the support packages mentioned in SAP Note 1468467 in the upgrade procedure. ---------------------- ---------------------------- Phase: MAIN_NEWBAS/RUN_RSAIMMERGE_UPG To avoid a runtime error in your target system, increase parameter 'em/initial_size_MB = 1024' to 'em/initial_size_MB = 4096' in the instance profile. For more information, see SAP Note 1460004. ---------------------- ---------------------------- Phase: MODPROF_PFPAR_UPG If the following error occurs: 'MODPROF_PFPAR_UPG:fails even rc=0', add the following paramenter to the instance profile: 'SAPup_check_level = 5'. ---------------------- ---------------------------- Phase: MAIN_SHADOW/START_SHDI_FIRST Description: An RFC error occurs (RFC LOGIN FAILED) Solution: 8.

In the SAPup.par file, set the value of the /UNIX/sleep_after_shdsys_start parameter to 200. Restart the upgrade program and repeat the phase. ------------------------------------------------ Adjust Hostnames in Shadow Instance Profiles Manually When you have chosen option 'Take profiles from save' to reuse the profiles for the shadow instance of your previous upgrade, update the hostnames in the profiles for the shadow instance manually after the 'Configuration' roadmap step.

You can find these profiles under /abap//SYS/profiles. This workaround will be fixed for tools delivered with BS7i2010. ------------------------------------------- Phase: PARDIST_SHD Description: For Windows NT only The upgrade is terminated during the PARDIST_SHD phase. The PCONUPG.ELG log file contains an incomplete error text which was extracted from the DS. Repeat the phase. • Page 10 of 14 SAP Note 1299009 - Central Note: Upgrade Systems on SAP NetWeaver 7.0 EHP 2 -------------------------- ----------------------- Phase: REQJOBRES Description: Windows only - SAPup issues the error message value returned by call sappfpar.exe Start_Program_01 pf=.is incorrect.

Please analyze the content of.putlogNTPARVAL.LOG You can ignore this error. Repeat the phase to continue. ------------------------------------------------- Phase: KX_SWITCH (Windows only) Description: Upgrade stops with an error message which asks you to checkfile NTPARVAL.LOG. In this file, messages like the following are displayed: fopen(.): Invalid argument Check that the last text line in all profiles ends with a line feedback.To check the profile, open a profile file with a text editor, go down with the cursor, and ensure that the last line is empty.

If it is not, add an empty line at the end of the file and save it. ------------------------------------------------- Phase: KX_SWITCH (Windows only) Description: Because SAP MMC is running, SAPup stopped with the following error message: SAPup>SEVERE ERROR: Could not delete file '.sapstartsrv.exe'. Reason: 'ErrorMessage: Access is denied. In this case, shutdown SAPMMC and SAP service of your system and repeat the phase. ------------------------------------------------- Phase: KX_SWITCH (Windows only) Description: If parameter DIR_SERVER_ORAHOME has not been commented out,SAP up will stop with the following error message: Error: value returned by call sappfpar.exe Start_Program_01 pf=.is incorrect.

Please analyze the content of.NTPARVAL.LOG. The NTPARVAL.LOG states: immediate.sapcpe.exe pf=.Illegal Parameter in Default Profile: 'DIR_CLIENT_ORAHOME'. Sapparam: Illegal Parameter in Default Profile: 'DIR_SERVER_ORAHOME'. (no Default-Value) In this case, comment the parameter out and repeat the phase. ------------------------------------------------ Phase: XPRAS_UPG Description: The phase issues the following short dump: 'GEN_BAD_MACRO_SOURCE' for program /1BCDWB/ You can ignore this message.

------------------------------------------------ Phase: MODPROFP_UPG Description: When you are performing a dual-stack upgrade (ABAP and Java system at the same time), in phase MODPROFP_UPG the ABAP system is started together with the Java system part for the first time. The phase may fail if the SAP J2EE Engine does not start fast enough. Check manually if the SAP J2EE Engine is running and if so, choose 'repeat' to repeat the upgrade phase. ---------------------------------------------------------------------- Phase: CHK_POSTUP Note: 996953 Description: Log file LONGPOST.LOG prompts you to migrate a CMOD project • Page 11 of 14 SAP Note 1299009 - Central Note: Upgrade Systems on SAP NetWeaver 7.0 EHP 2 although no project exists.

---------------------------------------------------------------------- VII/ Problems After the Upgrade -------------------------------------------------- Reconfiguration of User Reauthentication If you have performed the upgrade from a source release lower than SAP NetWeaver 7.0 EHP1, you have to reconfigure the user reauthentication after the ugprade. As of SAP NetWeaver 7.0 EHP1, there is a new implementation of the user reauthentication and it is not active until you have configured it.For more information, see SAP Note 1532874. --------------------------------------------------- Missing Table If you included SAP_ABA 702 SP 06 into the upgrade, the you see the following in transaction DB02 under 'Missing Tables and Indexes': Results of Consistency Check Object missing in the database Tables X TASYB You can either ignore this issue or create the table in the database in transaction DB02. If you included a lower or higher Support Package into the upgrade, thisissue does not occur. ------------------------------------------------ Ignore Short Dump If the following short dump occured during the enhancement package installation, you can ignore it: Category ABAP Programming Error Runtime Errors CALL_FUNCTION_NOT_FOUND Except.

CX_SY_DYN_CALL_ILLEGAL_FUNC ABAP Program CL_ENH_TOOL_BADI_IMPL=========CP Application Component BC-DWB-CEX Date and Time 08:59:40 -------------------------------------------------- Delete CUA Load after the Upgrade If after the upgrade you face an issue with the CUA load in your SAP system, delete the CUA load using report 'RSLANG20' as described in SAP Note 110910. ---------------------------------------- ------------------------------------------------ Ignore obsolete tables 'PATRTVERS2','PATRTCONF', and 'PATRTPHASE' If you run into the table 'PATRTVERS2', 'PATRTCONF', 'PATRTPHASE' • Page 12 of 14 SAP Note 1299009 - Central Note: Upgrade Systems on SAP NetWeaver 7.0 EHP 2 (SPAM-specific), or table 'sap_tmp_stmt_stats_tab' (MS SQL server-specific) after the upgrade, ignore these tables. They have become obsolete and will be deleted automatically! --------------------------------------------------- Windows Only: Ignore obsolete table 'sap_tmp_stmt_stats_tab' If you run into the table 'sap_tmp_stmt_stats_tab' (MS SQL server-specific) after the upgrade, ignore this table. It has become obsolete and will be deleted automatically. --------------------------------------------------- Syntax error in TREX ABAP Client after the upgrade If you perform an upgrade from SAP NetWeaver 7.00 SP17 or higher to SAP NetWeaver 7.0 including enhancement package 1 SP2 / SP3 / SP4 or to SAP NetWeaver 7.0 including enhancement package 2 SP1, you will get a syntax error in class your TREX ABAP client (CL_TREX_FACADE). To solve this issue, check SAP Note 1355746.

------------------------------------------ ----------------------------------------------- SPAU: Names of interface methods are truncated Some methods (ABAP objects) that were modified and overwritten by the upgrade can be displayed in transaction SPAU with their names shortened to 30 characters. As a result, the system may also incorrectly sort methods in SPAU under 'Deleted objects'. Caution: Deleted objects are not displayed in the standard selection in SPAU. It is easily possible to overlook these! For more information about the correction, see Note 547773. ---------------------------------------------------------------------- Date.Topic.Short description ----------------------------------------------------------------------- MAR/18/12.VI.SAP JVM 6.1.00.6 Error at Startup DEC/05/11.VI.Use of Back- and Next-Button during upgrade procedure OCT/19/11.V.LINUX systems: Pay attention to correct kernel for the upgrade DEC/23/10.VII.Reconfiguration of User Reauthentication NOV/30/10.VII.Missing Table JUL/27/10.VII.Ignore Short Dump JUL/15/10.VII.

Delete CUA Load after the Upgrade.