Opalis Integration Server Log Purge times out or returns an exception

Opalis Integration Server Log Purge times out or returns an exception

  • Comments 1
  • Likes

KBSymptoms

When using the Opalis Integration Server "Log Purge" functionality either scheduled or directly from the Opalis Integration Server Client via the "Purge Now..." button, the purge operation either times out and does not complete or returns an exception.

Cause

The Log Purge functionality has a hard coded timeout value to complete the execution of the SQL queries that are being called.  If this timeout period expires, then the log purging operation does not complete successfully.

Resolution

Log Purge functionality has three options:

  1. Keep last x number of records
  2. Keep last y number of days.
  3. If records are older than y number of days, keep last x number of records.

These three options dictate how the stored procedure “sp_CustomLogCleanup” is called.  To call the stored procedure in a manner that mimics the Log Purge functionality (but without the hardcoded timeout) you can execute one of the following three scripts in SQL Management Studio where @XEntries is the number of entries to keep and @YDays is the number of days to either keep entries or the number of days to determine when entries should be processed:

Option #1

DECLARE @Completed bit
SET @Completed = 0
WHILE @Completed = 0 EXEC sp_CustomLogCleanup @Completed OUTPUT, @FilterType=1,@XEntries=1000

Option #2

DECLARE @Completed bit
SET @Completed = 0
WHILE @Completed = 0 EXEC sp_CustomLogCleanup @Completed OUTPUT, @FilterType=2,@YDays=7

Option #3

DECLARE @Completed bit
SET @Completed = 0
WHILE @Completed = 0 EXEC sp_CustomLogCleanup @Completed OUTPUT, @FilterType=3,@XEntries=1000,@YDays=7

For more information and all the details of this issue see the following new Knowledge Base article:

KB2290555 - Opalis Integration Server Log Purge times out or returns an exception

J.C. Hornbeck | System Center Knowledge Engineer

clip_image001 clip_image002

Bookmark and Share
Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • The problem with Opalis isn't so much that the cleanup stored procedures timeout is hardcoded (although that is def. a bad practice).  The real problem is the design of the back-end db.  All PK's are GUID's & all joins happen on those GUID's.  If you guys (MS) reworked that design I bet a hard coded timeout will no longer be an issue.

    Just my 2 cents.  I'm a big fan of this product & want to see it succeed.