SAP BASIS Interview Questions and Answers.
SAP BASIS Interview Questions and Answers.
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
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.
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.
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
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.
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
ASHISH MISHRA
5
(MISHRA.ASHISH0123@GMAIL.COM)
x. Select Yes for Trust Relationship
xi. Save
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
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.
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
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
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
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;
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.
ASHISH MISHRA
10
(MISHRA.ASHISH0123@GMAIL.COM)
f. If the server node has some issue, check dev_server0, std_server0, jvm_server0 log files
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”
Refresh activity:
Post-refresh activity:
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
Visual Admin
Note: Visual Admin is replaced by NWA (NetWeaver Administration) for AS JAVA >=7.1
NWA is online browser-based administration tool for AS JAVA.
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.
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.
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.
➢ 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
➢ 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.
➢ 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.
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.
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.
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
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:
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
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
JAVA System:
a) HTTP Port: 5<NN>00
b) HTTPS Port: 5<NN>01
c) P4 Port: 5<NN>04
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.
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
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.
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
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;
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)