You get an error " Client is not available in this system" when trying to login to the SAP system.
Login to the SAP system using client 000. Execute transaction code SCC4 to check all the client list that are available in the system.
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.
This job will start as soon as possible, subject to job priority and the availability of background work processes. Users granted the appropriate authorizations for background processing can have their jobs released automatically as soon as they are scheduled, without special attention from a system administrator.
The job will start at the date and time specified, subject to job priority and the availability of background work processes. You can further define a time frame in which the job will run by specifying a time later than which a job will not run. One use of this feature is to prevent periodic jobs from running when they should not. For example, a routine clean-up job scheduled to run only at night is delayed. By defining a start-time window, you will keep this job from being started during the day, when dialog users are active and fewer system resources are available.
The job will start on the completion of the specified job. You can specify whether the preceding job must complete successfully or not. Jobs scheduled to start when a preceding job completes cannot be specified as "Periodic jobs".
The job is triggered by the specified event, descriptions of which follow. This start condition lets you define a sequence of individual jobs to model complex activities in your system. For example, a data transfer program that generates a batch-input session can, once the session has been completely generated, use an event to trigger another job that processes the session.
The job will start when the specified operation mode becomes active in the SAP System.
The job will start on the specified day of the month (for example, the third to last day of the month)
By specifying the appropriate SAP factory calendar, your scheduling can accommodate the occurrence of holidays or other non-workdays. You can further specify how the job should be handled if the start day lands on a non-working day. For example, you can have the job started on the workday before or after the actual scheduled date, or allow the job run in anyway, or have the job be skipped on that day entirely. Verify that the calendar you choose has been correctly defined. If, for example, the calendar ends with the current year and your job is to be started next year, the job will terminate abnormally. If a calendar problem occurs, you can review system's error messages in the job log of the terminated job.
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.
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.
The following describes how the buffer quality of the SAP buffers should be in a SAP System with good performance.
The qualities of the Repository buffers can reach 99.9% in a system that has been running for a few days. If the buffer quality is less than 95%, you should investigate the situation further. Check the:
• Available freespace
• Available directories
• Object swaps
• Buffer history
The program buffer contains the generated ABAP programs (load). Critical effects on the program buffer is transports. Every time a new source is transported into the system using the R3trans program, all entries in the program buffer are invalidated, and all other buffers are cleared (equivalent to the $SYNC command). Unlike the other buffers, the program buffer is not empty after transport, but is filled with invalid programs. Therefore, it is better to execute as few transports as possible and to collect data to do several transports at once.
The quality should also be above 95%. Also check available freespace and the freespace history.
The quality of the single key buffer increases very slowly from system startup. Therefore, bad quality (< 90%) should only be of concern if there is no freespace left in the buffer. The quality of the generic key buffer should be greater than 95% and can be up to 99%.
Requests after the end mark are not imported during the next import. The end mark is automatically deleted only when the next import has completely ended. Afterwards, the requests can be imported.
1. Choose the transport request. Go to Queue > Move end mark.
or
2. Open the import queue (the import queue may accidentally lock by user). Click on the lock icon (next to lorry icon).
Note:
You can check who lock the import queue via SLOG file (/usr/sap/trans/log)
STOP SET STOPMARK SID 1234 ITSITI DHIYA |
START REMOVE STOPMARK SID 2345 ITSITI DHIYA |
STOP REMOVE STOPMARK SID 5678 ITSITI DHIYA |
