BW_monitoring & Error Handling

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 ChainModelling Aspects

Process ChainArchitecture & Functionality

Process ChainMonitoring & Error Handling

BW Transport Management System

Periodical jobs and tasks

Monitoring Changerun

Load Balancing & Number Range Buffering

BW Statistics and Query Tuning with Aggregates(RSRT)

Data Modelling from thetechnical point of view

Usage of Basis Transactions(SM50, …) for applicational people

2


Process ChainsProcess ChainsProcess ChainsProcess ChainsMonitoringMonitoringMonitoringMonitoring & Error Handling& Error Handling& Error Handling& Error Handling

Metachain

BWCCMS

RSPCM

ST03, FM: RSPC_RUNTIME_ANALYSIS

External Tools

Logview of process chain

Error Handling in Process Chains

3


Monitoring of Individual Process Chain

Logview for Monitoring a individual process chain in detail available

Access to different logs from log view of the proce ss chain � Data Loading Monitor (rsmo)

� Batch Monitor (sm37)� Application log (slg1)

Restartability of processes in the the process chain, when processchain terminates� Either it is possible to restart the same process a gain or the

subsequent process

4


Monitoring of Individual Process Chain

Execution of process chain

right

Use Right mouse click in order to see the available functionality.

With the log view of a process chain, monitoring of special BW processes (like infopackages, change run, precalculation) and common activities (like drop/create index) is possible. Right mouse click on a process icon gives you the available log functionality.

Different processes are clearly arranged in one view and directly linked to the corresponding logs.

Some processes (depending on the process type) are restartable.

5


Monitoring jobs in the BW system

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.

6



Metachain

BWCCMS

RSPCM


External Tools



7


Restartability of Process Types

DDDDepending on the process type someprocesses are immediately repeatable

AAAAfter the failing process is successfullyrepeated, processing the chain is continued, ifit was not already continued before

Failed processitself restartable

subsequent processis restartable

Case 1: process type ‚restartable‘ Case 2: process type ‚n ot restartable‘

8


Restartability of Process Types

FFFFor each process type (self definedor standard) re-starting is a featurewhich is set in table: RSPROCESSTYPES

9



Metachain

BWCCMS

RSPCM


External Tools



10


Structuring/Monitoring with Meta-/Subchains

1. Bundle different process chains within metachains in order to get a single point of Monitoring

2. Single point of Monitoring with metachain vs. Monitoring of complex process chains

3. Schedule Data WarehouseActivities with (small) process chains Jump to the Local

Chains possible!

Logview

11


Systemwide Monitoring – Metachain

12


Example: Success Message

SSSSometimes it is useful to get a message after the process cha in was finishedsuccessfully, in order

tttto identify hanging process chains quickly

tttto get information about the runtime without any log analys is

...

‚Dummy‘ ABAP programas workaround forsending a successmessage to the BW

Administrator

Email can be sent to indicate successful or completion of a process too.

13



Metachain

BWCCMS

RSPCM


External Tools



14


Process Chains: CCMS integration

Monitoring via SAP Computing Center Management System (CCMS): Menu path: Tools �� CCMS �� Control / Monitoring �� Alert Monitor �� <BW Monitor>

Chain_3

Legend:

Process chain ran success-fully for the last 7 days

Highest alert for the last 7 days: still running orhanging process chain

Highest alert for the last 7 days: terminated processchain

Process chain didn‘t run forthe last 7 days or CCMS collector job is missing orprocess chain monitoring isswitched off

(green)

(yellow)

(rot)

(white)

Note 738681 Correction: No chain status display in CCMS (BW 3.0: SP22, BW 3.1: SP16, BW 3.5: SP 5)

15


SAP_CCMS_MONI_BATCH_DP - Monitoring

Transaction SM37

Jobname: SAP_CCMS_MONI_BATCH_DP

Report:RSAL_BATCH_TOOL_DISPATCHING

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.

16


SAP_CCMS_MONI_BATCH_DP - Monitoring

AAAActivate 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 collectorswhich are used in CCMS. Thisjob is not BW specific!

DDDDeletion of job SAP_CCMS_MONI_BATCH_DPinfluences other basismontioring 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.

17


Monitoring jobs in the BW system

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 exspected 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.

18


Monitoring of Process Chains - Setup

SAP_CCMS_MONI_BATCH_DPmonitors each Process Chain by default !

Switching off the automatic monitoring of Process chains :

� You can globally switch off the monitoring by setting the parameterDAYS_TO_KEEP_LOGS of method RSPC_CCMS_AGENT to ‘OFF’ (Note 644436)

� You can switch of the monitoring for one specific Process ChainsProcess Chain -> Attributes -> Monitoring : Chain is not Monitored Automaticallyor (table RSPCCHAINATTR field UNWATCHED, Note 708480)

