Error analysis and correction in the databases and the SAP system
Time window for batch jobs becomes smaller and environments more complex
Maintaining the availability of critical business processes not only requires a high-quality infrastructure, but also places equally high demands on the management and operation of the underlying SAP NetWeaver and SAP HANA platforms due to their high complexity. These platforms are often referred to as SAP Basis.
Tasks such as the update of components, the insertion of security updates or monitoring should be further automated. It is recommended to use only one automation tool (SAP Solution Manager or SAP LVM). Custom solutions and scripts should not be used or replaced with standard tools if possible, because otherwise different script languages and script versions will have to be managed, resulting in a lot of maintenance. Standardised SAP scripts are welcome here. A useful definition of thresholds, for example on the basis of historical system behaviour, must also be defined for monitoring.
Involving business departments in job planning
The Advanced Memory thus contains mainly user contexts of different work processes, if these cannot be loaded completely into the roll area. Since the storage area is accessible for all work processes, the work processes can also access external user contexts that lie here. In addition, the Advanced Memory contains a global area where data can be stored independently of user contexts. The extended memory size is determined by the values of em/initial_size_MB and em/global_area_MB. The first parameter determines the size of the storage area in which user contexts can be stored, and the second determines the size of the global area. Parameters for Private Storage Last but not least, there is the private storage, which is only used when the user context of a work process has used up all the other storage areas available to it, i.e. its share of the extended memory and its rolling area. In this case, the workprocess goes into PRIV mode. A workprocess in private mode is bound to its current user context and will not become free for other tasks until the current request is completed. If it has used up all the private memory allocated to it, the workprocess will then be restarted and the memory released. This behaviour is controlled with the abap/heaplimit parameter. At times, the user context may exceed the value of abap/heaplimit. The parameters abap/heap_area_total, abap/heap_area_dia and abap/heap_area_nondia define an upper limit for private storage. The abap/heap_area_total parameter defines how much private storage all workprocesses can use in total. The parameters abap/heap_area_dia and abap/heap_area_nondia, on the other hand, determine how much private storage a single (non-)dialogue workprocess can use.
The dataowner should be the adm of the target system, which you can change (in the Unix console) with "chown adm K12345.DEV" (respectively R12345.DEV for the data file). To change the access permissions, you can use the command "chmod 664 K12345.DEV". Attach transport jobs in the SAP system Once this has been done, you can attach the transport orders in your SAP system to the import queue. This is done by using the STMS -> Import Overview (F5) to display the import queues. Select the import queue of the target system with a double click. After that, you will receive a pop-up under "Additions"->"More orders"->"Attach", which you can use to attach the transport orders to the import queue. In the pop-up you have to name the exact transport order. The correct name for this is as follows: The first three characters are the file extension of the two files you copied into the transport directory. The last characters consist of the file name of the cofiles file. In our example transport the transport would be called "DEVK12345" (deriving from the cofiles file K12345.DEV) This should now return a positive message from SAP and the transport is attached to the import queue. Now you can import this transport into the system just like any ordinary transport order. Step-by-step Summary Copy Cofiles/data file to transport directory Normally /usr/sap/trans, if not —> AL11 -> DIR_TRANS Customise file owners and permissions chown adm chmod 664 In SAP system: STMS -> Import Overview -> Select Import Queue -> Additions -> Additional Jobs -> Attach Enter Transport Jobs ().
With "Shortcut for SAP Systems" a tool is available that greatly facilitates some tasks in the SAP basis.
You would like to know more about what is happening on your SAP systems - then I recommend that you take a closer look at the Solution Manager Usage Procedure Logging (UPL) functionality.
Then click Run or alternatively press F8 View of the DBA Cockpit Invoke the input query and drop the first SQL query View the results of a query to query the users of a system.