cancel
Showing results for 
Search instead for 
Did you mean: 

Fill Level reached 130 %

Former Member
0 Kudos

Dear All,

In my XI 3.0 Production Server, Archiving has not been set at the time of implementation. Now the Fill level has reached at 130% and there are more than 1132818 messages at present. Following the status as output by 'RSXMB_SHOW_REORG_STATUS" report

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

- Messages to be flagged for archiving: 0

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

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

Message and adapter status is considered in the following

- Asynchronous messages without errors to be flagged: 327.723

Message and adapter status is ignored in the following

- Synchr. msgs not in retention period (can be deleted): 738.785

- 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: 419.899

- Synchronous messages with errors to be flagged: 318.523

Number of messages already flagged for deletion

-


- Messages to be deleted: 0

I need to retain messages of last two years at least. Kindly suggest if I configure archiving now, will it archive the old messages as well ?

Also If i need to delete processed messages before Year 2006, how can I do that ?

I tried configuring Archiving in DEV server and I was able to archive new processed messages.

Thanks

Jitendra Tayal

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Jitendra,

the flag "To Be Archived" or "To Be Deleted" is set on messages once they enter XI if the corresponding interfaces are defined as "archivable" in SXMB_ADM.

This means that if you define now the interface as "To Be Archived" all messages for this particular interface entering XI from now onward will be archived.

All the messages that where already in will not be archived, but will directly be deleted.

To delete processed messages before Year 2006, set the corresponding Retention period for "XML Messages Without Errors Awaiting Deletion" accordingly.

For further info have a look at the help box in SXMB_ADM->Define Interfaces for Archiving and Retention Period -> Retention Period.

BTW: 2 years of retention period looks really much, do you have some special requirements?

Kind Regards,

Sergio

Former Member
0 Kudos

Dear Sergio Cipolla,

Thanks for your swift reply !

2 Years of retention period is the requirement from functional side ( may be some compliance issue).

Can I delete these messages directly or I need to flag them fro deletion first ? I am asking this because in the reorg report it shows

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

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

Message and adapter status is considered in the following

- Asynchronous messages without errors to be flagged: 327.723

Message and adapter status is ignored in the following

- Synchr. msgs not in retention period (can be deleted): 738.785

- 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: 419.899

- Synchronous messages with errors to be flagged: 318.523

Number of messages already flagged for deletion

----


- Messages to be deleted: 0

Please guide.

Jitendra Tayal

Former Member
0 Kudos

The deletiong flag is automatically set by the jobs.

The job in a first step flags all messages that can be deleted or archived and in a second step delete or archive messages according to the flag.

Anyway consider that 2 year of retention means 2 year of messages in the database, this might have an high impact on performances.

If you archive messages after 5 days you will still be able to find messages in archives in the file system and you can keep them for 2 years without affecting DB size and performance.

Just a point to think about.

Kind Regards,

Sergio

Former Member
0 Kudos

You are right Sergio !

We also intend to archive messages for two years and not keep then in DB.

But are you sure that messages already processed without setting up archiving for that interface, can not be archived now and can only be deleted.

Thanks

Jitendra Tayal

Former Member
0 Kudos

Yes,

and you can check this having a look at the help box in SXMB_ADM->Define Interfaces for Archiving and Retention Period -> Retention Period.

It says:

Also note that you must decide which messages should be archived before the first message has been processed, since every message has the flag To Be Archived or To Be Deleted.

Do not forget to close the thread if you questions are answered.

Regards,

Sergio

Former Member
0 Kudos

Thanks Sergio !

You have answered my question well.

Answers (0)