How to Check ABAP System Logs & Traces

1. During the starting of SAP system, events are written to log files. These files are extremely important from the point of view of identifying and troubleshooting problems. Logs of the SAP start process are stored in the file system and can be opened and read by the <SID>adm user.

2. Log file in Windows.

• Filepath where logs reside : <Drive>:\usr\sap\<Sys-ID>\DVEBMGS<Sys-Nr>\Work.
• dev_w0 file contains logs about the current work process.
• dev_dispatcher gives information about the dispatcher's activities.
• stderr files report errors with sapstart process.

3. Log file in Unix.

•    The path is typically : /usr/sap/Sys-ID/DVEBMGS<Sys-Nr>/work
•    dev_w0 work process contains information about the latest ABAP work process. But it can happen at time that the other work processes may fail or create errors. If that is the case , one has to identify the work process by its number and open the log file and examine the issue

4. Information about trace files.

During the start process, the STDERR<n> log files are created by the SAP service. The starting processes write to the individual files, depending on the sequence in which they are listed in the start profile. The contents of these log files therefore depends on the individual system setup, and could, for example, be as follows:
• STDERR1: Information about the start process of the database system.
• STDERR2: Information about the start process of the message server.
• STDERR3: Information about the start process of the dispatcher.

How to Specify Update Server Name if Load Balancing is Deactivated

In the standard system, this parameter, rdisp/vbname specifies the name of an update server (set when the update server is created). 

If rdisp/vb_dispatching is set to 0, the updates are only processed by the server in rdisp/vbname. 

If the parameter has not been set correctly (not to an update server), this is reported when the installation check is performed (transaction sick ). You need to specify the name of the update server that is to process the updates if load balancing is deactivated ( rdisp/vb_dispatching = 0 ). 

Go to RZ10, select Instance Profile & Extended Maintenance. Scroll to find & define the paramater rdisp/vbname .

How to Configure & Activate SAP TMS Backup Domain Controller

Configuring the Backup Domain Controller

Prerequisites
In your transport domain, the SAP System that is configured as the domain controller is of special significance. If this SAP System fails, you cannot make changes to the TMS configuration during this time. Therefore if your transport domain contains more than three SAP Systems, we recommend configuring a backup domain controller. If your domain controller fails, the backup controller can assume the function of the domain controller.

Procedure
To configure a backup domain controller:

1. Log onto the SAP System functioning as the transport domain controller.
2. Enter Transaction STMS.
3. Choose Overview > Systems. The system overview appears.
4. Position the cursor on the domain controller.
5. Choose SAP System > Change. The brings you to the screen Change TMS Configuration: System <SID>.
6. In the field Backup, enter the SAP System you want to use as the backup controller of your transport domain.
7. Save your entries and distribute the configuration change.

Note:
• The SAP System that you want to use as the backup controller must have the same release version as the domain controller. Otherwise, configuration information may be lost when changing the transport domain controller.

Activating the Backup Domain Controller

Prerequisites
If your domain controller failed and you have to make changes to the TMS configuration, you can activate the backup controller.

Procedure
To activate the backup domain controller:

1. Log on to the SAP System functioning as the backup domain controller.
2. Enter Transaction STMS.
3. Choose Overview > Systems. The system overview appears.
4. Choose Extras > Activate backup controller.
5. Confirm the prompt.

Result
The backup domain controller is activated as the transport domain controller. The configuration change is distributed to all SAP Systems in the transport domain. The status bar indicates SAP System in which the configuration is being adjusted.

Note:
• When you have activated the backup domain controller, the "old" domain controller is automatically made the "new" backup controller, if it can be accessed.
• As long as the information that the domain controller has changed cannot be distributed to all the SAP Systems of the transport domain, the system overview of the new controller shows that the backup controller activation is still incomplete. You can only change the transport domain configuration if the backup controller is completely activated.

How to test RFC authorization for TMSADM & Reset TMSADM

Symptom

When you try to execute authorization test for TMSADM in transaction code SM59, you see this error, " User TMSADM has no RFC authorization for function group SYST ".

(SM59 ->  TMSADM@<SID>.DOMAIN_<DomainController <SID> -> Test Connection / Remote Logon)

Solution

1. Check the TMSADM authorization profile S_A.TMSADM is already assigned or not. The TMSADM must be check via client 000.

2. Reset the TMSADM user in client 000.

Procedure to reset TMSADM User

If you want to reset user TMSADM to the default, or if the configuration of this user was damaged, then:

1. Log on to the SAP system where you want to reset the TMSADM user. Call transaction STMS. Choose Overview > Systems. The system overview appears. Choose Extras > Reset User TMSADM. The system user TMSADM is regenerated with the default authorizations.

How to Find SAP Objects in Requests & Tasks

This program searches for objects in requests and tasks. You can specify the objects in the selection screen. Some object types used frequently are already listed, you only need to enter the name of the object itself (generically if you want). You can enter other object types yourself. You can restrict the requests/tasks by entering, for example, the number of the request, the owner, date changed, status, or the request type.

1. Execute transaction code SE03, select on Search for Objects in Requests/Tasks and click execute. Select any objects you want to find, put the requests/tasks list and execute again.

2. Tick the box at the left side of request and click on speck icon for details.

3. As the result, you can find the objects short description, program ID, object type and object name.

Additional note:
• Objects often consist of many sub-objects. If you also want to search for all sub-objects, select the option Also search for sub-objects. This option is normally deactivated, since the set of objects can be very large.

How to Troubleshoot Mapping Error: JCO Communication Failure

Sympton

• In transaction code SMQ2, you received "XI Error JCO_COMMUNICATION_FAILURE.MAPPING: Queue error".
• When executing the RFC test connection on AI_RUNTIME_JCOSERVER, AI_VALIDATION_JCOSERVER, LCRSAPRFC and SAPSLDAPI, you received error " ERROR: program AI_RUNTIME_SID not registered".

Cause

At first, go for the logs file. From there, you'll find the specific root cause of the error. Normal caused are,
• Connection broken between ABAP and Java
• Out of memory / overload
• SAPJSF user

Solution

• Restart the XI Java engine
• Delete & recreate the JCO RFC destinations (need to restart the Java engine)
• Check the SAPJSF user authorizations, validity and password.

How to Delete Short Dumps from the SNAP Table

There are different ways of deleting short dumps from the SNAP table. However, before you delete them, you must analyze the cause of the short dump using transaction code ST22. If the issue related to short dumps is resolved, you can proceed to remove the short dumps before they all filling up the hard disk of your system. Here are the several ways to delete the short dumps:

1. Dump analysis: Reorganization
• Go to transaction code ST22. Choose 'Reorganize'. You can now select all short dumps older than n days for deletion.
CAUTION: If a large amount of records are deleted simultaneously during the reorganization, ORACLE error ora1562 'failed to extend rollback segment …' may occur. In this case, refer to error Note 6328.

2. Drop and recreate the SNAP table
• With the database utility transaction code SE14, you can drop and recreate the SNAP table.
CAUTION: When you do this, ALL short dumps are deleted.

3. Reorganization program RSSNAPDL
• To avoid database problems, this program deletes old short dumps gradually from the SNAP table unless they are selected for retention. With standard setting all short dumps that are older than 7 days and that are not flagged are deleted. Since this program occupies the database when large datasets are processed, it should be scheduled to run overnight.

4. The SNAP is also automatically reorganized. With each short dump that occurs in the dialog box (the dump is displayed as soon as it occurs), a maximum of 20 short dumps are deleted from the SNAP that are older than 7 days. In normal production operation this reorganization should be sufficient.