Archiving vs Deleting messages in PI/XI

Hi, I have successfully set up archiving on the PI system. No separate delete jobs are running, only the delete job in the connection with the archive process.
The questions is, will archiving delete and keep the DB from growing as good as the delete jobs would? Yes, the archive files need some space on the filesystem, but it seems that only archiving is enough to keep PI in a healthy state concerning the DB size. Am I correct?

Hi,
In XI All the data are transferred in form of messages and it may necessary to Archive data for future references .When we do the Archiving all the processed messages will be out of system and also it improves the performance. In General Rule the messages are multiplied into 10 times when compared to data which is sent,(Ex. If the data is 1 MB, the size of the message will be 10 MB.
Messages that have been processed correctly are deleted by default. You must archive all messages that are not to be deleted. Since correctly processed messages are flagged as either To Be Archived or To Be Deleted (and because this indicator cannot be changed), you must decide which messages you want to archive before the first message is processed.
History entries are spots for observing XML message processing. They are generated by persisting at the end of a processing step for an XML message and contain the current status and the execution date.
History entries remain in the database for an unspecified length of time and must be deleted at some stage so that the database table does not overflow. The deletion process only deletes history entries for XML messages that have already been archived or deleted. The history entry is kept in the database for at least seven days after an XML message has been deleted. This is necessary since history entries are also required for the quality of service Exactly Once.
The default retention period is 30 days.
Regards
Aashish Sinha
PS : reward points if helpful

Similar Messages

How to archive and delete messages in SXMB_MONI

Hi all,
We are working on SAP XI Development environment wherein we have File to IDoc scenario running twice daily and creating many messages.
How to archive and then delete these messages ?
Does accumalation of past messages affect the speed and performance of the system?
Thanks in advance.
Ajay

Ajay,
For step by step procedure of how to archieve and delete messages in XI go through the urls:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/402fae48-0601-0010-3088-85c46a236f50
Delete Messages SXMB_MONI
http://help.sap.com/saphelp_nw04/helpdata/en/0e/80553b4d53273de10000000a114084/frameset.htm
Too many questions on Archive/Delete messages.
---Satish

The "Edit Undo" command is extremely slow, taking 10-15 seconds to undo an archive or deleted message. Is this typical?

Everything in Thunderbird seems to be operating fine. I'm very happy with the performance, EXCEPT: The "Edit > Undo" command takes a very long time to take effect. If I accidentally archive a message I want back in my inbox, and hit "ctl Z", it takes a good 10-15 seconds for the message to return to my inbox. Is this typical?

Oops!
Just saw that I hadn't updated my hardware profile, so I just did.

Archiving and Deleting of XML Messages in SAP NetWeaver PI 7.31 single stack

Hello my XI friends!
Need step by Step Guide to Archiving
and Deleting of XML Messages in
SAP NetWeaver PI 7.31 single stack
Similar to these instructions
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0afdd69-a8a7-2d10-7e9a-cbf6fa21c5a7?quicklink=index&overridelayout=true
Regards,
Rinaz

Please check the below blog for archiving java only-(XMLDAS)
http://scn.sap.com/community/pi-and-soa-middleware/blog/2011/11/16/aae-archiving-in-sap-pi-711-with-xmldas
For deletion there is standard delete job..
https://help.sap.com/saphelp_nw73ehp1/helpdata/en/48/b2e0036b156ff4e10000000a42189b/frameset.htm
Message was edited by: Hareesh Gampa

How to set the "delete" button in Mail to actually delete instead if Archive Google Mail messages...

I know these kinds of questions are asked a lot, but I just wanted to ask my specific question for a nice specific answer.
I understand Gmail's thoughts on archiving and labels, but it makes gmail a beast to work with on mail clients. I FINALLY have everything set up perfectly on my Mac's Mail app so that everything syncs and I get no duplicate messages.
The only issue I have is that when I highlight emails and press the "trash" icon in the toolbar (and hit the delete key I assume) the message(s) is/are archived in the All Mail folder instead of going into the "Trash" folder. The only way I can truly delete messages is to drag and drop them into the Gmail/Trash folder in the side bar, which can get tedious.
Is there anyway to set the "delete" icon and delete key to actually send messages to the trash instead if archiving without causing syncing issues, or do I just need to stick with the drag and drop method?
Thank you.
Respectfully,
JAC151

Take a look here: http://jeffschuette.com/2012/03/07/setting-up-apple-mail-to-rock-and-roll-with-g mail/
Jeff explains why it happens and how to deal with it.

PI Message Archive and Delete

Hi Guys,
How will check PI messages whether particular messgae we can do ARCHIVE or particular message we can DELETE ?
Can any one one pls help me on this how to check in PI.
Thanks,
Siva.

Hi Siva,
In SXMB_ADM (t-code) >>> Define Interfaces for Archiving and Retention Periods.
Mention all the interfaces for which you intend the archive the messages.
Click on Multiple Selection>>>> Select all required interfaces >>>> Press F8.
All interfaces will apprear under u2018Interfaces to Be Archivedu2019. Messages of all interfaces that are excluded here will be marked for deletion.
Regards,
Naveen

Delete message without archiving before

Hi,
how can I delete messages (only successful processed messages) without archiving before.
I thing RSXMB_DELETE_MESSAGES just deletes messages archived before.
Thanx
regards
Wolfgang

Hi,
From the help.sap.com link:http://help.sap.com/saphelp_nw70/helpdata/EN/0e/80553b4d53273de10000000a114084/frameset.htm -
"Messages that have been processed correctly are deleted by default. You must archive all messages that are not to be deleted."
So I think as far as you didn schedule the job for archiving the selected interface messages, it will be automatically getting deleted. But you need to configure SXMB_ADM>Integration Engine Configuration>Specific Parameters.
Regards,
VIneetha.

PI 7.11 AAE- Archiving and deletion

Dear All,
I just want to get confirm on my understanding regarding AAE archiving and deletion.
We have 98% interfaces using only AAE in our landscape.
I had set up XMLDAS archiving for AAE ( After fixing so many issues ) which archives the AAE messages into the local file system. So no issues in that .
Now my requirements are,
1) I would like to keep only 7 days of data in the database and 100 days of data in the file system
2) I do not want to set up any rules for Archiving /Deletion. It means i would like to archive messages older than 7 days in the file system.
The steps are ( My understanding )
1) Set the persistence duration in NWA to 7 days . So only 7 days of data will be stored in table BC_MSG.
2) Set up the archival job in the background processing through RWB without ANY RULES. So all processed messages older than 7 days will be achieved in the file system. And Archive will come with default delete procedure as well hence Archived messages will be deleted from table BC_MSG.
3) Deactivate the delete job . If i have the active delete job in the background processing, it will delete all messages older than 7 days which i don want. The deletion of messages from BC_MSG will be taken care as part of archival job.
Is my understanding correct?
Thanks
Rajesh

