Article Content
Article Number | 000038446 |
Applies To | RSA Product Set: RSA Identity Governance & Lifecycle RSA Version/Condition: 7.x |
Issue | When 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:
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. |
Cause | This 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. |
Resolution | To 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:
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:
|
Notes | When 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. |