SAP - deleting entries from SAP Table

Note : This will EMPTY SAP Table (be careful)

- go to SE14 entry TABLE NAME YOU WANT TO EMPTY.. and click on EDIT button.

Now select "Delete data" (1)  and than "activate and adjust database" (2) option .
if it is large table " use background option " (3) .

SAP -- Heap Memory Parameter Changes while system is running

Follow below procedure if you want to change Heap memory while SAP System is up and running.
this is sometime required if you running short of memory.
-- Execute Report

              --- go to "se38"
              --- run report "RSMEMORY"

now Change parameters and click on copy.

Note: Changes will be lost after system restart.

LOAD_PROGRAM_LOST dump in SAP

Solution is to clear buffer on Dialog Instance or restart Dialog which has the issue.

Causes (explanation on error ) 

• Before you can execute an ABAP program,  you must make sure that the program load is loaded in the program buffer (PXA).
• This is locked when you execute a program load so that it cannot be displaced from the buffer.
• Since the program buffer is limited in size, the program locks may not be retained for longer wait times (for example, user interaction). Therefore, all previously set locks are released within the rollout.
• If the system works intensively on the application server, the program load may be displaced from the buffer after a short time.
• If you now change the program (because of a transport, for example) before the application continues, the database detects that the program has changed (the total time stamp is newer) when you reload the program (RELOAD).
• To avoid inconsistencies when executing the program (the program may have changed so much that follow-on errors occur), the system triggers the short dump " LOAD_PROGRAM LOST.
• You must not change the terminated program itself.
• Changing a dependent object can also cause this termination.
• You can use the report RSDEPEND to determine when the program was last generated and due to which change the total time stamp was set. This may be the case, for example, due to change to the DDIC types or program includes that are used.
• In the result list of RSDEPEND, search for objects that have the same or similar time stamp to the total time stamp. You can quite easily find the trigger in this way. These dependent objects were then changed by a transport of by a direct change in the system.

• If the short dump occurs regularly, you should initiate measures to ensure that its occurrence is less likely.
• These are
• Increase the program buffer so that no more swaps occur.
• Make sure that you import transports only when there is no load or a low load. Particularly in a production system.