Below are few of my learnings

1. Operating System

2. Database

3. Application

4. Middleware

5. SAP BASIS Daily monitoring and checks

6. Oracle Advanced level Compression

Operating system referred to below is of HP UX and Database is Oracle.

OS level Parameters

HP-UX 11.31 Itanium and PA-RISC (HP-UX 11iv3)

1. Ensure you follow the OSS note.

SAP on HP-UX: OS Kernel Parameter Recommendations (SAP Note 172747)

2. Size the SGA based on the capacity (CPU and RAM) on Database servers

Oracle 11g – 1431798 – Oracle 11.2.0: Database Parameter Settings

Database SGA

SGA Max size

Shared pool size

DB Cache size

Log buffer

Db writer processes

Redo log size

3. Application level parameters :

Schedule a SAP Technical Performance Optimization Service on solution manager and based on the report change the below parameters.

ICM Parameters

icm/traffic_control

icm/max_sockets

icm/max_conn

icm/server_port_1

icm/server_port_2

icm/HTTP/server_cache_0/max_entries

icm/HTTP/server_cache_0/memory_size_MB

icm/HTTP/server_cache_0/size_MB

icm/min_threads

icm/host_name_full

icm/server_port_0

icm/keep_alive_timeout

mpi/total_size_MB

Buffers

rsdb/ntab/entrycount

rsdb/ntab/ftabsize

rsdb/ntab/sntabsize

ztta/parameter_area

ztta/roll_area

rdisp/ROLL_SHM

rdisp/ROLL_MAXFS

rdisp/PG_MAXFS

abap/heap_area_dia

abap/heap_area_nondia

abap/heap_area_total

ztta/roll_extension

rdisp/wp_ca_blk_no

rdisp/appc_ca_blk_no

abap/buffersize

rsdb/cua/buffersize

rsdb/ntab/irbdsize

rsdb/obj/buffersize

rsdb/obj/mutex_n

rsdb/obj/large_object_size

rsdb/obj/max_objects

rtbb/max_tables

rtbb/buffer_length

sap/bufdir_entries

zcsa/db_max_buftab

zcsa/presentation_buffer_area

zcsa/table_buffer_area

rsdb/esm/large_object_size

rsdb/esm/max_objects

rsdb/esm/buffersize_kb

rsdb/otr/mutex_n

rsdb/otr/max_objects

rsdb/otr/buffersize_kb

abap/heaplimit

em/blocksize_KB

ict/exclude_compression                                *.zip,*.rar,*.arj,*.z,*.gz,*.tar,*.lzh,*.cab,*.hqx,*.ace,*.jar,*.ear,*.war,*.gzip,*.uue

Daily Monitoring

Daily Checks

Database overview                                             DB02/DBACOCKPIT

Table space maintenance                                 DBACOCKPIT/BRTOOLS

Correcting ST22 dumps & SM21 errors          ST22/SM21

File system monitoring                                       DBACOCKPIT/OS level

Jobs Monitoring                                                   SM37

Creating missing indexes                                  DBACOCKPIT

Work Load Analysis                                            ST03

Database Alerts Check                                      ST04

Check TemSe Status                                          SP12

Check Spool Output Requests for Errors        SP01

Backup Log Overview                                        DB12

Database Locks Check                                      DB01

Backup Calendar                                                                DB13

SMLG                                                                     SMLG

Transport Management System                       STMS

ICM Status                                                            SMICM

Overview of Send Orders                                  SOST

Work Process Status                                           SM50

Running Jobs Status across all systems        SM66

SAP Server / Work Process Status                   SM51

Check Lock Entries                                             SM12

Update Requests List                                         SM13

Dump Analysis                                                    ST22

Operating System and FS Check                     ST06

System Log Analysis                                          SM21

Buffer Analysis and Status                                ST02

CRM Checks

CRM Middleware Monitoring Cockpit              SMWP

Analyze Object and Sub Object logs               SLG1

qRFC Outbound Queue Monitor                       SMQ1 or SMWP or  RZ20

QOUT Scheduler                                                                 SMQS

qRFC Inbound Queue monitor                         SMQ2

QIN Scheduler Status                                         SMQR or SMWP or RZ20

Message Flow Statistics                                     SMWMFLOW

BDoc Messages/Summary                                               SMW01/ SMW02/ SMW02A/ SMW03

Check Flow Definitions                                      SMO8FD

