Creating and Scheduling a Reorganization Schema 

Use

You can create your own reorganization schema to define the period of time over which performance data should be retained in the performance database. After this period, the data is flagged for deletion and deleted when the reorganization is next run. You can also determine whether or not to retain data after it is flagged for deletion, in case you want to access this data at a later date.

SAP's default reorganization schema is SAP_DEFAULTSCHEMA. The performance database is reorganized once a week, when the basic data that is reported to the monitoring architecture is aggregated and summarized into weekly data. The basic data is then deleted from the database, so that only the compressed data remains.

To create an reorganization schema, you must execute two programs, RSALPREORG and RSALPFPOLICY to populate the tables that contain the schema itself. The reorganization schema is run as a background job, which the system administrator also needs to schedule.

The system automatically schedules the background job. You can check its progress by calling Transaction SM37 or by choosing System ® Own jobs.

Procedures

To create a reorganization schema

  1. Choose Development ® ABAP Editor. Alternatively, call Transaction SE38.
  2. Enter program RSALPREORG in the input field and choose Execute. Enter the system name, MTE class name and the schema ID and choose Save.

Program RSALPREORG populates the table that stores the system ID, MTE class and the schema ID. This enables you to assign a different reorganization schema to different MTE classes in different systems.

  1. Next, execute program RSALPFPOLICY as described above . This program determines the actual policy itself. Enter the name of your reorganization schema in the Schema ID field.
  2. Specify the days, months, quarters or years over which you want to keep the performance data. For example, if you want to keep the performance data for 15 days and you have not accessed that data after 15 days, then the system flags the data to be deleted. The data is deleted when the reorganization schema is next scheduled to run (see below).

You may still want to access this data even after it has been flagged for deletion. In this case, enter the number of additional days, weeks, quarters or years that the data should be retained. For example, if you specify that the performance data should be kept for 15 days but deleted after an additional 5 days, the data is deleted after 20 days.

  1. Save your data.

To schedule the reorganization schema as a background job

You now have to schedule when the performance database reorganization will take place. The reorganization is scheduled as a background job. You can either define a time and date for the job, or change the date and time that has already been defined.

There are two steps to this background job: the first is to define the frequency of the data collection, the second is to define the date and time of the reorganization.

  1. Choose CCMS ® Configuration ® Alert monitor. Alternatively, call Transaction RZ21.
  2. Choose Technical infrastructure ® Performance database ® Define background job. The system displays when the performance data is collected and stored in the performance database. To change this background job, choose Change start date/time. You can change the frequency of the collection here, although SAP recommends that the performance data is collected every six hours.
  3. When you have made the necessary changes, choose Save. Then choose Next step to display when the performance database is to be reorganized according to the schema that you have previously defined. To change this background job, choose Change start date/time. Make and save the necessary changes.

 

See also:

 

Background Processing