search cancel

Considerations For Upgrading/Migrating Nolio RA's Oracle DB

book

Article ID: 109962

calendar_today

Updated On:

Products

CA Release Automation - Release Operations Center (Nolio) CA Release Automation - DataManagement Server (Nolio)

Issue/Introduction

We are planning to upgrade Oracle 12c to Oracle 19c. What considerations should be taken into account for Nolio Release Automation?


Environment

Release : 6.x

Component : CA RELEASE AUTOMATION RELEASE OPERATIONS CENTER

 

Resolution

Considerations include:

  1. Making sure that the version of Nolio Release Automation that you're on supports the version of Oracle you are planning to upgrade/move to. You can find this by reviewing the following sections in the System Requirements page:
    • Database Support
    • Oracle Installation Requirements
  2. Backup the Nolio Release Automation database/schema to make sure you have a working copy. 
  3. Connection details might change.
    • Backup a copy of the NACInstallDir/webapps/datamanagement/WEB-INF/distributed.properties.
    • Search for any uncommented entries with "database" in the distributed.properties file. The entries are further documented here: Manually Configure Communication with the Database
      • Share these entries with your DBA to see if any of that information is going to change.
      • If yes, make sure to update those values after the upgrade/migration.
  4. Before the database is upgraded/migrated it is recommended to stop the management server's services.
  5. After the database upgrade/migration is complete, 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 to the database then you will not receive a prompt for username/password when attempting to launch the ROC (Release Operations Center) web ui.