Archive Services Hanging

Has anyone else encountered an issue in which the Archive Services and Archive Server Data services never complete? We have approximately 700K rows in our WMERROR table and I’m unable to archive any data.

I’m currently attempting to reproduce the error in another envioronment with only 50K rows of data. The Archive Server Data service has been running for over an hour.

Yes we do had this problem. Service Pack and fixes resolves this. we are using
wM 6.0.1, SP3.

Regards
Kartheek

Hi fhousse,

the webmethods provided archiving services are far from efficient. If your archiving seems to last forever, or takes a long time and does not do anything in the end, (and in our case using oracle) check your temp and undo tablespaces. They might be running out of space because of the large query-results, and these types of errors are not reported back to your server log

have fun!

Hi,

how are you trying to archive your data?

All data execpt today?

Maybe try to archive from oldest to newest data day by day.

This can reduce the amount of data being processed per run.

If you don�t need the data any longer, remember to select “Delete Only” option otherwise your DB-Size won�t decrease.

BTW:
There is an issue with Oracle Databases not freeing the LOB-Pointers after Deleting the data from the appropriate tables.

Regards,
Holger

If you are running 6.1, ask TS for fix TNS_6-1_Fix6. This fix adds attributes that make the archive service more efficient. The following text was taken from the readme.

HTH,
Michelle

The wm.tn.archive:archive service performs the entire archive or
delete operation as one database transaction, which does not
efficiently use database resources, such as, transaction
rollback, locks, etc. Additionally, when using a SQLServer
database, a long running archive operation can cause deadlock
when the archive/delete operation is running at the same time
Trading Networks is attempting to save an incoming document
to the database.

To improve the archive and delete operations, this fix introduces
two new system properties to allow Trading Networks to perform
the archive/delete operations in multiple smaller database
transactions rather than in one large database transaction. The
two new system properties are tn.archive.batchSize and
tn.archive.batchBackoffTime.

Trading Networks uses the tn.archive.batchSize property to
determine the number of documents to archive/delete in a single
smaller database transaction. After archiving/deleting the number
of documents specified by the tn.archive.batchSize property, the
archive/delete thread sleeps for the number of seconds specified
by the tn.archive.batchBackoffTime property. When the number of
specified seconds elapses, the archive/delete thread continues
operating on the next batch of documents. Trading Networks
continues the archive/delete operation in this manner until
it processes all documents to be archived/deleted.

Performing the archive/delete operation in multiple smaller
batches of documents uses the database resources more
efficiently. The backoff time between batches allows other
database operations to be performed (e.g., saving document
content to the database).

High row counts can appear to hang the archive.
Please bump up IS logging level to 9 and select only 0119 Monitor and 0120 Monitor (Database layer) to view SQL execution and Archive/Purge steps.
Also, have your ORACLE DBA view the active sessions and check for locks held.
I have inadvertantly locked up my archive execution. You must patiently wait until the previous archive completes, or kill the session (in ORACLE).

I have spent many days learning the tricks of Monitor Archive/purges in v6.1.

Ken

We are using wm6.1 with sql*server and cannot run any of archive/delete processes on wmError due to the ‘locking/time issues’. At present the most convenient way for us to clear out the table in non-production databases is to have periodic outages and truncate the table. As discussed above, the standard procedures provided by WM are clunky at best - we don’t have the patch mentioned above, but I wonder whether it applies just to TN or to all the data.

Is there a patch that exists for running archive/delete service data for version 6.1? We are using wM 6.1 with DB2.

We had this problem with wm.tn.archive:archive service. Going to check the tablespaces. We are on oracle 10 and webMethods 6.5