6.2 Performing the Upgrade

Upgrade the existing OAA installation to the latest version.

  1. On the installation host where you downloaded the installation files, navigate to the $UPGRADE_WORKDIR/oaa-install directory:
    cd $UPGRADE_WORKDIR/oaa-install
  2. Run the installManagementContainer.sh script as follows:
    ./installManagementContainer.sh -t ./<oaa-image>.tar

    This will upgrade the installed oaamgmt chart. As the upgrade progresses you will be prompted to answer various questions and perform certain tasks. The table below outlines some of the questions or tasks you may be asked to answer or perform:

    Output Action
    Version check failed for podman, would you like to use docker instead? [Y/N]: This message will appear if the installation host does not have podman installed as per the Installation Host Requirements. If you do not have podman at the required version then choose to use Docker by answering "Y".
    Use 'podman login' to login into your private registry if you have not done so previously.Login successful? [Y/N]:

    Note:

    If using Docker the above will show docker login
    		If your private Container Image Registry (CIR) where you store images requires a login, use podman login or docker login to log into the CIR and enter your credentials when prompted:
    podman login <container-registry.example.com>
    or: 
    docker login <container-registry.example.com>

    Note:

    The table above does not include an exhaustive list of all prompts you will see during the upgrade as most are self explanatory.
  3. When asked Would you like to perform an upgrade? [Y/N], enter Y.
  4. Once the Management Container installation is complete you will see output similar to the following:
    ...
Copying OAA properties file to oaans/oaamgmt-oaa-mgmt-7dbfbd87dc-r7v29:/u01/oracle/scripts/settings
Use command 'kubectl exec -n oaans -ti oaamgmt-oaa-mgmt-7dbfbd87dc-r7v29 -- /bin/bash' to get a shell to the OAA mgmt pod.
From pod shell, use command 'kubectl get pods' to verify communication with the cluster.
Continue OAA installation from the OAA mgmt pod.
OAA management installation complete.

    If there are any problems during upgrade, refer to Troubleshooting the Installation.

  5. As per the output connect to the new OAA management pod, for example:
    kubectl exec -n oaans -ti oaamgmt-oaa-mgmt-7dbfbd87dc-r7v29 -- /bin/bash
    This will take you into a bash shell inside the OAA management pod:
    [oracle@oaamgmt-oaa-mgmt-7dbfbd87dc-r7v29 /]$
  6. Inside the OAA management pod perform the upgrade:
    [oracle@oaamgmt-oaa-mgmt-7dbfbd87dc-r7v29 /]$ cd ~
[oracle@7dbfbd87dc-r7v29 ~]$ ./OAA.sh -f installOAA.properties

    During installation the deployment progress is shown on the screen. If you need more detailed information, you can view the install.log. The log is accessible from within the management container at /u01/oracle/logs, or outside the container at <NFS_LOGS_PATH>.

  7. Once the upgrade is complete you should see the upgrade is successful and the deployment details are printed to the screen. See, Printing Deployment Details.

    If there are any problems during the upgrade, refer to Troubleshooting the Installation.

  8. Run the following command to make sure all the pods are running:
    kubectl get pods -n <namespace>
    For example:
    kubectl get pods -n oaans
    The output should look similar to the following:
    
NAME                                                  READY   STATUS    RESTARTS   AGE
oaainstall-customfactor-b5cf55778-rwg5l               1/1     Running   0          6m29s
oaainstall-email-65dc5f679-6xtmd                      1/1     Running   0          6m29s
oaainstall-fido-5b46884c68-q9dxp                      1/1     Running   0          6m29s
oaainstall-oaa-65779f845b-b9g6c                       1/1     Running   0          6m29s
oaainstall-oaa-admin-ui-6689c9d4cd-jhfzx              1/1     Running   0          6m29s
oaainstall-oaa-drss-9f68f4856-849x4                   1/1     Running   0          6m29s
oaainstall-oaa-kba-6b8c4cfb-x2xsm                     1/1     Running   0          6m28s
oaainstall-oaa-policy-7997547c98-8jl4n                1/1     Running   0          6m28s
oaainstall-push-58b478c4f9-fx95n                      1/1     Running   0          6m28s
oaainstall-risk-68bf8b75b7-gg99q                      1/1     Running   0          6m28s
oaainstall-risk-cc-6f669d5c5c-sfhfx                   1/1     Running   0          6m28s
oaainstall-sms-786d684994-lktfz                       1/1     Running   0          6m28s
oaainstall-spui-94f6f5f9b-pmhc2                       1/1     Running   0          6m28s
oaainstall-totp-7759f4598d-8rqwv                      1/1     Running   0          6m27s
oaainstall-yotp-5f865df96-c5x52                       1/1     Running   0          6m27s
oaamgmt-oaa-mgmt-7dbfbd87dc-r7v29                     1/1     Running   0          16m
  9. If you have Push Notifications for Android configured and are upgrading from a release prior to June 24, check that push notifications work successfully. See Accessing a Protected Application Using Android Push Notification.
  10. If you previously have used Archiving and Purging, then you must run /u01/oracle/db_purge/archive/create_oaam_rebuild_index.sql inside the management container.
    1. Enter a bash shell for the OAA management container: 
      kubectl exec -n <namespace> -ti <oaamgmt-pod> -- /bin/bash
      For example:
      kubectl exec -n oaans -ti oaamgmt-oaa-mgmt-7dfccb7cb7-lj6sv -- /bin/bash
    2. Inside the management container, navigate to the /u01/oracle/db_purge/archive directory and login to the OAA database as the OAA schema user, for example DEV_OAA:
      sqlplus <schema_name>/<password>@//db.example.com:1521/orcl.example.com
    3. Run the create_oaam_rebuild_index.sql script to update the rebuild index procedure:
      SQL> @create_oaam_rebuild_index.sql