Hi All,

While trying to archive old audit data in MWS. It is saying User does not have permission to archive. Any one can please suggest what action to be performed to achieve this.

Regards,
Sunil

https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files3/7061c9728378af97b84c2daf9afb29be155fbd5d_2_1035x385.png 1.5x, https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/7061c9728378af97b84c2daf9afb29be155fbd5d.png 2x" data-dominant-color="E7ECEC">

ArchiveIssue.PNG1125×420 30.4 KB

Hi Sunil,

make sure that all prerequisites for archiving have been setup correctly.

Refer to Monitor Users Guide for further informations.

This affectes settings in WmMonitor package, IS JDBC-Pools settings, SAML Resolver URL in IntegrationServer as well as grants and certain configurations in the database schemas for auditing and archiving.

Which user are you trying to use for starting the archiving via MWS?
Administrator or other user?

Are there several IntegrationServer defined in MWS or not?
If there is only one IntegrationServer defined, this should be working if all other things are setup correclty.
If there are several IntegrationServers are defined, then this will not work as the Archiving pportlet does noit include the IS server selector portlet (at least up to 9.5 SP1; I am not sure for newer versions).

Which version of wM are using?

Addendum:
Does archiving work when being invoked directly from IntegrationServer packahe management - > browse for services → pub.monitor.archive:*?
Try to Test the services and fill in the parameters you have shown in the screen shot.

Please note the differing values for certain fields:
Status: COMPLETED or COMPLETED-FAILED
Action: ARCHIVE or DELETE
"Days to retain" and "Retention period start" are mutually exclusive.

This is described in the Monitor Buil-tn-Services Guide.

When using the UI the values will be translated and mapped behind the scenes accordingly.

Regards,
Holger

Hi Holger,

Which user are you trying to use for starting the archiving via MWS? - Administrator

Are there several IntegrationServer defined in MWS or not?- Single server

Which version of wM are using?- 8.2

Regards,
Sunil

Hi Sunil,

Administrator user is fine.

Are there any Fixes applied to Monitor, Monitor UI, MWS, IntegrationServer, SharedComponents?

Please check your IS server.log and MWS fuill.log for further informations for your error message.

Regards,
Holger

Hi Holger,

I have set the prerequisites for this archival process and now I am getting the different error like:

Error in deleting driver tables and commiting: java.sql.SQLSyntaxErrorException: [sag-cjdbc42-0011][Oracle JDBC Driver][Oracle]ORA-00942: table or view does not exist

Even though the tables are existing in the DB.

Can you please suggest what is going wrong in this and what all other things we can perform.

Regards,
Sunil

https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/71377a35fadae3e9dd31448ff4c484bc14d98bf6.png 1.5x, https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/71377a35fadae3e9dd31448ff4c484bc14d98bf6.png 2x" data-dominant-color="E6EAEA">

ArchiveIssue.PNG973×463 34 KB

Hi Sunil,

looks like you have an issue with the JDBC-Pools for ISCoreAudit and Archiving.

Did you setup archiving schema with proper grants for ISCoreAuditSchema?
Did you update OPERATION_PARAMETER table in Archive schema with the name of the ISCoreAudit schema?

Regards,
Holger

Hi Holger,

I have taken the server log and in the log it is saying WMSERVICE_DRIVER table is not existing. I checked for this table in the DB, But no where this table available.

