We have added search box. Key in SAP issue keyword to search
TopBottom

Announcement: wanna exchange links? contact me at sapchatroom@gmail.com.
Showing posts with label Allocation. Show all posts
Showing posts with label Allocation. Show all posts

Basis Displaying the Technical View: Method Allocation

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Use

The individual monitoring tree elements (MTEs) of the Alert Monitor are assigned methods. These methods determine the data collection of the MTEs (data collection methods) and the possible reactions to an alert in the MTE (auto-reaction and analysis methods). You can find out the assigned methods by selecting an MTE and choosing Properties. This method is very time-consuming for obtaining an overview of the assigned methods for the MTEs of an entire monitor. The technical view Method Allocation exists as an alternative for this purpose. This view displays the method assignments for the MTEs of the entire monitor:

· Assigned data collection method: If the MTE is assigned an active data supplier, the system will display in the corresponding column, as the active data suppliers are not defined in the monitoring architecture

· Assigned auto-reaction method

· Assigned analysis method

Note

· The nodes are always colored green in the technical view Method Allocation; as it contains no alert information.

· Summary nodes or monitoring objects can always be assigned methods; these assignments only take effect for the subordinate monitoring attributes, which can inherit their method assignment from the superordinate nodes.

· If no analysis or auto-reaction method is assigned to the MTE, is displayed in the corresponding column here.

Procedure

To activate the Central Method Allocation technical view, follow the procedure below:

...

1. Choose CCMS ® Control/Monitoring ® Alert Monitor, or call transaction RZ20.

2. Expand the monitor set that contains the monitor that you require, and choose Load Monitor.

3. Choose Views ® Method Allocation. The alert tree now no longer displays the alert status and reported values, but information about the methods assigned to the MTEs of the monitor.

This graphic is explained in the accompanying text



Keyword: BASIS
Title : Basis Displaying the Technical View: Method Allocation

Memory Allocation Problems under OSF/1 from DEC

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Symptom

Under the operating system OSF/1 from Digital Equipment Corporation, and under UNIX operating systems (64-bit), R/3 processes with the following error message are canceled: mprotect failed, rc = 12 error code ENOMEN (not enough core)

Corrective action

The cause of the problem may be that the value of the OSF/1 kernel parameter VPAGEMAX has not been increased. You must increase this parameter value so that the SAP memory management system can be used.

You can find detailed information on increasing the parameter VPAGEMAX under OSF/1 in the R/3 installation guide OS Dependencies. You receive this document with all R/3 installation and upgrade packages.

You can find additional information on VPAGEMAX in the man-page mprotect under OSF/1, return code ENOMEN.

The value for VPAGEMAX is calculated in the following way: The sum of values for all R/3 system profile parameters em/initial_size_MB on all R/3 application servers of the host system divided by its page size:

S (initial_size_MB of all R/3 servers)/page size



Keyword: BASIS
Title : Memory Allocation Problems under OSF/1 from DEC

ztta/roll_first: Initial Allocation Size from the Roll Area

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Use

This is the amount of roll memory allocated to a dialog work process before R/3 Extended Memory is allocated.

See Allocating Memory for User Contexts

Activities

Unit: Bytes

Default value: 1000000 (1 MB)

Recommended value: 1 (1 byte)

Under IBM AS/400: 167731120 (16 MB, value from ztta/roll_area).

One (1) byte means that only one small amount of memory specifically for that system is allocated and then goes in to the Extended Memory. If there is not a lot of Extended Memory available, a higher value (1 MB or higher) is useful (see Recognizing and Correcting Problems).

Changes: Under IBM AS/400, only SAP is allowed to change this parameter. Under UNIX and Microsoft Windows, you can only change this parameter value in accordance with the configuration examples (Contents button) or for Windows NT in accordance with the information in Maximum Use of Extended Memory.



Keyword: BASIS
Title : ztta/roll_first: Initial Allocation Size from the Roll Area

T r a n s l a t e to your language