Update the Aternity Database for Aternity v9.x

As a licensed DBA (only), you can update your Aternity database to the required Oracle versions for Aternity 9.x:

  • Oracle Database version 12c Enterprise Edition 64-bit, with patch set 12.1.0.2

  • Oracle Database 11gR2 Enterprise Edition 64-bit with patch set 11.2.0.4

You MUST use the Aternity Database Verification Utility to check and fix the database structure, schemas, and content to ensure they are compatible with Aternity 9.x. The utility creates a report of the changes required to prepare the database for Aternity 9.x.

Use the Aternity Database Verification Utility as part of the database update for Aternity 9.x

You must run the Aternity Database Verification Utility several times before and after updating the database (learn more):

  1. A week before updating, run the Aternity Database Verification Utility from the Management Server to find any issues with the existing database.

    Fix all the flagged items listed in the reports by updating the settings in your legacy Aternity or by asking a DBA to change the database directly.

  2. Run the utility a second time before updating, to check there are no more actionable changes.

    Tip

    We strongly advise you to submit this report to Customer Services to confirm your database is ready for the update.

  3. Ask your DBA to update Oracle. Aternity 9.x requires that the Aternity Database Server runs either Oracle 11.2.0.4 or 12.1.0.2

    You can download either version of Oracle from the Related Links of the Riverbed support site.

  4. After the database update, run the utility again to check if there are issues with the updated database.

    Implement the required fixes. To resolve an issue from within Aternity's settings, you must first complete all the server updates, then implement those fixes.

During updates, set the utility to run two scripts, one to check the database structure, and the other to check the schema and existing data.

Before you begin

  • When you run the Aternity Database Verification Utility for the first time, you must still have a fully functioning Aternity v7.1.x or v8. This allows you to make any required changes to Aternity's settings, like its Monitors tree.

  • If your legacy Agents communicate over TCP, you must first test then switch from TCP to HTTP(S).

  • Ensure you have local administrator privileges on this computer.

  • Ensure you have a username and password to the Oracle database which has SYSTEM privileges. If you cannot obtain SYSTEM credentials, contact Customer Support for a script which your DBA can run separately.

  • Allow yourself several days to check the status of your existing database with the Aternity Database Verification Utility, update the database, and verify the updated database.

  • Prepare the Aternity Database Server with the following requirements:

    Attribute Requirement

    Oracle version for Aternity Database Server

    Aternity 9.x requires that the Aternity Database Server runs either Oracle 11.2.0.4 or 12.1.0.2 (including support for Oracle Data Guard):

    • Oracle Database version 12c Enterprise Edition 64-bit, with patch set 12.1.0.2

    • Oracle Database 11gR2 Enterprise Edition 64-bit with patch set 11.2.0.4

    You can download either version of Oracle from the Related Links of the Riverbed support site.

    Operating system for Aternity Database Server

    Windows Server 64 bit 2012 R2 or 2008 R2 Enterprise Edition. Set the date and time formats to Control Panel > Regions > Formats > English (United States).

    You can also install the Database Server on Linux CentOS 5.8 or Linux RedHat Fedora.

    Hardware

    Hardware specifications depend on the size of your Aternity on-premise deployment. Choose the sizing and hardware specifications for your deployment size.

    Permissions

    Ensure you have local administrator privileges on this computer.

Procedure

  1. Step 1 Access the Aternity Management Server.
  2. Step 2 Log in to the computer as a local administrator.

    To verify you are a local administrator on this computer, not a domain administrator, open the System control panel, select Advanced system settings > Computer Name, and confirm the Change button is active.

  3. Step 3 A week before updating, run the Aternity Database Verification Utility from the Management Server

    Download the latest version of Aternity on-premise from our website. Copy the Aternity Database Verification Utility to the Management Server computer.

    Important

    For updates, you MUST run this utility from the Management Server.

  4. Step 4 Launch the Aternity Database Verification Utility.

    Right-click and select Run as administrator.

  5. Step 5 Choose a destination directory to install, then proceed.
  6. Step 6 For updates only, run both scripts to check both the structure and the content of the database.
    For an existing deployment, choose both verification options.
  7. Step 7 Enter the details required to connect to the Aternity database to verify its compatibility.

    Typically, the system already fills these fields based on the existing database.

    Enter connection details to the Aternity database
    Field Description
    Username / Password

    Enter the username of the database which has SYSTEM privileges, and its password.

    Database Host

    Enter the hostname, IP address, or DNS name of the Database Server.

    Port

    Enter the port required to access the Database Server (default is 1521).

    Service

    Enter the database service name (usually Aternity). This is the alias to the instance of the Aternity database.

    Verify Platform Database Credentials

    Displays that the utility checks the existing structure and content of the database.

    Platform Database Username

    If your database already has the schema set up, it would automatically detect and display ATERNITY as the schema name which you are checking.

  8. Step 8 Select the size of your deployment.

    The parameters of the database are different depending on the size of your deployment, measured as the number of monitored devices. You must choose the same size in this screen and in the same screen during the setup of the Management Server.

    The database parameters depend on the intended size of the deployment
  9. Step 9 View the compatibility report for each script.

    You can copy each report to the clipboard, or view the location to find the report as a plain text file.

    View each compatibility report

    You MUST act on the items in the top part of each report, as they are errors. The remainder of the report (after the title Additional Database Information) contains optional warnings which we recommend you change.

    Tip

    We strongly advise you to submit this report to Customer Services to confirm your database is ready for the update.

  10. Step 10 Fix all the flagged items listed in the reports by updating the settings in your legacy Aternity or by asking a DBA to change the database directly.
  11. Step 11 Run the utility a second time before updating, to check there are no more actionable changes.

    Fix all the flagged items listed in the reports by updating the settings in your legacy Aternity or by asking a DBA to change the database directly.

    Tip

    We strongly advise you to submit this report to Customer Services to confirm your database is ready for the update.

  12. Step 12 Ask your DBA to update Oracle. Aternity 9.x requires that the Aternity Database Server runs either Oracle 11.2.0.4 or 12.1.0.2

    You can download either version of Oracle from the Related Links of the Riverbed support site.

  13. Step 13 After the database update, run the utility again to check if there are issues with the updated database.

    Implement the required fixes. To resolve an issue from within Aternity's settings, you must first complete all the server updates, then implement those fixes.