Useful Basis Troubleshooting Tips_2:

SAP Solution Manager Features

 SAP Solution manager Overview

 Describe SAP solution manager features

 How does SAP solution manager adds value to the business?
 What is current version of Solution Manager?
 What are Solution Manager’s core application life cycle processes?

---------------------------------------------------------------------------

SAP Solution Manager is the central lifecycle management hub for SAP systems.

The SAP Solution Manager is a platform that provides the integrated content, tools, and methodologies that you need to
implement, support, operate and monitor your enterprise's solutions from SAP.

 With SAP Solution Manager, companies can minimize risk and increase
the reliability of their IT solutions.
 SAP Solution Manager helps reduce TCO (Total Cost of Ownership)
throughout the solution life cycle.
 SAP Solution Manager helps companies manage their core business
processes and link business processes to the underlying IT infrastructure.
 SAP Solution Manager supports both SAP and non-SAP software and
helps companies get more from their existing IT investments.
 SAP Solution Manager enables you to obtain the maximum value from
your SAP investments

SAP Solution Manager brings direct value to your business by

 Ensuring a cost-effective implementation and operation of new technologies

such as SAP HANA
 Providing mobile apps, enabling your workforce to take informed decisions
always
 Leverage the full potential of new technologies like SAP Hana, Mobility , Cloud
etc

The current version is SAP Solution Manager 7.2

SAP Solution Manager supports 11 core application lifecycle processes

What are the functions of SAPOSCOL ?

This article answers following queries :

 What is SAPOSCOL ?
 What are the functions of SAPOSCOL ?

SAPOSCOL is an operating system collector. It is a standalone program that runs in operating system
background.
SAPOSCOL collects data about operating system resources like

 CPU Utilization
 Usage of Physical Memory
 Usage of Virtual Memory
 Usage of filesytems
 Usage of Physical disks
 Usage of running processes

SAPOSCOL runs exactly once per host and runs independently of the sap system.

By default, SAPOSCOL collects data every 10seconds and records it. It also records the hourly
average statistics for the last 24hours in shared memory. This data will be fetched by background job
“SAP_COLLECTOR_FOR_PERFORMANCE” and writes it to the MONI performance database table.
Applying sap license

 How to apply SAP license in a SAP system?

 When to apply license for an SAP system?
 How to delete an existing license of an SAP system?
 What is the transaction code used to apply license in SAP?
 Explain the process of applying license in SAP?
 How to request an SAP license key?

----------------------------------------------------------------------------------------

In SAP environment, there will be a requirement to install a license to a new installed SAP
system or to a system refreshed from another system. This is the primary step in the post
refresh activities of an SAP system.
SAP license key can be requested from Service Market Place from the following link :
http://service.sap.com/licensekey
Please download license key for a SAP system and store in your local desktop.
Once the license files are downloaded from market place, login into 000 client using SAP*
user into ABAP stack of an SAP system on which you would like to apply license.
SLICENSE is the transaction code for applying license in SAP system.
Execute transaction SLICENSE, which results in a screen similar to below

To list old licenses existing in the system, click on “Old Licenses” tab in the above screen. It
lists all the old licenses.
Select each license and delete license by navigating as shown in above screen
Repeat this step until all old licenses are deleted.
To install new license click on install button shown in the below screen

It opens screen as shown below. Please navigate to the location where license file that was
downloaded from market place was kept in your desktop and select the file and click open
to input the license file.

It then displays message as below after successful installation of license key.

Transport Error – Transport Control Program tp ended with error code 0247

This article answers the following queries:

 How to resolve the transport error “Transport Control Program tp ended with error code
0247?
 How to resolve the transport error – Errors: addtobuffer has problems with data- and/or
cofile?
 How to resolve transport issue encountered while adding a transport to import queue of
target system?

--------------------------------------------------------------------------------------
Sometimes, while you are adding a transport request into import queue of target system as shown
below, you might encounter error as
“Transport Control Program tp ended with error code 0247 "?
Errors: addtobuffer has problems with data- and/or cofile? (Please refer screenshot 3)
After pressing Yes in the above screen, you may encounter below error:
Most probable reasons for this issue could be, due to transport did not get released from the source
system.
Please login to the source system of the transport and goto transaction SE01 and provide the
transport number as shown below and click on display pushbutton to view the release status of the
transport
In the below screen, please drill down the transport and check whether all the transports under this
are released ( if there is tick mark after the transport, it means it was released).
If there is no tick mark on any of the transports below the given transport number it means the
transport is not yet released. In those cases, you can even view truck symbol in the active state.