Recommendation:It‘s not recommended to switch off the monitoring in theproduction environment. Only if a Process Chain is monitored by this job, all post-processing processe s are executed and the Alert-Monitoring gets a notificati on in case of an error !

By default all Process Chains are integrated automatically in the job SAP_CCMS_MONI_BATCH_DP. This makes sure that all error situations are caught by the system, the post-processing is triggered and the Alert-Monitor gets a notification message.

If you want to exclude a Process Chain from the monitoring (e.g. it isn‘t important and therefore there is no need to monitor it), please refer to note 708480. Attention: It‘s not recommended to switch off the monitoring within the production environment !

19


CCMS: Parameter DAYS_TO_KEEP_LOGS

� Transaction RZ21 �Method definitions �Display overview

� Double click on RSPC_CCMS_AGENT

Default:

7 days

If the parameter DAYS_TO_KEEP_LOGS is missing, the BW system uses the default value of seven days.

Please refer to note: 738681 (Correction: No chain status display in CCMS) (included in BW3.0B SP22, BW3.1C SP16, BW3.5 SP4/5)

Symptom:

The status of a chain is not displayed in the CCMS (transactions RZ20

and BWCCMS). Specifically:

o After a day without any new activity (activity interval),monitor

attribute nodes in the current view become white (inactive)

o Within the activity interval, the following applies: If achain

has the active status, this is not displayed, the status of the

attribute node is in accordance with the status of the highest

alerts within the chain ( normally green, or red in the case of

an incorrect process).

20


CCMS: Parameter DAYS_TO_KEEP_LOGS

Method RSPC_CCMS_AGENT -> Parameter DAYS_TO_KEEP_LOG S:Specifies how many days the logs for a Process Chain run are available in CCMS Alert Monitoring

Note:

Setting the value DAYS_TO_KEEP_LOGS greater than 7 days means more load on the job SAP_MONI_BATCH_DP

Recommendation:Set the parameter respectivly small and adapt it on your

CCMS monitoring frequency

By the parameter DAYS_TO_KEEP_LOGS you can determine how long the logs of a Process Chain run are displayed in the CCMS. The default setting is seven days. Because the runtime of job SAP_MONI_BATCH_DP increases with the number of Process Chains to be monitored, it is recommend to adapt this parameter on your CCMS monitoring frequency.

Example:By default, the job SAP_MONI_BATCH_DP is running hourly. This means that the maximum delay until an error situation is reported to the CCMS is one hour (please note that additional time for the process type itself must be considered e.g. monitor wait time for requests, maximum wait time for ODS Data Activation). Therefore you´ll probably watch at the central CCMS Monitor for example every two hours. In such a case you probably won‘t require log entries of the CCMS of the past seven days. Therefore you can reduce the parameter DAYS_TO_KEEP_LOGS to one or two. Additionally all logs of a Process Chain run will still be available in the BW system.

21


CCMS – SAP BW Monitors

Transaction RZ20

The creation of userdependent monitors is

possible

By a double click youcan jump directly to the

Process Chain Log

Current

Open AlertView

22


Additional Notes

MMMMTE Class for Monitoring Infrastructure: ‚BW_MonCls_Process_Chains‘

WWWWhen process chain is executed, there is an active datacollector (Method RSPC_CCMS_STARTUP), which is triggere dimmediately and creates the new CCMS alert entry

FFFFinisher status of an running process chain is transferredperiodically via passive data collector (RSPC_CCMS_AGE NT) ‚which is triggered by the periodical background job SAP_CCMS_MONI_BATCH_DP.

•MTE Class ‚BW_MonCls_Process_Chains‘ is built for Alert Monitoringpurposes. It is not build for monitoring currently running proc ess chains.

•After starting a process chain there is an active data collector (MethodRSPC_CCMS_STARTUP), which is triggered by the process chainimmediately and creates the new CCMS alert entry without anyvalidation (means white colour!)

•Finisher status of an running process chain is transferred periodicallyvia passive data collector (RSPC_CCMS_AGENT) ‚ which is triggeredby the periodical background job SAP_CCMS_MONI_BATCH_DP. Information appears about terminations within process chains in BWCCMS with a time delay (default: up 1h).

23


CCMS Documentation

For more detailed information about the CCMS Alert Monitoring tool, please refer to the Online-

Documentation:

Computing Center Management System (BC-CCM)

http://help.sap.com/saphelp_bw30b/helpdata/en/60/4d81294c5f11d192f30000e829fbc6/frameset.htm

The Alert Monitor

http://help.sap.com/saphelp_bw30b/helpdata/en/28/83493b6b82e908e10000000a11402f/frameset.htm

