000038446 - After applying a patch, an 'ORA-06502: PL/SQL: numeric or value error: character string buffer too small' error occurs when starting RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Feb 11, 2020
Version 1Show Document
  • Comment • 0
  • View in full screen mode

Article Content

Article Number000038446
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.x
 
IssueWhen starting RSA Identity Governance & Lifecycle after applying a patch, the application startup fails and the system is inaccessible. 

The aveksaServer.log file ($AVEKSA_HOME/wildfly/standalone/log/aveksaServer.log) has the following errors:

01/27/2020 17:49:07.597 ERROR (ServerService Thread Pool -- 106) 
[com.aveksa.migration.jdbctool.CheckDatabase] ORA-06502: PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at "AVUSER.STATISTIC_TABLES", line 55
ORA-06512: at "AVUSER.STATISTIC_TABLES", line 55
ORA-06512: at "AVUSER.DATABASE_STATISTICS", line 21
ORA-06512: at "AVUSER.DATABASE_STATISTICS", line 21


Please refer to RSA Knowledge Base Article 000030327 -- Artifacts to gather in RSA Identity Governance & Lifecycle to find the location of the aveksaServer.log for your specific deployment if you are on a WildFly cluster or a non-WildFly platform.
 
CauseThis error can occur when processing Database_Statistics if there is a database table name longer than 30 characters. We have seen this issue when customers have created custom tables with table names greater than 30 characters in length in the avuser schema.
ResolutionTo determine if this is the issue, as avuser, run the below query to find the list of all tables in the avuser schema and their table name lengths:
 

select table_name, length(to_char(table_name)) as table_length from user_tables 
order by 2 desc;


If you find that there are any custom tables with a table name length greater than 30 characters, then any one of the below options maybe used to resolve the issue:
  • Drop the custom table if the table is no longer used. Run this command as avuser.


    DROP TABLE <TABLE_NAME>;

  • Rename the table name and make sure the length of the new table name is less than 30 characters. Run this command as avuser.

    ALTER TABLE <TABLE_NAME> RENAME TO <NEW_TABLE_NAME>;

NotesWhen you rename an Oracle table you must be aware that Oracle does not update applications (HTML-DB, PL/SQL that referenced the old table name) and PL/SQL procedures may become invalid. So please make sure any reference of the old table name is updated.

Attachments

    Outcomes