In the above screenshot, all the underlying transports were released(as there is tick mark after those
transports), but the main transport is not yet released as indicated my active status of the truck. In
these cases, just keep the cursor on the main transport number and click on truck symbol to release
the transport.
Please note that you can release the transport only if you have access to do the same. If basis
administrator do not have access, he/she should approach the respective team and get this
transport released as per the process mentioned above.

Please find below another scenario, in which 2 of the 3 child requests not released. In this case, each
of the individual transport to be selected and released (by clicking truck button) and finally release
the main transport.
Once the main transport is released, data file and cofiles will be generated for that transport
request in the source system. Then no longer, the error mentioned above will be encountered will
adding the transport request to import queue of the target system as the request was released and
data and cofiles were also generated under /usr/sap/trans/data and /usr/sap/trans/cofiles
directories of the system.
How to post system message in SAP ?

This article answers the following queries :

 How to post system message in SAP ?

 How to delete the posted system message in SAP later?

-----------------------------------------------------------------------------------------
Occasionally, SAP system will be shut down due to various maintenance activities like kernel
upgrade, offline backup, client copy etc. Before doing any of these activities it is best practice to
communicate to SAP users that system won’t be available during that time so that users will plan
their work accordingly.

This system message can be posted using SM02 transaction code in SAP.
A message like “R3 system won’t be accessible between 4:00am to 5:00am due to planned kernel
upgrade activity. Please plan your work accordingly” can be posted to keep the customers informed
about the downtime of the system.
Go to Transaction SM02 and click on create button as shown below :
This pops up another window as shown below. In this window, you can compose the message that is
to be published. In that window, you will have to provide details like client number, server name,
logon language, expires on, delete on fields as shown below.
If specific client is specified in the above window, only users of that client can view the system
message posted. If an SAP system consists of more than one application server, you need to select
application server on which this message should appear.
Specify expires on field to mention the system when this message should expire so that message
won't be visible to users after that.

The delete on field is used to mention the date and time on which the posted message should be
deleted from the system.

In case you would like to delete the system message manually, you can even do so, by selecting the
system message and clicking on delete icon as shown below.

System prompts to confirm deletion as below. Message gets deleted if confirmed by pressing Yes
button in the below screen.
SAP Web Dispatcher and its functions

This article answers the following queries :

 What is SAP Web dispatcher ?

 What is Demilitarized zone (DMZ)?

 What are the advantages of DMZ ?

 Where does SAP Web dispatcher runs?

 What are the functions of SAP Web dispatcher ?

SAP WEB DISPATCHER :

SAP web dispatcher is used to distribute web requests. It is based on the same technology as SAP
ICM(Internet Communication Manager).

Please note that apart from web dispatcher, web requests can also be distributed through message
server or ICM. However, these have only limited functionality and some disadvantages and is
therefore not recommended by SAP.

SAP web dispatcher is the SAP recommended process/method of distributing web requests as it has
some advantages and additional functionality.
Demilitarized Zone (DMZ) :
In computer networks, a DMZ is a computer or a small network inserted as a neutral zone between
a company’s private network and the outside public.
It prevents external users from directly accessing the company’s server and thus provides security.

In SAP scenario, DMZ is a neutral zone inserted between internet and SAP Netweaver Application
server so that external users from internet cannot directly access SAP netweaver application server.

SAP Web Dispatcher runs within the DMZ

Functions of SAP Web Dispatcher :

 Distribution of requests to both ABAP or Java application instances

 Denial of unwanted requests (i.e. request filtering)

 Buffering of web requests

 Ensures that customers can access the SAP system via one address

 Provides security as it runs in DMZ (Demilitarized zone)

 Handles distribution of both http and https requests.

 How to unlock if SDM user id got locked in SAP ?

This article answers the following queries :

 How to unlock if SDM user id got locked in SAP ?

 SDM deployments fail due to SDM account lock. How to unlock?

 SDM account got locked after 3 successful attempts. How to unlock?

Sometimes, you encounter a situations like

