on 08-23-2016 10:05 AM
Hello Experts,
We are working on SAP PI 7.4 dual stack.Currently we are facing issue with the abrupt increase in the database.
The Issue has started from last 15 days.Before that, the increase in database size was very normal. Not sure what happened in last 15 days that is causing the database to grow abruptly since almost same number/sizeof message is flowing now also.Deletion job is also working fine.
I have checked many notes and links,but nothing is working.
Can some one please suggest the reason for this.
Thanks,
Rashid Eqbal
SAP PI Consultant
Hello Rashid,
the exact DB table has to be known in order to understand the reason. Most probably the problem is because of long retention period for processed messages. To get more details, do the following:
1. Execute the reports
- RSXMB_SHOW_STATUS
- RSXMB_SHOW_REORG_STATUS
2. Execute SQL query:
SELECT table_name from ALL_LOBS where segment_name='SYS_LOBxxxxxxxxxxxxxxxx$';
where segment name is a segment which occupies the biggest DB space in your case.
Best regards,
Vadym
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vadym,
Earlier the retention period was 30 days.Now that has to be changed to 15 days.
I am mentioning below the status of report RSXMB_SHOW_STATUS and RSXMB_SHOW_REORG_STATUS.
Table SXMSCLUP and SXMSCLUR has highest number of entries.
*******************************************RSXMB_SHOW_STATUS*******************************************
| |=========================================================================
| |Overview (Time Stamp Not Included)
| |
| 828618|Number of Messages in Database
| 828618|Number of Messages in Client
| 828618|Number of Messages for Reorganization in Client
| 10353|Number of Messages to Be Archived in Client
| |Number of Logically Deleted Messages in Client
| |Number of Archived and Logically Deleted Messages in Client
| |
| |================================================================================
| |Message Status
| |
| |Message Status: 000
| |Message Status: 001
| |Message Status: 002
| 818203|Message Status: 003
| |Message Status: 004
| |Message Status: 005
| |Message Status: 006
| |Message Status: 007
| |Message Status: 008
| |Message Status: 009
| |Message Status: 010
| |Message Status: 011
| |Message Status: 012
| |Message Status: 013
| 57|Message Status: 014
| |Message Status: 015
| |Message Status: 016
| |Message Status: 017
| 3|Message Status: 018
| |Message Status: 019
| 2|Message Status: 020
| 10353|Message Status: 021
| |Message Status: 022
| |Message Status: 023
| |Message Status: 024
| |Message Status: 025
| |Message Status: 026
| |Message Status: 027
| |Message Status: 028
| |Message Status: 029
| |Message Status: 030
| |Message Status > 030 to < 100
| |Message Status: 100
| |Message Status: 101
| |Message Status: 102
| |Message Status: 103
| |Message Status: 104
| |Message Status: 105
| |Message Status: 106
| |Message Status: 107
| |Message Status: 108
| |Message Status: 109
| |Message Status: 110
| |Message Status: 111
| |Message Status: 112
| |Message Status: 113
| |Message Status: 114
| |Message Status: 115
| |Message Status: 116
| |Message Status: 117
| |Message Status: 118
| |Message Status: 119
| |Message Status: 120
| |Message Status: 121
| |Message Status: 122
| |Message Status: 123
| |Message Status: 124
| |Message Status: 125
| |Message Status: 126
| |Message Status: 127
| |Message Status: 128
| |Message Status: 129
| |Message Status: 130
| |Message Status > 130
| |
| |================================================================================
| |Adapter Status
| |
| |Adapter Status of Messages with Message Status: 003
| 818203|Adapter Status: 000
| |Adapter Status: 001
| |Adapter Status: 002
| |Adapter Status: 003
| |Adapter Status: 004
| |Adapter Status: 005
| |Adapter Status: 006
| |Adapter Status: 007
| |Adapter Status: 008
| |Adapter Status: 009
| |Adapter Status: 010
| |Adapter Status > 010
| |
| 828618|Number of Entries in Table SXMSPMAST
| 828618|Number of Entries in Table SXMSPEMAS
|8537722|Number of Entries in Table SXMSPVERS
| 10416|Number of Entries in Table SXMSPERROR
|8537722|Number of Entries in Table SXMSCLUP
|8549020|Number of Entries in Table SXMSCLUR
**************************************RSXMB_SHOW_REORG_STATUS**************************************
Overview
========
Retention periods and message and adapter status ignored in the following
Number of messages in DB: 828.628
Number of messages in client: 828.628
Number of messages in client still to be reorganized: 828.628
Retention Periods
=================
Type Status Action | Configuration
| Start Time (INDIA)
--------------------------------------------------------------------------------
Asynchronous Without errors Archiving | 015 Day(s)
| 08.08.2016 15:22:42
|
Asynchronous Without errors Delete | 015 Day(s)
| 08.08.2016 15:22:42
|
Synchronous With errors Delete | 015 Day(s)
| 08.08.2016 15:22:42
|
Synchronous Without errors Delete | 015 Day(s)
| 08.08.2016 15:22:42
Archiving
=========
Message and adapter status is ignored in the following
- Msgs not in retention period (can be archived): 10.353
- Msgs in retention period (cannot be archived): 0
Message and adapter status is considered in the following
- Msgs not in retention period (can be archived): 10.353
Delete
======
Message and adapter status is ignored in the following
- Asynchr. msgs not in retention period (can be deleted): 56.590
- Asynchr. msgs in retention period (cannot be deleted): 761.685
Message and adapter status is considered in the following
- Asynchr. msgs not in retention period (can be deleted): 56.532
Message status is not considered in the following
- Synchr. msgs not in retention period (can be deleted): 0
- Synchr. msgs in retention period (cannot be deleted): 0
Message status is considered in the following
- Synchronous messages without errors to be deleted: 0
- Synchronous messages with errors to be deleted: 0
***************************************************************************************************************
Hi Vadym,
I have set up the deletion Job to delete the message.I have not gone with the archival option.
As far I know, for the manually cancelled messages,message have to be archived first and then gets deleted.Do I have to set up the Interface for archive so that messages are deleted.Is there any other way in which I do not need to set up the Interface for archival and the normal deletion job deletes the cancelled messages as well.
Hi Rashid,
You can find any answer for your questions in the following note:
872388 - Troubleshooting Archiving and Deletion in PI
Also please check this site too about the Archiving and Deletion jobs:
Regards,
Balázs
User | Count |
---|---|
81 | |
24 | |
11 | |
9 | |
7 | |
5 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.