1. What is the formula of HIT RATIO?

Generally, in database terms, hit ratio is the number of times a record/row is requested versus the number of times the record/row is found in the buffer. So if record/row 140 of table BSEG is requested 5 times but only the first time does it need to be pulled into the buffer and is already there for the other 4 reads - that would make the hit ration 80%. Of course, that assumes that the row/record hadn't been swapped out of the buffer due to other objects needing the buffering space. 2. How to know whether a system is Unicode or non Unicode? in sm51 t-doe we can find the release notes button in the application tool bar if u click, u can see the total information like database, os, kernal version and unicode or non unicode. Go System >click on Status It will give the server information. On SAP SYSTEM DATA in UNICODE SYSTEM field YES or NO At OS level in cmd prompt type "disp+work -version". 3. What is Primary memory, Heap memory in SAP Basis? Primary memory is the memory space assigned to a process in which it loads its user context often called roll area. It is allocated per process using the parameter ztta/roll_area. When this part is exhausted, extended memory is assigned. Extended memory is assigned as pool in which every work process has a part reserved. It is defined using em/initial_size_MB. Heap Memory stores User Context when Extended Memory allocated to a work process gets exhausted and the work process requires more space to continue. Heap Memory stores contains same type of Data as Extended Memory. Heap Memory is allocated dynamically according to requirement and not during system startup. When the work process starts using heap area it enters in to PRIV mode. Heap area is defined as a block for whole instance and not for individual process using abap/heap_area_total. Sequence of allocation of Memory in case of Dialog work process:This is the order in which the memory space is used. If Roll memory is filled then the memory in extended memory is used and soon as shown below. The memory allocation sequence is same in windows & UNIX. Initially every work process is assigned some part of roll area. This part is decided by ztta/roll_first. When this part is exhausted, part from extended memory is provided. This part is defined as ztta/roll_extension.

When this part is also exhausted, then remaining part of roll area is given to process to utilize. This is defined as ztta/roll_area. If memory requirement is still not fulfilled, heap memory is provided from ABAP/Heap_Area_total and process is marked as PRIV. ztta/roll_first ztta/roll_extension ztta/roll_area abap/heap_area_dia maximum size of Roll memory max size of extended memory max size of local roll area max size of heap memory

When a process is in PRIV mode, it is dedicatedly assigned to a user. If more processes are in PRIV mode, they are dedicatedly assigned to a user, leaving less no. of processes for other users. This drastically decreases the server performance by increasing the response time. If work process still require more memory, it is marked for restart and all memory freed up from this returned to Application. http://help.sap.com/saphelp_nw04s/helpdata/en/34/d9c8b9c23c11d188b40000e83539c3/cont ent.htm Sequence of allocation of memory in case of Non-dialog work process:Memory allocation of non-dialog work process in UNIX. In UNIX, if Roll memory gets full, Heap memory is occupied and if heap memory gets full extended memory is used. But in windows it is different, after roll memory (ztta/roll_first) is filled the work process uses Extended memory, after extended memory is fill then remainder of roll memory (ztta/roll_area - ztta/roll_first) is used soon and then Heap Memory is allocated Unix or Unix like systems Roll Memory up to ztta/roll_area | | \|/ Heap Memory up to abap/heap_area_nondia or HM Exhaust | | \|/ Windows Roll Memory up to ztta/roll_first | | \|/ Extended Memory up to ztta/roll_extension or EM Exhaust | | \|/

Extended Memory up to ztta/roll_extension or EM Exhaust

Roll Memory Remainder of ztta/roll_area | | \|/ Heap Memory up to abap/heap_area_dia

