I'm looking for documentation on how to update the database information (point to a database backup) in RSA Identity Governance and Lifecycle 7.1.0.168534 P09. The only solutions I have found so far have simply to uninstall and re-install the software to point to the new location.
I see instructions on page 188 of the 7.1.1 installation guide and on page 216 of the 7.1 installation guide (both freshly downloaded). IIRC, RSA support also gave us similar instructions, although they said that reinstalling is the best way. This is highly relevant for me as we are starting to migrate our database to an Exadata machine.
I do not mind being wrong! I did not know that section was there. (RSA Identity Governance and Lifecycle 7.1.1 Installation Guide )
This sentence worries me a bit as the instructions are not explicit. I hope its easy to find these references.
System scripts may reference the Oracle SID. The setDeployEnv.sh script in the /home/oracle,
/home/admin, and /root directories must be updated for the scripts to execute properly.
Perhaps have a look at my comment in How to point Remote DB?. I updated it slightly based on this discussion so it might work for you.
I should have looked at your answer more carefully before going off and updating things. It would have saved me some time. We had updated ORACLE_SID but not ORACLE_SERVICE_NAME or ORACLE_CONNECTION_ID. I changed our script to update ORACLE_SERVICE_NAME, but not ORACLE_CONNECTION_ID. It "works for me" with a few caveats:
I'll be opening support cases for (2) and maybe (3). It may just be that our export was bad.
I honestly never knew about that parameter you mentioned in steps 1. Not sure if it will get auto-updated upon the next application startup or not but would be good if you can share the results from your test.
As for items 2 and 3, those shouldn't happen from this kind of change. Keep us posted on the findings from your support cases.
Unfortunately, it does not seem to be updated on startup or shutdown.
My own investigations have identified the cause of the “exact fetch” issue, though I don’t know how to solve it. It seems to be happening because our new environment is a RAC. The installation guide for IGL says that RAC is supported. Does anyone know if the installer uses different versions of packages in a RAC vs. non-RAC scenario?
Sent from Outlook<https://aka.ms/qtex0l> on iOS
Yes the RAC problem with ASRs is already fixed starting 7.1.1 P04 (ref: ACM-99240)
Thanks Mostafa! That's going to save me a lot of time! Is there a DOC for this?
Yes there is now a general page for all 7.1.1.x patch release notes: RSA Identity Governance and Lifecycle 7.1.1.x Release Notes . It is a collective list of all changes and fixes in all patches up till now.
Mostafa Helmy, given that there is a different method in the product documentation, is Ian's initial answer actually the "correct" answer? It sounds to me like the situation is more complicated than that.
I could not mark the answer as incorrect, so I deleted my answer.
If you need to remove a Mark Correct flag, just let me know! I can take care of that for you.
Regards,
Erica
Perhaps have a look at my comment in How to point Remote DB?. I updated it slightly based on this discussion so it might work for you.