Hello, any know what did they do to delete the files from the file system after 100 days?
We have the same problem, when we deleted manualy some messages from SO AIX but they still appear from the RWB, and when we clic over them we get an error: ...... java.lang.Exception: XML DAS GET command failed with ErrorCode: 598; ErrorText: 598 GET: Error while accessing resource; response from archive store: 598 I/O Error java.io.FileNotFoundException: /usr/sap/PID/javaarch/archive/usr/sap/pid/x
Is there any way to delete messages without generating errors / inconcistencias?

Cannot delete messages from inbox, cannot move messages out of inbox, message do not copy to "sent" or "draft"

The following problems occur:
- cannot delete messages,
- cannot move messages out of inbox,
- messages do not copy "sent"
- messages cannot be saved to "draft"
This applies to imap and to gmail accounts.
The following has not helped:
- compact trash and other folder
- deinstall and reinstall TB 31.4.
- archive profile with mozbackup and replace profile from archive after reinstall of TB.
- deinstall and reinstall TB 31.3 downgraded
- delete all folders and files with "trash*" in the file name (all IMAP)
- delete all files of 1 mail account completely in the TB profile and resync from server (IMAP)
This might coincide with these system changes:
- upgrade to TB 31.4.
- some of these email accounts were installed on ios8 iphone.
Not sure if the problems had already started before these 2 occurrences.
Any help is appreciated to solve this.
Thanks!
fashi

What type of mail account is this (POP, IMAP, .Mac)? If POP, what are your Preferences > Accounts > Advanced > Remove copy from server settings?
You may be able to get rid of those messages in Mail doing Edit > Cut (⌘X) (for best results do it with one message or just a few at a time), but you should remove them from the server first if they’re still there.
Does this account allow web access? If not, you may find the Account Info window useful to solve this problem — choose Get Info (⌘I) from the Action menu (gear icon) located below the mailboxes list in the main Mail window.

Question about Archive Log Deletion policy

