1.How to check the number of application servers an SAP system has? (Except SM51)
You can use tcodes 0s07, rz03, rz10, Smlg
2. You have configured a application (Basically a ABAP program) where a mail will be sent to some person. But the Queue does not move out automatically, u have to sent it manually. What might be the problem and what services you need to check?
SAPCONNECT is running, else schedule to run report RSCONN01 like every 5 mins
SCOT –> click on Job icon ( Shift + <F7> ) , if you see a job there check the Period , it
will show how often this job is executed. If you don’t see any job there click on create
button to there to Schedule the job. Other way of checking is SM37 –> enter RSCONN01
against ABAP program name , user * , jobname * ; if scheduled it will show the job
3. How to delete SAP*, list command? Any precaution needs to be done?
* Delete from usr02 where bname = ‘SAP*’ and mandt = ‘***’;
* Can delete from SU01
If you delete the userid, SAP*, from the database, SAP has this userid defined in its kernel (the SAP executable code that sits at
the operating system level, i.e., disp+work).So it will allow to login again with sap* after system restart. And it will have the following properties
The user is not subject to authorization checks and therefore has all authorizations.
The user has the password “PASS”, which cannot be changed
To avoid this the parameter login/no_automatic_user_sapstar should be set to a value greater than zero in default profile.
http://help.sap.com/saphelp_nw2004s/helpdata/en/52/671792439b11d1896f0000e8322d00/content.htm
or
delete from <SID>.USR02 where BNAME=’SAP*’ and MANDT=’<client>’.
Ensure all the charecters in USR are capital and <SID>= SID of your system
After doing this you can login to corresponding client with user sap* and default password
“pass”
When you delete the user SAP*, please make sure you also add the parameter
login/no_automatic_user_sapstar = 0 to instance profile (your need to restart the SAP
insttance)
As NW2004S, that parameter prevent SAP* login using PASS password.
But before you do this, please just try to delete the SAP* user first and login using PASS
password, if that not work than you should add the parameter and restart the SAP.
4. Explain Lock concepts? Briefly?
Lock concept is detailed, in short..dialog work process processes the user request and triggers the enqueue work process which locks that record against that user id. The lock table resides in the main memory. To release lock either go to sm12 or end user session via sm04.
It works in First In First Out manner when it comes to unlocking an Object.
When it happens automatically system will not log it but when you manullay unlock it using SM12 it will log.
5. How many minimum dialog work process an instance must have and why?
- Dialog work processes handle screen changes and interaction with the SAP graphical user interface (through the dispatcher). By default, two dialog work processes are assigned to each instance; the maximum number of dialog work processes is 99 per instance.
- The number of other work process types can only be increased if there are more than two dialog processes. Number of DIA processes must be larger than or equal to the total number of update processes and background processes.
- When a tcode is executed, it is carried out in a number of dialog steps in parallel in order to enable this we must have minimum of 2 dialog processes.
- if the tRFC is called from the update or the background processing, it needs a free dialog work process.
