000038569 - 'Request could not be handled' error exporting metadata from RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Mar 16, 2020
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000038569
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.0.x, 7.1.x, 7.2.x
 
IssueWhen exporting metadata in RSA Identity Governance & LifecycRSA Identity Governance (Admin > Import/Export > Export), the metadata export fails with:
 
The request could not be handled

 

User-added image


 
CauseThis issue has two known root causes:
  1. Corrupt data in one or more metadata objects being exported.

When exporting metadata, if any of the table definitions being exported have invalid or corrupt data in those tables, the metadata export will fail.


  1. Insufficient privileges on one or more metadata objects being exported.

When exporting metadata, if any of the table definitions being exported belong to a custom table to which avuser does not have select privileges, the metadata export will fail.

 
ResolutionTo resolve this issue, the corrupt data needs to be fixed and the select privilege needs to be granted on any custom tables in the avuser schema.

If corrupt data is suspected, one known corruption has been reported in RSA Knowledge Base Article 000035732 -- 'Request could not be handled' and 'No enum constant com.aveksa.server.core.DataCollector.Status.InActive' errors exporting metadata from RSA Identity Governance & Lifecycle. For any other suspected data corruption issues that might be affecting the metadata export, please contact RSA Identity Governance & Lifecycle Support for further assistance.

For any custom tables in the avuser schema, follow these steps to grant the proper privileges to those tables:
  1. Login to SQL as the avuser
  2. Execute the following SQL grant statement:


grant select on <table | view> to avdwuser


For example:



grant select on custom_table_1 to avdwuser

 
NotesWhen the avdb schema is initially created, the avdwuser is given select privileges on all tables using the following script file:
 
$AVEKSA_HOME/database/Create Scripts/Grant_Select_To_Reports.sql 
 

Any tables created after the avdb schema has been created need to have the grant select statement executed manually.
 

Attachments

    Outcomes