Troubleshooting Archiving

Hi All,
I am trying to archive my messages on my XI server and had used the pdf located at https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/402fae48-0601-0010-3088-85c46a236f50 .
I have set up the archiving objects BC_XMB on t-code SARA and flag the appropriate interface for archiving. I have also checked that my messages are not in the retention period by running the report RSXMB_SHOW_REORG_STATUS and are flagged for archiving. However none of the messages were archived despite the archiving jobs running properly. This is confirmed in the job log when it stated 0 XML messages were archived.
I would like to check a few things:
1. In the Assigning the Physical Path to Logical Path for Windows, is it correct to assign the Physical Path as "C:<FILENAME>".
2. How can I troubleshoot as to what is exactly causing the archiving job not to archive any of the XML messages?
Edited by: lookman on Feb 5, 2008 11:08 AM

Hi,
The below link will clarify your doubt about Physical and Logical path for archiving
http://help.sap.com/saphelp_nw04/helpdata/en/8d/3e4ec2462a11d189000000e8323d3a/frameset.htm
In the Physical File field, enter the required physical file name.
The following parameters are of particular interest here:
¡        PARAM_1: Two-character application abbreviation (for example, HR, CO, MM) for the classification of the archive files in the system. The value of the definition is determined from the relevant archiving object at runtime.
¡        PARAM_2: Single-character alphanumerical code (0-9, A-Z). If, when creating a new archive file, an existing file with an identical physical name would result in a conflict, the ADK increases this value by 1. This value must, therefore, always be a part of the physical name.
¡        PARAM_3: This parameter is filled at runtime with the name of the archiving object. In archive management, this enables you to check the file contents or to store the archive files by archiving objects.
To enable maximum space in the name range for the archive file, the following entry is recommended:
(Syntax group WINDOWS NT)
thanks
Swarup

Similar Messages

Archiving issue

Hi XI guru,
We have an XI system gone live for in 5-6months. and right now found sxmb_moni-> persistency layer analysis have high Current Fill Level, about 40-50. And we do have setup message deletion job, so all these left messages are unprocessed/error message.
Now we just setup archiving job according to PDF<Archive and Delete Messages in SAP XI: A Step-by-Step Guide> mentioned in another thread. And We also Canceled all error message. So ideally, archiving job should saved these messages in archive file and flag these message. finally delete job will delete these message with archive flag.
But when after archive job ran, according to job log, 0 XML message archived. So this confused me.
Am I understand this wrong? or Archive should setup at very beginning, all message happened before archive setup will not be archived?
Thank you for your time to reply

Hi Keimer,
I also checked OSS Notes:872388 as you mentioned in another threads. I did checked each step in <Troubleshooting Archiving / Deletion of XML messages and history entries in the Integration Server>, and it looks ok to me.
it finally let me run report <RSXMB_SHOW_REORG_STATUS>, and sent OSS message, I will do that. But I'd like to post report result here for your reference, probably you have some clue from the following data.
Reorganization Status of XI Messages in the Database
Retention periods and message and adapter status ignored in the following
Number of messages in DB:          16.047
Number of messages in client:       16.047
Number of messages in client still to be reorganized:         16.047
Archiving
============
Number of messages to be flagged for archiving
Message and adapter status is ignored in the following
- Msgs not in retention period (can be archived):       12.791
- Msgs in retention period (cannot be archived):             0
Message and adapter status is considered in the following
- Messages to be flagged for archiving:     12.762
Number of messages already flagged for archiving
- Messages to be archived:            0
Number of archived messages that can now be deleted
- Messages to be deleted:          0
Delete
=======
Number of messages to be flagged for deletion
Message and adapter status is ignored in the following
- Asynchr. msgs not in retention period (can be deleted):       3.254
- Asynchr. msgs in retention period (cannot be deleted):            2
Message and adapter status is considered in the following
- Asynchronous messages without errors to be flagged:              0
Message and adapter status is ignored in the following
- Synchr. msgs not in retention period (can be deleted):           0
- Synchr. msgs in retention period (cannot be deleted):            0
Message and adapter status is considered in the following
- Synchronous messages without errors to be flagged:              0
- Synchronous messages with errors to be flagged:                0
Number of messages already flagged for deletion
- Messages to be deleted:          0

