Saturday, 24 August 2013

How to Import SAP Transport Request at OS Level

1. Make sure the transport request is released from the source system. Log onto the target systemas <SID>adm.
2. To add the transport request to the buffer (Single command line).
tp addtobuffer DEV12345 QAS Client=000
3. To import the transport request (Single command line).
tp pf=/usr/sap/trans/bin/TP_DOMAIN_<DOMAIN_SID>.PFL
tp pf=/usr/sap/trans/bin/TP_DOMAIN_DEV.PFL
import DEV12345 QAS U128 client=000

Tuesday, 20 August 2013

What is the main difference between remote client copy and client export in SAP

Remote Client copy :-
This is one step process
RFC connection is required. 
CC can be used with multiple parallel processes
Remote CC is better if you have small data to be copied. 
Remote CC might be little bit slower than the export due to its network constraints. 
Need to check Network, Database ( generation of archive logs, table space usage ) through out the CC.  


Export-Import :-
This is 3 step process ( export- import-post processing).
RFC connection is not required between systems. 
Multiple parallel processes can not be used. 
Export-import is generally used for copying larger amount of data. 
Export-import is relatively faster than the remote CC.
Need to check DB constraints at the import process.

SAP BASIS OS Level (UNIX) Commands

dpmon d
Dispatcher queue monitor
Sapdba (up to SAP R/3 -4.7)/ brtools
database administration
Running work process
ps -eaf|grep dw
process overview
ps -eaf|grep ora
check oracle service is running
Ps –eaf | grep dw kill -9
Kill work process
msmon pf=profile path name=sid
to check the message server status
gwmon pf=profile path nr=num
to check the gateway status
Ps –eaf | grep lsnrctl
Listener status
Rslgview pf =-r –ft | pg
System logs
Disp + work –v
to check the version of r3 kernel
R3trans –d ,tnsping
Checking the connection with database
Df –k
File system monitor
Du –k
Display all directories and size of current directory
“/as sysdba” (new versions)
SQL prompt and database connection
Saplicence  -get
to get hardware key
saplicense -install
to install license
sappfpar all pf=profile path
display all profile parameters
sappfpar check path=profile path
checks the required space for memory
to check the available space for heap and swap memory
Remote system login
telnet <ipaddress><dispatcherportnum>
to check the remote sap system is up and running
file transfer protocol
remote copy of files
Start/stop sap
Start / stop Sap instance
check destination host reachable
check connection between server and a client by transferring packets
check the configuration of system
Ps -aef
Processes status
lsps -a
Swap space

Monday, 19 August 2013

Kernel Upgrade Interview Questions

1)What is your present patch level?
A: 710

2)From which patch level did you upgrade it?
A: 720

3) Why do you go for kernel patch upgrade?
A: we usually do it when there is a problem with the existing kernel files &
When we go for latest functionality like support packs implementation or add-ons or plug-in implementation.
When sap recommends in early watch alerts we go for the kernel patch upgrade.

4)What are the files do you downloaded from service market place?
A: 1) sapexe file (db independent) & sapexedb file (db dependent)……

5)How many ways do you know the current patch level?
A: At os level -> login with sidadm and use the command disp+work
At sap level -> system -> status.

6)What are the problems do you faced while kernel patch upgrade?
PROBLEM 1:we generally forgot about file permissions
PROBLEM2: we should stop saposcol & listener otherwise it give problems.

7)What are the prerequisites for kernel patch upgrade?
A: we should take the backup of old kernel & check for the existing patch version to download latest version.

8)how do you uncar the downloaded car files?
A: By using command SAPCAR -xvf 

9)Why do you overwrite the old kernel instead of replace?
A: Because latest kernel consist only updated kernel files only so to use the remaining files we use to overwrite the kernel.

10)What are the post requisites for kernel patch upgrade and why?
A: run the scripts for the permissions in non windows environment & check for the kernel patch version whether it is updated or not?

11)What is default kernel location
A: Usually it is located in: </usr/sap/SID/SYS/exe/<uc or nuc>/<system>. it might also be located in /usr/sap/SID/SYS/exe/run 


Tuesday, 13 August 2013


  1. Tcode SHD0
  2. Enter the follow

    3. Button is invisible due to this variant. Deactivated this variant and transport button will visible again 

