000037254 - Migration fails with 'ORA-19011: Character string buffer too small' error when upgrading RSA Identity Governance & Lifecycle 7.x

Document created by RSA Customer Support Employee on Mar 25, 2019Last modified by RSA Customer Support Employee on Feb 14, 2020
Version 5Show Document
  • View in full screen mode

Article Content

Article Number000037254
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.1.0, 7.1.1
IssueThe RSA Identity Governance & Lifecycle migration fails when upgrading to 7.1.x.

The following error message is logged to the migrate.log file located in:
   $AVEKSA_HOME/wildfly/standalone/log/migrate.log if the migration was started from the RSA Identity Governance & Lifecycle user interface, or,
   $AVEKSA_HOME/database/log/migrate.log if the migration was executed from the command line.

Start time [Mon Mar 11 14:07:55 CDT 2019]
update t_av_entitlementreviewdef set configuration = replace(configuration,
        where review_type = 'U' and configuration not like '%<rev:review-analysis-config>%'
java.sql.SQLException: ORA-19011: Character string buffer too small

CauseThis issue occurs during the upgrade of Reviews if the configuration elements in part of the Review definition exceed 4000 characters (4K).  

Specifically, this may occur if the review contains an extensive explicit list of entitlements, roles, groups or data resources.

This issue is resolved in the following RSA Identity Governance & Lifecycle versions and/or patch levels:

  • RSA Identity Governance & Lifecycle 7.1.0 P08
  • RSA Identity Governance & Lifecycle 7.1.1 P02
  • RSA Identity Governance & Lifecycle 7.2
WorkaroundIdentify which Review item(s) have configuration objects that exceed 4000 characters (see Notes).

The following options may be used to work around this issue.
  1. Delete the problem review.
  2. Edit the problem review and remove or reduce entitlements, roles, groups or data resources.
  3. Edit the problem review and filter by groupings instead of individual items.

For example, instead of listing all AD groups individually, select AD groups by business source.
User-added image
NotesThe following SQL command may be used to identify which review has a configuration object that exceeds 4000 characters.

    length(xmltype.getclobval(configuration)) > 4000;