Update the Oracle Database Server for Aternity 10

The Oracle Database Server in Aternity on-premise 10.x supports the following Oracle versions:

  • Aternity 10.x requires Oracle Database version 12c Enterprise Edition 64-bit, 12.1.0.2 or Oracle Database 11gR2 Enterprise Edition 64-bit with patch set 11.2.0.4.

Therefore, whether or not you upgrade the Oracle version, you MUST still use the Aternity Database Verification Utility to check the schema and content, as the database requirements of Aternity 10.x are slightly different. If you changed your deployment sizing, this may also impact on the database. The utility creates a report of the changes required to prepare the database for Aternity 10.x.

For upgrades, you must run this utility on the computer Aternity Management Server.

Use the Aternity Database Verification Utility to prepare the database for Aternity 10

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 Aternity Management Server to find any issues with the existing database.

    Tip

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

    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.

  3. (Optional, only if you change Oracle versions) Ask your DBA to update Oracle. For Aternity 10.x, use Oracle 12.1.0.2 or 11.2.0.4

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

  4. (Optional, only if you change Oracle versions) 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.
Important

You must select Verify Database Schema Readiness for Upgrade.

Before you begin

  • Download the latest Aternity on-premise's main setup package from the Riverbed support site by selecting Software (size).

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

  • 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 a week to check the status of your existing database with the Aternity Database Verification Utility, to verify it is ready for Aternity 10.

  • Prepare the Aternity Oracle Database Server with the following requirements:

    Attribute Requirement

    Oracle version for Aternity Oracle Database Server

    For Aternity 10.x, use Oracle 12.1.0.2 or 11.2.0.4 (including support for Oracle Data Guard), specifically:

    • Aternity 10.x requires Oracle Database version 12c Enterprise Edition 64-bit, 12.1.0.2 or Oracle Database 11gR2 Enterprise Edition 64-bit with patch set 11.2.0.4.

    Note

    You do not need to update your Oracle if you already have one of these versions.

    The Oracle license MUST allow for Partitioning, Parallel, and Advanced Compression. However the other licensing features are optional, depending on your enterprise's policy and requirements: (Diagnostics and Tuning Pack and the Active Data Guard).

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

    Operating system for Aternity Oracle Database Server

    Windows Server 64 bit 2016 (for Aternity 10.0.1 only), 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 Oracle Database Server on Linux CentOS 5.8 or Linux Red Hat Fedora.

    Hardware

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

    In addition, check the ports which you must open on this server (learn more).

    Permissions

    Ensure you have local administrator privileges on this computer.

    Time zone

    Synchronize all Aternity components to have the same date, time AND time zone.

    Virtual memory

    Set the pagefile size to 1.5 times the RAM in the operating system of the Aternity Oracle Database Server.

    Network

    Ensure this server has a static IP v4 address, and that you open the required ports.

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 Aternity Management Server

    Locate the Aternity Database Verification Utility, DBVerfication_windows-x64.exe, which you downloaded as part of the Aternity on-premise server setup package.

    Copy it to the computer containing the Aternity Management Server's computer.

    Important

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

  4. Step 4 Launch the Aternity Database Verification Utility.

    Right-click DBVerfication_windows-x64.exe and select Run as administrator.

  5. Step 5 Choose a destination directory to install, then proceed.
  6. Step 6 Run both scripts:
    • Verify Database Settings and Privileges verifies that the Oracle Database Server is properly configured for Aternity and for the size of your deployment, and that the schema roles have the required privileges.

    • Verify Database Schema Readiness for Upgrade verifies the configuration of the Aternity schema to ensure its compatibility with the update.

    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 verification tool completes these fields based on the existing configuration.

    The tool displays this screen and the sizing selection screen only if you selected Verify Database Settings and Privileges.

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

    Enter the username and password of the database. This must be the username that has SYSTEM privileges.

    Database Host

    Enter the FQDN, hostname (recommended) or IP address of the Oracle Database Server.

    Port

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

    Service

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

    Verify Platform Database Credentials

    Indicates the utility checks the existing structure and content of the database, and confirms that the schema (Platform, Database Username) has the required privileges to function properly.

    For updates, this is always selected.

    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.

    During an Oracle Database Server update, the tool displays this screen and the sizing selection only if you selected Verify Database Settings and Privileges.

    The database parameters depend on the intended size of the deployment
  9. Step 9 Address the results of the Aternity Database Verification Utility reports.

    The Database Verification Results report describes the results of the database structure verification. The Database Schema ReadinessTest Results report describes the results of the schema verification.

    You can copy each report to the clipboard from the last screen of Aternity Database Verification Utility, or select the link to see the report as a plain text file.

    View each compatibility report
    Tip

    We strongly advise you to submit these reports to Customer Services for assistance in ensuring your database is ready for the update.

    You can address the errors at the top of the Database Verification Results report (above the title Additional Database Information) by updating the settings in your current Aternity deployment. Alternatively, a DBA can make required changes directly in the database. We recommend that you or the DBA address the errors with the assistance of Customer Services.

    Address errors or warnings in the Database Schema Readiness Test Results only with the assistance of Customer Services

  10. Step 10 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.

  11. Step 11 (Optional, only if you change Oracle versions) Ask your DBA to update Oracle. For Aternity 10.x, use Oracle 12.1.0.2 or 11.2.0.4

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

  12. Step 12 (Optional, only if you change Oracle versions) 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.