Migration to version 7.5.2 P03 or later completes with ORA-31011: XML parsing failed error in RSA Governance and Lifecycle

2 years ago

Article Number

000068251

Applies To

RSA Product Set: RSA Governance & Lifecycle
RSA Version/Condition:

RSA Governance & Lifecycle 7.5.2 P03 and later

Issue

After running the migration for version 7.5.2 P03, it was noticed that the migration was completed with errors, refer to the following figure for an example.

In the migration log, it is noticed that the script ACM_104766_1.sql is resulting in the error.

------- 
SQL/line#: /home/oracle/wildfly-24.0.1.Final/domain/servers/img-server-1/tmp/vfs/temp/tempe65acefd1d139d38/content-b169f480eaf6505a/contents/aveksa.war/WEB-INF/database/updates/7.5/ACM-104766_1.sql(4):
Start time [Fri Jun 16 13:09:23 EDT 2023]
.
.
<SQL Query>
.
.
--------------------------- Dbms_Output Begin ---------------------------
Migrating total attribute change rule: 3
Migrating rule with ID = 4
v_action_type is: pol:CreateChangeRequestAction
Error in migrating rule with ID = 4
ORA-31011: XML parsing failed
ORA-19213: error occurred in XML processing at lines 1
LPX-00242: invalid use of ampersand ('&') character (use &amp;)
ORA-06512: at "SYS.XMLTYPE", line 48
Migrating rule with ID = 3
v_action_type is: pol:CreateChangeRequestAction
Error in migrating rule with ID = 3
ORA-31011: XML parsing failed
ORA-19213: error occurred in XML processing at lines 1
LPX-00242: invalid use of ampersand ('&') character (use &amp;)
ORA-06512: at "SYS.XMLTYPE", line 48
Migrating rule with ID = 1
v_action_type is: pol:ReviewPolicyAction
v_action_type is: 
v_action_type is: 
There is no CreateChangeRequestAction, No Migration required.
Migrating rule version with ID = 15
v_action_type is: pol:CreateChangeRequestAction
Error in migrating rule version with ID = 15
ORA-31011: XML parsing failed
ORA-19213: error occurred in XML processing at lines 1
LPX-00242: invalid use of ampersand ('&') character (use &amp;)
ORA-06512: at "SYS.XMLTYPE", line 48
Migrating rule version with ID = 12
v_action_type is: pol:CreateChangeRequestAction
Error in migrating rule version with ID = 12
ORA-31011: XML parsing failed
ORA-19213: error occurred in XML processing at lines 1
LPX-00242: invalid use of ampersand ('&') character (use &amp;)
ORA-06512: at "SYS.XMLTYPE", line 48
Migrating rule version with ID = 4
v_action_type is: pol:ReviewPolicyAction
v_action_type is: 
v_action_type is: 
There is no CreateChangeRequestAction, No Migration required.
Completed migrating rule entitlement filter
---------------------------  Dbms_Output End  ---------------------------

Cause

In an attribute change rule, if the selected revoke entitlement like global-role, app-role, group, or entitlement has the "&" character in its name, then the script will break to migrate the Attribute Change rule.

Resolution

This issue is resolved in the following version:

RSA Governance & Lifecycle 8.0.0

Workaround

Contact RSA Customer Support and quote this KB article for the workaround for this issue.

Notes

Failure of migration of Attribute Rule will not cause Rule to fail but the Action will be Revoke All entitlement instead of Selected entitlement.

The fix is applied to handle the "&" character.

Any customer migrating from version 7.2.1 or 7.5.0 to version 8.0 will not face any issues.

Any customer migrating from version 7.2.1 or 7.5.0 to version 7.5.2 has to follow the workaround steps before migration.

For any customer to check if the issue will occur in the system migration, execute the following select query to check for the entitlements that have "&" in the name, then try to edit the name to remove the "&" character, if not possible refer to the workaround section.

select * from T_AV_PROV_ENTS 
where resource_name like '%&%'
OR app_name like '%&%'
OR name like '%&%'
OR action like '%&%';

Attachments

If the attachment does not open when clicked, please refresh the page and try again. You must be logged into view the file(s).

Don't see what you're looking for?

Related Articles

Trending Articles