i) SDM deployments fail and upon investigation you found that SDM account got locked. You can only
deploy again after unlocking the SDM account.
ii) User tried to login to SDM account with wrong password three t imes and account got locked.

Proceed as follows to unlock the SDM account :

If your operating system is windows, please proceed as follows :
i) Open the command prompt
ii) Login as sidadm
iii) Navigate to the following path :
<Drive>:\usr\sap\<SID>\JC<nn>\SDM\program
iv) At this path provide the following commands:

sdm jstartup “mode=standalone”

sdm changepassword “newpassword=Enterthenewpassword”
sdm jstartup “mode=integrated”
startserver.bat

If your operating system is Unix, proceed as follows :

i) Open a telnet window

ii) Login as sidadm user
iii) Navigate to the /usr/sap/<SID>/JC<nn>/SDM/program
iv) At this path provide the following commands :
./sdm.sh jstartup “mode=standalone”
./sdm.sh changepassword “newpassword=Enterthenewpassword”
./sdm.sh jstartup “mode=integrated”
./startserver.sh
Important SAP Basis Transaction codes
AL08 Global User overview
( Lists all the users of all the instances of the SAP system )
AL11 Display CCMS operating system files
AL12 Buffer synchronization
DB02 Missing database objects and space requirements
DB13 Scheduling (Used for scheduling various standard jobs
like checkdb, backups etc)
FILE This tcode is related to archiving.This is used to map
assignment between logical and physical names
OSS1 SAP service marketplace logon
PFCG Used for Role maintenance
RZ01 Graphical background job scheduling monitor
RZ03 This is control panel for operation modes and server states.
Operation mode can be chosen using this Tcode
RZ04 Used for maintenance of operation modes and instances
RZ10 Used for profile maintenance and changing SAP parameter values
RZ20 Alert Monitor
RZ21 Alert monitor customizing
SA38 To execute an ABAP program
SALE IMG Application Link Enabling
SCC1 Copy client via transport request
SCC3 Client copy Log
SCC4 Client Administration
SCC5 Delete Client
SCC6 Client Import
SCC7 Client Import post processing
SCC8 Client Export
SCC9 Remote Client copy
SCCL Local Client copy
SE01 Transport Organizer
SE03 Workbench Organizer Tools
SE06 Set up workbench organizer
SE07 Display status of transport system
SE09 Workbench Organizer
SE10 Customizing Organizer. This is used to view transport requests based on
type, user etc
SE16 Display table contents
SICK SAP Initial installation consistency check
SM01 Used to lock transactions
SM02 To post system messages in case of planned or scheduled
downtime of SAP systems
SM04 Local user list (It means it lists users belonging to only that instance you
have selected)
SM12 Used to display and delete SAP locks
SM13 Used to display update records
SM21 System log. It contains very important system messages
 and will be useful for troubleshooting most of the issues
SM28 SAP Initial installation consistency check (Same as SICK
tcode)
SM30 Call view maintenance
SM31 Table maintenance
SM35 Batch Input Monitoring
SM36 Schedule Background Jobs
SM37 Overview of background jobs
SM50 Overview of work processes
SM51 Overview of Instances
SM56 Number range buffers
SM58 Asynchronous RFC error log
SM59 RFC connections maintenance like creation, modification etc
SM63 Display/Maintain Operation Modes
SM64 Used to trigger an event
SM66 Global work process overview
SM69 Maintain external operating system commands
SMLG Used for Logon group maintainance
SMLI Used for Language Import
SMLT Used for Language Administration
SP01 Spool control. Used to view spool related details
SP02 Used to display output request details
SP11 Temse table of contents
SP12 TemSe Administration
SPAD Spool Administration and Printer Configuration
SPAM SAP Support Pack Manager
( Used for performing SAP support pack upgrade)
SPAU Display modified objects in the runtime environment
This tcode is used during SAP support pack upgrade
SPDD Displays modified DDIC objects
This tcode is used during SAP support pack upgrade
SPRO Customizing : Initial Screen
ST01 SAP system trace
ST02 Used to view all the SAP R/3 buffer statistics
ST03 Used to perfrom workload analysis
ST04 Used to view various statistics of RDBMS activities
ST05 Used to take SQL Trace
ST06 Operating system Monitor
ST07 Application Monitor
ST10 Table call Statistics
ST11 Display developer traces
ST22 ABAP runtime error analysis. Analysis of dumps
STMS Transport Management System
STUN R/3 Performance Menu
SU01 User Maintenance
SU01D User Display
SU10 Mass changes to User masters. Mass user maintenance
SAP System Log

