KEMBAR78
SAP BASIS Interview Questions and Answers. | PDF | Oracle Database | Load Balancing (Computing)
0% found this document useful (0 votes)
6K views25 pages

SAP BASIS Interview Questions and Answers.

The document discusses various topics related to SAP BASIS administration including: 1. Client copy can be done locally, remotely, or via import/export using transactions like SCCL, SCC9, and SCC8. This increases the tablespace and database size. 2. Transports can be done via transaction STMS_IMPORT or OS command tp between systems like production and development. 3. Key SAP work processes include dialog, background, and enqueue which handle interactive tasks, background jobs, and locking respectively.

Uploaded by

aravind
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
6K views25 pages

SAP BASIS Interview Questions and Answers.

The document discusses various topics related to SAP BASIS administration including: 1. Client copy can be done locally, remotely, or via import/export using transactions like SCCL, SCC9, and SCC8. This increases the tablespace and database size. 2. Transports can be done via transaction STMS_IMPORT or OS command tp between systems like production and development. 3. Key SAP work processes include dialog, background, and enqueue which handle interactive tasks, background jobs, and locking respectively.

Uploaded by

aravind
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 25

SAP BASIS

INTERVIEW Q&A
1. How will you do client copy?
Answer: Client copy can be done via 3 different ways:
Initially you need to create client using T-code SCC4.
a. Local Client copy:
- Logon to the newly created client with user sap* and password pass
- Execute T-code SCCL
- Select profile, source client and start immediately
b. Remote Client Copy:
- Logon to the newly created client with user sap* and password pass
- Execute T-code SCC9
- Select profile, source destination RFC and start immediately
c. Client Import/Export:
- Client Export is done from source system using T-code SCC8, select profile, target system
and start immediately
- Client Import is done from newly created client from target system by executing T-code
STMS_IMPORT and select the transport request number (TR) which was created while
doing export and import the selected TR

2. If SAP* is not available, then how will you do?


Answer: Check if the sap* user is there in table USR02 from database level or not. Delete the user if
present by executing sql command:
SQL> Delete from <schema_name>.USR02 where BNAME=’SAP*’ and MANDT=’<client>’ ;
Set the parameter login/no_automatic_user_sapstar = 0 in profile file and restart the instance.
Now you can login with user SAP* with default password “pass”.

3. After client copy, is tablespace and database sizes will be increased or not?
Answer: Yes, the tablespace and database sizes will increase after client copy as the data/entries is
copied between client.

4. How to do client copy fast?


Answer: There are number of factors which determined the speed of the client copy like database
size, hardware capabilities.
Local client copy is faster. Also, to speed up the process, you can increase the number of parallel
process.

5. What are various profiles available for client copy?


Answer: The various profiles available for client copy are:
S.NO Profile Description
1 SAP_ALL All Client-Specific Data w/o Change Documents
2 SAP_APPL Customizing and Application Data w/o Change Docs
3 SAP_APPX SAP_APPL w/o Authorization Profiles and Roles
4 SAP_CUST Customizing
5 SAP_CUSV Customizing and User Variants
6 SAP_CUSX Customizing w/o Authorization Profiles and Roles
7 SAP_PROF Only Authorization Profiles and Roles
8 SAP_UCSV Customizing, User Master Records and User Variants
9 SAP_UCUS Customizing and User Master Records
10 SAP_UONL User Without Authorization Profiles and Roles
11 SAP_USER User Master Records and Authorization Profiles

ASHISH MISHRA
2
(MISHRA.ASHISH0123@GMAIL.COM)
6. How to do transports between production and development?
Answer: From application level, transport can be done via T-code STMS_IMPORT.
From OS level, tp command is used to transport between production and development system.

7. How to apply OCS patches?


Answer: T-code SPAM (Support Package Manager) is used to apply OCS (Online Correction Support)
patches.

8. How to do transports from OS level?


Answer: To transport the TR from OS level, follow the below steps:
From Source System:
- Copy the data file and co-file of related TR from source to target if not available using
command:
Scp –pr <filename> <user>@<target IP>:<path>
e.g. scp –pr K9000123.<SID> <SID>ADM@IP address:/usr/sap/trans/cofiles (for co-file)
scp –pr R9000123.<SID> <SID>ADM@IP address:/usr/sap/trans/data (for datafile)
From target system:
- Add the TR to the buffer, execute below tp command
Tp addtobuffer <transport request> <SID> Client=<client number>
pf=/usr/sap/trans/bin/TP_DOMAIN_<DOMAIN SID>.PFL
- Import the TR, execute below tp command
Tp import <transport request> <SID> client=<client number> pf=/usr/sap/trans/bin/
TP_DOMAIN_<DOMAIN SID>.PFL

9. Where the transport data files will be placed?


Answer: The transport data files will be placed on directory data under following location:
/usr/sap/trans/data/

10. How to make security authorization report?


Answer: The simplest way to get security authorization report is by executing T-code SUIM (User
Information System).
You can find different scenarios to get data like
- Find User by Complex criteria, unsuccessful logon, by logon date and so on.
- Find Roles by user assignment, transaction assignment, authorization object and so on.
- Change Documents for users, role assignment, roles, profiles, security policies and so on.

11. In which table failed user login attempts will be there?


Answer: Table USR02 contains the number of failed logon attempts of the user.

12. How to see the table entry values?


Answer: You can see the table entry values using T-code SE16 or SE11.

13. How will you give new authorization?


Answer: New authorization can be assigned to users as:
- Create role using T-code PFCG
- Add the authorization object in that role, generate and assign the user.

14. How to configure TMS?


Answer: For TMS configuration, select the domain controller and member systems from the SAP
landscape i.e. from Dev, Qas and Prd which one should be Domain Controller and which one should
be member systems.

ASHISH MISHRA
3
(MISHRA.ASHISH0123@GMAIL.COM)
Configuration steps:
a. Execute T-code STMS in client 000 from domain controller system
- A pop-up window prompt to configure domain controller
- Specify the domain controller hostname
- System Number
- TMSADM user creation
b. Execute T-code STMS in client 000 from member system
- System will display the domain controller details
- Click save to add the member system in the domain controller
- Member system will be in waiting status and needs approval from domain controller
c. Approval from Domain Controller
- Logon to the domain controller in client 000 and execute T-code STMS
- Go to Overview→Systems
- Select the member system and from the menu choose ‘SAP System’→Approve
d. Configured Transport Route
- The routes are created to transport the changes between the SAP systems in a system
landscape as configured in STMS
- Two routes are created:
i. Consolidation Route: From Dev to Qas system and
ii. Delivery Route: From Qas to Prd system
- Transport layers are only used in Consolidation route as it is assigned to all development
objects and need to be sent through same transport route

15. What is transport domain?


Answer: The SAP system within your system landscape which is used to maintain and change
transport management system configuration is domain controller and all the system within the
landscape is transport domain.

