Before You Begin

Update the sqlnet.ora File for Oracle Database 19c

About This Task

Important: You need to first upgrade to APM V5.0.x. and then follow the steps to upgrade to V5.1.1.0.0. You can view the APM V5.0x documentation here.
Note: This update is applicable only to customers using the Oracle Database.
If you want to upgrade Oracle Database 19c hosted on the APM database using APM Database Upgrade Manager, you must update the sqlnet.ora file.

Procedure

  1. On the Oracle Database 19c machine that hosts the APM database, access the sqlnet.ora file. By default, the file is located in the ORACLE_HOME/network/admin folder.
  2. Add the following line in the sqlnet.ora file:
    SQLNET.ALLOWED_LOGON_VERSION_SERVER=8
  3. Save and close the file.

What To Do Next

You may need to change the password of the APM super administrator before the upgrade. After the upgrade, revert the change (that is, remove the line that you have added in the sqlnet.ora file). Otherwise, you may be required to change the password for all APM users.

Improve Upgrade Performance

About This Task

If the APM database contains a large number of Policy Execution History records, upgrading APM can take a long time. To improve the performance, only the most recent 3,000,000 Policy Execution History records will be upgraded. However, if these records contain a large number of hyperlinks, the upgrade may still time out. Therefore, you can choose to remove some or all the Policy Execution History records before upgrading the APM database or you can configure the upgrade to process fewer records or skip upgrade of Policy Execution History records entirely.

This topic describes how to determine the number of Policy Execution History records in your database. You can then remove some or all of them or adjust the upgrade configuration.

Procedure

  1. Access APM.
  2. In the Applications menu, select TOOLS > Queries.
  3. Select Create New.
    The Design workspace appears.
  4. Select SQL.
    The SQL workspace appears.
  5. Enter the following query, and then select .
    SELECT Count(MI_POLICY_EXEC_LOG.PLOG_KEY) "Count"
FROM MI_POLICY_EXEC_LOG
    The query results appear, displaying the number of Policy Execution History records.
  6. If the number of Policy Execution History records is excessive, you can remove some or all the records or configure the upgrade utility to process fewer records. For instructions, contact GE Vernova Support.