This article answers following queries:

 What is System log? How it will be useful?

 How to check system log in SAP?
 How to check all remote systems log in SAP?

---------------------------------------------------------------------
System Log:
In an SAP system, for every important action system log will get updated. So, in
case of any issues with the system, basis administrators need to check the
system log first to identify any errors or warnings.
Many times, we can resolve system issues by checking the system log and
searching for relevant notes in the market place using keywords found in the
system & applying them.
In case of issues like update failure, lock table overflow, spool overflow,
operating system issues, network issues, table space full issues and other
database issues system log will get updated with the error message and the
relevant time stamp. By using this timestamp and error message, basis
administrator can identify the cause for the issue and can fix the issue.
Based on the issue and the time stamp in system log, in many cases, you can
find out relevant ABAP runtime dumps in ST22 (which provides much more detail
about the issue) and the issue can be tackled accordingly.
How to check System Log?
System log can be checked using SM21 transaction code. Login to SAP system
and goto SM21 which results in the similar screen as below:
As shown in the above screen, we can mention From date/time and To date/time
and we can view system log based on problem classes.
As shown in the above screen there are 3 problem classes

 Problems Only
 Problems and warnings
 All message

Based on the requirement, any one of the above problem classes can be
selected.
By default, User text box is left empty. It means it displays system log related to
all the users. In case you would like to view system log of any specific user, you
can mention the user id there.
After providing these input selections, to view the system log of the
application server on which you have logged on, please click “Reread
system log” pushbutton (which was highlighted in red). It displays similar
screen as below:

As shown in the above screen, in the system log you can view following
information:

 Time Stamp
 Type of work process
 System Number
 Client Number
 User id (who executed the transaction)
 Tcode executed
 Priority
 Text related to the issue
Based on al l the above details, basis administrator can figure out the
issue. In most cases, if additional details are required related to dumps,
they can check in ST22 transaction.
How to check All remote system logs?
Please note the above process of checking system log is for only one
application server (i.e. dialog instance) in which we have logged in.
If your sap system is a distributed system comprising of many
instances/application servers, it would be difficult to log in to every
instance separately and checking system log. To overcome this, SAP has
provided an option of checking all remote system logs (i.e. logs of all
instances of an SAP system) in SM21. So, using this by logging into any
instance of an SAP system, logs of all other remote instances can be
checked. By default, this option is not enabled.
To view “All remote system logs”, navigate as shown in below figure in
transaction code SM21

After choosing “All remote system logs” option as above, pls provide
selection criteria and click on Reread system log pushbutton to view logs
of all instances of an SAP system as shown below
 How to view OSS messages based on their various criteria?

This article answers the following queries:

a) How can we check OSS messages owned by us?
b) How to check OSS messages of other users ?
c) How to spool a report on the oss messages created between any 2 intervals?
d) How to view all Oss messages based on their status for any given period?
e) How to export Oss messages list to an excel?
------------------------------------------------------------------------------------

How to check Oss messages owned by us

Login to Service Market Place and navigate to “ my Inbox” as shown below :

It displays all the customer messages that are owned by you.

(However in the example above there are no messages displayed, as I haven’t
created any)

How to check Oss messages owned by others

Please select Customer Messages from the drop down of Search for (highlighted
in the above screen) and click on Go button , to proceed to the following screen
As shown in the basic search of above screen, Oss messages can be filtered and
viewed based on:
 Customer Number

 Installation Number (based on particular system)

 Reporter Name ( User who has created the message)

 Status ( based on status of message)

 Create date ( based on create date interval)

 Changed within last days (based on last change)

 Priority

 Component

 Message Number

How to spool a report on the OSS messages created between any 2

intervals
Advanced search tab will have much more options than basis search as shown
below
For example : If I have to view all Oss messages, which are in Status “In
Processing by SAP” and “Customer Action” and whose priority is Very
high/High/Low and messages which were created between 15.09.2011 to
22.09.2011, I can select as shown in the above screen.
After selecting all these, click on Search push button which displays all the Oss
messages which meets these criteria as shown below:

Click on Down All pushbutton (highlighted) in the above screen, to download

these oss messages into an excel sheet for further processing/reporting
How to download SAP kernel

This article answers the following queries :

 How to download SAP kernel ?

 What is the process to be followed to download SAP kernel?
 What is the best practice for SAP kernel upgrade?

----------------------------------------------------------------------------------------

SAP Kernel can be downloaded from Service Market Place(SMP).

To download SAP Kernel, login to SMP and goto Software Downloads ->
Software Downlad Center. From there please navigate as below
Under Support packages and Patches, navigate to My Company’s Application
Components -> My Company’s Software

Click on "My company's software" link to view all the company’s software that
is available as below:
From the above list, please select your software for which kernel upgrade to be
done example : SAP Netweaver PI or SAP Netweaver or SAP SCM or SAP R/3 or
SAP R/3 Enterprise etc)

In the below example am selecting SAP Netweaver as my software and

proceeding further
In the above list, select the correct version of software for which you would like
to download kernel. In this example, am selecting “SAP EHP1 FOR SAP
NETWEAVER 7.0” and proceeding further.

Note : The current software version can be identified from SAP ABAP System’s
menu. Please navigate to System -> Status. After under SAP system Data tab,
by clicking Component Version/Component details you can view the version of
the software.

After selecting software, select Entry by Component link as below

It lists components as below :
Please select Application Server ABAP in that list and proceed further. It leads to
below screen.

Please select the appropriate kernel from the list based on your SAP system
setup like 32 / 64bit , Unicode/NonUnicode, Operating system on which your
system runs :

In my case, am selecting SAP kernel 7.01 64bit Unicode and Operating system
as Windows on x64 64bit.
After this click on #Database independent link as above to view below screen

Select the kernel patch which you would like to download and click on Add to
Download Basket tab. This results in below screen

Next in the above screen, click on database in which your sap system is running.
In my case, am selecting MS SQL server as the database and proceeding further.
 In the above list select the kernel patch which you would like to download and
click on “Add to Download Basket”. Once you click this button, a screen similar
to below will appear
Click on download basket pushbutton which displays screen as below:

In the above screen, click on the above items and save these files in your local
desktop and later transfer these files into the desired server in which you would
like to perform kernel upgrade.

Best practice is to download N-1 kernel patch from the Service Market Place. It
means if the current kernel patch is 176 and the prior kernel patch is 150 and if
you are in a lower kernel version (for ex: 124 etc), it is better to upgrade to N-1
kernel patch i.e. to 150 instead of upgrading directly to 176. The reason for this
is sometimes upgrading to latest kernel may lead to some issues like
performance problems, system startup failure etc. To avoid this, it is suggested
to apply N-1 kernel patch.
CCMS – Availability and Performance Overview in SAP

This article answers the following queries:

 How to check system availability in SAP using RZ20?

 What is the use of CCMS – Availability and Perform Overview ?

--------------------------------------------------------------------------------------
If your landscape is very big and contains more than 50 servers, it would be
tough to manually monitor all those systems. So, it is better to get CCMS
configured in Solman system and all other satellite systems that are to be
monitored to be connected to that.
If in your landscape, CCMS monitoring is configured properly in Solution
manager, then you can configure receipt of CCMS alerts in case of any non-
availability/performance issue of any SAP system based on the thresholds set.
However, those alerts are not descriptive enough to understand the issue. To
troubleshoot the issue and to figure out the exact issue, you will need to follow
the below process:
Goto RZ20 transaction of Solution manager and navigate to “SAP CCMS Monitor
Templates” as shown below
As highlighted above, please click on “Availability and Performance Overview” to
proceed to below screen :
You will have 2 nodes as shown in the above figure :

 Availability
 GRMG-Tested Availability

Drill down in both of these nodes and figure out if any sub-node (i.e. SAP
system) is in red color. It means that there is some issue with that system.
Please find screenshot below :

We can further drill down these red systems to understand the issue in detail.
If you are able to capture SID of the affected system from the CCMS alert, then
you can directly go to that respective SID in the above screen and drill that node
down to figure out the issue as shown above.
 When file system is full – what need to be done?

