Re: a transport is imported into QAS in 2 minutes time.

the same transport when

imported into prd is taking more than 20minutes.why?and what to do?
Answer One reason for the above issue
# 1 could be that the QA system

has been defined as domain

controller and
since /usr/sap/trans is there in
the local system so the
time it takes to transport in QA is
very less and since in
case of PRD it has to travel over
network it will take more
time. You can check you network
also if incase there is any
issue.
Since in QA there will be less
number of users working, So
it may take less time. Whereas in
Production a huge number
of end users will be working and
the transports take lot of
time to import.
To resolve the concern prob. we
need to understand
background process of STMS.
There may be several reason depend
upon perticular
configuration at you end for the
concern delayed.
Verify following point to trace the
actual reason.
1. STMS CONSISTANCY
2. LOAD ON THE PERTICULAR SYSTEM
3. NETWORK CONFIGURATION.
4. what is inside in the requests &
configuration
difference between QAS & PRD.

Re: If the server buffer memory reaches 95% of memory what will will be the
measure have to take for solve that issue.

it depends upon the no.of

application servers u have in ur
prd,you may solve this issue with
Logon load balancing
using the tcode smlg. if it
repeatedly accuring and u have
enough memory u may increase the
abap/buffersize parameter
but prefered id do logon load
balancing so that it may not
repeat
Lets suppose we have 500 users in sap system 250 members are already logged into the
system and rest of the 250 are unable to login along with master users like sap* etc.
How do you troubleshoot this issue ?

Hi,
The login procedure always depends
on Ram Size and each
dialog WP can switch to 8 login at
a time .If the Ram size
is 512 MB then we could see
atleast 8 dialog WP and it can
accomodate atleast 60 logins at a
time in one instance with
same User credentials all over the
Network and usually when
coming to SAP the Ram size will be
in TeraBytes and not
less than that in Corporate
organizations which shoudl not
cause any difficulty .
Re: If a tcode is taking too long time to finish and I wand to end the work process in
sm50 how to find which work process is currently executing that tcode?
Answer Go to SM51, select one server and
# 1 press ctrl+shift+F7 -->

gives the users, terminal, T-codes

using right now.
If a Tcode is taking a long interval of time one can goto

Tcode SM50 it shows the list of local Users and can kill
the process displayed with the present TCode being used
by
User and can kill that process.If not one can make use of
Tcode SM66 which gives a list of Global Users and can the
kill the process and start a new session.
Usually If it is taking long time to execute Tcode.It is
due to performance issue and this is solved by Killing
process in Tcode "SMX" kill the process in SMX for
OSCollectors which is delaying executing processing or
execution of Tcodes and can overcome this issue.
Explain Parameters for SAP Memory Management?
Answer ztta/roll_first
# 1 Defines the first part of the roll

area that is allocated to

a dialog process.
ztta/roll_area
Defines the total roll area per
work process
rdisp/ROLL_SHM
Defines the size of the roll
buffer
rdsip/ROLL_MAXFS
Defines the size of roll buffer
and roll file
em/initial_size_MB
Defines the fixed size of extended
memory
ztta/roll_extension
Defines the user quota for
extended memory
abap/heap_area_dia
Defines the limit for the amount

of local memory allocated

to dialog work process
abap/heap_area_nondia
Defines the limit for the amount
of local memory allocated
to non-dialog work process
abap/heap_area_total
Defines the limit for the total
amount of heap memory
allocated to all work processes