Please make sure that the archive DB user has the rights to select and delete data from the regular schema.
Is the pool associated to the Archiving function in IS?
The grant statements need to be executed on the regular schema and is formatted like this:
Grant on
to ;
For my latest installation (wM 7.1.3) I used the following (Oracle-)Statements:
grant SELECT, DELETE on WMCONTROL to ;
grant SELECT, DELETE on WMCUSTOMDATA4X to ;
grant SELECT, DELETE on WMCUSTOMFIELDDEFINITION to ;
grant SELECT, DELETE on WMCUSTOMPROCESSDATA to ;
grant SELECT, DELETE on WMDOCUMENT to ;
grant SELECT, DELETE on WMERROR to ;
grant SELECT, DELETE on WMPROCESS to ;
grant SELECT, DELETE on WMPROCESSASSOC to ;
grant SELECT, DELETE on WMPROCESSDEFINITION to ;
grant SELECT, DELETE on WMPROCESSIMAGE to ;
grant SELECT, DELETE on WMPROCESSRECENT to ;
grant SELECT, DELETE on WMPROCESSSTEP to ;
grant SELECT, DELETE on WMPROCESSTRANSITION to ;
grant SELECT, DELETE on WMSECURITY to ;
grant SELECT, DELETE on WMSERVICE to ;
grant SELECT, DELETE on WMSERVICE4X to ;
grant SELECT, DELETE on WMSERVICEACTIVITYLOG to ;
grant SELECT, DELETE on WMSERVICEASSOC to ;
grant SELECT, DELETE on WMSERVICE_MIN_MAX to ;
grant SELECT, DELETE on WMSESSION to ;
grant SELECT, DELETE on WMSTEPDEFINITION to ;
grant SELECT, DELETE on WMSTEPTRANSITIONDEFINITION to ;
grant SELECT, DELETE on WMTXIN to ;
grant SELECT, DELETE on WMTXOUT to ;
Please check for the correct format for SQL-Server.
There might be more tables to be considered on newer versions of wM.
Did you run serviceArchive with the correct settings?
If Action is DELETE, there will be no archived data at all.
retainDays should be smaller than the total amount of days stored in the schema, otherwise the data is not considered for Archiving.
#webMethods-General#webMethods#Integration-Server-and-ESB#webMethods-Architecture