Error default version Archive job

Hello All
Runtime error standard job
see screenshot
Regards,
Rinaz

Hi Rinaz - I don't think it works.
If you are trying to configure archiving on AE, you should follow the below blog.
AAE Archiving in SAP PI 7.11 with XMLDAS
To archive interfaces in the Adapter Framework (AFW), the XML DAS (Data Archiving Store) has to be set up. If no archiving has been set up XML message will be deleted from the AFW by the standard deletion job after a default time of 1 day (releases 7.10 and higher). You can define which interfaces should be archived via archiving rules.
Reference : 872388 - Troubleshooting Archiving and Deletion in PI

Clearing JAVA Message Queue in PI 7.1

Hi Experts
I am working on a file to File Scenario, and file has been picked up on the sender CC and mesaages have been sent to JAVA queues, But the messages are stuck on the JAVA queues,
Java Queue name: File_http://sap.com/xi/XI/SystemRecv
How can I clear the JAVA message queue in PI 7.1
Thanks
PR

If the messages are on the queue, usually one of the actions must be performed: a) Fix the related scenario and restart the messages or b) Manually cancel the messages. This is also advised on the note below under item "3. Troubleshooting Archiving / Deletion in the Adapter Framework"
[Note 872388 - Troubleshooting Archiving and Deletion in PI|https://service.sap.com/sap/support/notes/872388]
If you are having performance problems, please check if the messages are taking long time in TBDL/Holding status. Let us know if this is the case.

Performance of PI Dev system

We are in the middle of the project and over the last one week, the PI Development environment slows down. The SXMB_MONI and other ABAP based transactions are okay but it takes ages to open the IR objects. I think there is something wrong with the Java Engine memory etc. After the system is restarted it goes well for 5 to 6 hours and slows down considerably after that.
Has anybody encountered problems like this.
Can somebody suggest how to delete the Message ( both success and error ones ) from the Java engine ( Adapeter etc.,). I have a feeling the retry mechanism of error messages is taking up the memory of Java Engine.

Notes you may find useful :
#872388: Troubleshooting Archiving and Deletion in XI 3.0
#862405   XI Configuration Options for Lowering Memory Requirements
#723909    Java VM settings for J2EE 6.30/6.40/7.0
#894509 XI Performance Check
Regards
   Kenny

How to configure message archieving in PI 7.1 / 7.11 ?

Hi,
I would like to configure message archieving in PI 7.11. Please advise on the any document / help that explain the step.
Thank You and Best Regards
Fernand Lesmana

The following guide explaing the step-by step procedure-
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/402fae48-0601-0010-3088-85c46a236f50&overridelayout=true
Also, the following links/notes might be usefull-
http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417200)ID1506029250DB00994126813914143097End?blog=/pub/wlg/12811
Note 836092 - Archiving/deleting work items in the XI
Note 872388 - Troubleshooting Archiving and Deletion in XI 3.0 / PI 7.0
I think there is no difference in archival setup procedure with PI7.1 and its same as it is in PI7.0

Switch or Simple procedure to Delete the job?

Hi
I want to delete all the data which are less than 6 months I have changed the staus from del to arch for those data which need to archived .I am really confused on selecting the delete procedure whether to select simple or switch
in my data base there are more than 500000 to be delete
The simple deletion procedure deletes all XML messages flagged for deletion or archiving from the database tables in records.
it is saying will delete all the records which are flagged for archiving also
in switch it is taking copy of the table to another i want to reduce the space from my data base
Kindly suggest me how can i achive my goal
Thanks
Jayaraman
Edited by: Jayaraman P on Jun 21, 2010 4:05 PM

