SAP Library - Find your answers

Yes! You can trigger an operation mode switch from a program that you have written yourself using a function module (RZL_PERFORM_BA_SWITCH).

It's possible via transaction RZ03.
Choose the instance and use Control -> Switch Operation Mode.

How do you find that an operation mode switch occurred? There are many ways

1) Go to sm50. If the no of dialog work processes or background work processes changes then a operation mode switch took place.

2) Go to transaction sm63. Here you can see the time when the operation mode is set. You can guess when the operation mode switch occurs.

3) Go to transaction RZ04, here you can see the list of operation modes and their time. You can guess that from here

4) Go to transaction rz03 , here you can see the current operation mode in which the server is running.

5) Call transaction Code sm62. Then view system events. If there is an event called SAP_OPMODE_SWITCH then operation mode switch occurred at that time. If you click on activity log you can see the time and date when the event was triggered. It is time and date of operation mode switch

Symptom:

Various error messages that refer to memory bottlenecks (a swap space bottleneck), for example: System Panic; cmemreserve: reservation overrun; ENOMEM, Not enough core; ENOSPC, No space left on device; SIGDANGER (only under AIX). In the R/3 System, the R/3 system log message "no memory of class perm" is output.

This problem can occur with R/3 processes and external processes as well. The relevant process cannot allocate anymore heap memory. This can lead to the database operation being ended or R/3 work processes being stopped.

In the R/3 System, error messages appear in the developer trace files dev_disp, dev_w, in the system log and in dumps. The following messages may appear: TSV_TNEW_; _NO_ROLL_MEMORY; NO_MEM; NO_MEMORY; RESIZE_EM_ALLOC_ERROR, Storage class PERM.

This problem mostly occurs if background jobs are active with large amounts of data.

Possible Causes

• There is no more swap space available (see
Alert Monitor).
• The highest value for one of the R/3 profile parameters that limit the swap space usage has been exceeded. In this case, the following parameters are relevant:
abap/heap_area_dia, abap/heap_area_nondia and abap/heap_area_total.
• The operating system limits for the process size (segment size) have been exceeded. Under AIX, no more than 256 MB can be allocated and under SINIX no more than 384 MB can be allocated.

Corrective action

Increase the swap space or decrease the R/3 Extended Memory. If the swap space already corresponds to the SAP recommendations, 1.5 to 2 GB may still be required. There should always be several hundred MB of free swap space available. You can reduce the maximum swap space need of the R/3 System by reducing the value of parameter abap_heap_area_total. For more detailed information, see Monitoring the Memory Management System.

You can also distribute the load onto several application servers and increase the roll area. Check if the maximum process size (operating system parameters) is sufficient.

Keyword: BASIS
Title : LiveCache operation modes

Go through the following to find if an Operation Switch Occured:-

1) Go to SM50. If the no of dialog work processes or background work processes changes then a operation mode switch took place.

2) Go to transaction SM63. Here you can see the time when the operation mode is set. You can guess when the operation mode switch occurs.

3) Go to transaction RZ04, here you can see the list of operation modes and their time. You can guess that from here

4) Go to transaction RZ03 , here you can see the current operation mode in which the server is running.

5) Call transaction Code SM62. Then view system events. If there is an event called SAP_OPMODE_SWITCH then operation mode switch occurred at that time.

If you click on activity log you can see the time and date when the event was triggered. It is time and date of operation mode switch.

How do you find that an operation mode switch occurred? There are many ways

1) Go to sm50. If the no of dialog work processes or background work processes changes then a operation mode switch took place.

2) Go to transaction sm63. Here you can see the time when the operation mode is set. You can guess when the operation mode switch occurs.

3) Go to transaction RZ04, here you can see the list of operation modes and their time. You can guess that from here

4) Go to transaction rz03 , here you can see the current operation mode in which the server is running.

5) Call transaction Code sm62. Then view system events. If there is an event called SAP_OPMODE_SWITCH then operation mode switch occurred at that time. If you click on activity log you can see the time and date when the event was triggered. It is time and date of operation mode switch

Keyword: BASIS
Title : Swap Space Bottleneck During SAP Operation

Payroll in a Background Operation




Related Books

• 
  
• Free Download Book Payroll Canada(PY-CA)
• Free Download Book Payroll Brazil (PY-BR)
• Free Download Book Payroll Belgium (PY-BE)
• Free Download Book Payroll Australia (PY-AU)
• Free Download Book Payroll Argentina (PY-AR)
• Free Download Book Training and Event Management P...
• Free Download Book Report Programming in HR
• Free Download Book Reporting in Human Resource Man...
• Free Download Book Wage Type Statement Wage Types
• Free Download Book Wage Type Reporter (H99CWTR0)
• Free Download Book Wage Type Distribution
• Free Download Book Wage and Salary Payments
• Free Download Book Master Data Distribution (Human...
• Free Download Book HR Tools (PY-XX-TL)
• Free Download Book HR Infotypes
• Free Download Book HR - Human Resource Management
• Free Download Book HR Funds and Position Managemen...
• Free Download Book HR Forms Workplace (PY-XX-FO)
• Free Download Book HR Form Editor (PY-XX-TL)