16. What is consolidation and delivery route? How will you identify them?
Answer: Consolidation Route - The route between development and quality system is called
consolidate route as it is required to transport the changes. Each transport layer has consolidation
route. Any modified objects that have a consolidation route set up for their transport layer are
included in transport request.
Delivery Route - The route between quality and production system is delivery route. Delivery route
have a source and a target system. To transport it into several systems, delivery route is used.

17. Transport error codes and their description?


Answer: The different types of transport error codes are:
- RC = 0, import successfully completed
- RC = 4, import ended with warning
e.g. Generation of programs and screens and columns or row missing.
The developers should be informed about the warnings.
- RC = 8, import ended with error
e.g. Syntax error, dictionary activation error, method execution error.
The developers should be informed immediately with error to take corrective actions.
- RC = 12, import is cancelled
e.g. due to object missing, connection problem between the systems
The administrator or developer needs to take corrective action based on the type of error.
- RC = 16, import is cancelled
e.g. system down during import, due to user expires, due to insufficient roles
The administrator needs to take the corrective action to resolve the issue.

ASHISH MISHRA
4
(MISHRA.ASHISH0123@GMAIL.COM)
18. Explain various Work Processes in SAP system?
Answer: The various Work processes in SAP are as follows:
a. Dialog (DIA) work process – It is used for interactive task in the system. It deals with the
requests from an active user to execute dialog steps. It executes one single dialog step at a
time and then available immediately for the next user request. The parameter to change the
number of DIA WPs in the system is: rdisp/wp_no_dia
b. Background (BTC) work process – It is used to execute the task in background without user
interaction. The parameter to modify the number of BTC WPs is: rdisp/wp_no_btc
c. Enqueue (ENQ) work process – It is used for handling the lock entries in the system i.e.
locking/unlocking of the objects. It allows application servers to synchronize their access to
the database and maintain data consistency. It is used to protect applications from blocking
among themselves during data access and avoid modifying a particular table by two different
users in parallel. The parameter to modify the number of enqueue work process in the
system is: rdisp/wp_no_enq
d. Update (V) work process: This work process is used to update the transactions in the
database when requested by dialog or background work processes.

19. How to find user used transaction codes which are not authorized for?
Answer: T-code SU53 is used to find the user last failed transaction code which he is not authorized
for.

20. How will you integrate existing ECC6 system with solution manager?
Answer: For integration of ECC6 system with solution manager,
- Perform Managed System Configuration for ECC system from solution manager by executing
T-code SOLMAN_SETUP and performing all the steps

21. How to lock or unlock transaction code using SM01?


Answer: Execute T-code SM01
- search for the T-code which you want to lock or unlock
- Check/Uncheck the Lock checkbox for lock/unlock the T-code
- Click Save

22. How to setup RFC connection in ECC system?