Hi,
Messages having status ARCH will not be deleted by the deletion job. only the messages having status DEL will be deleted by deletion job RSXMB_DELETE_MESSAGES.
This message status can be checked by the status of ITFACTION of SXMSPMAST table.
The type of deletion procedure simple or table swith has no effect on the messages that will be selected for deletion.
The messages that has the flag ARCH can be deleted only by the ARCHIVE job. Archive job has two steps it first archive those messages in to file system RSXMB_ARCHIVE_MESSAGE and then delete by RSXMB_DELETE_ARCHIVED_MESSAGES.
Please check the note Note 872388 - Troubleshooting Archiving and Deletion in PI for further assistance.
Thanks,
Francis
Edited by: Francis M. A. on Jun 21, 2010 5:13 PM

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

Automatic Deletion of error messges in Moni

Hi
Requirement of mine is to delete only the error messages which are more than 2 months in the non production system
Is there a way where we can automatically do this task .Please let me know the possiblities in this regard

Hi Anusha
Note #872388 Troubleshooting Archiving and Deletion in XI 3.0 / PI 7.0, contains all details on how to configure automatic deletion of XI messages.
Regards
Mark

SXMB_MONI retention period

Hi all,
I configured the retention period for deleting and archiving XML messages in SXMB_ADM.
My retention period for deleting messages is 30 days and the job is scheduled on a weekly basis.
When I go to the message monitoring in the RWB, I can see that all messages older then 30 days are deleted.
However when I go to SXMB_MONI I'm still able to see all messages.
In the persistance layer analysis, I see that the table keeps growing and currently is over 90%.
Does anyone know how I can remove the message out of the SXMB_MONI??
Kind regards,
Steven

Dear Steven,
you might have a look at OSS note 872388 'Troubleshooting Archiving and Deletion in XI 3.0' that provides a comprehensive collection of common issues regarding archiving and deletion. Please walk through section 5 'Troubleshooting Archiving / Deletion of XML messages and history entries in the Integration Server'.
You stated that 5-8% of all messages are deleted through running the deletion job. This indicates that you are not using table switch procedure, ruling out 5-i).
However, 7/30=23% of the messages should be deleted (provided that the message volume is constant over time). Often step 5-k)-2 (adapter status update missing) turns out to be the reason for not deleting XI messages. For the sake of completeness I recommend to have a look at entire section 5.
Best Regards,
Harald Keimer
XI Development Support
SAP AG, Walldorf

Low performance in SXMB_MONI

When accesing to the xml message versions of a single message in SXMB_MONI, it takes a very long time.
What could be the cause of this bad performance?
Thanks.

Hi Alberto
This can be caused by DB related issues. An update of the DB statistics usually resolves this.
If you use the Oracle DB, apply note #1020260 Delivering Oracle statistics.
Also, ensure you have configured Archiving and Deletion to ensure that XI messages are deleted from the DB tables. Too many entries in the DB tables can also cause this issue. See note #872388 Troubleshooting Archiving and Deletion in XI 3.0 / PI 7.0.
Regards
Mark

QC Adapter with SolMan - step by step guidance, if possible please

Hi experts,
I am embarking on linking QC tool with SolMan and request any help you can provide, including the following aspects -
(1) Sequence of steps from downloading the license from SAP - in brief
(2) Authorisation aspects
(3) Any SAP Notes that are must read before proceeding
(4) Any 'traps' to avoid or error messages to look out for
I have files from service.sap.com/solutionmanager and also from service.sap.com/rkt-solman
Your tips/inputs beyond these files will be valuable. If you would like to relate to those files, a clear guidance on sequence of reading/ executing them would be helpful too.
Thanks and regards,
Srini

Hello there!
The list of interfaces for archiving are located in transaction
SXMB_ADMIN -> Integration Engine -> Configuration -> "Define
Interfaces for Archivng and Retention Periods").
All interfaces which are not found in that list are flagged for
deletion by default.
Mor information in note: #872388 - Troubleshooting Archiving and Deletion in PI
Now, I'd like to give you a little explanation regarding the Archiving/Deleting procedures:
Checking out the report RXMB_SHOW_STATUS,
you can see the status of some messages, for example, if they're not in
status 000, 003 and 006, which means they're in final state, then it may
means that some messages were not ready to be processed by the default
job you configure.
There're three pre-requisites for deleting/archiving messages:
1- Age of message (older than the retention period)
2- Message status is final
3- Adapter status is final
Also, we have to consider the messages in report
RSXMB_SHOW_REORG_STATUS, that shows us the messages that are being
'considered' and those are being 'ignored'.
The first one takes all the three pre-requisites in account; the second
one takes only the first pre-requisite in account.
The status of the messages are take in account when the default job
you set up runs.
Hope it is complete to you
Best regards,
Caio Cagnani