2017-05-30 15:17:07 BST [MOD.0120.0770T] DB URL: jdbc:wm:oracle://10.142.1.92:1527;serviceName=WMDB
2017-05-30 15:17:07 BST [MOD.0120.0770T] DB URL: jdbc:wm:oracle://10.142.1.92:1527;serviceName=WMDB
2017-05-30 15:17:07 BST [MOD.0120.0000T] got jdbc connection com.wm.app.jdbc.JDBCConnection@686e3c3d
2017-05-30 15:17:07 BST [MOD.0120.0000T] valid jdbc connection com.wm.app.jdbc.JDBCConnection@686e3c3d
2017-05-30 15:17:07 BST [MOD.0120.0032T] got connection: com.wm.monitor.db.ISConnection@1d34fe5b
2017-05-30 15:17:07 BST [MOD.0120.0000T] got jdbc connection com.wm.app.jdbc.JDBCConnection@4c06f46
2017-05-30 15:17:07 BST [MOD.0120.0000T] valid jdbc connection com.wm.app.jdbc.JDBCConnection@4c06f46
2017-05-30 15:17:07 BST [MOD.0120.0032T] got connection: com.wm.monitor.db.ISConnection@75c95f19
2017-05-30 15:17:07 BST [MOD.0120.0000T] got jdbc connection com.wm.app.jdbc.JDBCConnection@39774b29
2017-05-30 15:17:07 BST [MOD.0120.0000T] valid jdbc connection com.wm.app.jdbc.JDBCConnection@39774b29
2017-05-30 15:17:07 BST [MOD.0120.0032T] got connection: com.wm.monitor.db.ISConnection@46e78e38
2017-05-30 15:17:07 BST [MOD.0120.0000T] got jdbc connection com.wm.app.jdbc.JDBCConnection@35f986eb
2017-05-30 15:17:07 BST [MOD.0120.0000T] valid jdbc connection com.wm.app.jdbc.JDBCConnection@35f986eb
2017-05-30 15:17:07 BST [MOD.0120.0032T] got connection: com.wm.monitor.db.ISConnection@1108c9fc
2017-05-30 15:17:07 BST [MOD.0120.0001T] in method InterDbAccess.execUpdate()
2017-05-30 15:17:07 BST [MOD.0120.0020D] SQL statement: DELETE FROM WMSERVICE_DRIVER
2017-05-30 15:17:07 BST [MOD.0120.0001T] in method InterDbAccess.rollbackAndRemoveConnection()
2017-05-30 15:17:07 BST [MOD.0120.0024D] action: rollback
2017-05-30 15:17:07 BST [MOD.0120.0024D] action: remove
2017-05-30 15:17:07 BST [MOD.0120.0034D] encountered errors during connection
2017-05-30 15:17:07 BST [MOD.0120.0034D] encountered errors during connection
2017-05-30 15:17:07 BST [MOD.0120.0036T] removing connection from pool: com.wm.app.jdbc.JDBCConnection@686e3c3d
2017-05-30 15:17:07 BST [MOD.0120.0018T] released connection: com.wm.monitor.db.ISConnection@1d34fe5b
2017-05-30 15:17:07 BST [MOD.0120.0036T] removing connection from pool: com.wm.app.jdbc.JDBCConnection@4c06f46
2017-05-30 15:17:07 BST [MOD.0120.0018T] released connection: com.wm.monitor.db.ISConnection@75c95f19
2017-05-30 15:17:07 BST [MOD.0120.0002T] leaving method InterDbAccess.rollbackAndRemoveConnection()
2017-05-30 15:17:07 BST [MON.0119.0305E] Error in deleting driver tables and commiting: java.sql.SQLSyntaxErrorException: [sag-cjdbc42-0011][Oracle JDBC Driver][Oracle]ORA-00942: table or view does not exist

Regards,
Sunil

Hi Sunil,

can you please provide screenshots for the following:

• Overview of the JDBC Pools page from IS Admin UI
• Details for the JDBC Pools for IS Audit and Archiving function
• List of tables present in the db schema used for the Archiving function
• Content of the OPERATION_PARAMETER table in the db schema used for the Archiving function

In DB-Configurator there is a component named Archving. This one needs to be executed against the schema for the Archiving function.
This component should create all neccessary tables, packages etc. needed for archiving.

The WMSERVICE_DRIVER table as well as the other DRIVER tables are intermediata tables in which the context ids for the objects selected for archiving/deletion are recorded before starting the real archiving/dleletion process.

Regards.
Holger