Sap Netweaver Bw Administration And Monitoring Pdf

sap netweaver bw administration and monitoring pdf

File Name: sap netweaver bw administration and monitoring .zip
Size: 29640Kb
Published: 18.05.2021

We get asked all the time: what is SAP Basis?

In many BW Projects, we have seen Basis team and the BW consultants searching around for tracing the regular and best housekeeping options and activities provided by SAP for improving the performance of BW Production servers. I have made an attempt to summarize and mention most of the BW House Keeping activities under a single umbrella. Its recommended to include them while designing the process chain. In process chain, before loading the data to cube use the delete index process and load the cube and create index.

SAP NW BW Admin Cockpit

Reading Sample This reading selection offers the weekly administration and perfor- mance tuning tasks to help you keep your database small and your system operating within healthy limits.

The book provides tasks for daily, weekly, monthly, quarterly, and yearly completion. Consistent housekeeping keeps the database small and the system operating within healthy limits. While some of these tasks only need to be performed once weekly, others, such as process chain monitoring, may need constant supervision. We recommend that you consider any opportunity to automate weekly tasks, such as by leveraging SAP Solution Manager to configure thresholds and send alerts by e-mail.

Reporting of performance or systematic issues for weekly checks should be han- dled the same way as for issues with daily checks. Any sensitive or critical checks should be executed first so that the technical team is knowledgeable and aware of the systems operational health. Lets first look at weekly administration tasks.

Over time, thresholds for normal behav- ior will be apparent; these thresholds should be documented, and any abnormal behavior or deviations above or below normal should be noted and investigated. The resulting reports provide historical trends of each Review EarlyWatch Alert systems performance to aid in the analysis of performance related issues, as Rebuild BWA indexes seen in Figure 8. Clean up PSA and change logs Clean up application logs and trace files Execute housekeeping tasks Execute RSRV consistency checks The majority of these administration tasks, such as rebuilding BWA indexes, cleaning up logs, and housekeeping tasks, ensure that your system is operationally healthy and stable enough to support future demand.

The remaining administra- tion tasks, such as reviewing the EarlyWatch Alert and executing Transaction RSRV consistency checks, arm you with information about the relative health of your system. Depending on the complexity of your system or the expected reso- lution, acting on the information provided may need to be handled in a more structured way, such as a project or simply planned in advance as part of the monthly, quarterly, or yearly administration tasks.

The first weekly task should Figure 8. Recommendation 8. It is designed to help customers take rapid action before potential problems lead to unplanned downtime. The EWA pro- vides customers with information about the stability and performance of their After the initial configuration and activation in SAP Solution Manager, the first SAP systems, and it focuses on the following aspects: EWA session is automatically created for each system marked for monitoring.

By default, all subsequent EWA sessions are scheduled once a week, on Mondays. If the overall rating is yellow Configuration analysis 2 or green, results are sent to SAP Support only once every four weeks. It is also possible to have the reports e-mailed automatically to specific e-mail addresses.

Application analysis If the EWA issues a red or yellow rating, the reasons for the rating are specified Workload analysis right below the rating in the alert overview see Figure 8. Investigate must be activated and scheduled. The EWA collects performance data by run- the root cause of the issues and take corrective action.

The collected data is sent BW Reporting and Planning This subsection analyzes SAP BW runtime statistics and frontend distribution, checks query profiles, identifies the most popular queries and poorest-per- Figure 8.

BW Warehouse Management This subsection analyzes dataload statistics; identifies top DTPs, largest requests, and top InfoProviders by load requests and upload volume; and reviews process chain and change run performance. For example, if the report is always red because of a known and accepted issue, the monitoring team becomes falsely Performance DB accustomed to the red rating and does not recognize when critical issues do Landscape Service Information indeed arise.

This is a common behavior, but it is extremely reckless! If the issue cannot be resolved or is deemed an accepted risk, ABAP SP Maintenance adjust the rating so that the monitoring team is not lulled into inaction.

It is always the first document that should be requested to assess Application Profile the status of an existing system because it provides an overview supported by the 10 SAP System Operating Update Errors exact details of every facet of the system, and it usually provides specific clues to Program Errors ABAP Dumps solve performance issues and preserve operational health.

For this reason, we Password Policy strongly recommend activating and monitoring the EWA for all productive systems. Another slower Database Parameters growth scenario is an InfoCube, which is compressed with the elimination of 14 Database Administration Database Growth zeroes. In both of these scenarios, the deleted or eliminated data still remains in Database Release the BWA index but is not used for reporting. As a result, the BWA index consumes more memory than necessary. In addition to index growth, you should BW Reporting and Planning also adjust or rebuild indexes after changes are made to the relevant InfoProvider.