Wednesday, 7 August 2013

Common Background Job Errors & Troubleshooting

1. User and password Issues (Authentication/ Authorization) user lock, user id expiry, password change, lack of roles etc.
2. File system problems: BTC reads from the file system to update the database. File not opened, or corrupted, file sharing issues, file came with different characters, file not found as well.
3. Variants are not properly defined.
4. Dead locks issue (Lock mechanism congested)
5. Update mechanism failed
6. Table space over flow (ORA-1653; ORA-1654)
7. Table space max extent reached (ORA-1631; ORA-1632)
8. Archive struck (ORA-255; ORA-272)
9. The memory is not sufficient and errors
(No Roll Area, PXA (Buffer), Page Errors)
10. Problem in the program and inputs (Indefinite loops like 1/0)
11. Dependent jobs/ events failure
12. Target systems are not available to process the jobs.

SAP Common Transport Errors & Troubleshooting

1. The log for import post processing contains messages that indicate that objects are missing

Solution- Look for the missing objects on transport requests using the tools of the Transport Organizer (transaction SE03).
If the missing object is on another request, import it first.
If the missing object is not on a request, collect it and the incorrect object on a request and transport it. Do not import the original request again. Create a merge transport for the consolidation if necessary.

2. Objects are deleted during import postprocessing although they should have been imported

Solution- The object was transported as a deletion.
You can see this from the piece list of the request in that the objects to be deleted are marked with a deletion indicator.
Make sure that the object to be transported is active. When delivering BI Content, make sure that the delivery or shadow version exists

The request was included in a mass import and the object is in more than one request
Import the requests individually or create a merge transport by merging the object lists of the requests.

3. Objects were not activated or not found (especially process chains and DataSources)

Solution- The client-dependent parts could not be activated because the transport destination is incorrect or missing.
Maintain the correct transport destination:

4. troubleshoot when a transport is running for unusually long duration and not getting completed or terminated

Solution- Go to transaction STMS_IMPORT and identify the transport which is running since a long duration.

In the below screenshot, transport with the truck symbol is the long running one

Issue could be due to following reasons :

1)    Non availability of space to perform the operation (i.e filesystem or tablespace is 100% full)

Solution :

  • Check out if any of the filesystems (like sapmnt, oraarch etc) of the Central Instance, Database and  application servers  is 100% full. If so, please add necessary space, which resolves the issue automatically and completes the import of transport.

  • Also, check out tablespaces fill levels. If autoextend is off and tablespace is 100% full then add sufficient datafiles, which resolves the issue

2)   RD* jobs are not running in SAP system

Solution :

Check out in SM37 whether RDD* jobs(RDDIMPDP, RDDIC3L, RDDVERSL etc) are running or not. If not, please make sure they are scheduled and perform the import of the transport again

3)   Update got deactivated

Solution :

Checkout in SM13 whether update is active or not. If it is not active, activate it and import the Transported to Production System.

4)   There are no free background workprocesses

Solution :

Check in SM50 whether all background workprocesses are in running status. If so, you will need to wait for the free background workprocess to run RDD* jobs to complete the  import of the transport. To avoid this issue in future you may increase the number of background workprocesses


Transport is not getting terminated. How to do terminate?

1) If you are unable to terminate a transport which is running, goto SM50 and identify the pid of the transport process. Try to cancel the process---> with core or without core

2) If it is not getting terminated from SAP level, then goto Oslevel and kill.

Command for the same in AIX or HP-UX is  kill -9 <PID>  

What are common transport errors?

Return code (4) indicates imported ended with warning.
1. Generation of programs and screens
2. Columns missing and Rows missing.

Return code (8) indicates not imported ended with error
1. Syntax error.
2. Program generation error.
3. Dictionary activation error.
4. Method execution error.
Return code (12) indicates import is cancelled.
1. Import is cancelled due to object missing.
2. Objects are not active.
3. Program terminated due to job? RDDEXECL? is not
Return code (16) indicates import is cancelled.
1. Import cancelled due to system down while importing.
2. Import cancelled due to user expires whileimporting
3. Import cancelled due to insufficient roles.