4. What is the use of profile parameter ztta/roll_area? The value specifies the size of the roll area in bytes. The roll area is one of several memory areas, which satisfies the user requests of user programs. For technical reasons, however, the first 250 KB or so of a user context are always stored in the roll area, further data - up to the roll area limit ztta/roll_first, - in the extended memory, up to the limit ztta/roll_extension or if extended memory is exhausted, then - again in the roll area, until the roll area is full, then - in the local process area, up to the limit abap/heap_area_dia or abap/heap_area_total or until the address space or the swap space is exhausted. Followed by termination with errors like STORAGE_PARAMETERS_WRONG_SET an error code, that points to memory bottleneck Minimum data transfer with context change; however, the increase helps to avoid problems (address space, swap space, operating system paging). 5. What are the roll and page areas? Roll and page areas are SAP R/3 buffers used to store user contexts (process requests). The SAP dispatcher assigns process requests to work processes as they are received. If the work process is unavailable the process requests are queued in the roll and page areas. Paging area holds data from the application programs while Roll area holds data from previous dialog steps and data that characterizes user. 6. What is Private mode? When a work process is consuming Heap memory, it is called to be in private mode, shown as PRIV in SM50. It is called Private mode because Work process is a dedicatedly assigned to a User until its job is completed. 7. What is Rollin & Rollout? When task handler gets any request from work process, it will check for the user authorizations in user context memory so time taken for this process is called rollin. About Rollout when task handler gets this information it will store it in shared memory and this time is known as rollout. 8. What is dispatcher? Dispatcher is the central work process in an application server which along with operating system manages the resources for ABAP applications.

The dispatcher distributes the transaction load among various work process, connecting to the presentation level and organizing communication. The processing requests are first saved in request queues and then processed according to 'first in -- first out' rule. The data is processed in work process like dialog work process or background work process or update work process etc. The dispatcher only distributes load between work processes. There is no assignment of a work process to single user. The requests, which are created by user using SAPGUI, are distributed among the work process. Processing user requests sometimes requires data to be read from the database or written to it. For this, every work process is connected directly to the database. 9. Define an R/3 instance. An R/3 instance is a group of R/3 services that are started and stopped as a unit (by an R/3 dispatcher) and have a common instance profile. The name of an R/3 instance is composed of letters standing for the relevant services, and an instance number which is unique for each computer. The services may be D, V, E, B, M, G, or S, which respectively stand for dialogue, update, enqueue, background, message, gateway, and spool services. 10. What is a work process? A work process is where individual dialog steps are and the work is done. Each work process handles one type of request.

actually

processed

11. What are the different work processes in an SAP instance? DVEBMGS D Dialog (DIA) V Update (UPD or UP2) E Enqueue (Enq) B Batch/Background (Bgd) M Message Server ( use for load balancing) G Gateway (SAP to SAP communication or SAP or non SAP communication) S Spool (SPO) The Dispatcher and ICM also account for the above 12. What is the difference between a support package and a kernel replacement? A support package contains fixes to the ABAP code within a SAP instance. It must be applied using the SPAM transaction in the SAP instance. A kernel replacement is the replacement of the SAP executables on the OS level. 13. How to analyze/know the problem if CI is down? Check whether you are able to login to DB. Check listener. Check DEV_DISP, DEV_MS and DEV_W0 in /usr/sap/SID/instance/work Check profiles in /usr/sap/sys/profile using sappfpar -check 14. Which is Transport Background JOB? RDDEXECL

15. What is use of USR$ table? For maintaining user master and associated records. 16. At a time, how can you delete the 10 users? SU10 17. What are the Client profiles (Not Default profiles) Client copy profiles are called client profiles. 18. What is the DIFFERENCE SU01 & SU10? (EXCLUDE maintain User & Mass User maintenance) SU01 is used for single user maintenance and SU10 for mass user maintenance. You cannot copy in SU10. 19. During installation how to give license? Not possible since kernel is present after installation and unless and until SAP is up, you can not apply license. 20. A user rings you up and says they have made a huge error and need the database restored to the previous afternoon. How do you go about the restore? You do not restore the database. You liaise with the user to correct the error or refer to management to make a decision on the effect on the business. 21. When creating a logon group for logon load balancing. Which of the following cannot be specified? >>Maximum Allowable response time. >>Max number of users who may be logged on to the instance. >>Name of the instance defined for the logon group. >>Max number of session per user. ( Correct ) >>Name of logon group. 22. Which of the following is authorized to maintain R/3 user id Parameters? >>Only R/3 system administrator >>All R/3 users having an account in same client. >>Only the user himself >>only the R/3 system admin and User. (Correct) 23. Which of the hosts in this networked SAP System diagram must have its respective R/3 component(s) started up FIRST before the other hosts can start theirs? a. Dialog Instance b. CI Instance c. DB Instance d. Front End GUI System