4.8.1 Post Installation Steps for All Installations
Follow these post installation steps for all installation types; OAA only, OAA-OARM, OARM only, and OAA-OARM-OUA.
Import the policy snapshot by performing the following steps:
- Obtain the latest snapshot policy file from My Oracle
Support by referring to the document ID
2723908.1.
Note:
If the latest snapshot file is not available, use the/u01/oracle/scripts/oarm-12.2.1.4.1-base-snapshot.zip
file inside the management container. - Copy the latest snapshot file to the
<NFS_CONFIG_PATH>
. - Edit the
<NFS_CONFIG_PATH>/installOAA.properties
and add the following parameters to the bottom of the Common Deployment configuration:common.deployment.import.snapshot=true common.deployment.import.snapshot.file=/u01/oracle/scripts/settings/<latest_snapshot>.zip
Note:
If not using the latest snapshot file set:common.deployment.import.snapshot.file=/u01/oracle/scripts/settings/oarm-12.2.1.4.1-base-snapshot.zip
- Enter a bash shell for the OAA management pod if not already inside
one:
For example:kubectl exec -n <namespace> -ti <oaamgmt-pod> -- /bin/bash
kubectl exec -n oaans -ti oaamgmt-oaa-mgmt-7dfccb7cb7-lj6sv9 -- /bin/bash
- Run the following command inside the bash shell to import the policy snapshot:
cd ~/scripts ./importPolicySnapshot.sh -f settings/installOAA.properties
Note:
This will use theinstallOAA.properties
in the<NFS_CONFIG_PATH>
.The snapshot will import and if successful you will see the message
Successfully applied snapshot: 10001
or similar.Exit the bash shell.
- Edit the
<NFS_CONFIG_PATH>/installOAA.properties
and change the following parameter at the bottom of the Common Deployment configuration:common.deployment.import.snapshot=false
Note:
This is an important step to avoid overwriting and erasing policies during a future upgrade.