Answer: Basic steps for RFC creation are
- Execute T-code SM59
- Click on Create
- Enter RFC Destination Name
- Connection Type
- Target Host, Instance Number
- Username and password
- Select No in Trust Relationship
- Save
(If Trusted RFC needs to be created then:
i. save the created RFC first
ii. Execute T-code SMT1
iii. Select Create
iv. Enter newly created RFC
v. Continue and complete
vi. Again execute T-code SM59
vii. Select the RFC
viii. Delete the username and password
ix. Select Current user checkbox

ASHISH MISHRA
5
(MISHRA.ASHISH0123@GMAIL.COM)
x. Select Yes for Trust Relationship
xi. Save

23. Tell me steps for support package installation?


Answer: The steps for support package installation are:
- Download the support package software from SAP Service Marketplace
- Logon to the SAP system in client 000 using user DDIC
- Execute T-code SAINT
- From Menu “Installation Package” choose load package
- From Front End:
Select the SAR file from the local machine from the desired location. The SAR file will be
decompressed. Select Start and choose the correct support package. It will ask if you want to
install in dialog or in background mode, select the appropriate one and continue.
Confirm the queue to complete the installation.
- From Application Server:
Before selecting this option, copy the SAR file to the directory on application server and
extract the files in IN directory under /usr/sap/trans/EPS/IN using sapcar
e.g. sapcar –xvf <filename>.SAR –R /usr/sap/trans/EPS/in
Select Start and choose the correct support package. It will ask if you want to install in dialog
or in background mode, select the appropriate one and continue.
Confirm the queue to complete the installation.

24. How to adjust user master records?


Answer: User master records can be adjusted via T-code SU01. You can edit and change the user
details. By using T-code PFCG, you can adjust user for the role by user comparison.

25. How to check kernel, tp version?


Answer: Kernel Version:
- Logon to the SAP system, from menu System→Status→Other Kernel Info
- Execute T-code SM51, Goto Release Notes
- Execute disp+work from OS level
TP Version
- Execute tp command from OS level
- Execute T-code STMS, Menu Goto→tp parameters

26. Transport Request types and their syntax?


Answer: Type of Transport Request:
a. Workbench TR – Contains cross-client changes i.e. changes made to the repository objects of
ABAP workbench.
b. Customizing TR – Contains client specific changes recorded in a single client
c. Transport of Copies (TOC) – Allows to transport multiple transport request into one TR by
including the objects from multiple TR in TOC.

27. Where will you find transport error logs?


Answer: You can find transport error logs from application level as well as from OS level.
From Application Level: Click the particular transport request from STMS_IMPORT and from menu
Goto→Action Log or Transport Logs
From OS Level: From directory /usr/sap/trans/log

28. What is homogeneous and heterogeneous system copy and how will you do that?
Answer: In homogeneous system copy, the OS and database are same for both source and target
system.

ASHISH MISHRA
6
(MISHRA.ASHISH0123@GMAIL.COM)
e.g. Source System: Windows/Oracle 11g
Target System: Windows/Oracle 11g
In heterogeneous system copy, the source and target system is on different platform. In this, the OS
or Database is different from source.
e.g. Source: Windows/Oracle or Windows/Oracle
Target: RHEL/Oracle or Windows/DB2

29. At OS level in which directory oracle alerts are stored?


Answer: The directory where oracle alerts stored are:
$ORACLE_BASE/diag/rdbms/<DB_Name>/<SID>/trace/alert_<SID>.log
For SAP Application:
/oracle/<SID>/saptrace/diag/rdbms/<DB_Name>/<SID>/trace/alert_<SID>.log

30. If a lock entry is holding more than 24 hours, then what will you do?
Answer: A lock entry for more than 24 hours, suggest that the user has lost its connection from the
SAP system due to any reason.
To release a lock entry holding more than 24 hours, execute T-code SM12 select the lock and delete
it. But before deleting the lock ensure that the lock is not currently in use and the user Id specified in
the lock is no longer active in the system.

31. If another user wants to share the lock but the user using that lock haven’t been released and
he went for holiday what will you do?
Answer: If the user who went for holiday is still logged onto the system then log out the user from
the system using T-code SM04, it will release the lock and the user who want to share the lock can
use it. If still the user is unable to share the lock make sure to delete the lock from T-code SM12 but
after taking considerations like lock is not in use, user is not active, process is not running.

32. What will you do if you got update failure?


Answer: The SAP system sends update request to the database so that data changes are saved there
permanently. But sometimes due to any reason update may fail and get cancelled. You can use T-
code SM13 to check for cancelled updated in SAP system. You must notify the affected users if there
is any update failure and ask the user to execute the failed transaction again.

33. What will you observe in system log (SM21)?


Answer: The system log records all events, errors, problems and other system messages. From the T-
code SM21, we can monitor all the important warning and error messages of the SAP system.

34. How will you get help from SAP notes?


Answer: SAP Notes are small corrections delivered by SAP. It is frequently released for bug fixes, new
program developments or other updates by SAP.
SAP Note can be implemented in the system using T-code SNOTE.

35. How to extend tablespace and resizing of it?


Answer: A tablespace is a logical storage location in database where the actual data of database
objects can be kept.
Tablespace can be extended by using SQL command or by using brtools.
From SQL Command:
SQL> alter tablespace <TB_NAME> add datafile <FILE_NAME> size autoextend on/off;
e.g. alter tablespace SAPSR3 add datafile ‘/oracle/<SID>/sapdata1/sid_1/sid.data1’ size 5120M auto
extend on;
From BRTOOLS:
Login with orasid from OS level,

ASHISH MISHRA
7
(MISHRA.ASHISH0123@GMAIL.COM)
Execute brtools,
2 Space Management→1. Extend tablespace→Enter all the inputs as required and continue
e.g. 2 Space management→1 extend tablespace→ continue(c)→ continue(c)→1 extend→select
tablespace→enter details and continue

36. What is the need of having a development system?


Answer: The development system is where all the development and customization done in context
to the SAP system. The development system is separated from quality and production system as it is
solely used for development.

37. Difference between application server and central instance?


Answer: Before SAP NetWeaver 7.0, SAP central instance is one which contains both primary
application server, message server and enqueuer server in it.
As of NetWeaver 7.0, SAP central services instance is one which contains message server and
enqueue server which is used for administering the lock table for database and handles the
communication between the application servers. The central services instance is one per sap system.
Application server is one which process the actual business logic of the user’s request and contains all
the work processes for processing of logic.

38. How will you check whether database is active or not from OS level?
Answer: In many ways you can check whether database is active or not:
a. Check whether database services are running or not
b. R3trans –x to check SAP is communicating with database or not
c. From SQL prompt

39. How to lock a client? How to delete a client?


Answer: You can use Function Module “SCCR_LOCK_CLIENT” in T-code SE37 to lock a client.
Also, if you want to lock a client for no development then you can use T-code SCC4.
For deletion of client, T-code SCC5 is used.

40. How to login in to SAP from command level?


Answer: You can login in to the SAP from command level as:
a. Open Command prompt and enter command: sapgui <application server> <instance no>
b. Open Run in MS Windows and enter sapgui <application server> <instance no>

41. How to define logon groups? What is logon load balancing?


Answer: T-code SMLG is used to define logon groups.
Logon load balancing allows you to distribute the users to least loaded SAP application server thus
balancing the load within the SAP systems. The user will automatically log on to the server that
currently has best performance or fewest users with the help of logon load balancing configuration.

42. How to find SAP transaction code?


Answer: SAP transaction code can be found out using:
a. Using T-code SE93
b. SE16 and table name TSTC
c. Select the transaction from menu folder and goto Extras→Technical Details
d. From bottom right on the screen, you can see details like current T-code, current program,
system, client, user and so on.

43. How to find list of all the Tcodes for a role in SAP?
Answer: The way in which we can find all the T-codes for a role in SAP are:
a. By using T-code PFCG, enter role name and display→ Menu

ASHISH MISHRA
8
(MISHRA.ASHISH0123@GMAIL.COM)
b. T-code SUIM, goto Transactions→Executable for Role→Execute and enter the role name and
again execute

44. How can I delete a data file that was created by mistake?
Answer: You can use sql prompt or brtools to delete a data file by executing following command:
SQL> alter tablespace <name> drop datafile <name> including contents;
But you have to keep in mind before dropping the datafile:
a. The database must be open
b. The data file must be empty
c. You cannot frop one data file from tablespace

45. Users could not logon to the system? Why?


Answer: If the user is unable to logon to the system then following steps need to take care:
a. Check oraarch is full or not
b. Check whether the work processes are free or not
c. Check whether SAP and database services are running or not
d. Check R3trans –d is ok or not which is used for connectivity between SAP and database
e. Check if tablespace gets full
f. Check the log file of there is issue in SAP system to analyse and start the system

46. What is the difference between pfile and spfile?


Answer: Parameter files in database is text or binary files which is used to store initialization
parameters which is used by oracle instance during startup.
pfile is text file which can be edited using standard editor. The change of parameters in pfile requires
database to be restart to take effect. The location of pfile is $ORACLE_HOME/dbs/init<SID>.ora
spfile is a binary file which cannot be edited by text editor. The parameter can be changed by issuing
a command “ALTER SYSTEM SET” and the changes can be taken automatically with need to restart.
The location of spfile is $ORACLE_HOME/dbs/spfile<SID>.ora

47. If brtools is not working how will you add data file?
Answer: If brtools is not working, data file can be added via SQL prompt.
SQL> alter tablespace <name> add datafile <name> size <MB> autoextend on/off;

48. List of R/3 user types?


Answer: The R/3 user types are:
a. Dialog ‘A’: It is used for individual, interactive system access. System checks for
expired/initial passwords and multiple dialog logon. Users can change their own passwords.
b. System ‘B’: This user type is not for interactive session and used for internal system
processes like background processing, workflows, TMS.
c. Communication ‘C’: Dialog logon is not possible. Used for communication between systems
like RFC or CPIC. Users can change their passwords.
d. Service ‘S’: Service user is a dialog user that is available for anonymous system access for
larger group of users. The system does not check for expired/initial passwords. Only
administrator can change the passwords. Multiple login is allowed.
e. Reference ‘L’: It is a general user type which is not assigned to particular person. Used only
to assign additional authorization. No logon is possible. Reference users are implemented to
equip internet users with identical authorizations.

49. How to unlock the object?


Answer: If the object is captured in transport request, you can delete objects from T-code SE03.
T-code: SE03→Requests/Tasks→Unlock Objects→Enter the TR number and execute

ASHISH MISHRA
9
(MISHRA.ASHISH0123@GMAIL.COM)
50. Difference between SPDD and SPAU?
Answer: The SPDD/SPAU are the important activity during the upgrade process. All the objects of SAP
standard which are modified are overwritten with the objects after upgrade. To retain the modified
objects, SAP provides all modified objects which are redelivered in the upgrade adjustment of
transaction SPDD and SPAU.
SPDD/SPAU allows to carry forward the changes made to the standard objects or reset to original (i.e.
modification will be lost, and newer version gets overwritten) with the options of “With Modification
Assistant” and “Without Modification Adjustment”
➢ SPDD: The SPDD contains list of all modified data dictionary objects like tables, data
elements, views, indexes.
➢ SPAU: The SPAU contains list of all modified repository objects like programs, reports,
screens, function modules.

51. What is SSO? How to configure it?


Answer: SSO is a user authentication process that enables a user to log in once and access the
resources of multiple systems without being prompted to log in again.
SSO configuration between ABAP and JAVA systems:
a. Maintain the parameter in ABAP system and restart the system to save changes
permanently.
i. icm/host_name_full = <hostname.domain.com>
ii. Login/accept_sso2_ticket = 1
iii. Login/create_sso2_ticket = 2
b. Export the certificate from JAVA system
i. Login to the NWA of JAVA system with administrator user
ii. Goto Configuration→Security→Certificate & Keys
iii. Select TicketKeyStore from Key Storage
iv. Create new certificate if not exist
v. Export entry and download the .cert file
c. Login to the 000 client of ABAP system
i. Start T-code STRUSTSSO2
ii. Click on import certificate and select the downloaded file and ok
iii. Click “Add to certificate list” and “Add to ACL”
Note: Certificate must be added to ACL in individual client to enable SSO
d. Import Certificate Response from ABAP system using T-code STRUSTSSO2
e. Login again to the JAVA system to import ABAP certificate
i. Goto Configuration→Security→Trusted Systems
ii. Click Add Trusted System
iii. Import Certificate by manually uploading the file or by querying the system
f. Once done, the certificate will automatically added to the Certificate and Keys list.

52. If java is down how will you do troubleshooting?


Answer: There are many steps to be taken care for troubleshooting if java system is down:
a. Check if Database is running or not. Check the DB log files if issue is related to database
b. Check if listener is running or not
c. If the issue is with initial load while starting java system, check dev_jstart log file
d. If the issue is like startup fails due to offline deployment, check dev_deployment,
std_deployment, jvm_deployment log files
e. If the issue is like error during synchronization of binary data, check dev_bootstrap,
std_bootstrap and jvm_bootstrap log files

ASHISH MISHRA
10
(MISHRA.ASHISH0123@GMAIL.COM)
f. If the server node has some issue, check dev_server0, std_server0, jvm_server0 log files

53. Where can you see oracle parameters?


Answer: The oracle parameters can be seen out by:
a. From pfile which is located in $ORACLE_HOME/dbs/init<SID>.ora
b. V$PARAMETER from SQL prompt displays information about the parameter and also by
SHOW command

54. Difference between client copy vs system refresh?


Answer: Client copy means copying to a newly created client which may be locally in a system (same
SID) or remotely (different SID) by choosing various profiles.
It gives the options to choose what kind of data you want to copy like customizing data, user master,
application data, etc by choosing the profile you want.

System refresh/copy means refreshing/copying the existing data from source to target system. It is
done to update the target system with latest application/transactional data which is more useful for
testing environment.
e.g. System refresh from production to quality system in which complete database copy occurs.
Also, system copy is performed when you want to change your operating system or database. The
system copy can be performed by using “Backup – Restore Procedure” or by “Import – Export”

55. Steps for system refresh using backup restore procedure?


Answer: The Steps for system refresh using backup restore procedure are as follows:
Pre-refresh activity:

➢ Export of user master from target system using SCC8


➢ RFC export using TR or via OS level
➢ Snapshot of various transactions like SCC4, WE20, STMS, SMLG, RZ04, BD54 etc
➢ Complete offline backup of the source system should be available
➢ Backup the control file from target system
SQL> alter database backup controlfile to trace (file be created in trace directory of oracle
database)

Refresh activity:

➢ Stop the target system both SAP and database


➢ Remove all the oracle datafiles from target system
➢ Copy the backup file to the target system in appropriate directory like sapdata1, sapdata2,
saptrace etc
➢ Modify the control file and save it as .sql
➢ Create the control file from the script .sql
➢ Recover the database
SQL> recover database using controlfile until cancel
➢ Start the database in resetlogs mode
SQL> start database open resetlogs;
➢ Disable batch processing by setting the value of the parameter “rdisp/wp_no_btc=0”
➢ Start the SAP system

Post-refresh activity:

➢ Install SAP license

ASHISH MISHRA
11
(MISHRA.ASHISH0123@GMAIL.COM)
➢ Suspend the batch jobs from released to scheduled using report BTCTRNS1
➢ Restart the SAP system after setting the original value of the parameter “rdisp/wp_no_btc”
➢ Configure STMS
➢ Execute SGEN
➢ Import User master using STMS
➢ Import RFC export using STMS or via OS level
➢ Execute BDLS (logical system name conversion)
➢ Correct and configure the different transactions like SMLG, RZ04, SCC4, WE20

56. Difference between visual admin and config tool?


Answer: Config tool

➢ Offline configuration tool


➢ Doesn’t need JAVA system to start
➢ Database must be started to work on config tool
➢ Used to make changes to the memory parameters, UME and server nodes
➢ Is not password protected
➢ Configuration of services and managers can be done with config tool
➢ Restart of JAVA system required if changes has been done
Location of config tool: /usr/sap/<SID>/J<nr>/j2ee/configtool/
File name: configtool (.bat)

Visual Admin

➢ Online administration tool


➢ JAVA system need to be started
➢ User authentication is required
➢ Changes to parameter can be done at runtime
➢ AS JAVA can be started and stopped via visual admin
Location of visual admin: /usr/sap/<SID>/J<nr>/j2ee/admin/
File name: go (script file)

Note: Visual Admin is replaced by NWA (NetWeaver Administration) for AS JAVA >=7.1
NWA is online browser-based administration tool for AS JAVA.

57. Difference between SDM and JSPM?


Answer: Software Deployment Manager (SDM)

➢ Tool to manage and deploy JAVA support packages


➢ Only single patch can be deployed at a time
➢ It consists of SDM GUI, Server and Repository

JAVA Support Package Manager (JSPM)

➢ Tool to apply support packages on AS JAVA


➢ Allows to install components and support packages on AS JAVA
➢ Allows to import single support stack, support packages stacks, kernel and third-party
components
➢ JSPM connects to SDM for deployment i.e. JSPM indirectly connects to SDM
To start JSPM, execute go script file from location /usr/sap/<SID>/J<nr>/j2ee/JSPM/

Note: From NetWeaver 7.0 onwards, JSPM has been replaced by Software Update Manager (SUM).

ASHISH MISHRA
12
(MISHRA.ASHISH0123@GMAIL.COM)
58. How will you define background jobs? Which job class used and the status?
Answer: Background jobs are scheduled using T-code SM36.

➢ Execute T-code SM36


➢ Enter Job name, priority and server
➢ Goto Step and enter the ABAP program name, variant (if there), user for processing
➢ Goto Start Condition and enter the start options like date, time, after event, after job or
immediate
➢ Enter the frequency like daily, hourly

The job classes are:

I. Class A – High Priority: Used for urgent and critical tasks. It reserves one or more batch work
process for its execution.
II. Class B – Middle Priority: These jobs are executed after completion of Class A.
III. Class C – Low Priority: These jobs run once Class A & B gets completed.

The status of the batch jobs is:

I. Scheduled – The program name and variant are defined but not the start condition like start
date, frequency i.e. you have not defined when a job should be scheduled in the system.
II. Released – All required criteria are fulfilled for job definition. Without a start condition, a
job cannot be released.
III. Ready – The start condition of a job has been met and waiting in a queue for the
background work process for its execution.
IV. Active – Job has started running in the background. We cannot change the status of the
active job.
V. Finished – Job is executed successfully i.e. the processing of the program has been executed
without any error.
VI. Cancelled – The job has terminated abnormally either the job has been terminated
forcefully by the administrator or there is an issue with the job and terminated with error.
Error details can be found out in job logs.

59. If transport is imported or not where will you check?


Answer: There are many ways to check whether transport is imported or not:

➢ Using STMS, go to Transport Overview, select the system and click on Import History
➢ Using SE01, enter the transport number and click on Logs
➢ From OS level, from /usr/sap/trans/log ($transdir) directory, check for ALOG file or request
file
➢ Using SE16, table name E070, enter the transport number and execute

60. Kernel Upgrade Procedure?


Answer: The steps to upgrade kernel are as follows:

➢ Download the required kernel files from SAP Service Marketplace i.e. files is divided into two
parts Database specific (SAPEXEDB_XX.SAR) and Database independent (SAPEXE_XX.SAR)
➢ Copy the SAR files on server in any directory
➢ Login to the server with <sid>adm user
➢ Extract the downloaded SAR files in the directory using SAPCAR command
e.g. SAPCAR -xvf SAPEXE_XX.SAR and SAPCAR -xvf SAPEXEDB_XX.SAR

ASHISH MISHRA
13
(MISHRA.ASHISH0123@GMAIL.COM)
➢ Take the backup of the existing kernel directory
e.g. Backup folder: exe_old
Path: /usr/sap/<SID>/SYS/exe/
➢ Stop the SAP application and services i.e. all instances and hostagent.
➢ Copy and paste the extracted files to the existing kernel directory
➢ Login to the server using root user and execute saproot.sh file to correct the file permission
for the executables files
e.g. ./saproot.sh <SID>
➢ Start the SAP application and services and check the kernel version

61. Error in phase IMPORT_PROPER while applying support package using SPAM?
Answer: The IMPORT_PORPER phase imports all the repository objects and table entries if not
imported during INACTIVE_IMPORT phase while updating support package during SPAM.
There are various reasons for getting an error in phase IMPORT_PROPER phase.
For example – errors related to background jobs, temporary file not accessible, out of space on file
system, database related errors, error during conversion of DD objects, etc.

For analysis:
➢ Check the log files from SPAM screen itself first.
➢ Check the system log (SLOG), action log (ALOG) and user log (ULOG) for the root cause of the
error.
➢ If the system is unable to trigger batch jobs, ensure the TMS configuration is consistent.
➢ Free up the space on the file system if the file system gets full.
➢ Delete or move the older log file from /usr/sap/trans/log directory if the error related to
DIR_TRANS/log directory is big encountered.

62. How will you do client copy if user SAP* is not available in the system?
Answer: If SAP* user is not available, check from the database level whether the user exists or not
from below command:
SQL> select * from SAPSR3.USR02 where mandt=’<client>’ bname=’SAP*’;
Also, delete the user from DB level by using command
SQL> delete from SAPSR3.USR02 where mandt=’<client>’ bname=’SAP*’;

Set the parameter “login/no_automatic_user_sapstar” equals to 0 in the profile file and restart the
SAP application.
After restart, you are able to login with the user SAP* in the client and you can continue with client
copy.

63. If you have long running job how do you analyse?


Answer: We can analyse long running jobs by:

➢ Execute SM37, enter the details and select the long running jobs and goto job logs
➢ Identify the process and server and goto transaction SM50 to view more details of work
process
➢ Find the status of the work process and click on the reason to troubleshoot if the work
process in On Hold status
➢ If the work process is in running status with action sequential read then analyse the table
like how many records exist, proper indexing is there or not
➢ Transaction ST05 or ST12 can be used to trace the background job and identify memory or
buffer issues
➢ Transaction STAD to check the reason for high response time

ASHISH MISHRA
14
(MISHRA.ASHISH0123@GMAIL.COM)
64. What is redo log file?
Answer: Redo log file consists of two or more preallocated files that store all changes made to the
database as they occur which is the most crucial structure for recovery. Whenever something
changes in a datafile, database records the changes in the redo log. The redo log consists of groups of
redo log files. The redo log is used to recover a database after failure. To restore the database up to
recent data changes, redo log can be used so that work is never lost.
The redo log is stored as members in groups on different disks for higher availability.
e.g. Group 1 has two members as A_log1 and B_log1 and Group 2 has two members as A_log2 and
B_log2.

65. Synchronous and Asynchronous RFC in SAP?


Answer: Synchronous RFC performs a call directly and waits for the reply from the called function
module. The called system must be available when using synchronous RFC. The call is made only
once, and the call fails if the call system is not available.

In Asynchronous RFC, the calling function does not wait for the acknowledgement from the called
system and continue processing other steps i.e. user does not have to wait for their completion
before continuing the calling dialog. The asynchronous RFC is used whenever you need to establish
communication with a remote system but do not want to wait for the function’s result before
continuing processing.

66. How to create control file in database?


Answer: Control file is a small binary file that stores the physical structure of the database like
database name, name and location of datafile and redo log files, current log sequence number.
The control file is created during database creation. The control file must be available for writing
whenever the database is open. Without the control file, the database cannot be mounted, and
recovery is difficult.
The control file is created in database by performing executing script file (.sql)
➢ Shutdown the database
SQL> shutdown (immediate)
➢ Start the database in nomount stage
SQL>Startup nomount
➢ Execute the .sql script
SQL>@<filename>.sql
➢ Recover the database if necessary
SQL>recover database using controlfile until cancel
➢ Open the database
SQL> alter database open (resetlogs)
Note: Script file (.sql) contains the command like
CREATE CONTROLFILE SET DATABASE <SID>
LOGFILE GROUP 1 (‘<filename1>’,’<filename2>’),
GROUP 2 (‘<filename1>’,’<filename2>’),
GROUP 3 (‘<filename1>’,’<filename2>’)
RESETLOGS
DATAFILE ‘file1’ size <in MB>,
‘file2’size <in MB),
‘file3’ size in MB
MAXLOGFILES <nr>
MAXDATAFILES <nr>
ARCHIVELOG;

