sap periodical jobs and tasks

1

SAP AG 2005, BW System Administration / 1

BW Systemadministration – Portfolio

Extraction and Data Transfer

Data Load Monitoring, Reload and Repair

ODS and Datamart Handling

Process Chain

Modeling Aspects

Process Chain

Architecture & Functionality

Process Chain

Monitoring & Error Handling

BW Transport Management System

Periodical jobs and tasks

BW Basis Configuration

Load Balancing &

Number Range Buffering

Monitoring&Handling of Changerun

Data Modelling from the

technical point of view

BW Security and Authorization

Aspects

BW System Copy

BW Backup and RestoreBW Statistics and

Query Tuning with Aggregates(RSRT)

2


Contents

Periodical Basis Jobs

Periodical Application Jobs

Periodical Monitoring Tasks

3


SAP Basis Job: SAP_CCMS_MONI_BATCH_DP

Purposes:

1. Trigger post-processing successors of

failed process types (exceptions which

aren’t detected automatically)

2. Overall (not just BW) Application and

Basis Alert-Monitoring with CCMS-Alert-

Monitoring (RZ20)

Job: SAP_CCMS_MONI_BATCH_DP

Monitoring of Process Chains (all process types)

Post-Processing

The job SAP_CCMS_MONI_BATCH_DP is scheduled hourly by default and

collects alert information for the Alert-Monitoring-Tool (transaction RZ20).

In a BW system, this report contains a watchdog functionality for the Process Chains and is the interface to the Alert-Monitoring (RZ20). If any error situation occurs during a run of a Process Chain, this report sends a notification to the Alert-

Monitoring. On the other side it checks the execution of a Process Chain for not expected error situations meaning problems that can’t be handled by the BW

Process Chain architecture. This makes sure that the post-processing (red arrows) is executed in any case.

4


SAP Basis Job: SAP_CCMS_MONI_BATCH_DP

AAAActivating Background dis-

patching means that Batch Job

SAP_CCMS_MONI_BATCH_DP

is scheduled hourly

SSSSAP_CCMS_MONI_BATCH_DP

also collects information for all

other (passive) data collectors

which are used in CCMS. This

job is not BW specific!

DDDDeletion of job

SAP_CCMS_MONI_BATCH_DP

influences other basis

monitoring activities as well

RZ21:

The job SAP_CCMS_MONI_BATCH_DP is scheduled hourly by default. The

minimum time range between two executions must be higher than 300 seconds.

5


DB13: BRCONNECT

BRCONNECT/DB13

can be used to collect Oracle Optimizer statistics, perform a

database system check, collect space statistics….

alias: http://service.sap.com/dbaora

General Recommendation:

Schedule BRCONNECT database jobs as in R/3

6


DB13: BRCONNECT

BW specific recommendations

� Schedule an optimizer statistics update after large

changes in data. E.g. usually after the daily upload has

finished.

� With Oracle 9.2, use BRCONNECT 6.40

� Switching on the monitoring option and running BRCONNECT in parallel improve the performance of the

job.

For BW it is specifically recommended to use BRCONNECT 6.40 (Oracle 9.2)

BRCONNECT 6.40 contains additional functionality for Optimizer statistics collection, especially

for partitioned tables. Refer to SAP note 744483.

Switching on the monitoring option and running BRCONNECT in parallel improve the

performance of the job.

After installing BR*Tools 6.40, you must collect new statistics again for all tables, so as to have a

proper starting point for collecting column statistics. To do this, start BRCONNECT as follows:

brconnect -u system/<pwd> -c -f stats -t all -f allsel,collect,monit [-p 8]

DAILY procedure to renew statistics:

brconnect -u system/<pwd> -c -f stats -t all -f monit [-p 4]

Refer also to SAP note 129252

7


Contents




8


SAP_INFOCUBE_INDEXES_REPAIR

Functionality:

Report to check for and repair missing indexes

Run in transaction se38

Recommendation:

Schedule weekly

9


BW Customizing: RSMONASSISTANCE

Job: RSMONASSISTANCE

Monitoring of data requests only

Can run several times per day

E-Mail notification possible

