KERNEL UPGRADE:

Set system message using sm02 to inform users about downtime.

Download the kernel patches from the service market place.

Service Market Place -> Download->My companys Application compoenets ->
Select SAP KERNEL 64 bit (as our server is 64 IA server and installation in Non Unicode)
Download both Database independent and DB dependent Oracle (as our DB is oracle) parts of the kernel.

As we are going to upgrade to kernel patch level 201 of SAP kernel 700 please select that and add to download
basket .
Similarly add Oracle(DB dependent) part for Kernel patch level 201 also to download basket.
Start SAP download manager on ur desktop or the remote server and enter your service market credentials , it will
connect to your download basket and show the contents that you added in the above steps as ready to be
downloaded. Please start download.

Now transfer the two .SAR files on to the server where you want the Kernel upgrade to be performed. Using FTP or
WinSCP tool.

We are performing kernel upgrade on Q23 system on server er3as102. I have used winscp tool to transfer the .SAR
files to the folder /sapcd2/GRC/SANJEEV/SAPKernelPL201

Your kernel resides at the path /sapmnt/Q23/exe folder, keep a backup of the current kernel before you apply the
patch. In case if the kernel upgrade fails you will have your old kernel to revert back to.

Backing up your present Kernel as exe_old.

• Connect to the server er3as102 using putty/xmanager with your Signum Id ( if you dont have access take your
colleagues ;) )
• Give newid sidadm ( here q23adm) to switch user to sap admin user.
• Now Cd to the /sapmnt/Q23 directory

•
• now copy the contents of exe to a new folder exe_old. Using cp -R exe exe_old. It will take some time and after
its finished you will see a new folder when you do ls -l in sapmnt/Q23 directory.

Now we are done with the prerequisites of the kernel upgrade activity. The patch level of Q23 system is as below.
Shutdown the Q23 sap system at the mentioned downtime using stopsap command.

Once you are sure SAP is shutdown .

Cd /sapmnt/Q23
SAPCAR -xvf /sapcd2/GRC/SANJEEV/SAPKernelPL201/SAPEXE_201-20001205.SAR -R /sapmnt/Q23/exe

this will extract/unzip the DB independent part of the kernel PL 201 to exe folder.

SAPCAR -xvf /sapcd2/GRC/SANJEEV/SAPKernelPL201/SAPEXEDB_201-20001205.SAR -R /sapmnt/Q23/exe

this will extract/unzip the DB dependent oracle specific files to exe folder.

Once this is done, start the SAP system Q23 by issuing the startsap command.

Troubleshoot the errors if you face any, if nothing works out replace the exe_old back to exe and bring the system
up before the downtime finishes.

1. What are the issues relate to transport if transport has been fired and not able to import.
Ans. Issue related to Transport is following:
1. RFC connection issues
2. Trans dir. Is full
3. Tr is inconsistent
4. No correct authorization
5. Transport request is after the end mark in the Import Queue

2. What is SAPRouter and how to setup. And How SAP People login to the system.
Ans. SAProuter is an SAP program that acts as an intermediate station (proxy) in a network connection between
SAP Systems, or between SAP Systems and external networks. In short, SAProuter provides you with the means of
controlling access to your SAP system.
3. All T-codes for monitoring and their details
Ans.
SM21 -- Job: SNC_APP_STOCK_TRANSFER_2480
ST02 -- OK
SM66/SM50 -- OK
SM13 -- Ok.Update is active
SM12 --- No old locks
ST22 --- Record total number of short dumps from yesterday and investigate recurring short dumps 10 dumps
ST03N --- Record Average Dialog Response day for previous day 13/10/2010--1.182,5
SMQ2 -- ok
SMQS -- ok
SM58 -- OK
Database Check
DB12 "Backup completed successfully-11.10.2010 19:00:15"
DB02 95,86% used
ST04 98.75%
SP01 – Spool job
AL08 – Active users
SM50 – Work Process
SM51 -
SM37
ST22
SM21
ST02
SM12
SM13
SM58
DB12
DB02
ST04
Checking Dialog users
AL08 - no of active users 6
No of Dialog processes in Waiting state 22

Background Job status

Number of batch process in Waiting State / free 22
Number of Active jobs 6

SAP Memory (Current use % )

Roll area 0,41
Page area 0,02
Extended memory 9,18
Heap memory

CPU Utlilization (%)

