#SAP ECC 7.00 UPGRADE#
If you are having any Application servers based on the OS you have upgrade the kernel and then run the SGENġ8. Finally execute the SGEN on IBM-I system.
#SAP ECC 7.00 INSTALL#
Refer the SAP Note 1097997 to install the New RFC SDK on System iġ7. Refer the SAP note 1882691 prevent errors while displaying the job logsġ6. Rdisp/wp_max_no = Sum of:( rdisp/wp_no_dia + rdisp/wp_no_vb2 + rdisp/wp_no_btc + rdisp/wp_no_vb + rdisp/wp_no_spo + rdisp/wp_no_enq ) To prevent errors from occurring, deactivate it by setting the following parameters: in instance Profile However, this function is not fully compatible with NW 7.00 and NW 7.01. The 720 and 721 kernel versions support the dynamic increase of the number of work processes at runtime.
#SAP ECC 7.00 CODE#
Implement the SAP Note 1610716 for correction in the finds and rectifies the inconsistencies alignment and transaction code SM66ġ5. Due to the situation described in note 1517379, you have to set the following instance profile parameterġ4.
Only necessary for a dual-stack system: you must set the following parameter in the default system profile DEFAULT.PFL:įor dual-Stack and Java-only systems: in all (Dnn, DVEBMGSnn, Jnn, JCnn etc.) instance profiles, you must set the following parameter:ġ3. Logoff & logon SIDADM Start the SAP Instance with new kernel,ġ2. In stratup profile remove the parameter “ Start_Program_06 = local $(DIR_EXECUTABLE)/DLTOLDPKGS SID”Īdd the parameter in Instance profile – dbs/db4/dltoldpkg = noġ1. Delete the SAP ABAP database Sql packages, From the SAP SIDADM user option number 4. Kernel upgrade completed then check the log kernel apply log in \rootbin\sapmnt\PEC\patches\log\apysidkrn*.logĩ. Apply the kernel new kernel, from the kernel sar files copied in to /SAPK7x/*ĪPYSIDKRN SID() ARCHIVES(‘/SAPK7x/*’) SAVSAR(*NONE) MODE(*FULLY) CHGENV(*NO) UPDAPAR(*NO)ĭuring the process you may get the below message Just reply ‘Y’ NOTE: You can check the user concept in SIDADM user environment variable using the command “WRKENVVAR LEVEL(*JOB)”Ĩ.
If you’re starting kernel is still running with the ‘classicuserconcept’ set:ĪDDENVVAR ENVVAR(CLASSICUSERCONCEPT) VALUE(‘Y’) If you’re starting kernel is already running with the ‘newuserconcept’ set:ĪDDENVVAR ENVVAR(CLASSICUSERCONCEPT) VALUE(‘N’) Set the authorities of the objects in SAP_TOOLS by these commands iletools’)Ħ.3 – Check the SAP_TOOLS library after unpack you may find all kernel objectsħ. iletools’)Ħ.2 – CALL QP2SHELL PARM(‘/QOpenSys/usr/bin/csh’ ‘-c’ ‘SAPCAR -xvf SAPEXE.SAR iletools ILE_TOOLS. First unpack the ILE.SAR & then SAP kernels sar filesĦ.1 – CALL QP2SHELL PARM(‘/QOpenSys/usr/bin/csh’ ‘-c’ ‘SAPCAR -xvf ILE.SAR iletools ILE_TOOLS. Change the current folder name to ILE folder (For example SAPILE” CHGCURDIR /SAPILE”), a nd then add the library to SIDADM userĦ.
Create the new library using the SAP SIDADM user id “ CRTLIB SAP_TOOLS”ĥ. Add the ‘ALLOBJ’ authority in SIDADM user as mention below screenshotĤ. Create the two folder in ‘rootbin’ share (Example folder names SAPK7x (SAP kernel files SAPEXE.sar,SAPEXEDB.sar,IGSEXE.sar & IGhelper.sar) & SAPILE (ILE.sar & ilrtools)ģ. SAP ECC 6 NW 7.00 SP 21 on IBM i(OS / DB V7R1).Ģ.
0 kommentar(er)
