Upgrade of 10.2 to 10.3 causes an issue in Oracle DB

Document ID : KB000045886
Last Modified Date : 14/02/2018
Show Technical Document Details

 Issue:

 Upgrade of 10.2 to 10.3 causes an issue in Oracle Databases

 During EM startup, there is the following error message in the EM log :

[ERROR] [main] [Manager.AppMap] Unable to migrate existing pre-10.3 universe users - PreparedStatementCallback; SQL [insert into aca_acl(acl_id, service_provider_id, service_provider_instance_id, resource_type_id, resource_id, group_id, user_id, capabilities_allow, capabilities_grant, last_update) values( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]; ORA-00001: unique constraint (OBL104CEM.ACA_ACL_AK1) violated

 

 Environment:

 EM version 10.3, this problem applies to both fresh install (only if you make a backup of the 10.2 DB, perform a fresh install and then migrate that DB over to the new  install) and upgrade.

 This is only seen on Oracle DB.  Postgres is not affected

 

 Cause:

 Error happens during the migration of pre-10.3 Universe permissions to 10.3 structure. This happens because unique indices defined for Oracle do not allow new  records to be inserted into table ACA_ACL. As a result, the migration process fails. Because of this, some non-Admin users might not have Universe permissions  defined and will not be able to access Universes.

 

 Workaround:

 Execute the following commands in the Oracle database by an Oracle Admin:

 drop index ACA_ACL_AK1;

 drop index ACA_ACL_AK2;

 Then EM should be restarted. 

 If the error is not seen in the EM log anymore, then migration of Universe permissions was completed successfully.

 

 Additional Information:

 This problem is fixed in 10.4