BW Warehouse Management If delta indexes are used, routinely merge them with the main index. As seen in 2 in Figure 8. Due to potentially long run times and the impact on query performance, you should schedule this utility during a period of low system usage by end users when pos- sible. Figure 8. For example, in a scenario with two groups, A and B, the rebuilds of one group A can be scheduled during the first and second weeks of every month, and the rebuilds of the second group B can be scheduled during the third and fourth weeks.

As indexes grow in size, you may find that you need to reorganize or redistribute indexes across the blades in the appliance. The same messages from the monitor can also be seen in the system checks in Trans- Figure 8.

BWA alerts can be of the four recommended methodologies to check potential database growth. These checks can also be The other methodologies are avoidance, summarization, and archiving.

These consistency checks should be scheduled on a routine basis. Large PSA and DSO change log tables impact data load performance, increase the downtime for maintenance, and increase the cost of data storage.

The size of the PSA and change logs can be explained by the fact that entries in these tables are never updated or overwritten. The only operations on these tables are inserts or deletions. For example, full loads on a periodic basis increase the size of the PSA table much faster than the actual data target, which is either overwritten in the case of a DSO or InfoObject, or dropped and reloaded in the case of an InfoCube.

For delta loads, changes to previously extracted records are overwritten in DSOs and InfoObjects or compressed into a single record in InfoCubes assuming that compression occurs routinely. From a strategic perspective, the only reasons to retain entries in the PSA tables are to facilitate error resolution and to mitigate the need to re-extract data from sources that are either poor performing or delta capable.

In the case of full loads, only the latest PSA entry should be retained, and all other entries can be deleted once the latest entry is successfully loaded into the PSA. For delta loads, a reten- tion period for PSA data should be set based on the risk of data loss i. In most cases, 15 days is more than sufficient to mitigate this risk. In many cases, a full repair load can be executed to recover any lost deltas without a sig- nificant performance impact, so this risk is usually applicable for delta Data- Sources that require the population of setup tables in the source system, such as Figure 8.

The deletion strategy for PSA tables should differentiate between master data 8. Change logs should be treated like delta loads for transaction data. An During the load processing of large volumes of master and transaction data into SAP BW, there is usually a significant amount of storage consumed by temporary additional consideration should be the periodicity of the data load from the transaction data and system-related metadata.

Routine housekeeping activities source. For example, if a full InfoPackage is loaded monthly, the previous should remove unused, unwanted, and unneeded data. Regularly performing months load should be retained in the PSA, so the retention period should be 31 these activities ensures optimum utilization of system resources and increased days. Table 8. BW system. Even though the acceptance of patterns in the selection criteria simplifies mainte- nance of the deletion jobs, PSA and change log tables are still too easily omitted from cleansing.

To combat this, custom programs published on SCN can help identify those tables with entries that are unmanaged or otherwise excluded from existing deletion variants. We do not recommend that you use these programs routinely because PSA deletions should not be scheduled while data is being loaded. Therefore, it is best to schedule the relevant process variants directly in the process chains after data has been loaded.

This helps mitigate the risk of database contention by ensuring that these conflicting jobs do not overlap. Schedule a weekly PSA and change log deletion process chain to catch any data loads for which deletions are not scheduled as part of the load process chains. This helps mitigate the risk that a PSA table or change log could grow exponentially, thereby keeping the database growth in check and optimizing system resources.

Keeping these tables cleansed on a weekly basis ensures optimal per- parameter screens accept parameters with patterns on DataSource for PSA tables formance of the ABAP system overall.

This section will cover routine housekeep- and DSOs for change logs , as illustrated by 1 in Figure 8. The number of days ing jobs that should be executed routinely to minimize the impact of log and trace growth over time. Ironically, many routine housekeeping jobs gen- DELETE, enter an appropriate date from which to cleanse logs, and select the erate more application logs, which can consume more storage capacity than the checkbox to delete logs that can be deleted before their expiry date, as shown in housekeeping jobs free up.

For example, every request that is deleted from the PSA in Figure 8. Use the option Only calculate how many to show how many logs or change log generates an application log. Therefore, it is important to clean appli- can be deleted. Before cleansing, consider the util- weekly basis.

Some of the tasks in this task list require that param- cleansed to reclaim that storage capacity and improve the overall performance of eters be entered; these tasks each contain a text editing icon in the parameter administering the system.

Rememberthe fewer logs in the table, the quicker it column, as illustrated by 2. In most statistics cases, the report can be scheduled, but the results should be monitored for excep- RSM Delete update requests tions or errors. Schedul- ing so many elementary tests for each InfoProvider would be a laborious burden and likely not worth the effort. Fortunately for you, SAP has provided combined tests see Figure 8. These combined tests should be evaluated and scheduled for routine batch processing.