ASHISH MISHRA
15
(MISHRA.ASHISH0123@GMAIL.COM)
67. What is logical system in SAP?
Answer: Logical system is used to identify an individual client in a SAP system for ALE communication
between SAP systems. When data is distributed between different systems, each system within a
network has to be clearly identifiable and this is why each client is assigned a unique logical system
name.
The naming convention for logical system is: <SID>CLNT<client number>
e.g. ECDCLNT333, Q02CLNT100
The logical system for client is created using T-code BD54 and then assign it to client using T-code
SCC4.

68. What is SAP buffer hit ratio?


Answer: The buffer hit is when the objects in the buffer are accessed and doesn’t need to fetch the
data from the database.
The buffer hit ratio is the percentage of data accesses from the buffer and do not require database
access.
The hit ratio for the buffers should be 98% or better.

69. What is load balancing? Steps to configure logon load balancing?


Answer: Load balancing allows to dynamically distribute the SAP users to application server
instances. The load balancing increases the efficiency and performance as the least loaded
application instance is called when user request goes to message server.
Logon groups are used for load balancing. We can add and delete the logon groups using T-code
SMLG.
The steps to configure logon load balancing for SAPGUI logon is as follows:

➢ Create logon group using T-code SMLG


➢ Assign instances to the newly created group
➢ Make an entry in service file of the client system
File Location: C:\widnows\system32\drivers\etc\
File: services
Entry: sapms<SID> 36<nr>/tcp
Where SID is System ID and 36<nr> is message server port number/instance number
➢ Hit enter after the entry in service file
➢ Go to SAPGUI logonpad
➢ Configure the connection details as
• Click New Item
• Provide description
• Provide message server details
• The logon groups should be visible in the Group/Server tab, select one
• Click OK

