SAP How to Reset Buffers in Sap

You should run the following in SAP command field.

Note: Resetting of the buffers could change the performance of the entire system

/$DYNP - To reset the screen buffer of the application server
/$SYNC - This command resets the buffers of the application server
/$CUA - This resets the CUA buffer of the application server
/$TAB - This resets the TABLE buffers of the application server
/$NAM - To reset the nametab buffer of the application server

SAP How to exclude a table in client copy

If you want to exclude a table x from copying in client copy run report RSCCEXPT
Goto transaction SA38 , enter the report name and execute. You will see the output screen as

Enter the table you want to exclude and save it

SAP Transaction DB05 Performance Analysis

Transaction DB05 is can:

• Determine the cardinality of column combinations. This is often an easy way to answer the question as to which the adding of another column to the index actually increases the selectivity of the index.
• Display unequal distributions in the column values. It is displayed how many values there are for the individual column values or combinations of column values.

Transaction DB05 is very often used before recommending multiple indexes from a combination of rather unselective columns, if the corresponding table is not too large.

Warning This procedure is not suitable for large tables because the entire table is read. Depending on the size of the table this is very expensive.

In transaction DB05 you enter the table name and description of the columns to be analyzed.

In the upper part, the result returns the table size - this value is only correct if the primary key columns have been selected - (Requested bytes to be buffered 100%), the number of records of the table (Total number of rows) and the SAP buffer status (Current buffering mode).
The bottom table shows how many distinct values the combinations of analyzed columns have and how many records have to be read for the different combinations. Distinct values: Number of different values for an index (in the example below there are two values for the client and 418 different values for the combination of client and name_last. Number of areas that are specified by the generic key and contain the given number of rows:
Number of records that would have to be read for a certain value combination of index columns (in our example 1 to 10 records would have to be read for 415 of the value combinations, but there is also one value combination each for which 11 to 100, 101 to 1000, and 1001 to 10000 records would have to be read).

If an additional column is added to the index, you can check the resulting selectivity. In our example, adding the birthdt column to the index does not increase the selectivity! Extending the index would not result in an improvement.

SAP Maximum hold time for work processes in DEBUG mode

This useful parameter could find out for basis admin to reduce debug possibility for some "power users"


Maximum hold time for work processes in DEBUG mode

rdisp/max_debug_lazy_time =1 (sec)

SAP Transports hang during background steps

1. When you export a transport request in the Workbench or the Customizing organizer (Transaction SE01, SE09, SE10):

 A dialog box displays a message that the objects are exported. However, the export does not close even after a longer waiting period. The request has the status "open" when you go to the transport log display, and you receive the message that no logs were found or that the ADO (application-defined object) export has not yet been executed.

2. When you import one or more transport requests on the operating system level with tp:

             tp does not close even after a long waiting period.

In the section Solution, you find a description on how the symptoms vary in detail for the different error scenarios, and the suitable solution for each case.
Examine the SLOG file in the transport directory first and compare your error scenario with the situations described here before you consider one of the solutions.
Other terms
RDDDIC0L RDDEXECL RDDMASGL RDDDIC1L RDDDIS0L RDDGENBB RDDGEN0L  RDDVERSL RDDVERSE tp TRBAT TRJOB  RDDDIC3L batchjob looping
Reason and Prerequisites
This problem is due to various causes.
Solution

1. Symptom:

a) The last line in the SLOG file that starts with "START" or "STOP" has the form
START tp_getprots ......

b) After the above line, you find in the SLOG file, and in addition to further messages, a line of the form:
Background job not running properly. Function: ... Jobcount: ... Status: S
This line can occur repeatedly.

              
              Solution:
              In this case, refer to Note 26966.

2. Symptom:

a) The last line in the SLOG file that starts with "START" or "STOP" has the form
START tp_getprot.......

b) If you log on as the DDIC user in the client 000 of the SAP System and start the RDDIMPDP report, the system generates error message PU029:

                       Header ...: job ... is running
                       
              Solution:
              Using transaction SM37 (job overview), check whether all jobs displayed as "Active" are actually active.

a) Log on as the DDIC user to client 000.

b) Call transaction SM37.

c) Choose the selections:

                    Job name: RDD*
                    User: DDIC
                    Selection date: leave these fields empty
                    Only jobs with the status 'Active'.

d) For the resulting list, check the job status for each entry. You will find this function under the option "Job".

e) If you find a job that does not run even though it is displayed as "Active" in the status, reset this job to "Terminated" as suggested.

f) If the transport control program (tp) continued to run during these examinations, the transport control program will continue its work after this correction. Otherwise, start the transport control program with the same parameters as during the last call for which you noticed hanging transports. If you do not know the parameters or are not sure, start the following call:

tp getprots <SID>

3. Symptom:

a) The last line in the SLOG file that starts with "START" or "STOP" has the form
START tp_getprot.......

