Archive Job not creating any files at OS

[sathisharram]

Hi,

We configured XML archiving in our PI development system through SPRO with the following characteristics:

Mass Data Archiving

1) Cross-Archiving Object customizing

2) Crate Logical File path

3) Archiving Object-specific customizing

4) Required configuration has been carried out in Integration Engine

5)Retention period of 45 days maintained in SXBM_ADMIN

6) Create Schedule Archiving Job in SXMB_ADMIN

JOB was successfully executed but it is not create the archive file in physical location.

Also we verified SAP Note 872388 - Troubleshooting Archiving and Deletion in PI

Plz assist us in fixing this issue

Thanks in advance

Regards,

Satish

[rajasekhar_reddy14 · Accepted solution]

Hi,

it is difficult to say ,

check your configuration against this blog...

/people/deepak.shah/blog/2010/04/22/archiving-deletion-of-messages-in-pi--part-1

Regards,

raj

[sathisharram · Accepted solution]

Hi,

It seems, the configuration is done properly. However, when I run the report RSXMB_SHOW_REORG_STATUS, the following is the output. Number of messages for archiving shows 0. Any idea?

08/31/2010 Reorganization Status of XI Messages in the Database 1

-

---

08/31/2010 12:09:33 EST

<User>

001

<Instance>

Overview

=========

Retention periods and message and adapter status ignored in the following

Number of messages in DB: 162,643

Number of messages in client: 162,643

Number of messages in client still to be reorganized: 162,643

Archiving

============

Number of messages for archiving

-

---

Message and adapter status is ignored in the following

- Msgs not in retention period (can be archived): 0

- 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): 0

Number of messages already flagged for archiving

-

---

- Messages to be archived: 0

(Only possible with XI 2.0)

Number of archived messages that can now be deleted

-

---

- Messages to be deleted: 0

(Only possible with XI 2.0)

Delete

=======

Number of messages for deletion

-

---

Message and adapter status is ignored in the following

- Asynchr. msgs not in retention period (can be deleted): 354

- Asynchr. msgs in retention period (cannot be deleted): 0

Message and adapter status is considered in the following

- Asynchr. msgs not in retention period (can be deleted): 272

Message status is not considered in the following

- Synchr. msgs not in retention period (can be deleted): 136,444

- Synchr. msgs in retention period (cannot be deleted): 25,845

Message status is considered in the following

- Synchronous messages without errors to be deleted: 133,122

- Synchronous messages with errors to be deleted: 3,322

Number of messages already flagged for deletion

-

---

- Messages to be deleted: 0

(Only possible with XI 2.0)

[sathisharram · Accepted solution]

Hello All,

We have found that the following condition is not satisfing when the arching job is running.

SELECT *

INTO TABLE lt_master

UP TO max_rows ROWS

FROM (lv_master)

WHERE

rnd_number = lv_rnd

AND exetimest > last_ts

AND exetimest <= lv_max_ts

AND reorg = cl_xms_persist=>co_reorg_ini

AND itfaction IN rt_itfaction

AND msgstate IN rt_msgstate_xi

AND adapt_stat IN rt_adapt_stat

ORDER BY rnd_number mandt itfaction reorg exetimest.

The field itfaction in table exetimest is set to INIT. There are no messages set to ARCH. I think that is the reason, the archiving is not happening.

Can some one knows why the field is not chaging to ARCH from INIT?

Thanks in advance

Regards,

Satish

[sathisharram · Accepted solution]

Hello All,

Can any one look into this and assit me plzzz?

Thanks in advance

Regards,

Satish

[former_member334189 · Accepted solution]

Dear Satish,

the analysis you have carried out so far is correct. Currently no single message is flagged for archiving. This is either the configuration of interface actions (transactin SXMB_ITFACTION) has not been carried out at all or it was done belatedly.

Once a message enters the Integration Server or Integration Engine the PI Runtime Environment checks the interface action and assigns the result to this message; i.e. the result becomes a property of that message.Thus, setting up the interface action belatedly does not impact existing messages.

For changing the interface action of existing message belatedly report RSXMB_DEL_TO_ARCH was introduced. This report is available as of 6.40 SP22, 7.00 SP16 and 7.10 SP06. Due to complexity this report is not available as an advance correction per SAP Note. If the report is available in your system kindly check SAP Notes 1239882, 1282745 and 1499959 before using it.

Best regards,

Harald Keimer

XI Development Support

SAP AG, Walldorf

[sathisharram · Accepted solution]

Hello Harald,

Thanks very much for looking into this.

This is either the configuration of interface actions (transactin SXMB_ITFACTION) has not been carried out at all or it was done belatedly. 

Thus, setting up the interface action belatedly does not impact existing messages.

Having said the above, is it okay if we configure the interface actions (transactin SXMB_ITFACTION) first and perform the rest and then proceed with the archiving?

Thanks in advance

Regards,

Satish

[former_member334189 · Accepted solution]

Hello Satish,

actually you should do the configuration in transaction SXMB_ITFACTION for all interfaces you would like to be archived. Please keep in mind that this configuration will affect future messages only.

Secondly, consider which of the existing messages you would like to archive. For the interfaces of those messages change the interface action by running report RSXMB_DEL_TO_ARCH.

Finally, start the archiving session; this one shall pick up all messages that have been flagged for archiving before.

Best regards,

Harald Keimer

[Former Member]

Check if the job log has any entries that says has been archived

Or else, goto SXMB_ADM and schedule Archive job first and it should create 2 jobs Delete / HistDelete jobs.

Then follow the job status