Alert depends on Monitoring waiting time and job frequency

Catches exceptions that can’t

be detected by the system

automatically

BW Customizing - Setup

Monitoring of data requests only

Activities

Schedule the monitor assistant in the background. As a repeat frequency, select

how often you intend to load data.

Recommendation

The assistant investigates all new requests that were started after a certain date. Create a variant for the monitor assistant and enter this date. If no date is entered,

the actual date is used.

Further notes

If you are dealing with an upgrade system, and you chose a date in the past, the

first run time can possibly take a long time.

Error Notification and post-processing

In case of an error the system can be setup to sent an email. The maximum time passed between the occurrence of the error and the notification/post-processing

depends on the Monitor Waiting Time and the frequency of the job.

The system-wide setting of the Monitor Waiting Time is setup in the BW Customizing ‘Set Traffic Light Waiting Time’. In the Scheduler, you can set the maximum wait time after which a request is to be set to red in the Monitor for each

InfoPackage. Do this via Scheduler -> Timeout-Time/Warning Handling. This setting overrides the system-wide setting for a particular InfoPackage. The prerequisite for

changing the status after the maximum time has elapsed is that the request is analyzed by the Monitor assistant. Only if this happens can any resulting post-

processing processes be triggered by the request.

10


Application Log

BBBBW uses frequently the application log

AAAApplication log: tables: BAL* (mainly BALDAT)

PPPProblem: with huge application log tables read and write activities to the

related tables are slow

SSSSolution:

� 1. Method: Delete specific time range of application log with Tcode SLG2

(no restore possible!)

� 2. Method: archiving application log with archiving object:

BC_SBAL with Tcode SARA

ActionsWriteDelete

Management

BC_SBAL Archiving Object forApplication Log

Two methods for reorganizing possible:

Tcode SARA: archive data backup of application log information on a optical drive, etc. possible

Tcode SLG2: direct deletion of application log information possible, no restore possible

Display application log: Tcode: SLG1

Heavy use of application log in BW in all WHM acitivities (data load, rollup, compress, ...)

Check size of table BALDAT periodically

11


Deletion of Info IDocs

EEEEach IDoc is stored in tables EDI* (mainly EDI40)

HHHHeavy usage of Info IDocs in data load activities

WWWWith huge IDoc tables: starting of detailed view in data load

monitor takes a long time

SSSSolution: archive and delete IDocs: Tcode SARA, archiving

object: IDOC

ActionsWrite

DeleteRead

Management

IDOC IDOC – Intermediate Document

It is not possible to delete these IDocs without archiving

In Tcode SARA: Fixed sequence: First archive IDocs and then delete IDocs from table EDI40, etc

Because of less importance of old Info Idocs, archiving to filesystem is quite enough (usually no

optical drive, etc. necessary)

12


Report SAP_DROP_TMPTABLES

FunctionalityDrops unused BW temp tables

temporary tables starting with /BIC/01..., /BI0/02..., /BI0/03...

Recommendation:Define a variant for report SAP_DROP_TMPTABLES.

Schedule a monthly job called SAP_DROP_TMPTABLES, with report

SAP_DROP_TMPTABLES as a job step.

For detailed information: SAP Note 449891.

Report SAP_DROP_TMPTABLES removes temporary objects (temporary tables starting with

/BIC/01..., /BI0/02..., /BI0/03...) from the database. BW uses several temporary objects for query

and other processing. These temporary objects are often created outside the ABAP Dictionary for

performance reasons or because they cannot be defined there (like stored procedures or triggers).

13


BW Statistics

IIIIf BW statistics switched on for a certain infoprovider tables

RSDDSTAT* tables are filled.

TTTTables are growing continuosly

NNNNo archiving object for these tables available

Manual deletion necessary(e.g. yearly)

Details later in chapter ‚BW Statistics‘

For reorganisation of these tables use deletion button in RSA1 � Tools � BW Statistics � delete.

You have to specify the time range. Entries from all statistic tables RSDDSTAT* will be deleted.

Tool ‚RSA1 � Tools � BW Statistics � delete‘ refers to tables RSDDSTAT,

