Documentos de Académico
Documentos de Profesional
Documentos de Cultura
SPAM Level
Some friends ask me how to get information about support package level on their current SAP R/3
server. Actually it is very simple. Just follow this next step:
Type SPAM on your SAPGUI command screen.
You this SPAM screen. SPAM program also has its level. You can see it on the top of it. My current
SPAM version is 6.20 level 26.
To check other support package level, just press Package level button.
On the left side, you see support package component such as SAP_BASIS (SAP Basis
Component), SAP_ABA (Cross Application Component), SAP_APPL (Logistics and Accounting),
SAP_HR (Human Resources), etc.
For level package, just check level component. For example, SAP_BASIS has its level 64.
OK, thats all you need to know about your current support package level. On the next tutorial, Ill
guide you about how to increase your support package level.
====================================================================================
Previously we used SPAM for ABAP Patch upgrade and JSPM for JAVA Patch
upgrade and EHPI installer for EHP upgrade.Now SAP , Replaced all tools with SINGLE
Tool SUM .
With help of SUM we can do ABAP Support Pack Upgrade, Java Support Pack Upgrade,EHP
upgrade,Version upgrade,Unicode migration,S4 Hana migration.
Without knowing about SUM and its use,Nobody can be expert BASIS ADMIN,
<>HOSTNAME> ./STARTUP
*** Checking if C++ runtime is installed
*** Starting from /usr/sap/<SID>/SUM/sdt
** Checking username sidadm for compliance
Aug 30, 2016 5:43:05 AM [Info]: *************************
Aug 30, 2016 5:43:05 AM [Info]: Starting Server
Aug 30, 2016 5:43:05 AM [Info]: Reading server configuration.
Aug 30, 2016 5:43:07 AM [Info]: Reading service configuration UseCaseService.
Aug 30, 2016 5:43:07 AM [Info]: Configuring LogManager
Aug 30, 2016 5:43:07 AM [Info]: *************************************************
Aug 30, 2016 5:43:07 AM [Info]: Starting SL Controller listening on port 4241 ...
Aug 30, 2016 5:43:07 AM [Info]: Starting StorageService
Aug 30, 2016 5:43:07 AM [Info]: Initializing SecurityManager
Aug 30, 2016 5:43:11 AM [Info]: Server certificate fingerprint is A1 FC 90 0E 9F 2A AC 6D F6
16 ED 74 5F 2C DB E9
Aug 30, 2016 5:43:11 AM [Info]: Configuring HTTPManager
Aug 30, 2016 5:43:11 AM [Info]: Starting WebstartService
Aug 30, 2016 5:43:11 AM [Info]: Starting RoleService
Aug 30, 2016 5:43:11 AM [Info]: Starting AlertService
Aug 30, 2016 5:43:11 AM [Info]: Starting NotesService
Aug 30, 2016 5:43:11 AM [Info]: Starting ProcessService
Aug 30, 2016 5:43:11 AM [Info]: Starting MIDService
Aug 30, 2016 5:43:11 AM [Info]: Starting FileService
Aug 30, 2016 5:43:11 AM [Info]: LogService switched off.
Aug 30, 2016 5:43:11 AM [Info]: Starting MailService
Aug 30, 2016 5:43:11 AM [Info]: Starting services
Aug 30, 2016 5:43:11 AM [Info]: Starting service UseCaseService
Aug 30, 2016 5:43:12 AM [Info]: Starting MIDService
Aug 30, 2016 5:43:17 AM [Info]: Service UseCaseService started
Aug 30, 2016 5:43:17 AM [Info]: Services started.
Aug 30, 2016 5:43:17 AM [Info]: Starting HTTP server listening on port 4239 ...
Aug 30, 2016 5:43:17 AM [Info]: HTTP server started.
Aug 30, 2016 5:43:17 AM [Info]: SL Controller started.
Once SL Controller is started ,we can launch SUM tool from browser From the logs its clear
that it opens HTTP port on 4239.
====================================================================================
After successful authentication itll redirect to below page : Navigate as below to reach Software
Update Manager SUM latest SAR file.
From (A-Z index ) select S then SL TOOlSET
====================================================================================
Here you'll get different set of tutorials <Beginner level ,Advance level ,SAP
Upgrade related,Oracle Basis related ,Solution manager related >
====================================================================================
I hope ,you really got some useful information related to "Maintenance Planner " .Can you please give
30 sec of your time now to have a look into main tutorials collection home page ,I guarantee you will get
very useful tutorials over there.
Here you'll get different set of tutorials <Beginner level ,Advance level ,SAP
Upgrade related,Oracle Basis related ,Solution manager related >
====================================================================================
Click on the green checkmark only after making setting in Start option as below:
SPAU: This transaction is used for adjusting the objects imported during the upgrade
SPDD: This transaction is used for adjusting the data dictionary objects imported during the
upgrade
Click on the green checkmark.
There are some BW pre-steps that need to be done before downtime (upgrade)
Goto Tcode : STC01
Select Task list: SAP_BW_BEFORE_UPGRADE and execute
Go to Tcode : /n/ASU/UPGRADE
Perform all the pre steps mentioned by this transaction, Most of the steps should be covered by
STC01 transaction executed previously, Please cross check once again.
4. Activate all Data Store objects - valid for all SAP BW Releases 3.x and 7.0x
I hope ,you really got some useful information related to "BW Upgrade Presteps for 7.4 and 7.5 " .Can
you please give 30 sec of your time now to have a look into main tutorials collection home page ,I
guarantee you will get very useful tutorials over there.
Here you'll get different set of tutorials <Beginner level ,Advance level ,SAP
Upgrade related,Oracle Basis related ,Solution manager related >
====================================================================================
Error:
Validation of deployment queue completed with error: The stack does not match the system. Probably
the system was changed after the stack was generated. Synchronize the system with SAP Solution
Manager and then generate a new stack.
Fix:
Please cross check all the system usages are activated before generating stack file.
http://<HOSTNAME:PORT>/utl/UsageTypesInfo
http://<HOSTNAME:PORT>/utl/UsageTypesDetailedInfo
Detailed information about Usage Types UTL version
Usage Types
Sho
UT Activat List
Product Vend rt Descriptio Acti Requir Cover Deliver Mandat Configu Nati
Co ion ord
Name or Na n ve ed UT ed UT ed ory red ve
de date er
me
SAP
Process
NetWea sap.c AAS ,
PI PI Integratio No No No No No Yes
ver om AS
n
2004s
SAP
Mobile
NetWea sap.c AAS ,
MI MI Infrastruc No No No No No Yes
ver om AS
ture
2004s
http://<HOSTNAME:PORT>/utl/ProductsDetailedInfo
Products
http://<HOSTNAME:PORT>/utl/ComponentsDetailedInfo
Components
http://<HOSTNAME:PORT>/sap/monitoring/ComponentInfo
http://<HOSTNAME:PORT>/sap/monitoring/SystemInfo
I hope ,you really got some useful information related to "JAVA SYSTEM USAGE " .Can you please give
30 sec of your time now to have a look into main tutorials collection home page ,I guarantee you will get
very useful tutorials over there.
Here you'll get different set of tutorials <Beginner level ,Advance level ,SAP
Upgrade related,Oracle Basis related ,Solution manager related >
====================================================================================
During the upgrade we generally get below error in Check phase if we dont have correct Java Instance
ID of system:
Error:
The central instance ID that would be calculated by the batch config utility is <XYZ>.
The following problem has occurred during step
execution: com.sap.sdt.j2ee.services.servicesimpl.AnalyseChecksResultsException:
The detected instance ID <XYZ> and the one calculated from the box number <ABC> do not match. A
possible reason for that is that you have changed the box number in the central instance
instance.properties file.
Root Cause:
This error comes if during the system copy/refresh java part was not taken care by standard SAP tool
We fixed java manually from Configtool after system refresh.
Solution :
Please take Java export of source system and again perform Java Import in target system using System
copy tool SWPM.
I hope ,you really got some useful information related to "SUM Upgrade " .Can you please give 30 sec of
your time now to have a look into main tutorials collection home page ,I guarantee you will get very
useful tutorials over there.
Here you'll get different set of tutorials <Beginner level ,Advance level ,SAP
Upgrade related,Oracle Basis related ,Solution manager related >
====================================================================================
In order to get those business functionalities in upgraded system ,we need to activate
corresponding Business Function else There is no use of upgrade from Business point of view.
NOTE: Its very dangerous to activate Business Functions without knowledge / proper
understanding ,Dont Do it in Production directly as some business functions are not
reversible.
After activation business functions,we need to activate related services from SICF.
Refer SAP documentation for activation of Business Functions for more details.
====================================================================================
JSPM was advance tool compare to SDM.It automatically calculate Queue and import Java
Patches ,We can say easy method to deploy java Patches.
But internally JSPM calls SDM only and patches are deployed with SDM only.
Step 3 :Start SDM= JStartup in standalone mode means not intregated with Java-
sdm.sh jstartup mode=standalone
Step 4: Deploy Java Patch with below command-
sdm.sh deploy file=<complete path of SCA/SDA file>
Goto /usr/sap/<SAPSID>/DVEBMGS<instance_number>/j2ee/configtool
where <Oracle_client_major_version> is the major version of the Oracle client that you are using
after this upgrade.
Make sure correct ODBC jar file should be pointed.
2)Use the Edit mode to replace the driver location in the following property sheets that contain
the string rdbms.driverLocation= followed by the driver location: cluster_data/Propertysheet
instance.properties.IDXXXXXXX/IDXXXXXXX.JavaParameters
where XXXXXXX is the instance number
NOTE
Make sure that you change all occurrences.If you have more than one server or dispatcher you
must modify all relevant property sheets.
3) Close Editor mode and do global search and change correct rdbms.driverLocation.
2) Open the file with your text editor and search for the property rdbms.driverLocation.
2) Open the file with your text editor and search for the property rdbms.driverLocation
3) Replace the old driver location with the new
one:/oracle/client/<Oracle_client_major_version>x_64/instantclient/<java_class_archive>.jar
====================================================================================
Click on display.
3.If GUI Scripting is not enabled, then Current value will be FALSE
4. To enable, click on Change Value ()
5. Change the New Value as TRUE and put a tick mark on Switch on all severs .
F. Click on Save.
====================================================================================
1. Login as root as <sidadm> doesnt have permission for executing SAP HOST AGENT commands.
2. cd /usr/sap/hostctrl/exe {navigate to directory where sap host agent is installed}
3. execute command ./saphostexec -version
Please screenshot shows SAP Host Agent version of my system is at
721_REL and patch level 15.
====================================================================================
1. Login as root as <sidadm> doesnt have permission for executing SAP HOST AGENT commands.
2. cd /usr/sap/tmp
3. mkdir hostagent {create new directory}
4. cd hostagent
5. Uncar SAP HOST AGENT Sar file as belowSAPCAR xvf SAPHOSTAGENT114_114-
20005727.SAR <SAPHOSTAGNET SAR FILE ,We need to download it from service market place>
====================================================================================
1. Login as root as <sidadm> doesnt have permission for executing SAP HOST AGENT commands.
2. cd /usr/sap/hostctrl/exe {navigate to directory where sap host agent is installed}
3. execute command ./saphostexec USE BELOW MENTIONED OPTION
USE OPTION for doing action which you want as for -start use ./saphostexec -
start
-install : Install the agent
-upgrade [-archive SAPHOSTAGENT_ARCHIVE] : Upgrade the agent [from
SAPHOSTAGENT archive]
-uninstall : Uninstall the agent
-restart : Start or Restart the agent
-stop : Stop a running agent
-status : return the status of the agent
-version : return a detailed version
information
Please Read similar Articles of SAP HOST AGENT using same option for more
details.
As of kernel release 7.20, SAP has therefore introduced a new method of securely storing the database
password and for connecting to the database: "Secure Storage in File System" (SSFS). The encrypted
password for the SAP database user is then no longer stored in the database, but in the file system.
Prior to SSFS, the connection between the SAP system (AS ABAP) and the SAP tools that use the ABAP
database interface (R3trans, R3load etc.) to the database via SQLNet (using the database alias name, for
like configured in TNS) worked in such a way that an OPS$ connection (with the database user
OPS$<SID>ADM) that was authorized by the operating system user sidadm was created first ( via
"connect /@TNS"). With this approach access to the table OPS$<SID>ADM.SAPUSER, and to this table
was only allowed. It contains the encrypted password for the actual database connection of the SAP
database user (default name Schema User).
Referred SAP Notes:
1. 1639578 = Documents Basis instructions/steps below.
2. 1623922 = Provides overview on how to connect to the Database using SSFS.
3. 1622837 = Documents steps/instructions to be taken care of by DBA team.
SW pre-requisites:
We should at a minimum, needs to be at Kernel 720, Patch 98. Referred SAP Note 1611877.
setenv rsdb_ssfs_connect 0
setenv RSEC_SSFS_DATAPATH /sapmnt/<SID>/global/security/rsecssfs/data
setenv RSEC_SSFS_KEYPATH /sapmnt/<SID>/global/security/rsecssfs/key
NOTE: Make sure you are updating these env variable for app server also else app server will not
come up after this activity.
4. Change the ORA SCHEMA user password to your password from BR-Tools:
Find out schema user from env : dbs_ora_schema=<schema>
Please refer any link to change ORA Schema (SAPSR3) user password.
Note: For doing bounce come out from sidadm and do again sudo su sidadm and then
perform system bounce.
6. Setting up the SSFS data storage and checking the access rights and perform check:
Change the Profile parameter : rsdb/ssfs_connect = 1 in Default profile .Initially we set it =0.
Update below mentioned env variable in .sapenv * profiles in home directory of sidadm ( Eg:
/home/sapsys/<SID>adm) of all servers.
Note: For doing bounce come out from sidadm and do again sudo su sidadm and then
perform system bounce.
Check below entries in SM50 work process log --- B read_con_info_ssfs(): DBSL supports extended
connect protocol
B ==> connect info for default DB will be read from ssfs
download BRTOOLS DBA per note 1764043, require version 7.20 execution - uptime (10
patch 28 is required minutes)
create brtools user DBA create user brt$adm execution - uptime 5 minutes
create storage DBA Create dir rsecssfs/data and execution - uptime 5 minutes
directories rsecssfs/key Under
/oracle/<SID>/security
drop OPS$ users DBA lock OPS$ users execution - uptime 5 minutes
After getting system back from DBA team perform a clean system bounce and perform system
validation:
I hope ,you really got some useful information related to "SSFS" .Can you please give 30 sec of your time
now to have a look into main tutorials collection home page ,I guarantee you will get very useful tutorials
over there.
====================================================================================
What is SLD.
How to push ABAP system data to SLD <Step by Step procedure with screenshot>
What is RZ70 and What we don in RZ70.
SLD is System Landscape Directory ,A central repository containing complete System
Landscape information in terms of System component,Hardware Components,Software
Updates and many more.
RZ70 TCODE is used to configure SLD to that local system and used to send
ABAP system data to SLD.Please follow below steps to send System data to
Central SLD.
Proceed as 1 >2>3>4
Click on activate and Execute.You will get MSG Administration Data activated
successfully
Yes.
It will execute SLD data transfer in dialog also will schedule SLD data
transfer Jon in background.
====================================================================================
Suppose the< icmadm> password id locked or you have forgotten the password so below is the trick to
get new password for <icmadm user>.
cd /usr/sap/<SID>/sapwebdisp
Step 2:Delete icmauth.txt file: This file is a authorization file for <icmadm> user and contains
the password information.
rm icmauth.txt
Step 3 :Run BOOTSTRAP: Bootstrap is used to generate new webdispacter profile.But here well
not generate new profile as we have already existing profile and here our objective is to change
get password.
cd /usr/sap/<SID>/sapwebdisp
====================================================================================
=> (place cursor on 1st row of 'Buffer Gets') => Sort => SQL text is all the way to the right;
dbl click on SQL text => Explain => bdl click on lines below SELECT statement to show which
====================================================================================
In the next screen based upon your selection criteria you can process all TRFC on single click
Press Execute:
====================================================================================
Imp. Note: DONT DELETE the SEC directory ( this holds the SSL certificate,
intermediate certificates and some other stuff), controlWD.sh,icmbnd &
sapwebdisp files.
===============================================
save webdispatcher profile
==============================================
===============================================
===============================================
======
3) Copy from files form /exe directory to /usr/sap//sapwebdisp (or
/sapmnt//sapwebdisp/ where we have already installed dispacther )
===============================================
===============================================
======
cp -p icmadmin.SAR /usr/sap//sapwebdisp
cp -p wdispadmin.SAR /usr/sap//sapwebdisp
===============================================
===============================================
======
4) Extract the files in the sapwebdisp directory
===============================================
===============================================
======
===============================================
===============================================
======
5) Extract the new version of SAP cryptos to /usr/sap//sapwebdisp
directory.
===============================================
===============================================
======
===============================================
===============================================
======
6) Check the sap cryptos. (hpux-11.11-64 in our case ,please check your os
hardware version from uname -a then select correct folder)
===============================================
===============================================
======
check the binaries libsapcrypto.sl and sapgenpse are both the same version
under /exe directory and under /usr/sap//sapwebdisp/hpux-11.11-64
directory.
===============================================
===============================================
======
7) Now upgrade the sapwendisp as ROOT ID.
===============================================
===============================================
======
://usr/sap//sapwebdisp> ls -ltr
total 13234
-rr 1 adm sapsys 878 Nov 13 2001 LEGAL.TXT
-rr 1 adm sapsys 374 Nov 13 2001 ticket
-rr 1 adm sapsys 822 Feb 19 2003 LICENSE.TXT
-rr 1 adm sapsys 2766 Apr 17 2009 WHICH.TXT
-rr 1 adm sapsys 0 Mar 8 2011 Ver555.pl32
-rw-r 1 adm sapsys 1426 Mar 24 2011 hpux.txt
drwxr-xr-x 2 adm sapsys 96 Apr 4 2011 hpux-11.11-32
drwxr-xr-x 2 adm sapsys 96 Apr 4 2011 hpux-11.31-64
drwxr-xr-x 2 adm sapsys 96 Apr 4 2011 hpux-11.0-32
drwxr-xr-x 2 adm sapsys 96 Apr 4 2011 hpux-11.0-64
drwxr-xr-x 2 adm sapsys 96 Apr 4 2011 hpux-11.11-64
-rw-r 1 adm sapsys 33345 May 2 2011 Changelog.txt
-rwxr-xr-x 1 adm sapsys 186251 May 20 2011 icmadmin.SAR
-rwxr-xr-x 1 adm sapsys 186251 May 20 2011 wdispadmin.SAR
-rwsr-x 1 root sapsys 1720616 Aug 31 2011 icmbnd
-rwxrwxr-x 1 adm sapsys 4566584 Aug 31 2011 sapwebdisp
-rwxrr 1 adm sapsys 14178 Aug 31 2011 controlWD.sh
drwxrwxrwx 2 adm sapsys 1024 Sep 2 2011 sec
-rwxr-xr-x 1 adm sapsys 973 Feb 3 04:11 sapwebdisp.pfl_bkup2012_0203
-rwxr-xr-x 1 adm sapsys 970 Feb 3 04:13 sapwebdisp.pfl_03302012
-rwxr-xr-x 1 adm sapsys 970 Feb 3 04:13 sapwebdisp.pfl
-rw-rr 1 adm sapsys 725 Mar 21 02:20 dev_webdisp.old
-rw-rr 1 root sapsys 1504 Mar 21 02:20 dev_icmbnd
-rw- 1 adm sapsys 1339 Mar 21 02:20 nohup.out
-rw-rr 1 adm sapsys 48971 Mar 26 12:01 dev_webdisp
drwxr-xr-x 6 adm sapsys 96 Mar 30 04:17 admin
://usr/sap//sapwebdisp> pwd
/usr/sap//sapwebdisp
://usr/sap//sapwebdisp> id
uid=0(root) gid=3(sys)
groups=0(root),1(other),2(bin),4(adm),5(daemon),6(mail),7(lp),20(users)
://usr/sap//sapwebdisp> ./controlWD.sh UPGRADE
cp -p /usr/sap//sapwebdisp/sapwebdisp
/usr/sap//sapwebdisp/sapwebdisp.old
cp -p /sapmnt//exe/sapwebdisp /usr/sap//sapwebdisp/sapwebdisp
cp -p /usr/sap//sapwebdisp/icmbnd /usr/sap//sapwebdisp/icmbnd.old
cp -p /sapmnt//exe/icmbnd /usr/sap//sapwebdisp/icmbnd
===============================================
==============
UPGRADE DONE; PLEASE check the sticky bit on icmbnd
If needed use Command ==> chmod 4750 icmbnd
===============================================
================
===============================================
===============================================
======
ssl/ssl_lib=/usr/sap//sapwebdisp/hpux-11.0-64/libsapcrypto.sl
after change
ssl/ssl_lib=/usr/sap//sapwebdisp/hpux-11.11-64/libsapcrypto.sl
===============================================
===============================================
======
9) Now run the bootstrap process to regenerate sapwebdisp.pfl profile and
icmauth.txt file
===============================================
===============================================
======
it will regenerate the new sapwebdisp profile and icmauth.txt file with a new
password.
Number of IPC-Objects..: 8
Number of removed IPC-Objects: 8
*************************************************************
**
NO WebDispatcher running in sid with PID=19492 ; Re-starting WD
*************************************************************
**
===============================================
====================
Web Dispatcher STARTED with PID=20880 on 03/30/12-04:46:31
===============================================
====================
http://:81/sap/wdisp/admin/public/default.html
12) Shutdown webdispatcher and then copy the old profile values from the
saved sapwebdisp.pfl( saved OLD version) to the new sapwebdisp.pfl and
then restart the webdisp.
User Requests -- > Sap Web dispatcher --> Web dispatcher distributes to the application server
cd /usr/sap/<SID>/sapwebdisp
cd /usr/sap/<SID>/sapwebdisp
Start the web dispatcher with AUTO Restart: If in case of any crash, web dispatcher will start
automatically.
cd /usr/sap/<SID>/sapwebdisp
Execute Command: ./sapwebdisp pf=sapwebdisp.pfl auto_restart
-auto_restart With this option you can enable high availability for the SAP Web dispatcher at process
level.
====================================================================================
From Basis side high level steps for installation are mentioned below:
Steps for GRC 10.1 system:
What is SPUMG
SPUMG is very important tool used in Non unicode to Unicode conversion.It is standrad Tcode
provided by SAP based upon our SAP release.
SPUMG is used in Preconversion Phase:
Preconversion phase means,before doing actual unicode conversion,We need to complete many
presteps or we can say we need to prepare our system for Unicode Conversion so mostly
preconversion presteps are covered bt SPUMG Tcode.
Please read : How to perform addional steps with SPUMG for Unicode Conversion
http://www.sapbasis1solution.com/unicode-conversion-preparation-spumg/
====================================================================================
First Please read to Undersatnd What is SPUMG and How to start it.
Start SPUMG:
Go to Tcode: SPUMG and click on addional steps button as per below screen.
with this step report UMG_ADD_PREP_STEP will be initiated which consists of several reports
which were created for deleting corrupt or obsolete table data prior to Unicode conversion. On
the next screen the included reports are displayed. Choose Background. All reports will be
executed automatically.
Once Job finish then check status of all steps mentioned above.
====================================================================================
Central system:
Dialog work processes 15 (minimum 6)
System change options (SCC4) Allowed changes to repository and Cross-client customizing
Sender system:
Dialog work processes 15 (minimum 10)
Receiver system:
Dialog work processes 15 (minimum 10)
UNDO tablespace ~2% of estimated data transfer, UNDO RETENTION TIME set
appropriately (lowered)
Make sure to set the Database in NOARCHLOG mode for Central & Receiver Systems before
starting the copy.
The Database will be unmounted and remounted during the archivelog mode change.
Also, please make sure you have adequate freespace available in DB of the Receiver system.
Also, keep an eye on filesystem /usr/sap/ of Central system as the size of stats file will increase
rapidly during copy which may lead to the filesystem getting full.
====================================================================================
3. In the Directory section, select All Support Packages and click the Display button.
4. The All packages window opens. Verify that the correct package is installed for the SAP
release you are using (see Checking Package and Patch Versions Installed on the SAP
Application Server).
If the correct package is installed, a green light icon is displayed in the Status column.
If you do not have the required package installed, download and install it.
For more information on downloading and installing the required package, see SAP OSS
note # 480149.
3. Click the Other kernel information button . The System: Kernel information dialog
box opens.
4. In the Kernel information section, check the value of the Sup. Pkg. lvl.
If the level is lower than the required level for the SAP release you are using
(see Checking Package and Patch Versions Installed on the SAP Application Server), you
must download the latest kernel version and upgrade your existing one.
For more information on downloading and installing the required kernel patch level, see
SAP OSS note #480149.
====================================================================================