CPU utilization of DB Server "Utilization user % 72
system % 28
idle % 0
io wait % 0"
CPU utilization of App Server NA

4. For SPAM (Support pack) where we can find the log file at OS level.
Ans. Usr/sap/trans/log/slog
5. What may be the possible reason if background job is keeping running for very long time and how to resolve?
Ans. –
1. Background work process already busy in other job and no free work processes
2. If job is updating something in DB and update work process is busy
3. in case of after event or after job, the event is not trigger so job will not start
4. ABAP program starts a loop
5. Authorization issues
6. How many request generates when we do the client export and import
Ans.
When the export is finished, and depending on the chosen copy profile, you get the following
transport requests:
� TT1KOnnnnnn (cross-client objects)
� TT1KXnnnnnn (client-dependent long texts)
� TT1KTnnnnnn (client-dependent tables)
where TT1 is the SID and <nnnnnn> is a system-generated transport number.

7. How to schedule the ABAP program as background job.

Ans.
T-Code – SM36
Enter Job name and Job class click on job steps.
There we can find the option for ABAP programs, external commands and external programs
In start condition button we can define all the start conditions – Immediate, date time, after event, after job and at
operation modes.

8. Which one you will prefer-- remote client copy or client export and why
Ans. Client Export is better than remote client copy –
1. If there is no LAN connection
2. The data is to be buffered
3. A client transport differs from a client copy in that it does not use RFC. Like a client copy, however, a client
transport is used to copy data between different clients. A client transport can be used to replace a local or remote
client copy.
4. A client transport consists of two steps: First a client export extracts client data from the source client to files at
the operating system level. Then the data is imported from the operating system files into the target client.
TADM – 12_2_62 – page – 388
9. Roles and responsibilities
Ans- my Roles and responsibilities contains:
1. Day to day monitoring to the system and reporting to the management
2. Monitoring the work process and their status time to time
3. Maintaining RFC connection b/w different SAP systems
4. Background Job management like – Monitoring and scheduling the job.
5. Transport related work
6. Client management like- Client creation and client copy
7. Kernel Upgrade
8. Roles and profiles
9. Work related to SMP like- Register developer and object in marketplace to get access keys. Check OSS and
HTTP connection and open that according to the requirement. Maintain the S-user id in SMP and download the
kernel and patch files.
10. In Solution manager, we use to create the project and keep all the demand numbers in that to track all the
development related to that project that is happening in dev system.

10. What are roles and profiles and how to create and assign to a user
Ans.
11. How to enable the trace and how to use that
Ans. For enabling the trace we use ST01 –

The following components can be monitored using the SAP system trace:
• Authorization checks
• Kernel functions
• Kernel module
• Database accesses (SQL trace)
• Table buffers
• RFC calls
• Lock operations (client side)
The last 4 components can also be monitored using Performance Analysis (transaction ST05).
Performance :
Use ST05 –

