Archana (Customer) asked a question.
RSA IGL Migration from 7.2.1 to 7.5.2 : Remote database Upgrade from Oracle 12C to 19C
Hello all,
As part of migration to RSA IGL 7.5.2 version, we have some confusions on the steps to be followed.
We have software bundle installation, with Remote Oracle 12C database(RSA Provided). We couldn't see the clear documentation on RSA Migration on the steps to upgrade this in remote database. Which steps we should follow.
Quote from the 7.5.2 Upgrade and Migration Guide (https://community.rsa.com/s/article/RSA-Governance-Lifecycle-7-5-2-Upgrade-and-Migration-Guide), Chapter 7, page 48:
we followed the steps as per document “IGL_7.5.2Upgrade_and_Migration_Guide_7.5.2.pdf”
We could successfully upgrade the application. As our configuration is for remote database, we tried to follow steps mentioned in page number 48.
But when we tried to run upgradeOracle.sh from database server we are getting below error
Could not find /tmp/aveksa/staging/aveksa.ear
Missing file/directory in the staging directory /tmp/aveksa/staging. Exit Installation.
The file aveksa.ear should not be needed for the database upgrade. Try the following command (to create an empty file) and then attempt the upgrade again to see if it moves forward:
touch /tmp/aveksa/staging/myfile.txt
We were able to proceed with the update script & in logs everything showed successful. But once the operation is complete the environment variables are still set to 12c & unable to connect with database. We could see like both 12 & 19 folders present in /u01/app/oracle/product/1
Do we neeed to change these manually or what should be the next step in this?
I've done something similar in the past and I had to change the database settings in the files: "Aveksa_System.cfg", "setDeployEnv.sh" and the wildfly configuration for the 7.2.1. this was the "aveksa-standalone-full.xml" file but for 7.5.2. they changed this to some other file I don't have at hand.
This is not a good situation. In my experience the upgrade scripts work correctly if the original installation of Oracle was done in using our scripts. The failure of the upgrade scripts to work correctly suggests something is non standard with the original 7.2.1 (or earlier) installation.
My recommendation would be to stop trying to recover this system and do a fresh installation of the database (with an import of the legacy data). If you have this problem you will likely have problems running the appliance updater and you will have problems with future upgrades and patches. At some point you have to start over with this database installation and my recommendation would be that now is that time.
It is very difficult to cleanup the failed uninstall of Oracle 12c and this will require engineering assistance.
Please open a support ticket for this issue so that we can give you specific advice.