pub.monitor.archive:serviceArchive throwing"Error in archiving: com.wm.monitor.util.MonitorException

Hi All,

Could you please help me on below issue?

Am invoking the “pub.monitor.archive:serviceArchive” using flow service with following input parameters.

days -1
archiveAction- DELETE

When am invoking the service, am getting the follwoing exception:
Error in archiving: com.wm.monitor.util.MonitorException: OTHER EXCEPTIONS OCCURRED!-903ORA-00903: invalid table name

server log:
[590] at
[589] at
[588] at
[587] at
[586] at
[585] at
[584] at
[583] at
[582] at
[581] at
[580] at
[579] at
[578] at
[577] at
[576] at
[575] at
[574] at
[573] at
[572] at com.wm.lang.flow.FlowState.invoke(
[571] at com.wm.lang.flow.FlowState.step(
[570] at com.wm.lang.flow.FlowState.invokeNode(
[569] at com.wm.lang.flow.FlowInvoke.invoke(
[568] at
[567] at
[566] at
[565] at
[564] at
[563] at
[562] at
[561] at
[560] at
[559] at
[558] at
[557] at
[556] at
[555] at
[554] at java.lang.reflect.Method.invoke(
[553] at sun.reflect.DelegatingMethodAccessorImpl.invoke(
[552] at sun.reflect.GeneratedMethodAccessor340.invoke(Unknown Source)
[551] at pub.monitor.archive.serviceArchive(
[550] at
[549]2013-09-25 05:34:35 GMT [MOD.0120.0000I] com.wm.monitor.util.MonitorException: OTHER EXCEPTIONS OCCURRED!-903ORA-00903: invalid table name

Before running this service did you set up Archiving tables in the back end? as you need to configure first archiving before you run any of the archive services…please check with your wM Admin/DBA about the set up etc…

Also review the documentation pertaining to the archiving service.


1 Like

Thanks a lot for your reply:)

My requirement is to delete audit logs older than one day. Also, this task should be scheduled(May be daily basis).

Is there any approach to do this activity without setting up the archive tables? Please advise. Thanks for your help:)

Hi Prasath,

you will require the archive tables for deleting the audit logs.
These tables are used for preparing the entries to be deleted.

Dependent on your wM Version these tables should be placed in a different db schema than the live data.

See Monitoring Guide for details.

The archiving service can be scheduled but you might need to implement a wrapper for these as it is not possible in all wM versions to assign Input values to scheduled services. Recent versions of the wM 9.x stream allow assigning Input values to scheduled services.


You can also schedule the archive stored procedures, which get installed when you create the Archive schema, directly on the database. This is my preferred approach.


At present we are having oracle jobs in the DB which takes care of this task.

@Percio, can you please eloborate about your statement.


Sure. When you install the Archive database component using the Database Configurator, it creates a schema/database, and inside that schema/database it creates some stored procedures. E.g.: PROCESS_ARCHIVE_START_PROCESSARCHIVE, SERVER_ARCHIVE_START_SERVERARCHIVE, SERVICE_ARCHIVE_START_SERVICEARCHIVE, etc.

When you call the archive services inside the WmMonitor package, those services are simply calling these stored procedures behind the scenes (assuming you didn’t check the box “Enable JDBC Archive (Disable Stored Procedure Archive)” in the WmMonitor home page). Therefore, instead of scheduling these services to run on the IS, you can simply schedule these stored procedures to run directly on the database. In SQL Server, for example, you can do it via the SQL Server Agent, and in Oracle, you can do it via the Oracle Scheduler, if I’m not mistaken.

The advantages of doing this are:

  • No IS resources are consumed (CPU, threads, memory, etc)
  • Reduced network chatter
  • It delegates data archival to database administrators instead of webMethods admins/developers
  • Archival happens whether the IS is up or not

Hope this helps,