12. How to check ABAP dump and how to analyze the issue
Ans. For this use the T-Code- SM22
Details from notebook
13. How to create transport Domain and configure transport describe in detail.
Ans. TADM
14. How to add the system in SMP.
Ans. N/A
15. Performance check for SAP System
Ans. ST05
16. How to check that from how much time that work process is running.
Ans.
17. ST02 - What are the details u find and when you can tell that there may be a issue and how to resolve.
Ans. Try to have a look at OS response time : ST06 : look at CPU, Memory, Swap, Disk and Lan response time.
Try to have a look at buffer quality : ST02, if many fields are red, investigate each fields dependant parameters.
Try to have a look at DB response time : ST04N, databuffer quality (SGA zone), how much physical reads /
logical reads Ratio, wait times, number of user calls, Shared Pool cache hit ratio should be >96%, Sort usage, Redo
logging
18. In SM50 what are the details you find and when you can tell that there may be an issue and how to resolve.
Ans.
19. In AL08, what are the details u find.
Ans.
20. In 3 profiles, tell the sequence of that when SAP system getting up.
Ans. Notebook
21. Descriptions of all the profiles and how to update.
Ans.
22. in SPAM, where we can get the log
Ans. USR/SAP/Trans/Log
23. What is SWAP?
Ans. Swapping is the process whereby a page of memory is copied to the preconfigured space on the hard disk,
called swap space, to free up that page of memory.
Swapping is necessary for two important reasons. First, when the system requires more memory than is physically
available, the kernel swaps out less used pages and gives memory to the current application (process) that needs the
memory immediately. Second, a significant number of the pages used by an application during its startup phase may
only be used for initialization and then never used again. The system can swap out those pages and free the memory
for other applications or even for the disk cache
24. What is the name of Kernel File?
Ans. SAPEXE_201-xx and SAPEXEDB_201-xxx
25. How to do client copy, have u access of sap*
Ans. yes
26. Getting response from database very slow, what will be the reason?
Ans.
27. Details of ST03
Ans.
28. Details of ST02
Ans.
29. How to provide access keys
Ans.
30. Kernel upgrades procedure in Detail
Ans. In starting of this book
31. How to apply Support pack in details
Ans.
32. Check the work process status at OS level in Sap.
Ans.
33. What is the difference between SAP R/3 and ECC?
Ans.
34. What does Sap_All and Sap_New Parameters define for a user who is granted with permissions?
Ans.
35. How to check cup utilization at UNIX level.
Ans.
36. How to check CPU utilization at SAP level.
Ans.
37. User is not able to login to the SAP system
Ans.
38. SAP system is very slow
Ans.
39. Work process detail at UNIX level.
Ans.
40. What is transport layer and transport route and how to configure.
Ans - A layer is the path to move the development objects and is always assigned to consolidation route.
A route defines the source and target system to move the objects and there are two routes---
1. Consolidation route bet. DEV and QAS
2. Delivery route bet. QAS and PRO.
if you build 3 systems ABC, DEF and GHI unless you define route they wont be able to act as DEV QAS and PRD
So route defines role of a system. if you check the TMS configuration you will see 2 layers* between the DEV and
QAS, SAP and ZADB, SAP layer is for delivering SAP standard objects and ZADB is for delivering customized
objects, customized means ABAP developments , standard means, SAP default which SAP has provided and that is
present already.
Layer defines in which system developments will be made
Route defines which system will act as what? dev qas and prd

41. What’s the difference between R3trans and Tp in SAP-DBA?

Ans - R/3trans is the r/3 system transport program which can be used for transporting data between different sap
systems even when they don’t belong to the same group .R3trans normally is not used directly but called from the
Tp control program or by the R/3 upgrade. Tp is the basic tool for the transporting the request.
Actually R3TRANS is used by TP (Both are SAP Kernel Programs) for anything to write from /to to database.
R3 Trans also write transport logs in the DIR_TRANS/tmp directory which after the job is finished is moved to
DIR_TRANS/log directory. TP is the master controller program for all the jobs to be done by all the transport.

42. What is the difference between support packages and kernel upgrade?
Ans- Support package: SAP delivers Support Packages to remove any errors that appear in important transactions.
Support Packages may contain language-dependent data such as message texts ABAP texts or screen texts. Once
you have used transaction. SPAM to import a Support Package the translated texts for these objects are up-to-date
for all languages in the system.
Kernel upgrade: The SAP system consists in general terms of a kernel and applications. The kernel is the central
program that is Essential to the SAP system applications. You can upgrade the kernel to a higher release while
keeping the applications at the original release.

43. How to install multiple Central Instances on the same physical machine?
Ans- A SAP system can contain one and only one Central Instance. In the Central Instance you will have Message
Server and Enque Work processor. The Message Server should be only one per a single SAP system.

44. What are the differences of a sap SID and host name?
Ans- SID is nothing but a name for an Instance. Host is the system which hosts the Instance.
Local Installation: Here we have both Database Instance [DB SID] and the Central Instance [SAP SID] in same
system. I.e. Hostname is same.
Domain Installation: Here we have different hosts to hosts Database instance & Central instance. i.e. 2 hosts.
The Host name is the name of the Computer where the instances (Database/SAP) are installed. The SID refers to all
the instances in a SAP system or a Database.

45. Explain RMAN and how it can be used for database backup & recovery?
Ans- RMAN IS THE recovery manager of oracle backups it will recover the backups and put them in the repository
catalogue RMAN is used by the oracle only in SAP BR tools are used for the recovery of backups But these BR
tools are also integrated with the RMAN only

46. Define the term “GROWTH OF THE DATABASE" and how should I find the growth of database in SAP R/3?
Ans- Database Growth can be monitored from the T-Code DB02. Here you can find the growth of individual
tablespaces also.

47. When spool buffer is full and new spool request is raised what happens to the request? Where does the request
stored?
Ans- The new spool request will be in the queue. If it is urgent request then the current request will be stopped and
new request will be send.