RSDDSTATAGGR, RSDDSTATAGGRDEF, RSDDSTATWHM. RSDDSTATCOND

14


Table Reorganisation

RRRReasons for table reorganization

� Performance for accessing data

� Reuse of diskspace for other tablespaces (issue for upgraded systems)

� Change of physical locations (tablespace)

� Change of storage parameters

� Archiving

RRRReorganize using the BRSPACE tool (note 647697).

15


Standard Jobs Standard Jobs Standard Jobs Standard Jobs –––– Reorganization Jobs Reorganization Jobs Reorganization Jobs Reorganization Jobs SAP NOTE 16083 R/3 + BW 449891SAP NOTE 16083 R/3 + BW 449891SAP NOTE 16083 R/3 + BW 449891SAP NOTE 16083 R/3 + BW 449891

SAP_DROP_TMPTABLESSAP_DROP_TMPTABLES (>= 3.x 449891)

WeeklyRSPO0042 (>=4.6B 168529)PSPO0042 (TSPEVDEV XOM interface)

weeklyRSBTCDEL2RSBTCDEL2 (728947)

dailyyesRSTS0024RSTS0024 (>= 4.6B 666290)

dailyyesRSPO1043RSPO1043 (48400)

hourlynoRSAL_BATCH_TOOL_DISPATCHINGSAP_CCMS_MONI_BATCH_DP (>=4.6A)

weeklyyesRSXMILOGREORGSAP_REORG_XMILOG (>= 4.6C 182963)

monthlynoRSBTCPRIDEL (307970)SAP_REORG_PRIPARAMS (>= 4.6B)

hourlynoRSN3_STAT_COLLECTOR (>= 6.20)SAP_COLLECTOR_FOR_NONE_R3_STAT

hourlynoRSCOLL00SAP_COLLECTOR_FOR_PERFMONITOR

dailynoRSBPCOLLSAP_COLLECTOR_FOR_JOBSTATISTIC

monthlyyesRSBPSTDESAP_REORG_JOBSTATISTIC

dailyyesRSSNAPDLSAP_REORG_ABAPDUMPS

dailyyesRSBDCREOSAP_REORG_BATCHINPUT

dailyyesRSPO1041SAP_REORG_SPOOL (130978 + 48400)

dailyyesRSBTCDELSAP_REORG_JOBS

RepeatVariantProgramJob name

The above table is provided so that you can check the necessary required jobs and

their required execution frequency. With the newer SAP versions the TC SM36 can

be used to plan these jobs, however first delete the planning before using the

transaction to insure the jobs are only in the system as required. Multiple executions

of the SM36 will plan additional executions.

16


Contents




17


Operations Manual – Basis Monitoring

Many BW Basis monitoring tasks are similar to those in R/3

Recommendation

An operations manual that covers specific production tasks

and responsible persons.

18


Monitoring Query Performance – ST03

1. Switch to

‚Expert Mode‘

and press

‚Save View‘

2. Choose right

Aggregation

Level (Cube or

Query level)

3. Sort by

number of

navigations

4. Check for

log running

queries

The data comes

from table

RSDDSTAT,

which contains

all this

information +

some more

details.

Sometimes it is

useful to table

RSDDSTAT

directly

19


Basis Monitoring - CCMS

CCMS – Monitor set for BW

http://service.sap.com/monitoring

Basis parameters for BW systems: Note

20


Basis Monitoring – General

� SAP Buffer Monitor – ST02

NB: Export/import buffer SHM (OLAP Cache):

� Operating System Monitor – ST06

� Database Performance Monitor – ST04

NB: BW query statements do not use bind variables so arenot stored in the Oracle SQL cache

� Database Monitor – DB02

� System log - SM21

� ABAP Runtime Errors (short dumps) – ST22

� RFCs in BW and each connected source system - SM58, SMQ1

� Background jobs - SM37

Basis parameters for BW systems: Note

21


Basis Monitoring - General

� RSRV checks

� Review EWA Reports

sap periodical jobs and tasks

Documents

bw system administration

batch job sap

sap basis job

hourly sap

deletion of job sap

monitoring rz20 sap

bw application

aggregatesrsrt sap ag