Monitor Load Status                                            R3AM1 or SMWP

Monitor Request                                                  R3AR3 or SMWP

Replication objects                                              SMOEAC

Check Object Types from Admin Console     SMOECK

Status of generation processes                        GENSTATUS

Trace Status                                                         SMWTAD

Housekeeping

General Housekeeping

SAP_REORG_JOBS

SAP_REORG_SPOOL

SAP_REORG_BATCHINPUT

SAP_REORG_ABAPDUMPS

SAP_REORG_JOBSTATISTIC

SAP_REORG_UPDATERECORDS

SAP_COLLECTOR_FOR_JOBSTATISTIC

SAP_COLLECTOR_FOR_PERFMONITOR

SAP_COLLECTOR_FOR_NONE_R3_STAT

SAP_REORG_PRIPARAMS

SAP_REORG_XMILOG

SAP_CCMS_MONI_BATCH_STARTUP_DP

SAP_SPOOL_CONSISTENCY_CHECK

SAP_REORG_ORPHANED_JOBLOGS

SAP_CHECK_ACTIVE_JOBS

SAP_DELETE_ORPHANED_IVARIS

SAP_REORG_ORPHANED_TEMSE_FILES

DBA:CLEANUPLOGS

DBA:UPDATESTATS

DBA:CHECKDB

CRM Specific

SAP_REORG_CRM_PRODUCTS_INACTIV

SAP_SOA_ARCHIVE_PLAN

SAP_SOA_DELETE_HISTORY

SAP_SOA_DELETE_MESSAGES

SAP_SOA_TABLE_SWITCH

SAP_SOAP_RUNTIME_MANAGEMENT

ZCRM_ICI_TRACE_DELETE

ZRESTART_INBOUND

SMWP_BATCH/MW_S_COCKPIT_COLLECTOR_DWY

GN_GENERATE_CHECK/MW_S_CHECK_P_DWY

GN_WORKLIST_GENERATE/MW_S_GENERATE_P_DWY

SMO6_REORG2/MW_S_SMO6_REORG2_DWY

RSRLDREL

RSRLDREL – Object Links

BSP_CLEAN_UP_SERVER_COOKIES

HRBCI_ATTRIBUTES_BUFFER_UPDATE

Application Log Size (BALHDR)

System-wide performance can be impacted due to the large size of the application log tables, BALHDR etc. Reduce the number of entries in table BALHDR on a regular basis. Use transaction SLG2 to delete entries out of table BALHDR as described in SAP Note 195157.

Middleware tables SMW*_BDOC* can grow very large

Depending on the load of your trace or middleware log, tables can grow larger than 100 MB. Consequently, it can often be observed that expensive insert and read operations take place on the SMW3_BDOC* tables. Take administrative actions to reduce the size of the tables according to SAP Note 206439. Only increase the trace level if necessary.

Furthermore SAP Note 835761 has to be implemented to remove the BDocs in status I04.

Schedule report SMO6_REORG2 on a daily basis.

If the table SRRELROLES contains many entries with the OBJTYPE TRANSID consider the SAP Note 1385766 to reduce them. If the table SRRELROLES contains too many entries with the OBJTYPE BUS* you have remove them by archiving the corresponding objects using the transaction SARA.

MIME Repository consistency check:

After each SP import, execute the report RSIR_MIME_EXPIRY_CLEANUP on node /SAP in order to avoid repetitive download of static mime objects from the server that otherwise may be stored in the browser’s cache. Make sure Z-style sheets have at least 1 week caching time defined in the P-System.

CRM Middleware (CRM MW) Alert Monitor

Based on the SAP CCMS alert monitoring infrastructure Use transaction RZ20. This is available under the monitor collection “SAP CRM Monitor Templates” with the name CRM Middleware.

The CRM MW Alert Monitor monitors the following:

CRM MW-specific qRFC queues in SAP CRM system

CRM MW-specific qRFC queues in SAP ERP back-end system

The qRFC QIN scheduler of the SAP CRM system

The qRFC QOUT scheduler of the SAP CRM system

The processing status of messages in the BDoc message

The replication and realignment queues and the R&R queue demon

Status of the Communication Station

Enqueue Server shows slow performance –

We can go ahead and set the profile parameters .

1.       Note : 1353668 – Locks are retained due to network instabilities

2.       Set the instance profile parameter in the ABAP application server:

3.       enque/sync_dequeall = 1.

4.       Also set the following parameter in the standalone enqueue server:

5.       enque/encni/set_so_keepalive = TRUE

Follow the recommendations in SAP Note 1791958 to reduce the lock time on table VARINUM and avoid scheduling several background jobs simultaneously for the same program. Correction is not delivered in a Support Package. If required, you can implement the attached correction in the note.

Application log is too large

Should delete the obsolete entries. Need business decision to delete these entries (specially on the time – from which date can we go ahead and delete the entries).

Rebuilding the indexes – Run report RSORATD and check for the index storage quality and based on the requirement we can rebuild the indexes.

Please note that this report is very time and cpu consuming. So need to discuss on when we can run this report.

No reorg job scheduled to reduce size of tables SRRELROLES

706478 – Preventing Basis tables from increasing considerably

Growth of CRM_ICI_TRACES can slow IC

1712755 – Large ICI trace log affect the performance of IC function

It is recommended to keep the ICI trace log in a small size.

Delete the ICI trace on a regular basis.

To do this, you need to run program CRM_ICI_TRACE_DELETE to delete the old ICI trace log regularly.

By default, the program is pre-set to delete the ICI trace record log older than 14 days. You may set up your own delete trace age option according to the speed of the log growing in your system.

CRM WebClient performance related settings

Clear the inconsistent MIME objects. Refer to SAP Note 1277476 to clear out the inconsistent Mime objects and make the caching sufficient.

Adjust ICI trace parameter settings and remove out-of-date traces. Follow SAP Note 1712755 to adjust ICI trace settings and remove redundant ICI traces to improve the CTI integration performance.

To prevent a deadlock for IDoc update in parallel, you must configure at least number of dialog work processes >= n + rdisp/rfc_min_wait_dia_wp +1. Refer to SAP Note 565527 -Deadlock when using local update (IDocs). To avoid system hanging due to tRFC cascade, set rdisp/rfc_min_wait_dia_wp parameter >= 66% *(total number of DIA processes) per instance, refer to SAP Note 726148 -SAPLARFC occupies all work processes, RFC cascade.

Fragmented indexes

Based on the results of the Oracle Automatic Segment Advisor

(SQL: “Space_SegmentFragmentation_SegmentAdvisor”),the following indexes have allocated more than 100 MB of unused space and their storage quality is <= 50 %.

Rebuild the mentioned indexes as suggested by Oracle database in order to reduce fragmentation, and also regularly check for fragmented indexes. See SAP Note 771929 for more information regarding index fragmentation.

Database statistics for RFC-related tables

The statistics for RFC related Tables (ARFC*, TRFC*, etc.) are still generated through the standard BRCONNECT functionality. When the load is heavy and the RFC tables are inserted and deleted, the Cost Based Optimizer of Oracle may use the wrong access path. The transaction then takes a long time to execute.

Impact:

The Cost based Optimizer of Oracle may choose a sub optimal access path, resulting in expensive database access.

Recommended Task:

Follow the instructions of SAP Note 1020260 to generate the appropriate statistics.

ICM cache Configuration

Description:

The time recorded in Http Watch trace is longer than the time recorded in ST12 trace, which indicates that there is a lot of time spent on ICM.

The ICM cache was with default setting and was not tuned.Impact on Business:It will negatively affect the performance for HTTP request from BSP page to CRM backend.

Recommended Task:

Tune the following parameters as recommended.

Set icm/HTTP/server_cache_0/size_MB to 0 to disable the disk-level cache

Set icm/HTTP/server_cache_0/memory_size_MB to 1792

Set icm/HTTP/server_cache_0/max_entries to 25000

Refer the following documentation for more details: https://help.sap.com/saphelp_nw70ehp1/helpdata/en/48/405cbfca2331c3e10000000a42189d/frameset.htm

Please follow the sections from the SAP CRM Consultants Cook book.

https://scn.sap.com/docs/DOC-36041

Oracle Advanced level Compression

Compression for OLTP and OLAP.

Please refer to the below notes.

SAP note 740897 (Info about the Oracle license scope), Advanced Compression is an option contained in the Oracle database license offered by SAP

1289494 – FAQ Oracle compression

1436352 – Oracle Database 11g Advanced compression for SAP Systems.

Thanks for reading…

Ravi

New NetWeaver Information at SAP.com

Very Helpfull

 

 

User Rating: Be the first one !