This article answers the following queries:

 If file systems in SAP server is full, what need to be done?

 How to avoid file system full in SAP?
 How to delete un necessary files in file systems of SAP?
 How to delete core files in SAP?
 How to delete trace files in SAP?
 How to delete stat files manually in SAP?
 What is the transaction code used to delete stat files manually in SAP?
 What are various reports to be run to cleanup when file system is full?
 How to prune the file systems in SAP?
 How to delete old archive files in SAP?
 What is the location of work and data directories in SAP?
 What is the location of global directory in SAP?
 Can we delete old page file and role files when the SAP system is online?
 What is the sap parameter to set the trace level in SAP?

-----------------------------------------------------------------------------------------

Sometimes, a basis consultant will get alerts or information from customers that
the file systems are full. To avoid system issues and to increase uptime of the
SAP system, In those cases, we have 2 options.
i) Delete un-necessary files in the file system
ii) In case you found file system is defined as too small then increase the size of
them.

In this article, am covering the option 1 mentioned above.

Let us assume that the system id(SID) of the sap system is DP1. Then the

i) Work directory in (Unix, WindowsNT operating system)

is /usr/sap/DP1/DVEBMGSnn/work (where nn is the instance number)
ii) data directory in (Unix, WindowsNT) is
/usr/sap/DP1/DVEBMGSnn/data (where nn is the instance number)
iii) Global directory (i.e. for all instances) is
/sapmnt/DP1/global (for UNIX )
\\<sapglobalhost>\sapmnt\DP1\sys\global (for WindowsNT)

Please follow below steps to avoid this issue :

1) Delete core files from work directory

 Work directory in Unix often contains old core files which were generated due to
previous program terminations. These core files need to be deleted

2) Delete old log files and spool files

Under global directory there will be many log files which can be deleted
regularly.

Those files are

Log file type Naming Convention

Spool requests nnnSPOOL ( where nnn=client)

Job logs nnnJOBLG
Batch input logs BI<hostname><instance-number>

Following reports can be run using SE38 or through background job for selective
deletion of the files mentioned above.
RSPO0041 - This report is used for deletion of old spool files
RSBTCDEL – Used for deletion of old job logs
RSBDCREO - Report can be used for deletion of batch input log files and
reorganization.

3) Deletion of old ABAP/4 trace files

Some trace files with the name AT<instance number>nnnn will be in the data
directory. Old files of this type can be deleted. The maximum available space for
all files is defined by the parameter abap/atrasizequota. Also transaction SE30
can be used to delete the files.

4) Deletion of old archiving files

When old data is archived, some files are written to the global directory. The
naming convention of those files is Rxxmmddn (xx= application, mm= month,
dd=day, n=number). For example, RMM11056

If these files are already saved on tape and these data is no longer required for
productive operation, then these files can be deleted from the disk

5) Deletion of old output requests

Output requests are normally stored on the data directory. Naming convention
will be like SP*. Under normal scenarios, they are deleted automatically when
the output is completed. In case you see they are not getting deleted, you can
delete the same
6) Page file and Roll file

Under the data directory, normally page files and roll files are stored. Naming
convention will be like PAGFILnn and ROLLFLnn. Please note that page file and
roll files can only be deleted when the corresponding SAP instance is offline.

Deleting these files hardly makes any sense because these files will start
growing to the allowed maximum extent during the R/3 system start up.
However in some special scenarios (during or after client copy), the required
space can be retrieved by deleting these files. As mentioned earlier, please note
that this can be done only when the instance is offline.

The maximum size of the roll file is given by

(rdisp/ROLL_MAXFS – rdisp/ROLL_SHM) * 8 Kbytes

A similar formula applies to the paging file also.

In some scenarios, to avoid the file system full issue, we can even move these
page and roll files to a different file system by defining alternate values for R/3
parameters DIR_ROLL and DIR_PAGING

7) Deletion of Old sort and Extract files

By the ABAP commands SORT and EXTRACT, temporary files are created. The
location of these files are set using profile parameter DIR_SORT or
DIR_EXTRACT.

The temporary files for sort are named S+++++++<Extension> (On Windows
NT .dat is used as extension and on Unix there is no extension). Similarly for
Extract, E+++++++<Extension> will be the file naming convention.

These files will be automatically deleted after the execution of these SORT and
EXTRACT commands. However, in some scenarios, an abrupt termination can
happen and these files won’t get deleted automatically. Those old files can be
deleted by an administrator.

