Deleting SXMSPFRAWH Data in SAP XI


The performance headers for XI messages are maintained in SXMSPFRAWH table. You should run SAP_XMB_PERF_REORG job (ABAP report SXMS_PF_REORG) regularly to keep this table from growing endlessly with new XI messages coming in.

If you have not run this job for years or months, this table might already have a huge amount of data. Before you schedule SAP_XMB_PERF_REORG job, do the following:

1. Call SXMB_ADM, go to Integration Engine Configuration -> Category PERF and set these parameters:


2. Call transaction SE11 and create an index with the following details:
Table name: SXMSPFRAWH
Index ID:      AGG
Short description: Index for aggregation
Choose: "Non-unique index" and "Index in all database systems"
Field names:
SENDER
RECEIVER
COMPONENTID
PROCMODE
SOURCE
LASTTS

3. Run SAP_XMB_PERF_REORG job (ABAP report SXMS_PF_REORG) on a weekend or during low activity time. Do not set this job as a periodic one yet as the first run will delete all the data prior to 15 days.

4. After the first run completes, delete the index created in step 2.

5. Schedule the following jobs to aggregate and reorganize XI performance data with the settings provided:
Job name: SAP_XMB_PERF_AGGREGATE, ABAP Program: SXMS_PF_AGGREGATE Period:Hourly
Job name: SAP_XMB_PERF_REORG, ABAP Program: SXMS_PF_REORG Period:Hourly

If these steps do not help, you might need to implement SAP note 1082836. Before you apply the note, open an OSS message (Component: BC-XI-IS) to consult SAP as recommended in the note.

Comments

Post a Comment

Popular posts from this blog

OS/DB Migration - CMD. STR, TOC, EXT, R3load, DDLDBS.TPL and more

Image
With increasing need to improve performance or reduce costs or vanishing support for operating systems/databases it becomes inevitable to migrate to a better OS or DB. We feel take a quick look at the primary ingredients of the tools for OS/DB migration handled by R3SETUP. Tools - R3load, R3ldctl and R3szchk R3ldctl creates STRucture files, TemPLate files by reading the technical settings for table/indexes in SAP data dictionary. R3szchk calculates the database size object sizes (EXTent files) for the target system based on the STR files created by R3ldctl. The EXT and STR files can be later split into smaller groups. The most crucial tool R3load is responsible for unloading and loading data from the database. R3load uses the files created by R3ldctl and R3szchk and dumps the data into compressed binary format as .001, .002 .. files. It uses cmd files to achieve the task. If the cmd files are not present, it creates on its own. Files Command files*.cmd  are creat...
Read more

Fixing Inconsistent Table - Table activation fails due to inconsistency between DD and DB

If you find a table to be available on the database, but not active in ABAP dictionary, try calling SE14 as DDIC user, enter the table name and choose Table > Reconstruct, Execute. If this method fails follow these steps: Call transaction code SE37 and execute the function module  DD_TABL_ACTM with single test On the next screen, do not change any other field except the following and set them as shown below: MODE: 12 NTAB_PUTSTATE: N TABNAME: <enter the correct table name> Click on Execute The export parameter ACT_RESULT should show 0. To verify if the inconsistency is fixed, call transaction SE14 > Extras > Database Object > Check and  SE14 > Extras > Runtime object > Check.
Read more

301 Redirect Using SAP Web Dispatcher

301 redirects are typically used to redirect accesses that include www to non-www or vice-versa. Example, when you call http://blogger.com, the call is redirected to www.blogger.com. An end-user may prefer to call a URL in any manner. You must ensure that all these calls are redirected to relevant URLs with content. SAP web dispatcher can be configured to send a redirect (301) to the client. To enable redirection add icm/HTTP/redirect_<xx> to the web dispatcher's profile file. The parameter uses the following syntax: icm/HTTP/redirect_<xx> = PREFIX=<URL prefix>[, FROM=<pattern for URL>, FROMPROT=<incoming protocol>, FOR=<pattern for host name:port>,TO=<new URL prefix>, PROT=<protocol>, HOST=<host>, PORT=<port number/name>] Let's say you want to redirect all the HTTP requests on mysource.com on 80 port to mytarget.com on HTTPS 443 port icm/HTTP/redirect_0 = PREFIX=/, FROM=*, FROMPROT=http, FOR=mysource.com:80,...
Read more