Performing the Upgrade

17.2.7 Performing the Upgrade

To perform the upgrade you must create an upgrade pod and run several upgrade commands.

Note:

If the upgrade fails, see Restoring After a Failed Upgrade.

Run the following command to create the domain-upgrade-pod:

kubectl apply -f <workdir>/upgradescripts/domain-upgrade-pod.yaml

For example:

kubectl apply -f /OAM12CUPG//upgradescripts/domain-upgrade-pod.yaml

The output should look similar to the following:

pod/accessdomain-domain-upgrade created

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-domain-upgrade                               1/1     Running   0          2m3s

It may take a few minutes until the pod is in a status of READY 1/1.

Run the following command to enter a bash shell in the domain-upgrade pod:

kubectl exec -it %DOMAIN_UID%-domain-upgrade -n %NAMESPACE% -- /bin/bash

For example:

kubectl exec -it accessdomain-domain-upgrade -n oamns -- /bin/bash

This will take you into a bash shell in the domain-upgrade pod:

[oracle@accessdomain-domain-upgrade oracle]$

Inside the upgrade pod, navigate to the /u01/scripts directory:
```
cd /u01/scripts
```

Run the following command to run the Upgrade Assistant:

$ORACLE_HOME/oracle_common/upgrade/bin/ua -response /u01/scripts/domainUpgradeResponse.txt -logLevel TRACE -logDir /tmp

The output should look similar to the following:

Oracle Fusion Middleware Upgrade Assistant 14.1.2.0.0
Log file is located at: /tmp/ua<DATE>.log
Reading installer inventory, this will take a few moments...
...completed reading installer inventory.
UPGAST-00238: Warning: A dependency by component OIM on component SOA is unresolved. Upgrades of component OIM will be disabled.
A dependent component was not found while discovering upgrade components and their dependencies.
Make sure the required component has been installed.
Using response file /u01/scripts/domainUpgradeResponse.txt for input
 Oracle Platform Security Services schema examine is in progress
 Oracle Access Management Suite (Schema Upgrade) schema examine is in progress
 Oracle Audit Services schema examine is in progress
 Oracle Metadata Services schema examine is in progress
 Oracle Platform Security Services schema examine finished with status: ready for upgrade
 Oracle Access Management Suite (Schema Upgrade) schema examine finished with status: ready for upgrade
 Oracle WebLogicServer schema examine is in progress
 Common Infrastructure Services schema examine is in progress
 Oracle Metadata Services schema examine finished with status: ready for upgrade
 Common Infrastructure Services schema examine finished with status: ready for upgrade
 Oracle WebLogicServer schema examine finished with status: ready for upgrade
 Oracle Audit Services schema examine finished with status: ready for upgrade
Schema Version Registry saved to: /tmp/ua<DATE>.xml
 Oracle Audit Services schema upgrade is in progress
 Oracle Platform Security Services schema upgrade is in progress
 Oracle Access Management Suite (Schema Upgrade) schema upgrade is in progress
 Oracle Metadata Services schema upgrade is in progress
 Oracle Access Management Suite (Schema Upgrade) schema upgrade finished with status: succeeded
 Common Infrastructure Services schema upgrade is in progress
 Common Infrastructure Services schema upgrade finished with status: succeeded
 Oracle WebLogicServer schema upgrade is in progress
 Oracle Audit Services schema upgrade finished with status: succeeded
 Oracle Metadata Services schema upgrade finished with status: succeeded
 Oracle WebLogicServer schema upgrade finished with status: succeeded
 Oracle Platform Security Services schema upgrade finished with status: succeeded

Note:

The following message above can be ignored:

UPGAST-00238: Warning: A dependency by component OIM on component SOA is unresolved. Upgrades of component OIM will be disabled.
A dependent component was not found while discovering upgrade components and their dependencies.
Make sure the required component has been installed.

Enter a wlst prompt inside the domain-upgrade pod:

$ORACLE_HOME/oracle_common/common/bin/wlst.sh

The output will look similar to the following:

Initializing WebLogic Scripting Tool (WLST) ...

Jython scans all the jar files it can find at first startup. Depending on the system, this process may take a few minutes to complete, and WLST may not return a prompt right away.

Welcome to WebLogic Server Administration Scripting Shell

Type help() for help on available commands

wls:/offline>

Run the following commands at the wls:/offline> prompt to perform domain reconfiguration:

Set the domainHome:

domainHome='/u01/oracle/user_projects/domains/%DOMAIN_UID%'

For example:

domainHome='/u01/oracle/user_projects/domains/accessdomain'

Read the domanHome:
```
readDomainForUpgrade(domainHome)
```
The output will look similar to the following:
```
wls:/offline/accessdomain>
```

Update the domain:

updateDomain()

Note:

This command can take approximately 25 minutes to complete.

The output will look similar to the following:

<DATE> 9:28:33 AM oracle.security.jps.internal.config.xml.XmlConfigurationFactory validateFileLocation
INFO: JPS Config: /u01/oracle/user_projects/domains/accessdomain/config/fmwconfig/jps-config-jse.xml
<DATE> 9:28:34 AM oracle.security.jps.internal.config.xml.XmlConfigurationFactory validateFileLocation
INFO: JPS Config: /u01/oracle/user_projects/domains/accessdomain/config/fmwconfig/jps-config.xml
<DATE> 9:28:34 AM oracle.security.opss.internal.runtime.ServiceContextManagerImpl getContext
WARNING: Bootstrap services are used by OPSS internally and clients should never need to directly read/write bootstrap credentials. If required, use Wlst or configuration management interfaces.
<DATE> 9:28:35 AM oracle.security.jps.internal.config.xml.XmlConfigurationFactory validateFileLocation
INFO: JPS Config: /u01/oracle/user_projects/domains/accessdomain/config/fmwconfig/jps-config-jse.xml
<DATE> 9:28:35 AM oracle.security.jps.internal.config.xml.XmlConfigurationFactory validateFileLocation
INFO: JPS Config: /u01/oracle/user_projects/domains/accessdomain/config/fmwconfig/jps-config.xml
<DATE> 9:54:05 AM oracle.security.jps.az.internal.runtime.policy.AbstractPolicyImpl initializeReadStore
INFO: Property for read store in parallel: oracle.security.jps.az.runtime.readstore.threads = null
wls:/offline/accessdomain>

Close the domain:
```
closeDomain()
```

Run the following post upgrade steps at the wls:/offline> prompt:

Set the domainHome:

domainHome='/u01/oracle/user_projects/domains/%DOMAIN_UID%'

For example:

domainHome='/u01/oracle/user_projects/domains/accessdomain'

Set the RCUPREFIX and RCU_SCHEMA_PWD password:

wlsRuntimeUser='%RCUPREFIX%_WLS_RUNTIME'

schemaPassword='%RCU_SCHEMA_PWD%'

For example:

wlsRuntimeUser='OAMK8S_WLS_RUNTIME'

schemaPassword='<password>'

Read the domain:
```
readDomain(domainHome)
```

Change to the following directory:

cd('/JdbcSystemResource/WLSRuntimeSchemaDataSource/JdbcResource/WLSRuntimeSchemaDataSource/JdbcDriverParams/NO_NAME_0')

Set the CONNECTION_STRING:

dbUrl="jdbc:oracle:thin:@%CONNECTION_STRING%"

For example:

dbUrl="jdbc:oracle:thin:@mydatabasehost.example.com:1521/orcl.example.com"

Run the following to update the domain:

cmo.setUrl(dbUrl)

cmo.setDriverName('oracle.jdbc.OracleDriver')

set('PasswordEncrypted', schemaPassword)

cd('Properties/NO_NAME_0/Property/user')

cmo.setValue(wlsRuntimeUser)

cd('/')

updateDomain()

No output will be returned to the screen and you will just be returned to the prompt.

Close the domain and exit:
```
closeDomain()
```
```
exit()
```

Exit the domain-upgrade pod:
```
exit
```