70. Difference between init.ora and listener.ora file in oracle database.


Answer: The initialization parameter (init.ora) or pfile is a plain text file which contains various
initialization parameters used while starting a database. Oracle reads the parameter from either a
pfile or spfile as the database is starting. It tells the oracle programs how much memory to allocate,
location of existing files, control file locations and trace and dump file locations. The file name should
be as init<SID>.ora
The default location of the file is:
Linux: ORACLE_HOME/dbs
Windows: ORACLE_HOME\database

ASHISH MISHRA
16
(MISHRA.ASHISH0123@GMAIL.COM)
Listener is the oracle process that runs on the database server which receives incoming requests and
redirects these request to the database server i.e. it is used to provide communication between
client and database. The listener configured is stored in a configuration file called listener.ora. The
listener works on TCP/IP protocol and the default port is 1521.
The default file location of listener.ora: ORACLE_HOME/network/admin in Linux

71. How to check the status of the SAPOSCOL? How to start and stop the sapsocol?
Answer: SAP Operating System Collector (SAPOSCOL) is a program that runs in the OS background
and collects data about operating system which includes usage of virtual and physical memory, CPU
utilization physical disk/file system utilization and usage of running processes.
The steps to check the status of the sapsoscol and start/stop are:
➢ Log on to server using<SID>adm user
➢ To check status, run saposcol -s
➢ To start, run saposcol -l
➢ To stop, run saposcol -k