b) After the above line, you find in the SLOG file, and in addition to further messages, a line of the form:
Background job not running properly. Function: ... Jobcount: ... Status: Y
This line can occur repeatedly.

              
              Solution:
              Log on to the SAP system as the DDIC user. Call transaction SM37. Enter the following search criteria:
                    Job name: RDD*
                    User: DDIC
                    Selection date: leave these fields empty
                    Only jobs with status "Ready".
              If an entry is found, position the cursor on the job name and use the menu item "Job -> Display" and on the following screen the menu item "Process -> Job details". On the following screen, you find the ID number of the job. Compare this number to the number which is referred to as "Jobcount" in the above SLOG message. (If several jobs were selected, examine all jobs this way). If the ID number should match the Jobcount entered, an unexpected status is contained in the batch system.
              This status could indicate a permanent error in the batch system. Refer to Note: 37104.
              If the unexpected status of the entire batch system was only temporary, then you can solve the problem for the transport as follows:

a) To maintain the TRJOB table, use Transaction SM31.

b) Select the entry which matches the above SLOG message concerning the value "Function" and "Jobcount". Delete this entry.

c) If the transport control program continued running during these examinations and did not make any progress due to the temporary problem in the batch system, the transport control program (tp) will continue its work as soon as you have corrected the above error. Otherwise, start the transport control program with the same parameters as during the last call for which you noticed hanging transports. If you do not know the parameters or are not sure, start the following call:

tp getprots <SID>

4. Symptom:

a) The last line in the SLOG file that starts with "START" or "STOP" has the form
START tp_getprot.......

b) After the above line, you find in the SLOG file, and in addition to further messages, a line of the form:
Background job not running properly. Function: ... Jobcount: ... Status: P
This line can occur repeatedly.

              
              Solution:

a) Check the authorizations of the DDIC user in client 000 and in the client to which you want to import the transport. Logon to both clients as a DDIC user and execute the RDDNEWPP report (transaction SA38 or SE38). If the report does not end with the success message:

PU006 Background job ... was successfully ... scheduled in the client.

the authorizations of the DDIC user must then be enhanced in the respective client.

b) To do this, logon to the respective client under a user that is authorized for user maintenance. Change the authorizations of the DDIC user in user maintenance (Transaction SU01). Give the DDIC user the authorization for scheduling and starting background jobs. We deliver the authorization S_BTCH_ALL and S_BTCH_ADM (depending on the release) for this.

              Afterwards, apply the following correction steps in Release 3.0E or earlier:

c) Log on to the SAP system as the DDIC user. Call transaction SM37. Enter the following search criteria:

                    Job name: RDD*
                    User: DDIC
                    Selection date: leave these fields empty
                    Only jobs with statuses "Scheduled".

d) If an entry is found, position the cursor on the job name, and use the menu item "Job -> Display" and on the following screen the menu item "Process -> Job details". On the following screen, you find the ID number of the job. Compare this number to the number which is referred to as "Jobcount" in the above SLOG message. (If several jobs were selected, examine all jobs this way). If the ID number matches the specified job count, delete this job.

e) Position the cursor in the list of the selected jobs on the job to be deleted, and choose "Job ->Delete".

f) If the transport control program (tp) continued to run during these examinations, the transport control program will continue its work after this correction. Otherwise, start the transport control program with the same parameters as during the last call for which you noticed hanging transports. If you do not know the parameters or are not sure, start the following call:

tp getprots <SID>

5. Symptom:

a) The last line in the SLOG file that starts with "START" or "STOP" has the form
START tp_getprot.......

b) If you log on as the DDIC user in client 000 of the SAP System and start the RDDIMPDP report, the system generates the following message (PU014):

                       Header ...: No actions currently required
                       
              Solution:

a) Log on as the DDIC user to client 000.

b) To maintain the TRBAT table, use Transaction SM31.

c) Check whether you can find the following entries in the table:

                    An entry, in the "Request" field that has the value "HEADER", and that the "Return code" field has the value "F".
                    At least one additional entry that has the same value as the first entry in the field "Fct." and that has the value "8888" or "9999" in the "Return code" field.

d) For the first entry ("HEADER"), change the value in the "Return code" field from "F" to "B", and save this change.

e) If the transport control program (tp) continued to run during these examinations, the transport control program will continue its work after this correction. Otherwise, start the transport control program with the same parameters as during the last call for which you noticed hanging transports. If you do not know the parameters or are not sure, start the following call:

tp getprots <SID>

SAP profiles understanding

SAP profiles are operating system files that contain instance setup information. The profiles are stored under /usr/sap/SID/SYS/profile</strong> directory.

The following three types of parameter files are defined in SAP:

•    Default  -DEFAULT
•    Start profile -  START_DVEBMGS00_<hostname>
•    Instance profile - SID_DVEBMGS00_<hostname>

