ORA-64464 error when upgrading to RSA Identity Governance & Lifecycle 7.2.1
Originally Published: 2020-11-17
Last Modified: 2022-06-20
Article Number
Applies To
RSA Version/Condition: 7.2.1
Issue
Upgrade to RSA Identity Governance & Lifecycle 7.2.1 fails with the following message in the console.
Found invalid object(s) in the database. Please check the log for error(s). Schema Migration completed in Oh 0m 9s with errors.
The following errors are logged to the migrate.log file.
END;, Error Msg = ORA-64464: XML event error
ORA-19202: Error occurred in XML processing
In line 4 of orastream:
LPX-00242: invalid use of ampersand ('&') character (use &)
ORA-06512: at line 207
The aveksaserver.log shows that the startup has failed.
10/21/2020 22:07:34.879 INFO (default task-15) [com.aveksa.migration.jdbctool.CheckDatabase] Schema Migration 10/21/2020 23:39:06.072 ERROR (Schema Migration) [SystemErr] log4j:ERROR Attempted to append to closed appender named [null]. 10/21/2020 23:39:06.072 ERROR (Schema Migration) [SystemErr] log4j:ERROR Attempted to append to closed appender named [null]. 11/06/2020 13:08:38.190 ERROR (default task-12) [SystemErr] log4j:ERROR Attempted to append to closed appender named [null]. 11/06/2020 13:29:46.599 WARN (Schema Migration) [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] SQL Error: 0, SQLState: null
In addition, there could be secondary errors as the result of the migration failing to complete including but not limited to the following errors.
Found invalid object(s) in the database. Please check the log for error(s).
Cause
This is a known issue in the following versions.
- RSA Identity Governance & Lifecycle 7.2.1
- RSA Identity Governance & Lifecycle 7.2.1 P01
This issue only occurs if the migrated data includes the following Rule types and only if those Rules include references to Roles. It occurs if Role information referenced by the Rules has Role names that include extended characters.
- Role Membership Rule Difference
- Role Metric Change
- Role Missing Entitlements
Resolution
This issue is resolved in the following version.
- RSA Identity Governance & Lifecycle 7.2.1 P02
Note that as of January 2020 the official distribution on RSA Link for the 7.2.1 release has been replaced with the 7.2.1 P02 version which is not susceptible to this issue. Customers now downloading RSA Identity Governance & Lifecycle should not encounter this issue.
Workaround
If the customer is doing migration in multiple environments, they should be encouraged to download a new copy of the software.
Related Articles
WFLYCTL0344 Operation timed out awaiting service container stability error when patching RSA Identity Governance & Lifecycle 330Number of Views On database startup for RSA Identity Governance and Lifecycle the following error is seen: CRS-2501: Resource 'ora.avdb.d… 531Number of Views Report preview and/or generation fails with 'java.lang.NoClassDefFoundError: Could not initialize class net.sf.jasperrepor… 475Number of Views Windows Shared Folder Connection Error During Upgrade/Backup 342Number of Views Error "Request Entity Too Large" when upgrading RSA Authentication Manager from versions (8.2 SP1 up to 8.4 P13) to 8.5 365Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Reporting on RSA Authentication Manager 8.x users with On-Demand Token, a fixed passcode or a hardware/software token assi… How to Download OTP Token Seed Files from myRSA Anomalix idGenius - SAML Relying Party Configuration - RSA Ready Implementation Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?