24



Metachain

BWCCMS

RSPCM


External Tools



25


RSPCM – Monitor daily process chain

For assigningprocess chainto this monitor

Transaction RSPCM (not officially released):

By a double clickyou can jumpdirectly to the

Process Chain Log

Note:Note:Note:Note:

Just the last execution of the processchain is visible!

Status of last execution

26



Metachain

BWCCMS

RSPCM

FM: RSPC_RUNTIME_ANALYSIS

External Tools

27


Customer wants to know . . .

How long a Process Chain and the singleprocesses take?

How do we analyze such a problem?

SAP AG 2002, SAP ACTIVE GLOBAL SUPPORT 27

28


RSPC – Process Chain Monitor

Only tellsstart timebut no end time

No runtimeinformationfor thesingle chainlink inoverview

Where is the time spent?

SelectProtocoll

RSPC -> double click on process chain name, turn on detail view, choose logs

You get only the start date of the process chain, but no end time. You cannot tell if the runtime behavior is similar for the different runs on the past, or if the runtime was increasing or so

AND

29


Single Chain Link information

BackgBackgBackgBackg::::

Job Log (SM37) isdisplayed, whichcontains for manyprocesses the SQL Trace. It‘s giving thedetailled time.

ProcessProcessProcessProcess ----> > > >

ProcessProcessProcessProcess MonitorMonitorMonitorMonitor

(RSMO) right mouseclick to get thedetails of theinfopackage

Right click on single chain link, choose Displaying Messages

Take into accout that the time in Backg. contains the entire time for the single chain link, it‘s not only the scheduling job for the infopackage. Use Process tab -> Process Monitor (jumb to RSMO) to get the RSMO upload runtimes.

30


Workaround – Using Table RSPCPROCESSLOG

Table RSPCPROCESSLOG:Contains Logs for the Process Chain Runs

To get the sinlge execution times per single chain link we need to us SE11/SE16 against table RSPROCESSLOG.

The Log ID can be retrieved from RSPC using the log view.

31


RSPCPROCESSLOG

Table RSPCPROCESSLOG:Contain Logs for the Process Chain Runs UTC Time Stamps

(= Greenwich MeanTime)

Yyyymmddhhmmss,...

With table RSPCPROCESSLOG it is also possible to get the m apping betweenLogID and technical name of a process and vice versa.

LogID (generated)Instance names

for furtheranalysis

Export output of RSPROCESSLOG to Excel.

Use the columns STARTTIMES and ENDTIMESTA to calculate the runtime per single chain link.

Once you found

the long running infopackage and the request number in column ‚Instance‘ and then go to transaction RSRQ.In RSRQ enter the request number and then use the normal RSMO analyse method to find where the time is spent:column instance: REQU_9VZLQQ1KDKONTA8I06H1OHYC2-> input for RSRQ.

the long running Database Statistic Rebuild in Column instance, jump to the Joblog, in order to analyze the SQL Trace.

In RSPC1 enter the LogID 6NZ2168BA5IA8Q13XHUJ2V0W5 and check the Joblog for the process ‘DB Statistic Rebuild’

32


Function module RSPC_RUNTIME_ANALYSIS

Function module is available withBW 3.0B SP >=12

33


Result of Function moduleRSPC_RUNTIME_ANALYSIS

UTC Time Stamps(= Greenwich Mean

Time) Yyyymmddhhmmss,...

Calcuated duration in seconds

34



Metachain

BWCCMS

RSPCM

FM: RSPC_RUNTIME_ANALYSIS

External Tools

35


External Scheduling and Monitoring Tools

External Schedulingor Monitoring Tool(e.g. UC4, Tivoli, ...)

SAP BW3.x

CRM

SAP R/3

On process

level

On process

level

Recom-mended on

processchain level

Recommendation:

Scheduling, Monitoring of (small) processchains via external scheduling tool

36


Certified Partners

http://service.sap.com/bw -> Partner -> Certified Software Partner-> Job Scheduling for BW

UC4 Software [UC4:global]

TIDAL Software [TIDAL Enterprise Scheduler]

Redwood Software Europe [Cronacle]

ORSYP [Dollar Universe]

BMC Software [CONTROL-M]

Certification Status Quo (1.7.2004):

37


Types of Certified Tools

Three types of external scheduling/monitoring tools :

Type 1: Type 1: Type 1: Type 1: Just scheduling of process chain

Type 2: Type 2: Type 2: Type 2: Scheduling and Monitoring of process chain

Type 3:Type 3:Type 3:Type 3: Scheduling, Monitoring and Restarting of process ch ain

BW_monitoring & Error Handling

Documents

Transcript of BW_monitoring & Error Handling