48. What is spool buffer?

Ans- Spool buffer is the memory space which is allocated in DB level or OS level where all the data are stored in
that buffer area at the time giving prints. In another point of view we can say that all printing data's goes through
this buffer (memory). When it is created in DB level then its size is restricted. Due to this there is a chance to fill up
buffer area.

49. Where can we find the 4 files (saplogon.ini, sapmsg.ini, saproute.ini, sapdoccd.ini) of GUI at OS level (I mean
in which directory)?
Ans-

50. Can SAP Patches be installed when other users are online?
Ans- SAP Support Packs should never be applied while users currently in the system as the new object are being
imported in to the system. You will encounter lot of should dumps in the system due to objects being generated and
buffers getting refreshed No. During patch implementation the patch manager updates some tables and programs. If
any user use that programmed or table it can’t update those table or program. So it is better to apply patches when
there is no user logged in the SAP system. You better don’t do that because there will be a inconsistency if the same
objects are used by any user who is online and thus the system throws a lot of short dumps.

51. Which R/3 System user is used for starting external programs using SAP background jobs?
Ans- The user type is CPIC

52. Name the R/3 System transaction used for monitoring a spool requests.
Ans- Spool process is used for printing purpose for example printing pay slips, printing invoices, printing purchase
order etc.
Most of the spool requests are scheduled in back ground jobs because they are time consuming or expensive jobs,
BTC jobs are scheduled in T-Code sm36. Spool monitoring is done by T-Code sp01.
Spool process is used for printing purpose for example printing pay slips printing invoices printing purchase order
etc. Most of the spool requests are scheduled in back ground jobs because they are time consuming or expensive
jobs BTC jobs are scheduled in T-Code sm36.

53. What is the difference between transport layer and development class?

Ans- Firstly a Development Class is just like a package which holds a group of objects together. Transport Layer
just specifies the route through which these Development Class's objects has to move to the Consolidation system
from Integration system

54. How to schedule background jobs at OS level?

Ans- For data base back up generally client use different third party software like Tivoli by IBM Schedule task by
Microsoft Crontab by UNIX

55. Tell the architecture detail of SAP.

Ans.
56. How is database connected to the SAP system, means how SAP communicates to the SAP system?
Ans.
57. What is gateway server and message server, different system like XI and BI will be take request through
Gateway server.
Ans.
58. What are the Start, Default and Instance profile and what are the details mentioned in the Default profile.
Ans.
59. Detail of work process architecture
Ans.
60. What is SPAM and SAINT and How to install support pack
Ans.
61. What is TMS, how to configure and transport domain and transport route definition and detail.
Ans.
62. Suppose there are 2 users and they are not able to do one transaction, So How to analyze missing authorization
and how to assign that to user.
Ans.
63. What are diff. b/w remote client copy and client export and import, in which scenario we need the Client export
and Import
Ans.
64. What is local client copy and how to do and when it required?
Ans.
65. How to check database performance through SAP and how to take initiatives to correct that
Ans.
66. Questions from oracle database Architecture to backup recovery
Ans.
67. Tell some common commands to use in UNIX
Ans.
68. How to check the environment variable in UNIX
Ans.
69. In which case you need the remote client copy.
Ans.
70. How to analyze the ST03, work load monitor and different details for the transaction being slow.
Ans.
71. Tell about your system landscape.
Ans.
72. Oracle Questions:
A. Oracle Architecture
B. Startup process
C. Shutdown abort.
D. Installation of Oracle on UNIX.
E. Password got lock or expired, and how to analyze that password got locked.
F. Backup Process
G.

73. Which version of SAP you are working.

Ans.
74. Have you worked on XI or BI?
Ans.
75. Have you any question to ask?
Ans.
76. How to check environment variable in UNIX
Ans.
77. Where all the parameter resides of SAP in oracle parameter file internally at OS level. Means where we set
the parameter in SAP i.e. how database communicates through the SAP system.

Ans. – sap work processes send request thru listner after that db work processes will get started..like smon, pmon,
Archn then db instance will start.
using OS level authentication, for oracle using OPS$ Mechanism.
For the database, the SAP System is a single user, SAPR3 / SAP<SAPSID>, whose password is stored in
the table SAPUSER. Therefore, to access the database, the SAP System uses a mechanism called the OPS$
mechanism, which works as follows:
a. When the system accesses the database, it first logs on to the database as the user
OPS$<operating_system_user> , for example, OPS$<SAPSID>adm. (The OPS$ user that corresponds to
the operating system user must be defined in the database and identified as externally.)
b. It retrieves the password for SAPR3from the SAPUSER table.
c. It then logs on to the database as the user SAPR3.