72. How to find SAP up or not in unix?


Answer: We can check the SAP process to see if SAP is up or not using command below:
- Ps -ef |grep sap*
- Ps -ef |grep dw* (for dispatcher)
We can also check available.log file in work directory to check system availability.

73. How to check listener is running or not?


Answer: To check whether listener is running or not by executing command:
- lsnrctl status

74. What is SLD and its usage?


Answer:
➢ System landscape Directory (SLD) is the central information repository for SAP system
landscapes which stores information about all installable and installed components in
system landscape.
➢ It contains information about technical systems, landscapes, business systems, products and
software components in system landscape
➢ It provides web-based interface to manage and administer the components in SLD.
➢ It is contained in SAP Java Application server
➢ The URL to access SLD is http://<hostname>:<port>/sld
➢ There are following ways to send data to the SLD
• For ABAP based system – Data supplier transaction RZ70 is used
• For JAVA based system – Uses HTTP destination to send data to the SLD

75. Difference between shutdown abort and shutdown immediate command in oracle?
Answer: In shutdown immediate, shutdown of database proceeds with:
➢ No new connections/transactions are allowed to be started after the command
➢ The transactions which are not committed are rolled back
➢ The database disconnects all the active users

In shutdown abort:
➢ No new connections/transactions are allowed to be started after this command
➢ Currently active transactions are terminated immediately
➢ The database disconnected all active users
➢ Uncommitted transactions are not rolled back
➢ The instance recovery required after database startup to be in consistent state

ASHISH MISHRA
17
(MISHRA.ASHISH0123@GMAIL.COM)
76. How to disable “IMPORT ALL” button on stms for the queue?
Answer: To disable “import all” button on stms, follow the below steps:

➢ Log on to the domain controller in 000 client


➢ Execute transaction STMS
➢ Click on System Overview
➢ Double click on the system on which you want to disable this
➢ Click on change
➢ Go to Transport Tool tab
➢ Add parameter “NO_IMPORT_ALL” with value 1
➢ Save and update the configuration

77. How do you create password exception list and also how to create custom security policy?
Answer: Password exception list can be created using T-code SM30 (table maintenance)
➢ Execute T-code SM30
➢ Enter table name USR40
➢ Go to Menu “Table”→ Create entries
➢ Create the password exception list
Note: The changes will only be allowed if the client is open and cross-client changes setting is enabled
in SCC4.

You can create custom security policy and assign it to users if you explicitly do not want to use the
default values and assign it to different set of users. The steps to create and assign the security policy
are:
➢ Execute T-code SECPOL
➢ In change mode, create New Entries
➢ Enter a name and description of the security policy
➢ Click on the Attribute
➢ Choose New Entries
➢ Enter the policy attribute name and value as per requirements
➢ Choose Effective to apply the changes
➢ Save
➢ The system will display the error if any. Correct the error and save again
➢ Execute T-code SU01
➢ Enter the username and change
➢ On the Logon Data tab, enter a security policy name which you have created in the Security
Policy field
➢ Save

78. Explain R3trans, tp, R3load and R3szchk.


Answer: Transport control program (tp) is an OS level tool used for controlling transports between
R/3 systems. TP ensures that the steps in exporting and importing objects are performed in correct
order and the imports into a target system are done in same order as the exports from the source
systems.
R3trans is a transport tool which is used to transport data between R/3 systems. R3trans is called by
another program like tp and R3up (upgrade control program). TP doesn’t perform the actual
transport of data, it calls R3trans to transport.
R3load is used for table import/export during SAP installation, upgrade and migration. It
loads/unloads data from table from/into the database to database and platform independent file.
R3szchk is a tool which is used to calculate the database size, object sizes for the target system bases
on the STR files created by R3ldctl during the OS/DB migration.

