A set of middle ware programs and tools that provide the underlying base that enable applications to be inter-operable across operating systems. SAP Basis includes a RDBMS, GUI, and client server architecture. It's a piece of middle ware which links the application with the database and the operating system. Basis is most commonly associated with the GUI interface to the SAP.

Pages

October 19, 2013

SAP NetWeaver 7.0 Dual Stack Refresh Procedure -6

SAP NetWeaver 7.0 Dual Stack Refresh Procedure -Part 6

8.3 Post Refresh Steps

For QBI and SB1, the application server must be reinstalled. For SAPINST to work properly during the installation, we must request that the LDAP integration be disabled. Raise a ticket with GLMSE early to ask for this, or it will create a delay near the end of the refresh.

8.3.1 ABAP Stack

• Run “stopsap”

• Upgrade the kernel to the proper level. This will avoid the adjust Nametab error that indicates SAP is not communicating with the database. Depending on the system status, JSPM may be used to update the kernel to the correct level.

I. The current kernel for BI is patch 39 for 701. It can be found in /bswork/exe_AIX_701_39_nuc and /bswork/exe_AIX_701_39_uc. There are also Linux versions available if the system being refreshed has Linux application servers

III. Copy the NUC version to /usr/sap/<SID>/DVEBMGS<INSTNR>/exe cp –pR /bswork/exe_AIX_701_39_nuc/* /usr/sap/<SID>/DVEBMGS<INSTNR>/exe/IV. Double check that the UC version is available under /sapmnt/<SID>/exe/uc/rs6000_64 for AIX and /sapmnt/<SID>/exe/uc/linuxx86_64 for Linux application servers. Copy as necessary from the UC versions under /bswork.• Start the database only by running the startdb command as <sid>adm.• Run refresh perl script with the “clean” option to clean up tables and change what can be done from a script/DB2 command line perspective. All actions at this step are controlled through the clean.ini configuration file.The message “SQL0100W No row was found for FETCH, UPDATE or DELETE; or the result of a query is an empty table. SQLSTATE=02000” can be ignored. This indicates the table had no affected records when executing the SQL delete statement. When using the scj_refresh.pl script, this is returned with code 256.

• Run post steps script to repopulate, optionally, the user records, RFCs, PSE, ports, and partner profiles This may introduce issues with the Java stack as the ABAP user records and the Java UME will be out of sync. I. BI Systemscj_refresh.pl restore <SID>

• Enable batch processingDouble check the profile overall – ensure the correct instance and DEFAULT profiles are in place.Restore the batch processes number from prior to the refreshAlso check the profile for the SSO parameterslogin/accept_sso2_ticket = 1login/create_sso2_ticket = 2• Startsap• Apply license – Not always required. SAPINST attempts to install a temporary license, however this may fail Apply license as required depending on license type (old vs. new)• Old license application procedure saplicense at the command line• New license application procedure There is a new command line tool available in recent patch levelsUse “saplikey” at the command line to import new style keys instead of needing to unlock SAP* and follow this process of breaking into the system. This process needs to be verified.• Log into ABAP and add system message (SM02)• Update transaction SCC4 Changes without automatic recording Changes to Repository and cross-client Customizing allowed Protection level 0: No restriction• Check SM28 for installation problems• Run RSBTCDEL to delete canceled and finished batch jobs

• BDLS conversion – Execute in the foreground on a windows server (i.e. USRACIB05). There have been issues running some of the BDLS conversions in the background with Business Warehouse systems. Typically, there are workbench request prompts that cause the program to “hang” if run in background.

• This is now included in the scripts. Modify table RSLOGSYSDEST and update the RFC destination entries to correspond with the updated logical systems from the BDLS conversion step.

• This is now included in the scripts. Update table RSADMINA with correct user for BW_USER field.
o Ensure ALE<SID><CLNT> user is used and password is known and updated in the appropriate places.

• Check Partner Profiles in WE20 transaction
o Check Partner Status to ensure the profiles are active. We have seen that under certain circumstances, this is switched to “I” or inactive. Replace with “A” for active and save.

• RSA1 for BI system
o Run transaction RSA1
Double click Source Systems
Right click each logical system
Select Restore from menu to re-connect
o Log into SCM system
Run transaction RSA1
Double click Source Systems
Right click on BI logical system
Select Restore from menu to re-connect
o Notes: Both systems need to be open during the connection restore processes. If the restore process fails, it may be due to any of the following.
> RFC destination definition issues
> ALE user permission issues
> ALE user password issues
> WE20 partner profile settings incorrect
> WE21 TRFC port settings incorrect
> One or both systems locked via SCC4 settings
> ALE user needing to be Dialog to allow restoration
> Others I can’t remember right now

• The BI team needs to ensure the assignment of Source System IDs is correct in order for the RSA1 connections to be re-established.
o Navigate to RSA1
o From the Tools menu, select “Asgnmt of Srce Syst. To Srce Syst. ID” The following screen is displayed, however it is not Basis responsibility to fix any entries here.

• Update PSE
o This should be covered by the scripting at this point.
o Check STRUSTSSO2 for the appropriate system certificates
o Import PSE data that was exported during the preparation phase. This will load the appropriate certificates again.
o If the “Own Certificate” is incorrect, run SSFPSEMAINT through SE38 to generate the PSE

o RSPRECADMIN> Connect to the various precalculation servers and reset the status. The existing precalculation server definitions should be removed and the connections added once more. Check the RFC destinations also since if the RFC already exists, you cannot add the server in RSPRECADMIN. This is based on the name given during the server addition.> Production server USRACIA73> QA server USRACIQA000> Dev server USWAXDDA004> All three servers are configured in PBI. The two test servers are configured in QBI and SB1. Only the development server is configured in DB1. The sandbox systems only use precalculation on a need basis, so maintenance there is not required unless specifically requested from the BW team.