78. How to change the environment variable.

Ans.
79. What are the types of transport Route and describe it?
Ans.
80. Parent role and child role
Ans.
81. Client copy profiles
Ans.
82. Difference b/w 000, 001 and 066

Clients 000, 001 and 066 are standard clients that are pre-delivered by SAP. These clients are not supposed to be
used in development, quality and production environments.
Client 000 is basically used as working client only when you do support pack upgrade or ABAP load generations
(SGEN) and implementing additional languages, etc. Otherwise, client 000 should not be used as a working client.
The same applies to client 001. But the only exception with 001 is, with Solution Manager, 001 will be your
working client. You will do all configurations and obtain support from SAP through this client. With other Systems
like BW and CRM, this client (001) will not be a working client. Two standard users (SAP* and DDIC) are defined
in the clients 000 and 001.The client 066 is used only for EarlyWatch functions (Monitoring and performance). The
user EarlyWatch is delivered in client 066 and is protected using the password SUPPORT. This password needs to
be changed for security purposes.

Client 000 contains a simple Organizational structure of a test company and includes parameters for all applications,
standard settings, configurations for the control of standard transactions, and examples to be used in many different
profiles of the business applications. For these reasons, 000 is a special client for the R/3 system because it contains
the client-independent settings. Client 001 is a copy of the 000 client, including the test company; if this client is
configured or customized, its settings are client dependent. It does not behave like 000. It is reserved for the
activities of preparing a system for the production environment. SAP customers usually use this client as a source
for copying other new clients. Client 066 is reserved for SAP access to its customers' systems to perform

83. for local client copy which client we need to use, why not 000 or 001
Ans.
84. What client difference
Ans.
85. What are changes for different clients?
Ans.
86. What is transactional RFC?
Ans.
Synchronous RFC
The first version of RFC is synchronous RFC (sRFC). This type of RFC executes the function call based on
Synchronous communication meaning that the systems involved must both be available at the time the call is made.
Transactional RFC (tRFC)
Transactional RFC(tRFC, previously known as asynchronous RFC) is an asynchronous communication method that
executes the called function module just once in the RFC server. The remote system need not be available at the
time when the RFC client program is executing a tRFC. The tRFC component stores the called RFC function,
together with the corresponding data, in the SAP database under a unique transaction ID (TID).
If a call is sent, and the receiving system is down, the call remains in the local queue. The calling dialog program
can proceed without waiting to see whether the remote call was successful. If the receiving system does not become
active within a certain amount of time, the call is scheduled to run in batch.
tRFC is always used if a function is executed as a Logical Unit of Work (LUW). Within a LUW, all calls
1. are executed in the order in which they are called
2. are executed in the same program context in the target system
3. run as a single transaction: they are either committed or rolled back as a unit.
Implementation of tRFC is recommended if you want to maintain the transactional sequence of the calls.
Disadvantages of tRFC
1. tRFC processes all LUWs independently of one another. Due to the amount of activated
tRFC processes, this procedure can reduce performance significantly in both the send and the target
systems.
2. In addition, the sequence of LUWs defined in the application cannot be kept. It is therefore
impossible to guarantee that the transactions will be executed in the sequence dictated by the
application. The only thing that can be guaranteed is that all LUWs are transferred sooner or later.
Queued RFC (qRFC)
To guarantee that multiple LUWs are processed in the order specified by the application, tRFC can be serialized
using queues (inbound and outbound queues). This type of RFC is called queued RFC (qRFC).
qRFC is therefore an extension of tRFC. It transfers an LUW (transaction) only if it has no predecessors (based on
the sequence defined in different application programs) in the participating queues.
Implementation of qRFC is recommended if you want to guarantee that several transactions are processed in a
predefined order.