ASHISH MISHRA
18
(MISHRA.ASHISH0123@GMAIL.COM)
79. What is SLD and how data flow in SLD?
Answer: System Landscape Directory (SLD) is the central repository for landscape information used
for lifecycle management of the software. It stores information about all installable and installed
components of a system landscape. SLD is configured on JAVA system and it can be accessed from
the URL: http://<java_hostname>:<port>/sld
The data suppliers collect the data about SAP systems like SAP products, database parameters, hosts,
clients etc and send it to SLD.
➢ ABAP-based data supplier uses RFC connection to send data to the SLD
- Call T-code RZ70
- Enter the gateway host and port same as in SLD. (To find host and port, goto AS
JAVA system SLD→Administration→Details→Data Suppliers
- Scheduled the background job for periodic data transfer
- Save and Choose Start SLD Data Collection now
➢ JAVA-based data supplier uses HTTP to send data to the SLD
- Login to the JAVA NWA
- Go to Configuration→Security→Destination
- Create HTTP destination “SLD_DataSupplier” and enter the SLD host details
- Create HTTP destination “SLD_Client” and enter the SLD host details
- Save
- Go to Configuration→Infrastructure→SLD Data Supplier Configuration
- Choose Collect and send data

80. What is LMDB and how data flow to LMDB?


Answer: Landscape Management Database (LMDB) is the central landscape information repository in
SAP Solution Manager. System information in the LMDB is provided by synchronization with a SLD
which continuously gathers data by the data suppliers from the technical systems.
The LMDB is the source of providing technical system information to the SAP Support Portal to be
used by Maintenance Planner.
Data Flow to LMDB:

Technical System SLD LMDB SAP Support Portal

81. Default port used in SAP System.


Answer: The port used in SAP system are:
ABAP System:
a) ICM HTTP Port: 80<NN>
b) ICM SMTP Port: 25
c) Dispatcher: 32<NN>
d) Gateway: 33<NN>
e) Message Server: 36<NN>
f) Internal Message Server:39<NN>
g) SAP Router: 3299

JAVA System:
a) HTTP Port: 5<NN>00
b) HTTPS Port: 5<NN>01
c) P4 Port: 5<NN>04

Software Update Manager (SUM) tool:


HTTPS: 1129
HTTP: 1128
Software Provisioning Manager (SWPM) tool: 4237

ASHISH MISHRA
19
(MISHRA.ASHISH0123@GMAIL.COM)
82. Explain different phases during SUM execution.
Answer: There are 6 phases during execution of SUM tool:
a. Extraction:
➢ Check for SAP Notes i.e. implement SAP Notes to fix some bug or error
➢ Check for System Profiles
➢ Reads the profiles and check the status of the running instances
➢ Checks for OS and DB version
➢ Determines DB version and SAP Release
➢ Checks if tool connect to DB
➢ Checks the stack.xml file
➢ Gathers info about the instance of the system
➢ Job RSUPDTEC started which resolve inconsistencies in TABART-TABSPACE mappings
➢ Copies the original kernel to path /exe
➢ Reads profiles and prompts for passwords
➢ Reads the CVERS table content
➢ Test a kernel to install in /usr/sap/dir/SUM/abap/exe
➢ Scans the download directory and extract the packages
➢ Prepares the ABAP dictionary for importing upgrade tools on instance
➢ Check the tool version if system is Unicode
➢ Checks if the source and target system is valid for update
➢ Checks the SAP System release

b. Configuration:
➢ Main upgrade configuration, where you will give input parameters for -Advanced
(expensive downtime optimizes, higher complexity, high resource assignment)
➢ Keep database archiving on
➢ Execution strategy for transaction SGEN
➢ Maximum number of processes to be used for load generation. SGEN Processes
➢ Batch Process (Uptime)
➢ Batch Process (Downtime)
➢ Maximum number of DDL processes (Uptime and Downtime)
➢ Number of parallel import processes (R3trans -Uptime and Downtime)
➢ Parallel Phases (Uptime and downtime)
➢ Update Instances
➢ Enhancement package inclusion
➢ Add-On selection
➢ Modification Adjustment (SPDD transport request and SPAU transport request)

c. Checks:
➢ Checks whether activation error might occur during update
➢ b. Tests whether background server can access the update directory
➢ c. Ask to implement necessary SAP Notes
➢ d. Roadmap step: Execute various checks: database, kernel, OS, space calculation etc
➢ e. Checks the environment of <sid>adm and whether profiles can be modified
➢ f. FREECHK: Check the free space in file system
➢ g. SPACECHK_INI: Checks the database free space

ASHISH MISHRA
20
(MISHRA.ASHISH0123@GMAIL.COM)
d. Pre-processing:
➢ Check for locked objects
➢ ABAP Workbench locking
➢ Run shadow system for preparation of new release (ACT_UPG, PARDIST, SGEN)
➢ SPDD Adjustments
➢ Option to add additional add-on package
➢ DBCLONE: Target system copied from the current system, batch job started to create the
copies of the tables checks and asks the necessary questions for entering the downtime
➢ Creates the views on shadows
➢ SUM ask to confirm the locking of the ABAP Workbench on all SAP instances. These locks
prevent dev objects from being changed during update. You can continue to use the SAP
system. This phase displays all the repairs that are still open in TR, release the TR so that
you can continue

e. Execution:
Sum tool downtime is called as execution where actual are copied from Shadow to Main
Instance and system were unavailable during the downtime.
➢ Merging of shadow and Real Instance
➢ system upgrade
➢ Table conversion
➢ SUM runs job RUTDDLSCREATE which creates CDS Views after the migration
➢ SUM runs BW related checks before entering to downtime
➢ SUM starts the shadow system (3rd)
➢ SUM starts the standard instance after kernel switch with the target kernel.
➢ SUM starts the standard instance for postprocessing
➢ SUM starts the standard instance before kernel switch with the source release kernel
➢ XPRAS_TRANS, XPRAS_UPG and XPRAS_AIMMRG: XPRA or "Report after Put" is an ABAP
program or Function Module that is executed during a transport request import
sequence, the import of a Support Package and during Upgrades/Enhancement Package
installations. The reports that are executed during XPRA are application-related
conversions, adjustments, data mergers or alignments for the conversion of release-
specific SAP-shipped customizing that need to be adjusted during the upgrade. The
runtime of the XPRA phase differs from one application component to another -
however XPRAs are used by all SAP modules and applications. The XPRA phase reports
are run as one of the last steps of the upgrade. However, since table content is adjusted,
the XPRA phase needs to be done at application downtime. XPRA can also run as part of
the activation of extension sets and IS add-ons.

f. Post-processing:
➢ SPAU change
➢ Backup
➢ Create folder in trans directory (EHPi)

83. Use of table T000, TSTC, USR02, USR40, DEVACCESS, USREFUS, AGR_USERS and AGR_TCODES.
Answer: The uses of table are:
a. T000 – Contains list of all defined Clients as maintained in T-code SCC4
b. TSTC – Contains list of T-codes with program name

ASHISH MISHRA
21
(MISHRA.ASHISH0123@GMAIL.COM)
c. USR02 – Contains user details like username, initial password, valid from/through, user type,
last password change, creator, last logon date/time and so on.
d. USR40 – Contains Password exception list
e. DEVACCESS – Contains list of users with developer access
f. USREFUS – Contains list of users with their alias
g. AGR_USERS – Contains user to role mapping
h. AGR_TCODES – Contains role to t-code mapping

84. How to disable multiple user logins and allow some specific users for multiple login to the SAP
system?
Answer: To disable multiple user logins to the SAP system, set the parameter
login/disable_multi_gui_login = 1.
Also, to allow specific users for multiple login, set the parameter login/multi_login_users = <user1>,
<user2>, …. And so on separated by comma.

85. Steps to install and configure SAProuter.


