Skip to Content

Upgrading

This topic describes how to upgrade the product from an older version to a new one by migrating the database.

Warning

Important

You can only migrate a database from an older version to a new version only, not from a new version to an older version. To restore an older version, use your backup database.

Related topic

Installing

When upgrading the BMC AMI Ops Insight product, the application sometimes modifies the database schema because of changes in the new version.

Before upgrading to a new version:

  • Create a backup of the database.
  • Make sure you have sufficient space on the file system (preferably at least 2.5 times the size of the database files) because BMC AMI Manager creates a backup before updating the database. 
  • Make sure you have enough time to complete the upgrade without interruption.
Error
Warning

Failure to follow these steps might result in corruption of the database files and leave them in an unrecoverable state. 

To upgrade to the latest maintenance level

After applying the PTFs, use the following steps to refresh your existing AMIFTPG JCL in UBMCSAMP: 

Warning

Important

Perform these steps only if you have implemented the optional graph component (z/CX docker container) previously.

  1. Rename the existing AMIFTPG JCL member to AMIFTPGO.       
  2. Copy the FTPGRAPH member from PVZSAMP dataset to UBMCSAMP as AMIFTPG.
    The new JCL contains additional statements to FTP the new graph database container to z/CX.
  3. In the new AMIFTPG member, replace the SET statement (Line 8 to 16) with the old JCL member (AMIFTPGO).

  4. Configure the jobcard and submit the AMIFTPG job.
    This job will FTP the TAR files to your instance.         

    Warning

    Important

    Run AMIFTPG job only if you are running BMC AMI Ops Insight Docker container on z/CX. See related APAR for details.   

                                                            

To upgrade to the latest Docker container

When upgrading to the latest version of the Docker container, use the following steps:

  1. Stop and remove the older version of the Docker container.
  2. Download the latest version of the Docker container.
Warning

Important

For Playback Docker container using Docker Desktop on local device, when upgrading to the latest version of the Docker container, the models that were previously loaded are not visible in the Import file window because now they have the mlb.bk extension. Remove the .bk extension and import the models and playback files again.

To upgrade to BMC AMI Ops Insight 2.5.00

Before you begin:

  • Backup the database, environment members, and properties files of BMC AMI Ops Insight 2.0.
  • Make sure that Java 17 is installed on z/OS.

To upgrade to BMC AMI Ops Insight 2.5:

  1. From the Installation System, install BMC AMI Ops Insight 2.5.00. 
  2. Perform the installation and configuration jobs.
    If you are using the optional graph component, run AMIFTPG configuration job.
  3. Copy all BMC AMI Ops Insight 2.5 PROC members from the AMIHLQ.UBMCSAMP library to your system proclib.
  4. Update the following properties and environment members, and copy the customized values (if any) from the BMC AMI Ops Insight version 2.0 members to the version 2.5 members: 
    • Tomcat Environment member in AMIHLQ.BMCSAMP(AMITCEN7).
      In BMC AMI Ops Insight 2.0, the Tomcat environment member name was AMITCEN6.
    • Common Environment member in AMIHLQ.UBBSAMP(AMICMNEV).
      If you are running SSL and using a keyring certificate, use a double slash (//) in the keystore name in AMIHLQ.UBBSAMP(AMICMNEV).
      For example, AMIMGR_KEYSTORE_NAME=safkeyring://STCUSER/<certname>       
    • amipdt.properties member at USS path &AMIINST/aoidata/aoiinst/conf.
    • custom.properties member at USS path &AMIINST/aoidata/srhinst/conf.
  5. Copy the db directory from the BMC AMI Ops Insight 2.0 path &AMIINST/aoidata/aoiinst/db to the BMC AMI Ops Insight 2.5 path &AMIINST/aoidata/aoiinst/.
    If you have created Playback files, copy the dat directory from the BMC AMI Ops Insight 2.0 path &AMIINST/aoidata/aoiinst/dat to the BMC AMI Ops Insight 2.5 path &AMIINST/aoidata/aoiinst/.
    If you are using the optional graph component on zCX/ZLinux, stop and remove the running containers, and then restart the containers by using the ./run.sh command.
    For more information about commands, see Installing-dashboard-container-for-graph-functionality.
  6. Start all BMC AMI Ops Insight 2.5 started tasks.
  7. On the About page, verify that all the started tasks and data were successfully migrated from BMC AMI Ops Insight 2.0 to 2.5 by verifying your models, historical events, and so on.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI Ops Insight 2.5