1. Deploying and Managing Oracle Access Management on Kubernetes
  2. Administering Oracle Access Management on Kubernetes
  3. Patching and Upgrading
  4. Upgrading from Oracle Access Management 12.2.1.4 to 14.1.2
  5. Shutting Down the OAM Domain

17.2.4 Shutting Down the OAM Domain

Run the following commands to shutdown the Oracle Access Management (OAM) 12c deployment:
  1. Shut down the OAM deployment using the following command:
     kubectl patch domain %DOMAIN_UID% -n %NAMESPACE% --type=merge --patch "{\"spec\": {\"serverStartPolicy\": \"Never\"}}"
    For example:
     kubectl patch domain accessdomain -n oamns --type=merge --patch "{\"spec\": {\"serverStartPolicy\": \"Never\"}}"
    The output will look similar to the following:
    domain.weblogic.oracle/accessdomain patched
  2. Run the following kubectl command to view the pods:
    kubectl get pods -n %NAMESPACE%
    For example:
    kubectl get pods -n oamns
    The output will look similar to the following:
    NAME                                                      READY   STATUS        RESTARTS       AGE
accessdomain-adminserver                                  1/1     Running       0              21h
accessdomain-oam-policy-mgr1                              1/1     Running       0              21h
accessdomain-oam-server1                                  0/1     Terminating   0              21h

    The Administration Server pods and Managed Server pods will move to a STATUS of Terminating.

    After a few minutes, run the command again and make sure the pods should have disappeared before continuing.

  3. If a helper pod exists, then delete it:
    kubectl delete pod helper -n %NAMESPACE%
    For example:
    kubectl delete pod helper -n oamns