Answer: The steps to install and configure SAProuter are:
➢ Download latest media files from SAP Support Portal: saprouter<version>.SAR and
sapcryptolib<version>.SAR
➢ Create directory “saprouter”
➢ Extract the media (.SAR files) in saprouter directory using SAPCAR
➢ Set Environment variable
SECUDIR: <path_of_saprouter_directory>
SNC_LIB:<path_of_cryptolib_file>
➢ Generate certificate request by issuing below command
a. ./sapgenpse get_pse -v -noreq -p <path>/local.pse “CN=<host>, OU=<Org Unit>,
OU=SAProuter, O=SAP, C=DE”
Enter the PIN
b. ./sapgenpse get_pse -v -onlyreq -r certreq -p <path>/local.pse
It will create certreq file
c. Login to the SAP Support Portal and goto SAProuter tab from
Menu→Tools→Connectivity Tools→SAProuter and click on apply for SAProuter
certificates
d. Copy the content from certreq file and paste it there
e. Follow the steps and the certificate will be generated
f. Create the file srcert file in the respective directory and past the content from Support
portal on this file
g. Import the certificate into local.pse file by issuing below command
./sapgenpse import_own_cert -c <srcert file> -p <path>/local.pse
h. Execute the command for user login
./sapgenpse seclogin -p <path>/local.pse
i. Execute the command for verification
./sapgenpse get_my_name -v -n Issuer
j. Create saprouttab file containing all the list of servers for which you want to configure
the SAProuter i.e. allow/deny the SAP application servers

Command to Start/Stop and check status of the SAProuter:


Start: saprouter -r -S 3299 -K “CN=<host>, OU=<Org Unit>, OU=SAProuter, O=SAP, C=DE”
Stop: saprouter -s
Status: saprouter -l

ASHISH MISHRA
22
(MISHRA.ASHISH0123@GMAIL.COM)
86. Discuss various SAP Housekeeping Jobs.
Answer: The various SAP housekeeping jobs are as follows:
Job Name Program Variant Client-dependent Repeat

SAP_REORG_JOBS RSBTCDEL YES YES DAILY

SAP_REORG_SPOOL RSPO0041 YES YES DAILY

SAP_REORG_BATCHINPUT RSBDCREO YES YES DAILY

SAP_REORG_ABAPDUMPS RSSNAPDL YES NO DAILY

SAP_REORG_JOBSTATISTIC RSBPSTDE YES NO MONTHLY

SAP_COLLECTOR_FOR_JOBSTATISTIC RSBPCOLL NO NO DAILY

SAP_COLLECTOR_FOR_PERFMONITOR RSCOLL00 NO NO HOURLY

a. RSBTCDEL – The program is used for cleaning up the background jobs which have ran
successfully and at least X days old.
b. RSPO0041 – The program is used for cleaning up the spool objects. The spool objects are
generated every time the print requests are given. The spool objects can be deleted
depending on the input criteria of the variant.
c. RSBPCOLL – The program is used for calculating the runtime statistics information. This
program only takes the periodic jobs which have terminated normally and calculates an
average runtime statistic for each job.
d. RSCOLL00 – The program is used for collecting performance data across all application
instances.
e. RSSNAPDL – The program is used to delete old short dumps from the SNAP table.
f. RSBDCREO – The program is used for cleaning the batch input session log.

87. How to export/import RFCs from OS level?


Answer: The steps to export/import RFCs from OS level are as follows:
Export:
➢ Create script file with below mentioned data (For e.g. Filename = rfcexport)
Export
File = ‘<path>/<filename> (e.g. /usr/sap/trans/rfcdata)
select * from rfcdes
select * from rfcattrib
select * from rfcdoc
select * from rfccheck
select * from rfccmc
select * from rfcsysacl
select * from rsectab

➢ Run command “R3trans -w rfcexp.log <export_filename>” with <sidadm> user


Note: Create rfcdata file manually if not created after running this command and set user
and permission for <sidadm> user group accordingly.
➢ Check the log file and RC code should be = 0

Import:
➢ Create script file with below mentioned data (For e.g. Filename = rfcimport)

ASHISH MISHRA
23
(MISHRA.ASHISH0123@GMAIL.COM)
Import
File = ‘<path>/<filename> (e.g. /usr/sap/trans/rfcdata)
➢ Run command “R3trans -w rfcimp.log <import_filename>”
➢ Verify the log files and T-code SM59

88. How do you create control file? What is the command?


Answer: For creating the control file first locate all the datafiles and log files of the database.
Before creating the control file, shut down the DB and start with nomount.
Also, for creating the backup of the control file you can execute the below command, it will create
dump of the control file in trace directory and from there you can modify the control file creation
script.
SQL> ALTER database backup controlfile to trace;

The steps to create control file are as follows:


- Shutdown DB using SQL command
SQL> shutdown (immediate or abort if needed)
- Start the DB with nomount
SQL> startup nomount
- Create control file
SQL> CREATE CONTROL FILE SET DATABASE <DBSID>
LOGFILE GROUP 1 (‘<path_of_logfile1>’, ‘<path_of_logfile2>’),
GROUP 2 (‘<path_of_logfile1>’, ‘<path_of_logfile2>’),
GROUP 3 (‘<path_of_logfile1>’, ‘<path_of_logfile2>’),
RESETLOGS
DATAFILE ‘<path_of_datafile1>.dbf’ SIZE (IN MB),
‘<path_of_datafile2>.dbf’ SIZE (IN MB),
And so on….
MAXLOGFILES <NO>
MAXLOGMEMBERS <NO>
MAZDATAFILES <NO>
ARCHOVELOG;
- Recover the database (if needed)
- Open the database
SQL> ALTER DATABASE OPEN <RESETLOGS>

Note: To find the list of datafiles, logfiles and control files of existing database, execute
below command:
- For Log Files
SQL> SELECT member from V$LOGFILE;

- For Data Files


SQL> SELECT name from V$DATAFILE;
- For Control File
SQL> SELECT VALUE from V$PARAMETER where name = ‘control_files’;

89. List out various options of sapcontrol command.


Answer: You can use sapcontrol with options to start/stop SAP system and also to get other
information as startsap and stopsap command is obsolete.
The sapcontrol executable file is located under SAP hostagent directory
i.e. /usr/sap/hostctrl/exe --- For Unix
And %ProgramFiles%\SAP\hostctrl\exe – For Windows
You can also execute “sapcontrol –help” to find list of detailed options

ASHISH MISHRA
24
(MISHRA.ASHISH0123@GMAIL.COM)
a. To start SAP system
- sapcontrol -nr <instance_number> -function StartSystem
b. To stop SAP system
- sapcontrol -nr <instance_number> -function StopSystem
c. Get system instance list
- sapcontrol -nr <instance_number> -function GetSystemInstanceList
d. Get system process list
- sapcontrol -nr <instance_number> -function GetProcessList
e. Get version information
- sapcontrol -nr <instance_number> -function GetVersionInfo

ASHISH MISHRA
25
(MISHRA.ASHISH0123@GMAIL.COM)

You might also like