-
Notifications
You must be signed in to change notification settings - Fork 31
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Oracle SOA Suite hugo document changes for fix for 24.1.2 (#195)
- Loading branch information
1 parent
eabc905
commit bbbf042
Showing
43 changed files
with
944 additions
and
1,320 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -109,138 +109,6 @@ The script will perform the following steps: | |
| * Create a convenient utility script, `delete-domain-job.yaml`, to clean up the domain home | ||
| created by the create script. | ||
|
|
||
| #### Post install tasks | ||
|
|
||
| Review the Read Me file of each patch listed in the following MOS notes, depending on your Oracle Linux version. | ||
| - For Oracle Linux 7, see [35908803](https://support.oracle.com/epmos/faces/ui/patch/PatchDetail.jspx?patchId=35908803) | ||
| - For Oracle Linux 8, see [35915091](https://support.oracle.com/epmos/faces/ui/patch/PatchDetail.jspx?patchId=35915091) | ||
|
|
||
| Also, for SOA bundle 12.2.1.4.230827 patch post install tasks, see [35748499](https://support.oracle.com/epmos/faces/ui/patch/PatchDetail.jspx?patchId=35748499). Refer **Section 6: Post-Installation Instructions** in the Read Me file for instructions related to purge and maven plugin. | ||
|
|
||
| You can ignore the instructions to clean PS3 maven plugin files, since it will be automated as part of container image creation. | ||
|
|
||
| Perform the following steps to purge. | ||
|
|
||
| 1. Create a YAML file named `soapostinstall.yaml` with the following sample. The necessary SQL scripts are mounted inside pod at "/soa_purge". | ||
|
|
||
| > Note: Replace the domain namespace `soans` and SOA Suite image `soasuite:12.2.1.4` with the details specific to your environment in the following sample YAML. | ||
| ``` | ||
| apiVersion: v1 | ||
| kind: Pod | ||
| metadata: | ||
| name: soapostinstall | ||
| namespace: soans | ||
| labels: | ||
| app.kubernetes.io/name: dbclient | ||
| spec: | ||
| containers: | ||
| - name: dbclient-container | ||
| image: ghcr.io/oracle/oraclelinux8-instantclient:21 | ||
| command: ['sh', '-c', 'echo The dbclient pod is running! && sleep 3600'] | ||
| volumeMounts: | ||
| - mountPath: "/soa_purge" | ||
| name: soa-shared-volume | ||
| initContainers: | ||
| - name: soa-oh | ||
| image: soasuite:12.2.1.4 | ||
| command: ['sh', '-c', "cp -rf /u01/oracle/soa/common/sql/soainfra/sql/oracle/122140/ /soa_purge"] | ||
| volumeMounts: | ||
| - mountPath: "/soa_purge" | ||
| name: soa-shared-volume | ||
| volumes: | ||
| - name: soa-shared-volume | ||
| ``` | ||
|
|
||
| 1. Apply the YAML to create a Kubernetes pod named `soapostinstall` in the `soans` namespace. | ||
|
|
||
| ``` | ||
| $ kubectl apply -f soapostinstall.yaml | ||
| ``` | ||
|
|
||
| 1. Start a bash shell in the `soapostinstall` pod. | ||
|
|
||
| ``` | ||
| $ kubectl exec -it -n soans soapostinstall -- bash | ||
| ``` | ||
|
|
||
| 1. A bash shell opens in the `soapostinstall` pod. | ||
|
|
||
| ``` | ||
| [root@soapostinstall /]# | ||
| ``` | ||
|
|
||
| 1. Reload the SOA purge scripts as a SOAINFRA user. | ||
|
|
||
| - Change the directory to the location where the scripts for post installation steps are stored. | ||
|
|
||
| ``` | ||
| [root@soapostinstall /]# cd /soa_purge/122140/soa_purge12/ | ||
| ``` | ||
|
|
||
| - Connect to the database as a SOAINFRA user. | ||
|
|
||
| ``` | ||
| [root@soapostinstall /]# sqlplus <SOAINFRA_USER>/<PASSWORD>@<DATABASE_SERVICE> | ||
| ``` | ||
|
|
||
| For example, if the schema prefix is `SOA1`, schema password is `Oradoc_db1` and connection string to database is `oracle-db.default.svc.cluster.local:1521/devpdb.k8s`, you can connect to database as SOAINFRA user using the following command. | ||
|
|
||
| ``` | ||
| [root@soapostinstall /]# sqlplus SOA1_SOAINFRA/[email protected]:1521/devpdb.k8s | ||
| ``` | ||
|
|
||
| - Execute the following script. | ||
|
|
||
| ``` | ||
| SQL> @soa_purge_scripts.sql | ||
| SQL> show errors | ||
| ``` | ||
|
|
||
| 1. Verify the SOA purge scripts. | ||
|
|
||
| - Change the directory to location where the SOA purge scripts are stored. | ||
|
|
||
| ``` | ||
| [root@soapostinstall /]# cd /soa_purge/122140/verify12/ | ||
| ``` | ||
|
|
||
| - Connect to the database as a SOAINFRA user. | ||
|
|
||
| ``` | ||
| [root@soapostinstall /]# sqlplus SOA1_SOAINFRA/[email protected]:1521/devpdb.k8s | ||
| ``` | ||
|
|
||
| - Execute the following script. | ||
|
|
||
| ``` | ||
| SQL> @soa_verify_scripts.sql | ||
| SQL> show errors | ||
| ``` | ||
| 1. Recreate the auto purge jobs with new jobs added in 12.2.1.4.201210SOABP. | ||
|
|
||
| - Change the directory to location where scripts are stored. | ||
|
|
||
| ``` | ||
| [root@soapostinstall /]# cd /soa_purge/122140/soa_purge12/soa | ||
| ``` | ||
|
|
||
| - Connect to the database as a SOAINFRA user. | ||
|
|
||
| ``` | ||
| [root@soapostinstall /]# sqlplus SOA1_SOAINFRA/[email protected]:1521/devpdb.k8s | ||
| ``` | ||
|
|
||
| - Execute the following script. | ||
|
|
||
| ``` | ||
| SQL> @loadcompbasedpurgeprogram.sql | ||
| SQL> show errors | ||
| ``` | ||
|
|
||
| #### Start the domain | ||
|
|
||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Large diffs are not rendered by default.
Oops, something went wrong.
Oops, something went wrong.