Well examine the following: Figure 8. Therefore, you should analyze the logs using Transaction Rebuilding DB indexes and statistics SLG1 for any combined tests that are deemed valuable to schedule on a weekly basis, as shown in Figure 8. The first task is monitoring BI statistics. The system records run- nical BI Content queries and web templates provide ready-made views of the times for statistical events by calculating the difference between the start and end information for flexible analysis.

See Figure 8. This indicates that database partitions in the F-fact table are aggregated into a single record in the E-fact table. Potential solutions include compressing dropped from the F-fact table. If none of these solu- managed when a high number of delta records results in substantial growth. Com- tions are satisfactory, consider installing BWA which may be a regretful pur- pression provides performance benefits from a data loading perspective, as well chase or migrating to SAP HANA.

Ideally, you should execute compression after each data load, although it is not Query Runtime by Component necessarily a critical path item. Monitor this process chain exactly like any other process chain. To combat this phenomenon, you should also rebuild DB indexes on a rou- tine basis. You can delete and repair DB indexes in dialog mode or delete and re-create them in a batch.

Statistics queries and web reports should be executed and monitored for excep- tions to average runtimes on a weekly basis. You should investigate and resolve The database statistics are used by the system to optimize both query and com- any significant exceptions or deviations from normal.

BW310 SAP BW - Enterprise Data Warehousing

Each of these roles creates a complete menu structure for the use of ILM in an application system, that is, in the Retention Warehouse system. The roles have the following attributes: Access to the complete scope of functions with administration rights Access to a limited scope of functions for Line of Business-specific rules without administration rights More information: Assigning Authorizations for SAP NetWeaver ILM Functions Terminology: Audit package replaces work package For the purpose of exactness and standardization, the term "audit package" replaces the term "work package". End-to-End Audit Area An audit area defines the content and purpose of a check, for example, of a tax audit or product liability check. The retention rules are defined according to the audit area. This means that the relevant retention rules are based the purpose of a check. In Retention Warehouse, you can define different audit package templates based on an audit area. You create an audit package on the basis of an audit package template.

Reading Sample This reading selection offers the weekly administration and perfor- mance tuning tasks to help you keep your database small and your system operating within healthy limits. The book provides tasks for daily, weekly, monthly, quarterly, and yearly completion. Consistent housekeeping keeps the database small and the system operating within healthy limits. While some of these tasks only need to be performed once weekly, others, such as process chain monitoring, may need constant supervision. We recommend that you consider any opportunity to automate weekly tasks, such as by leveraging SAP Solution Manager to configure thresholds and send alerts by e-mail.

Query Runtime Statistics2. Context menu for access to more detailed information or BI TransactionException definition for intuitive display of critical monitoring data optional. Business Package BI Administration 1. BI Administration Cockpit can run in a central or in a local portal. SAP NetWeaver 7. Schedule Technical Content Process Chains only needed if not done in step 1 3. Check Updating of Statistics 2.

BI Admin Cockpit

Embed Size px x x x x Query Runtime Statistics2. Context menu for access to more detailed information or BI TransactionException definition for intuitive display of critical monitoring data optional.

Begin with system landscape design, system connections, change management, and system parameters. Implement a layered scalable architecture and adopt effective data loading and management techniques. Your account Help. The comprehensive resource.

bw administration cookpitpdf

SAP HANA Administration

Embed Size px x x x x Query Runtime Statistics2. Context menu for access to more detailed information or BI TransactionException definition for intuitive display of critical monitoring data optional. Business Package BI Administration 1. BI Administration Cockpit can run in a central or in a local portal. SAP NetWeaver 7. Schedule Technical Content Process Chains only needed if not done in step 1 3.

Но у него не выдержали нервы. Он слишком долго говорил ей полуправду: просто есть вещи, о которых она ничего не знала, и он молил Бога, чтобы не узнала. - Прости меня, - сказал он, стараясь говорить как можно мягче.

Дверь повернулась до положения полного открытия. Через пять секунд она вновь закроется, совершив вокруг своей оси поворот на триста шестьдесят градусов. Сьюзан собралась с мыслями и шагнула в дверной проем.

Беккер молчал. - Ja. Дверь слегка приоткрылась, и на него уставилось круглое немецкое лицо. Дэвид приветливо улыбнулся.

4 COMMENTS

Charlotte L.

REPLY

Donjon et dragon 2e edition pdf persuasion jane austen pdf download

Hope F.

REPLY

If you includes these too then ur blog will be incomparable : :.

Eve K.

REPLY

Weekly monitoring and administration can prevent small issues from growing into critical est SAP BW objects; analyzes the number and types of each InfoProvider; ana- lyzes configuration SAP NetWeaver AS ABAP. SAP NetWeaver AS.

Platt D.

REPLY

Implementing SAP NetWeaver BW on SAP HANA Implementing SAP NetWeaver the Administration Console of the SAP HANA Studio Monitoring SAP HANA.

LEAVE A COMMENT