- Making sure that the version of CA Release Automation that you're on supports Oracle 12c. You can find this by looking at the system requirements page for the version of CA Release Automation you're using. This URL is the documentation URL for version 6.6. But there is a versions dropdown on the page where you can select the version you're using. https://docops.ca.com/ca-release-automation/6-6/en/installation/system-requirements
Note: Some versions of RA certify version 12c with specific patch levels (considered the minimum patch level for it to work).
- Backup the CA Release Automation database/schema to make sure you have a working copy so if there are any problems you can get it restored someplace and maybe just point CA Release Automation to a different system. I personally use expdp and impdp to backup/restore Oracle Schemas. Please let us know if you have any other problems/questions.
- Oracle 12 does introduce PDBs. It might change the connection details which might cause connection errors when RA starts. To try and avoid this I would recommend reviewing your NACInstallDir/webapps/datamanagement/WEB-INF/distributed.properties file for any uncommented entries with "database" in them. Those are the details we use to make a connection to the database. I'd recommend copying those entries and sending them to your DBA to see if any of that information is going to change. If yes then make sure to update those values after the upgrade is complete and then start your NAC services.
- Before the database is upgraded it is recommended to stop the management server's services.
- After the database upgrade is completed be sure to update the distributed.properties file with any changes recommended by your DBA (from point #3 above) and then start the management server's services.
In general, after upgrading the database the NAC will either connect to the database or it won't. If it does not connect then you will not receive a prompt for username/password.