87. R3trans –d
Ans.
88. How to do mass user lock
Ans.
89. differences between client copy and client transport
Ans.
90. What is DPMON?
Ans.
91. How to do performance related work in SAP – ST05
Ans.
92. What is CHARM and how it works and its configuration
Ans.
93. Profiles for client copy
Ans.
Copy profile Description
SAP_USER Users, user roles and authorization profiles are copied.
The client is not reset.
SAP_UONL User without authorization profile and role
SAP_PROF Only authorization profile and roles
SAP_CUST Client-specific customizing including authorization
profile is copied. The application data is deleted, the user
data is retained.
SAP_CUSV SAP_CUST with variants
SAP_UCUS SAP_CUST with user master data
SAP_UCSV SAP_UCUS with variants
SAP_ALL All client data except change documents (see note
180949) and local data is copied.
SAP_APPL SAP_ALL without user master data
SAP_AAPX SAP_ALL without authorization profile and roles
94. Setting for client copy
Ans.
95. Tablespace is full, what to do now.
Ans. Either add new data file or increase the size of the existing datafiles.
96. Job name to delete spool job and background job.
Ans.
Recommended
Job Name ABAP Variant Repeat Purpose
Program Interval
SAP_REORG_JOBS RSBTCDEL Required; you Daily Delete old
must create a background jobs
variant.
SAP_REORG_SPOOL RSPO0041 Required; you Daily Delete old spool
must create a requests
variant.
SAP_REORG_BATCHINPUT RSBDCREO Required; you Daily Delete old batch
must create a input sessions
variant.
This job may not run at the same time as normal batch
input activity. Schedule this job for periods during
which no batch input sessions are run.
SAP_REORG_ABAPDUMPS RSSNAPDL Required; you Daily Delete old
must create a dumps produced
RSSNAPDL deletes old dumps. To save the trouble of variant by ABAP
scheduling this job, you can run the ABAP report abnormal
RSNAPJOB from the ABAP editor. This report terminations.
schedules RSSNAPDL with the following
specifications:

Job name: RSSNAPDL

Variant name: DEFAULT (you must create this
variant)
Start time: 0100 AM
Repeat interval: Daily
SAP_REORG_JOBSTATISTIC RSBPSTDE Required; you Monthly Delete job
must create a statistics for
variant jobs not run
since the
specified date
(statistics no
longer needed
since job was a
one-time
occurrence or is
no longer run)
SAP_REORG_UPDATERECORDS RSM13002 None required Daily Delete old
completed
You need to run this job ONLY: update records
(automatic
� I f you have deactivated automatic deletion of delete
update records after they have been processed. By deactivated);
default, automatic deletion is activated. This function delete
is controlled by system profile parameter incomplete
rdisp/vb_delete_after_execution; or update records
(automatic
� If you have deactivated automatic deletion of delete
incomplete update records (records partially created deactivated)
when an update header is created and saved but the
generating transaction then ends abnormally). By
default, automatic deletion is activated. This function
is controlled by system profile parameter
rdisp/vbreorg; or

� If you have deactivated processing of U2 update

components after the processing of the associated U1
updates. This function is controlled by system profile
parameter rdisp/vb_v2_start.

For more information, see Managing Updates.

SAP_COLLECTOR_FOR_JOBSTATISTIC RSBPCOLL None required Daily Generate
runtime
statistics for
background jobs
SAP_COLLECTOR_FOR_PERFMONITOR RSCOLL00 None required Hourly Collect system
performance
This job was previously also called statistics
COLLECTOR_FOR_PERFORMANCE_MONITOR.
Please schedule this job under the new name.

RSCOLL00 schedules all of the reports that need to

run for the performance monitor. RSCOLL00 uses
table TCOLL to determine what to run. See the
CCMS Guide for more information on setting up
RSCOLL00.

97. What is LUW

Ans- The Open SQL statements INSERT, UPDATE, MODIFY, and DELETE allow you to program database
changes that extend over several dialog steps. Even if you have not explicitly programmed a database commit, the
implicit database commit that occurs after a screen has been processed concludes the database LUW.
A logical unit consisting of dialog steps, whose changes are written to the database in a single database LUW is
called an SAP LUW. Unlike a database LUW, an SAP LUW can span several dialog steps, and be executed using a
series of different work processes. If an SAP LUW contains database changes, you should either write all of them or
none at all to the database. To ensure that this happens, you must include a database commit when your transaction
has ended successfully, and a database rollback in case the program detects an error. However, since database
changes from a database LUW cannot be reversed in a subsequent database LUW, you must make all of the
database changes for the SAP LUW in a single database LUW. To maintain data integrity, you must bundle all of
you database changes in the final database LUW of the SAP LUW.