The exact file names for these are stored in the profile parameters FN_SORT or
FN_EXTRACT

8) Deletion of trace files

Trace files are created during a new system startup and they can be deleted.
They are contained in the work directory

9) Deletion of stat file or moving to different location

 Please check whether the stat file which consists the work load statistics, has not
been reorganized for some time and has therefore become too large. In
emergency cases, this file can be either deleted manually or can be moved to
different location.

To delete the stat file manually, please proceed as follows:

Goto ST03 transaction , call the delete function on the relevant instance by
choosing :
Workload -> Reorganize -> Delete seq.stat.file

To change the location of stat file, change the value of system parameter
‘stat/file’ to a new location.

10) Deletion of job logs at operating system level

In some emergency cases, where you cannot start the R/3 system at all, the
measure is to delete the job logs at operating system level and run RSBTCDEL
report in forced mode.

Note: How to delete job logs at operating system level will be covered in a
separate article later

11) Changing the trace level

If the trace files (dev_*) in the work directory are very large(normal size 0.1 to
20Kbyte), it is likely that the trace level is set to very high value. In SAP,
rdisp/TRACE parameter is used to set the trace level. Normal value for trace is
1.

Please cross check this SAP parameter and reset to 1 if the value is maintained
as 2 or higher. If this value is set to high, much more detailed trace will be
collected and trace file sizes are likely to increase. Therefore recommending to
decrease or set the trace level to 1.

Please refer below link to know, how to set the trace level in SAP.

Iam sure, if you duly follow the steps mentioned above, file system full issues
can be addressed. However, if after carrying out all the above steps there is no
improvement, then please consider to increase the file system size by requesting
space to the relevant team.
Explain Java Virtual Memory in SAP

This article answers following queries :

• Explain memory management of Java Virtual Machine(JVM) in SAP

• Explain JVM memory areas in SAP
• Explain Young generation, Tenured generation and Permanent
Generations
• How to maintain JVM parameters in SAP?
• Which tool is used to configure Java VM settings in SAP?
• How JVM automatically takes care of memory allocation?
• Explain Used memory, Allocated memory, Virtual memory

----------------------------------------------------------------------------------

The JVM automatically takes care of allocation of memory space for java
applications.

A “generation” reserves space in the address area of the host.

While starting sap system, the java virtual machine allocates operating
system memory for each of the generations. This initially allocated
memory is termed as “initial” or “initial size”. After complete usage of
initial size, the java virtual machine further allocates memory in stages
upto a maximum defined value termed as “max size”.

The memory space that is available is called the available memory or

allocated memory. Since this space is reserved by the operating system,
it is also called as “reserved space”. The space that is not reserved is
called as “virtual memory”.

The “ reserved space” is available to the JVM. However, not all the
memory is used always. It will be used based on the requirement. The
memory that is actually used by the java applications is termed as “used
memory”. If less space is required by the java application, the memory is
returned to the operating system in stages.

The memory area of JVM is mainly divided into 3 areas as listed below
• Young generation
• Tenured generation
• Permanent generation

The 3 memory areas Young, Tenured and Permanent differ based on the
data stored in them. Each of these generations has an initial and
maximum size.
Young Generation : The objects that have been newly created by the
applications are stored in the younger generation.

For younger generation, we can define initial size and maximum size with
the parameters -XX:NewSize and –XX:MaxNewSize respectively

Tenured Generation: The objects that have been required for a longer
period of time by an application are automatically moved to the tenured
generation
For tenured generation, we cannot directly set initial size and maximum
size directly. These are calculated from the parameters of the younger
generation and the parameters –Xms and –Xmx.

The parameter –Xms is the “start heap size” or “initial heap size” and it
defines the total initial size of the young and tenured generations.

The parameter -Xmx is the “max heap size” and it defines the total size
of the young and tenured generations.

So indirectly, it means that

Initial size of tenured generation = (-Xms) - (-XX:NewSize)
Maximum size of tenured generation = (-Xmx) – (–XX:MaxNewSize)

Permanent Generation : The objects that are permanently required by the

JVM such as classes and objects are stored in the Permanent Generation.

For permanent generation, we can define initial size and maximum size
with the parameters –XX:PermSize and –XX:MaxPermSize respectively

Config Tool is the only tool used to set JVM parameters in an SAP java
system.