Upgrading
When upgrading the BMC AMI Ops Insight product, the application sometimes modifies the database schema because of changes in the new version.
(BMC.AMIOPS.SPE2210)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.
To upgrade to the latest maintenance level
After applying the PTFs, use the following steps to refresh your existing AMIFTPG JCL in UBMCSAMP:
- Rename the existing AMIFTPG JCL member to AMIFTPGO.
- 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. - In the new AMIFTPG member, replace the SET statement (Line 8 to 16) with the old JCL member (AMIFTPGO).
Configure the jobcard and submit the AMIFTPG job.
This job will FTP the TAR files to your instance.
To upgrade to the latest Docker container
When upgrading to the latest version of the Docker container, use the following steps:
- Stop and remove the older version of the Docker container.
- Download the latest version of the Docker container.
To upgrade from BMC AMI Ops Insight 1.2.00
When upgrading from BMC AMI Ops Insight version 1.2.00 to 2.0.00, update your existing Tomcat started task (AMITCJCL) JCL to run with 64-bit JVM in version 2.0.00.
- Set TCENV=AMITCEN6
- Set VERSION=86
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*