98. Parameter files for SAP with Oracle database.

Ans.
99. How to register a system in SMP
Ans.
100. How to delete a client
Ans. Use SCC5 to delete a client
101. What will happen if you delete the row from SCC4? Can you still login to the client?
Ans- We cannot login to that client if the row is deleted from the SCC4, but that client detail still exist in the SAP
system; again we need to maintain that detail for login to that client

102. Users in SAP

Ans-
Type Purpose
Dialog Individual, interactive system access.
System Background processing and communication
within a system (such as RFC users for ALE,
Workflow, TMS, and CUA).
Communication Dialog-free communication for external RFC
calls.
Service Dialog user available to a larger, anonymous
group of users.
Reference General, non-person related users that allows
the assignment of additional identical
authorizations, such as for Internet users
created with transaction SU01. No logon is
possible.

There are five types of users in sap

Dialog users (A)

A normal dialog user is used for all logon types by exactly one person. This is used to logon using SAP GUI.
During a dialog logon, the system checks for expired/initial passwords. The user can change his or her own
password. Multiple dialog logons are checked and, if appropriate, logged. These users are used for carrying out
normal transactions. This is an interactive type of logon. The initial multiple logons are 6. They are set according to
companies policy.

System Users (B)

These are non interactive users. They are used for background processing and internal communication in the system
(such as RFC users for ALE, Workflow, TMS, and CUA). Their passwords cannot be changed by the end users.
Only the user administrator can change their passwords. Multiple logon is permitted in these type of users. Dialog
logon is not possible for these type of users.

Communication Users (C)

Used for dialog-free communication between systems. It is not possible to use this type of user for a dialog logon.
Their passwords are valid for certain period of time so they expire. The users have option to change their own
passwords.

Service User (S)

Dialog user available to a larger, anonymous group of users. The system does not check for expired/initial
passwords during logon. Only the user administrator can change the passwords. Generally, highly restricted
authorizations are given to this type of users.

Reference User (L)

A reference user is, like the service user, a general non-person-related user. Dialog logon is not possible with this
kind of user. A reference user is used only to assign additional authorizations. To assign a reference user to a dialog
user, specify it when maintaining the dialog user on the Roles tab page

Dialog User System user Communication Service User Reference User

User

Logon with SAPGUI possible/

Interactive

Yes No No Yes No
Multiple logon permitted yes NA yes yes yes
Password Expires or NA NA Expires or ----NA---
initialized initialized

Password can be changed by End user User

Administrator

103. In our DB server these files exists in 2 locations

initPRD.ora
initPRD.sap
spfilePRD.ora
location 1: /oracle/PRD/102_64/dbs/ and
location2: /oracle/PRD/sapbackup/PRD/

For the BRBACKUP and SMB backups it getting the initPRD.ora from this location
/oracle/PRD/102_64/dbs/initPRD.ora
So whats the use of files in location /oracle/PRD/sapbackup/PRD/
Ans- In oracle, init<SID>.ora is the profile file and spfile.ora is the system profile file. These files are needed by
oracle while startup. These files will be usually available in the path $ORACLE_HOME/dbs (where
$ORACLE_HOME=/oralce/<SID>/102_64). These files are just like the profile files for SAP (available in the
location /usr/sap/<SID>/SYS/profile).

While taking a backup, a copy of these profiles will be taken in the backup stage directory. This happens whenever
a backup is scheduled using BRTools. These are just copies and nothing to do with the oracle startup.
spfilePRD.ora = the parameters that Oracle uses
initPRD.ora = the old file that Oracle used in the past, now BRTOOLS uses it to read Oracle parameters. it gets
created everytime you start any BRTOOL.

initPRD.sap = file that BRTOOLS uses for its functionnality

Location 1 (/oracle/PRD/102_64/dbs) is default location for you parameter files in Oracle. When you bring up your
database unless you specify the location of your parameter file , by default oracle will look for the parameter file in
that location.

The file which you are seeing under sapbackup directory is the backup copy of the file under location 1, but again
thats the backup copy of the current file only if you have configured you backup with the location 2 as your backup
destination ( as you know when you do database backup the parameter file is also backedup).

Otherwise its just a mannual copy done by someone else.

You can find that out by checking the data stamp on the file and your backup log.

104. Which parameter needs to change for open the session more than 6 in SAP?
Ans- max 6. we can make it less that 6 with parameter rdisp/max_alt_modes
105.