I've a problem to understand the Archive Log Deletion policy, and I I'd like to this problem explain with the following example.
Messages of the database are in German, but I guess you'll understand them.
SQL> startup
ORACLE-Instance hochgefahren.
Total System Global Area 5344731136 bytes
Fixed Size 2129240 bytes
Variable Size 2684355240 bytes
Database Buffers 2617245696 bytes
Redo Buffers 41000960 bytes
Datenbank mounted.
Datenbank geöffnet.
SQL> archive log list
Datenbank-Log-Modus Archive-Modus
Automatische Archivierung Aktiviert
Archivierungsziel E:\oracle\thetis_iv\arch
Älteste Online-Log-Sequenz 17917
Nächste zu archivierende Log-Sequenz 17919
Aktuelle Log-Sequenz 17919
SQL> alter system switch logfile;
System wurde geändert.I created a brand new archive log.
SQL> exit
Verbindung zu Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options beendet
D:\OracleDB\product\11.1.0\db_1\BIN>dir E:\oracle\thetis_iv\arch
Datenträger in Laufwerk E: ist Volume
Volumeseriennummer: 3EBD-77E5
Verzeichnis von E:\oracle\thetis_iv\arch
06.04.2011 15:04 <DIR> .
06.04.2011 15:04 <DIR> ..
06.04.2011 15:04 17.137.152 ARC17919_0721667907.001
 1 Datei(en), 17.137.152 Bytes
 2 Verzeichnis(se), 41.073.258.496 Bytes freiand this is the only archive log in the directory. Now I start rman:
D:\OracleDB\product\11.1.0\db_1\BIN>rman target / catalog rmanrepo@rmanrepo
Recovery Manager: Release 11.1.0.7.0 - Production on Mi Apr 6 15:05:35 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Mit Ziel-Datenbank verbunden: ENTWIV (DBID=21045568)
Kennwort für Recovery-Katalog-Datenbank:
Verbindung mit Datenbank des Recovery-Katalogs
RMAN> show all;
RMAN-Konfigurationsparameter für Datenbank mit db_unique_name ENTWIV sind:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP OFF;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'E:\oracle\thetis_iv\backup\CF_%F_ENTWIV.ORA';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'ENV=(TPDO_OPTFILE=D:\Services\Tivoli\TSM\AgentOBA64\tpdo.opt)';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BZIP2'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 2 TIMES TO 'SBT_TAPE';
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\ORACLEDB\PRODUCT\11.1.0\DB_1\DATABASE\SNCFENTWIV.ORA'; # defaultThe archive log deletion policy says the the logfiles have to be backed up for two times before they get deleted.
Now I backup all archive logs, that havn't been backed up for at least two times.
RMAN> run { backup archivelog all not backed up 2 times
2> format '%d_AR_%Y%M%D_%s_%t'
3> tag 'ARCHIVE LOGS'
4> DELETE ALL INPUT;
5> }
Starten backup um 06.04.2011 15:08:01
Aktuelles Log archiviert
Zugewiesener Kanal: ORA_SBT_TAPE_1
Kanal ORA_SBT_TAPE_1: SID=253 Device-Typ=SBT_TAPE
Kanal ORA_SBT_TAPE_1: Data Protection for Oracle: version 5.5.1.0
Kanal ORA_SBT_TAPE_1: Backup Set für Archive Log wird begonnen
Kanal ORA_SBT_TAPE_1: Archive Logs in Backup Set werden angegeben
Eingabe-Archive-Log-Thread=1 Sequence=17919 RECID=147 STAMP=747759899
Eingabe-Archive-Log-Thread=1 Sequence=17920 RECID=148 STAMP=747760081
Kanal ORA_SBT_TAPE_1: Piece 1 wird auf 06.04.2011 15:08:02 begonnen
Kanal ORA_SBT_TAPE_1: Piece 1 auf 06.04.2011 15:08:09 beendet
Piece Handle=ENTWIV_AR_20110406_23_747760082 Tag=ARCHIVE LOGS Kommentar=API Version 2.0,MMS Version 5.5.1.0
Kanal ORA_SBT_TAPE_1: Backup Set vollstõndig, abgelaufene Zeit: 00:00:08
Kanal ORA_SBT_TAPE_1: Archive Logs werden gel÷scht
Archive Log-Dateiname=E:\ORACLE\THETIS_IV\ARCH\ARC17919_0721667907.001 RECID=147 STAMP=747759899
Archive Log-Dateiname=E:\ORACLE\THETIS_IV\ARCH\ARC17920_0721667907.001 RECID=148 STAMP=747760081
Beendet backup um 06.04.2011 15:08:10
RMAN> exit
Recovery Manager abgeschlossen.
D:\OracleDB\product\11.1.0\db_1\BIN> dir E:\oracle\thetis_iv\arch
Datenträger in Laufwerk E: ist Volume
Volumeseriennummer: 3EBD-77E5
Verzeichnis von E:\oracle\thetis_iv\arch
06.04.2011 15:08 <DIR> .
06.04.2011 15:08 <DIR> ..
 0 Datei(en), 0 Bytes
 2 Verzeichnis(se), 41.090.396.160 Bytes freirman deleted all archive logs, even I they are on tape only once by now.