Locked Queues

Hello SDN,
Sometimes message processing is not executed successfully and the error lock the queues.
When we check the message status (message monitoring / SXMB_MONI) it is "scheduled for outbound processing" or "System error".
We fixed the errors when they occur but the problem is that the error locks the queue therefore the messages waiting for execution in the same queue have to wait until a manual cancel of the message with problems to be executed.
I wonder if is there any way to configure that when an error occurs during the execution in a queue, the error always can be transfered to the message (as a message with a system error) and do not lock the queue, so the following messages can be executed.
Do someone have had the same problem?
Best regards,
Gustavo P.

Hi Gustavo,
Tine Related Parameter can be checked with ::
There are two ways of changing this timeout:
a) check out note: 824554 and try to change it in the instance profile
b) TCODE SXMB_ADM -> Configure Integration server -> change specific identifiers
Set Runtime parameter: HTTP_TIMEOUT
Rember to restart XI after the change
For Dealing with All knid of Time Out Errors ::
See
/people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts
Now Coming back to Queues getting Blocked I dont hink Queue Prioritization is a ggod Idea, We have to manually Deal with Queues and the Data in Ind, remember if are force to delete any data from the Queues Delete the Complete LUW rather then individual message.
Have a Look at this Blog as well::
/people/stefan.grube/blog/2006/04/27/how-to-deal-with-stuck-eoio-messages-in-the-xi-30-adapter-framework
Please Keep the Table of important SAP Notes for common XI work::
SAP Note     Description
856597     FAQ: XI 3.0 SOAP Adapter
856346     FAQ: J2EE JMS Adapter: Frequently Asked Questions
821267     FAQ: XI 3.0 File Adapter
831162     FAQ: XI 3.0 JDBC Adapter
730870     FAQ XI 3.0 RFC Adapter
813993     FAQ: Message status in the adapter framework
856599     FAQ : XI 3.0 Mail Adapter
816022     FAQ: XI 3.0 J2EE Adapter Engine / Messaging System
801868     Java(TM) Web Start in XI 3.0: FAQ/Troubleshooting
774854     FAQ XI 3.0 BC Adapter
830039     FAQ: Deployment of the XI adapter framework
813993     FAQ: Message status in the adapter framework
793669     FAQ: SUS in SRM 4.0 with XI 3.0
615740     FAQ: CCMS GRMG Availability Monitoring
872388     Troubleshooting Archiving and Deletion in XI 3.0
872508     XI 3.0 AF: BufferOverflowException when sending large msgs
764417     Information for troubleshooting of the SAP J2EE Engine 6.40
721548     Changing the passwords of the XI service users
886888     XI 3.0 Adapter Framework: XML parsing error for xmlns
885405     Troubleshooting End-to-End Monitoring in XI 3.0
821268     XI 3.0 Adapter Framework: Overview of available FAQ notes
858366     SAP XI 3.0 SP12: iWay Adapter Release Note
801951     XI30: Analyzing mapping problems
711947     ITK 1.5 FAQ
768148     Using a separate SLD for XI
764393     Configuration of the SAP System Landscape Directory
813029     Automatic processing of failed XI messages
913858     XI3.0 Alerting: Troubleshooting (new)
I hope it will help you :::-))
Regards
Piyush
Please reward Points if you find this helpfull::-))

SAP XI Server Cleanup Activities

Hi All,
what cleanup activities should we schedule in XI server to prevent 'hard Disk space getting full' problem?
Recently I had problem where there was only 2MB disk space left on XI Server. So I need to figure out strategy so as to prevent disk from getting full . what should i do. Please help.
Ranjeet Singh.

This one is for you
Note 872388 - Troubleshooting Archiving and Deletion in XI 3.0

Troubleshooting Archiving

Similar Messages

Maybe you are looking for