These parameters are used for setting the system parameters. These parameters can be maintained by the transaction <strong>‘RZ10’ </strong>or through the menu:

CCMS -Configuration -Profile maintenance

For creating a new profile:

1. Execute transaction  ‘RZ10’ 







2. Specify the name of the profile that is to be created and choose Profile -&gt; Create. The  system creates the version number automatically.

3. Enter a short description of the profile, the filename into which the profile should be activated, a reference server and the profile type. Then choose Copy.

4. You can maintain parameters and their values by flagging either Basic or Extended maintenance and choosing Maintain.

5. Once the changes are made, choose Copy to return to the initial screen of Transaction RZ10.

6. Then  check, save and activate the profile that has been created

7. After this the instance has to be restarted if parameter is not dynamically changable.

Exporting volumes with disk groups on VxVm

How to export and import disk group from one host to other by using Veritas Volume manager?
 
1.Check disk group which you want to export :

vxdisk list | grep mydg


2. Unmount file system which resides on the target disk.

 umount /software

3.Unshare all shares from this file systrem if they exist.

unshare 
  
4. For SAN presented disks represent LUN to target host and rescan disks

5. On the source host make deport of disk group  

 vxdg deport  mydg

6.On the target host make import of disk group 

 vxdg nimport mydg


7. Rescan disks 

 vxdisk scandisks

8. Check that your disk group exist on target host

vxdisk list 

DEVICE       TYPE            DISK         GROUP        STATUS
disk513    uto:cdsdisk    disk513      mydg                 online

9. Restart and resynchronize the disk group:


vxrecover -sn vol_name 

10. Add vx disk device file  and mount dir  ( i.e. /dev/vx/dsk/mydg/lvol1  /software ) to etc/fstab  

11. Remount your fs

mount /software 

SAP Setting up client specific system route STMS

You can use Extended Transport Control.

Extended Transport Control is another way to set up the Transport Route so that the route is system and CLIENT specific. 

In other words, when you release a change request in DEV Client 0XX it will not only automatically be added to the Import Queue for QAS but also 0X1, 0X2, of DEV. 

To set this up requires the steps below: 

1)   Open the file TP_DOMAIN_DEV.PFL (located on your transport domain controller such as the DEV box. The file will be in usrsaptrans/bin) 

Edit with notepad for each parameter on each system: 

DEV/CTC = 0 

Change to =1 

2)   Next you need to create Target Group before creating the transport route. 

Create a Target Group: 
Access the initial screen of the graphical or the hierarchical editor in change mode. STMS > Overview > Transport Routes (the default editor will appear, either Hierarchical or Graphical, to change the default editor : STMS > Extras > Settings > Transport Routes. You can also switch to one or the other from Goto > Graphical Editor.) 

> Configuration > Display Change > (or change icon or F5) 

Edit > Transport Target Groups > Create 

In the dialog box, Create Target Group: 
Enter a name for the target group /GR_QA/ (The name must begin and end with a forward slash /) 

...and a description Targets for Consolidation route 

Choose "Insert line" 
Enter the required target system/client combinations 
Use a separate line for each client. 

Example: 
Target System 
Target Client 
Client Name 

DEV 
0X1 
Sandbox 

DEV 
0X2 
Testing 

QAS 
0XX 
Quality Assurance System 

The idea is that we want to include the clients that will get an addition to their import queue when we release a change request from DEV. 

Choose Transfer 
Now you have to change the transport route to include the Target Group you created. 
STMS > Overview > Transport Routes > F5 (change mode) Edit > Transport Routes > Delete 
Now create a Transport Route with Extented Transport Control: 

STMS > Overview > Transport Routes > F5 (change mode) Edit > Transport Routes > Create > Extended Transport Control icon at lower left of dialog box. > Consolidation route, enter integration system and transport layer. In Target system/client enter the SID of either an R/3 System and a client or an existing Target Group. 

Each System must be specified by System and Client. The Target Group can be used for the consolidation system. 

Distribute and activate the changes as usual by choosing Configuration > Distribute and activate 

NOTE: After you set up Extended Transport Control there might be requests in an import queue that will show a red status in the CTL column. This is because these change requests need a client specified before they can be imported. These are old requests that were already in the queue. 

From Import Queue Screen Mark the change request 

Choose Request > Target Client > Set 

Enter the Target Client ID and choose Enter. 

To change a target client before starting an import: 
Import Queue Screen > mark Change request > target client > change > enter target client id and choose enter.

Now you are ready to set the automatic transport/import job

Goto TCODE STMS -> Overview Menu select Import -> Double click on the SID -> Click on Import all Requests truck -> Select At Start Time -> Enter a time and date -> Press F4 and select the period the job has to run -> Now the background job i scheduled and imports will be done in periodic intervals as mentioned in the job


if you wish to set up automatic transport only for a specific client (and not the entire queue containing requests for other clients), you just need to set a filter on column “client” before clicking on the Import all Requests truck.