Thats not what I expected. Where is my mistake?

Hi,
I do new tests it's very strange.
BACKUP ARCHIVELOG command is not obeying the policy of archivelog.
You can open a SR on MOS. (to check bugs)
I reproduce the same test and the result was the same, it seems that this is a bug.
CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 2 TIMES TO DISK;
RMAN> backup archivelog all not backed up 2 times delete all input;
Starting backup at 06-APR-11
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=15 RECID=16 STAMP=747753711
input archived log thread=2 sequence=20 RECID=17 STAMP=747753714
input archived log thread=1 sequence=16 RECID=19 STAMP=747753729
input archived log thread=2 sequence=21 RECID=18 STAMP=747753729
channel ORA_DISK_1: starting piece 1 at 06-APR-11
channel ORA_DISK_1: finished piece 1 at 06-APR-11
piece handle=+DATA/orcl/backupset/2011_04_06/annnf0_tag20110406t132210_0.304.747753731 tag=TAG20110406T132210 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
channel ORA_DISK_1: deleting archived log(s)
archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_1_seq_15.293.747753711 RECID=16 STAMP=747753711
archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_2_seq_20.295.747753715 RECID=17 STAMP=747753714
archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_1_seq_16.294.747753729 RECID=19 STAMP=747753729
archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_2_seq_21.298.747753729 RECID=18 STAMP=747753729
Finished backup at 06-APR-11
RMAN> list archivelog all;
specification does not match any archived log in the repositoryOracle Docs Says:
The BACKUP ARCHIVELOG ... DELETE INPUT command deletes archived log files after they are backed up.
This command eliminates the separate step of manually deleting archived redo logs.
With DELETE INPUT, RMAN deletes only the specific copy of the archived log chosen for the backup set.
With DELETE ALL INPUT, RMAN deletes each backed-up archived redo log file from all log archiving destinations.
As explained in "Configuring an Archived Redo Log Deletion Policy",
the BACKUP ... DELETE INPUT and DELETE ARCHIVELOG commands obey the archived redo log deletion policy
for logs in all archiving locations. For example, if you specify that logs should only be deleted when backed
up at least twice to tape, then BACKUP ... DELETE honors this policy.http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmbckba.htm#BRADV89524
But in ours case it's not honors this policy.
Only with the FORCE command should this happen. But it is not our case.
Oracle Docs:
If FORCE is not specified on the deletion commands,
then these deletion commands obey the archived log deletion policy.
If FORCE is specified, then the deletion commands ignore the archived log deletion policy.http://download.oracle.com/docs/cd/E11882_01/backup.112/e10643/rcmsynta010.htm#RCMRF113
Alternatively you can do the following:
Set the commands separately.
Check this:
RMAN> run {
2> backup archivelog all not backed up 2 times ;
3> delete archivelog all backed up 2 times to disk;
4> }
Starting backup at 06-APR-11
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=2 sequence=22 RECID=21 STAMP=747755128
input archived log thread=1 sequence=17 RECID=20 STAMP=747755127
channel ORA_DISK_1: starting piece 1 at 06-APR-11
channel ORA_DISK_1: finished piece 1 at 06-APR-11
piece handle=+DATA/orcl/backupset/2011_04_06/annnf0_tag20110406t134528_0.295.747755129 tag=TAG20110406T134528 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 06-APR-11
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=78 instance=orcl1 device type=DISK
RMAN-08138: WARNING: archived log not deleted - must create more backups
archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_1_seq_17.298.747755127 thread=1 sequence=17
RMAN-08138: WARNING: archived log not deleted - must create more backups
archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_2_seq_22.294.747755129 thread=2 sequence=22
RMAN>Edited by: Levi Pereira on Apr 6, 2011 1:35 PM

Can't delete messages in Mail

This is a brand-new issue that started yesterday — I cannot get rid of unwanted messages in Mail when I click on Delete. Nothing at all happens. I can do a "Move To" on some of the messages.
I also cannot select "Rebuild".
Who has solved this problem before?

I had the same problem and tried a solution I found on other forums. First archive a copy the affected mailbox in case something goes wrong. Then highlight the mailbox name in the navigation bar on the left, go to the "Mailbox" menu, and choose "Rebuild" from the bottom of the list. This worked for me.
There's also an option in Mail preferences to "Move deleted messages to a separate folder." I unchecked it and rechecked it, then closed Mail Preferences.
Somewhere along the line I also did a restart. It never hurts.
Hope this helps.

