SAP Periodical Jobs And Tasks


Published on

1 Comment
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

SAP Periodical Jobs And Tasks

  1. 1. BW Systemadministration – Portfolio Extraction and Data Transfer BW Transport Management System Data Load Monitoring, Periodical jobs and tasks Reload and Repair ODS and Datamart Handling BW Basis Configuration Process Chain Load Balancing & Architecture & Functionality Number Range Buffering Process Chain Monitoring&Handling of Changerun Modeling Aspects Process Chain BW Security and Authorization Monitoring & Error Handling Aspects Data Modelling from the BW System Copy technical point of view BW Statistics and BW Backup and Restore Query Tuning with Aggregates(RSRT) SAP AG 2005, BW System Administration / 1 1
  2. 2. Contents Periodical Basis Jobs Periodical Application Jobs Periodical Monitoring Tasks SAP AG 2005, BW System Administration / 2 2
  3. 3. SAP Basis Job: SAP_CCMS_MONI_BATCH_DP Job: SAP_CCMS_MONI_BATCH_DP Monitoring of Process Chains (all process types) Post-Processing 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)  SAP AG 2005, BW System Administration / 3The job SAP_CCMS_MONI_BATCH_DP is scheduled hourly by default andcollects alert information for the Alert-Monitoring-Tool (transaction RZ20).In a BW system, this report contains a watchdog functionality for the ProcessChains and is the interface to the Alert-Monitoring (RZ20). If any error situationoccurs 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 notexpected error situations meaning problems that can’t be handled by the BWProcess Chain architecture. This makes sure that the post-processing (red arrows)is executed in any case. 3
  4. 4. SAP Basis Job: SAP_CCMS_MONI_BATCH_DP RZ21: Activating Background dis- patching means that Batch Job SAP_CCMS_MONI_BATCH_DP is scheduled hourly SAP_CCMS_MONI_BATCH_DP also collects information for all other (passive) data collectors which are used in CCMS. This job is not BW specific! Deletion of job SAP_CCMS_MONI_BATCH_DP influences other basis monitoring activities as well  SAP AG 2005, BW System Administration / 4The job SAP_CCMS_MONI_BATCH_DP is scheduled hourly by default. Theminimum time range between two executions must be higher than 300 seconds. 4
  5. 5. DB13: BRCONNECT BRCONNECT/DB13 can be used to collect Oracle Optimizer statistics, perform a database system check, collect space statistics…. alias: General Recommendation: Schedule BRCONNECT database jobs as in R/3 SAP AG 2005, BW System Administration / 5 5
  6. 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.  SAP AG 2005, BW System Administration / 6For 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 6
  7. 7. Contents Periodical Basis Jobs Periodical Application Jobs Periodical Monitoring Tasks SAP AG 2005, BW System Administration / 7 7
  8. 8. SAP_INFOCUBE_INDEXES_REPAIR Functionality: Report to check for and repair missing indexes Run in transaction se38 Recommendation: Schedule weekly SAP AG 2005, BW System Administration / 8 8
  9. 9. BW Customizing: RSMONASSISTANCE Job: RSMONASSISTANCE Monitoring of data requests only BW Customizing - Setup 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  SAP AG 2005, BW System Administration / 9ActivitiesSchedule the monitor assistant in the background. As a repeat frequency, selecthow often you intend to load data.RecommendationThe 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 notesIf you are dealing with an upgrade system, and you chose a date in the past, thefirst run time can possibly take a long time.Error Notification and post-processingIn case of an error the system can be setup to sent an email. The maximum timepassed between the occurrence of the error and the notification/post-processingdepends on the Monitor Waiting Time and the frequency of the job.The system-wide setting of the Monitor Waiting Time is setup in the BWCustomizing ‘Set Traffic Light Waiting Time’. In the Scheduler, you can set themaximum wait time after which a request is to be set to red in the Monitor for eachInfoPackage. Do this via Scheduler -> Timeout-Time/Warning Handling. This settingoverrides the system-wide setting for a particular InfoPackage. The prerequisite forchanging the status after the maximum time has elapsed is that the request isanalyzed by the Monitor assistant. Only if this happens can any resulting post-processing processes be triggered by the request. 9
  10. 10. Application Log BW uses frequently the application log Application log: tables: BAL* (mainly BALDAT) Problem: with huge application log tables read and write activities to the related tables are slow Solution: 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 BC_SBAL Archiving Object for Application Log Actions Write Delete Management  SAP AG 2005, BW System Administration / 10Two 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 possibleDisplay application log: Tcode: SLG1Heavy use of application log in BW in all WHM acitivities (data load, rollup, compress, ...)Check size of table BALDAT periodically 10
  11. 11. Deletion of Info IDocs Each IDoc is stored in tables EDI* (mainly EDI40) Heavy usage of Info IDocs in data load activities With huge IDoc tables: starting of detailed view in data load monitor takes a long time Solution: archive and delete IDocs: Tcode SARA, archiving object: IDOC IDOC IDOC – Intermediate Document Actions Write Delete Read Management  SAP AG 2005, BW System Administration / 11It is not possible to delete these IDocs without archivingIn Tcode SARA: Fixed sequence: First archive IDocs and then delete IDocs from table EDI40, etcBecause of less importance of old Info Idocs, archiving to filesystem is quite enough (usually no optical drive, etc. necessary) 11
  12. 12. Report SAP_DROP_TMPTABLES Functionality Drops 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.  SAP AG 2005, BW System Administration / 12Report 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). 12
  13. 13. BW Statistics If BW statistics switched on for a certain infoprovider tables RSDDSTAT* tables are filled. Tables are growing continuosly No archiving object for these tables available Manual deletion necessary (e.g. yearly)  SAP AG 2005, BW System Administration / 13Details 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 13
  14. 14. Table Reorganisation Reasons 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 Reorganize using the BRSPACE tool (note 647697). SAP AG 2005, BW System Administration / 14 14
  15. 15. Standard Jobs – Reorganization Jobs SAP NOTE 16083 R/3 + BW 449891 Job name Program Variant Repeat SAP_REORG_JOBS RSBTCDEL yes daily SAP_REORG_SPOOL (130978 + 48400) RSPO1041 yes daily SAP_REORG_BATCHINPUT RSBDCREO yes daily SAP_REORG_ABAPDUMPS RSSNAPDL yes daily SAP_REORG_JOBSTATISTIC RSBPSTDE yes monthly SAP_COLLECTOR_FOR_JOBSTATISTIC RSBPCOLL no daily SAP_COLLECTOR_FOR_PERFMONITOR RSCOLL00 no hourly SAP_COLLECTOR_FOR_NONE_R3_STAT RSN3_STAT_COLLECTOR (>= 6.20) no hourly SAP_REORG_PRIPARAMS (>= 4.6B) RSBTCPRIDEL (307970) no monthly SAP_REORG_XMILOG (>= 4.6C 182963) RSXMILOGREORG yes weekly SAP_CCMS_MONI_BATCH_DP (>=4.6A) RSAL_BATCH_TOOL_DISPATCHING no hourly RSPO1043 (48400) RSPO1043 yes daily RSTS0024 (>= 4.6B 666290) RSTS0024 yes daily RSBTCDEL2 (728947) RSBTCDEL2 weekly PSPO0042 (TSPEVDEV XOM interface) RSPO0042 (>=4.6B 168529) Weekly SAP_DROP_TMPTABLES (>= 3.x 449891) SAP_DROP_TMPTABLES  SAP AG 2005, BW System Administration / 15The above table is provided so that you can check the necessary required jobs andtheir required execution frequency. With the newer SAP versions the TC SM36 canbe used to plan these jobs, however first delete the planning before using thetransaction to insure the jobs are only in the system as required. Multiple executionsof the SM36 will plan additional executions. 15
  16. 16. Contents Periodical Basis Jobs Periodical Application Jobs Periodical Monitoring Tasks SAP AG 2005, BW System Administration / 16 16
  17. 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. SAP AG 2005, BW System Administration / 17 17
  18. 18. Monitoring Query Performance – ST03 1. Switch to 2. Choose right 3. Sort by 4. Check for ‚Expert Mode‘ Aggregation number of log running and press Level (Cube or navigations queries ‚Save View‘ Query level) The data comes from table RSDDSTAT, which contains all this information + some more details. Sometimes it is useful to table RSDDSTAT directly SAP AG 2005, BW System Administration / 18 18
  19. 19. Basis Monitoring - CCMS CCMS – Monitor set for BW  SAP AG 2005, BW System Administration / 19Basis parameters for BW systems: Note 19
  20. 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 are not 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  SAP AG 2005, BW System Administration / 20Basis parameters for BW systems: Note 20
  21. 21. Basis Monitoring - General RSRV checks Review EWA Reports SAP AG 2005, BW System Administration / 21 21