Problem encountered during database schema migration RSA IG&L 7.1.1 to 7.2.1

[JacquesAdankon]

Hello,

When trying to migrate RSA 's oracle database to a newer version, I got an error.

First of all, I had RSA 7.1.1 installed  as software bundle using customer supplied database, both installed on separated machines.

Then I decided to upgrade to RSA 7.2.1. So I installed RSA 7.2.1 on a third server using the same customer supplied database.

The installation process went successfully, but when tried to access the RSA IG&L IHM, I got this message "Schema Migration is required. Current database schema version is 7.1.1.161195. New server schema version is 7.2.1.179069."

I entered the password given in "IGL_7.2.1_Upgrade_and_Migration_Guide" and processed the schema migration and I got errors. 

This is what I get when trying to access RSA IG&L IHM 7.2.1.

I joined as attachments "migrate.log" and "aveksaServer.log" files.

Thanks in advance for your help.

[IanStaines]

I moved this post to the RSA Identity Governance & Lifecycle community. 

[MHelmy]

Take a look at this KB article:

000035667 - Startup fails with Initialization Status error message 'Found invalid object(s) in the database' after migration or patching RSA Identity Governance & Lifecycle

However in all cases I would strongly recommend raising a case with RSA Support to check your logs and give you a definitive fix.

[IanStaines]

Yes the particular failure is very unusual

ORA-06508: PL/SQL: could not find program unit being called: "AVUSER.PUBLIC_SCHEMA"

I think there is something wrong with the permissions on the target database.  This is not a simple migration failure, something is fundamentally wrong. 

I am going to remove the attachments from the post as they may contain sensitive information.  I recommend you open a support case for this issue. 

[JacquesAdankon]

Hello,

Thank you both for your help. I will try these solutions.

[IanStaines]

Note that this issue has been identified as a defect in the way Rule data is migrated.  This is under investigation in ACM-108383.   If you encounter this problem please open an RSA Customer Support case for guidance until an official fix is announced.  

[IanStaines · Accepted solution]

Here is the KB article for this issue:

https://community.rsa.com/docs/DOC-115091