Delete messages stuck in status 12, Recorded for Outbound Processing

I am on a PI 7.10 SP8 system. I have 59,000 XML messages showing in status 12 ( Recorded for Outbound Processing) that I would like to just delete or cancel. These have accumulated over several days of testing interfaces. If I have to allow them to be processed, that would also work but is not needed. I have read about 6 different forum threads and tried several things but nothing has worked yet. 
The messages can not be cancelled from SXMB_MONI. 
The queues are no longer showing in SMQ2. 
I have tried restarting and re-registering the queues. 
I've tried RSXMB_RESTART_MESSAGES and RSXMB_CANCEL_MESSAGES. 
SWPR & SWPC show nothing to restart. 
Any ideas on something else to try? 

Hi,
You can try to delete or archive mesages. use following links.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/402fae48-0601-0010-3088-85c46a236f50
Delete Messages SXMB_MONI
http://help.sap.com/saphelp_nw04/helpdata/en/0e/80553b4d53273de10000000a114084/frameset.htm
Too many questions on Archive/Delete messages.
Inder

Archiving Adapter Engine Messages

For AE we have implemented the Archiving:
The steps for AE we took are as follows:
1. Created archive store, and after that done home path synch and assigned it to an archive path.
2. created the archiving background job in RWB with rules and have default delete job in place.
Archiving job is running once in a day. But Default persistance duration of messages in AE is 30days.
Here I have some confusions in understanding the core logic.
1. Whether messages which have completed their 30 days of life will be archived ?
2. or messages which have completed 1 day of life will be archived(Since archive job runs every day) ?
3. I have seen Archive and delete jobs have different run times, even though delete job didn't completed yet, archive job
is deleting the messages from database. Why it is happending like that ?
4. Does we need both the archive and delete jobs or archive job alone is fine ?
Thanks
kumar

Kumar,
Here are my thoughts.
1. Whether messages which have completed their 30 days of life will be archived ? - NO
2. or messages which have completed 1 day of life will be archived(Since archive job runs every day) ? - YES
3. I have seen Archive and delete jobs have different run times, even though delete job didn't completed yet, archive job
is deleting the messages from database. Why it is happending like that ? -
Archive jobs will archive the files to the directory mentioned. you might not have access to the archive directories. i don't think the files will be deleted if you have specified Archive parameter.
4. Does we need both the archive and delete jobs or archive job alone is fine ?
Archive jobs alone is fine, if you have a specific directory to hold archive msgs.

Cannot Delete Messages in XI (PI)

HI,
We are using SAP NetWeaver PI v7.00 SP15. Our PSAPSR3DB tablespace is growing and we can't delete the messages. If I run RSXMB_SHOW_REORG_STATUS it shows 615,086 asynchronous messages not in retention period (can be deleted). There are only 1314 messages in the retention period. There are 113,759 messages without errors to be flagged.
If I run RSXMB_DELETE_MESSAGES through TCODE SXMB_ADM I get these results:
07.10.2008 13:10:21 Job started
07.10.2008 13:10:21 Step 001 started (program RSXMB_DELETE_MESSAGES, variant &0000000000027, user ID DBARBOUR)
07.10.2008 13:10:34 0 XML messages deleted
07.10.2008 13:10:34 Step 002 started (program RSXMB_TABLE_SWITCH, variant &0000000000027, user ID DBARBOUR)
07.10.2008 13:10:34 Job finished
I'm working through Note 872388 Troubleshooting Archiving and Deletion in XI 3.0 / PI 7.0 and others, but nothing is working.
I've even tried using the http screen suggested in 807615, but still can't get rid of the old messages. My configuration is set to 'simple" (without table switch?) so it's somewhat puzzling the deletion job tries the switch, although I'm not sure if that's signifigant.
Can someone help me out here?

David,
I had similar issues, but note 872388 solved my problems. I am also running without table switch.
-Regards

Simple Delete messages in XI/PI

We have scheduled these jobs to simple delete and it's working fine.
One of the questions arrived that why Moni messages are still there, even though it's not required. Can we delete any trace of messages after 30 days? Is it duable?
Please let me know Appreciated in advnace

Hello!
You have two alternatives to treat the messages:
1-Enabling the 'Swith Procedure';
2-Scheduling the interfaces for 'Archiving' and 'Deletion';
More information about both methods, you can found out here:
#872388 - Troubleshooting Archiving and Deletion in PI
Regards,
Caio Cagnani

Archiving vs Deleting messages in PI/XI

Similar Messages

Maybe you are looking for