Purpose
DBaaS Tool is used by all of the DB service-related Cloud automation functions. (dbaastools_exa rpm a.k.a. Cloud Tooling)
This include :
- Creating and deleting databases
- Patching both the DB and GI using UI or exadbcpatchmulti
- DBaaS tool is released frequently and generally contains new functionality as well as important fixes.
- Dbaas Tools include exadbcpatch, exadbcpatchmulti, dbaascli, dbaasapi etc.
- Provides one click or one command operation to stage and apply GI/DB patches
Oracle highly recommends that you maintain the same version of cloud tooling across your Exadata DB system environment.
It is recommended to update to the latest version of the cloud tools before performing any patching operations.
Scope
In Exadata Cloud Service environment (Cloud at Customer, OCI-C and OCI) customer manages the software that directly affects their application in this case DOMU.
Privileges Required : System Administrators - access to the Operating System is required in order to perform this collection.
System Impact : None - following the collection instructions given will have no impact on the system.
In many cases this set of information will be sufficient for diagnosis - in some cases, additional specific diagnostic data may be required at a later stage.
Details
Process:
Step 1: Stage DBaaS Tool- Oracle Cloud Ops stages DBaaS Tool to OSS on customer OCC once or twice every month (Oracle responsibility)
Step 2: Update DBaaS Tool On Every Node (DomU) - Customer updates DBaaS Tool on every node with the latest version (Customer responsibility)
Perform the following procedure on *every compute node* in the Exadata DB system in order to update to the latest patch cloud tooling utility.
Steps to update the Cloud tooling.
1. Connect to the compute node (DomU) as opc user then switch to root user account.
#sudo -s
2. Display info of your current Exadata cloud tooling version installed on DomU
# rpm -qa --last|grep -i dbaastools_exa
The format of the output shows the version and release ---> dbaastools_exa-<version-release>_<YYMMDD>.<string>.platform
e.g. dbaastools_exa-1.0-1+21.4.1.1.0_220128.0941.x86_64 Mon 07 Feb 2022 02:09:32 PM UTC
The release_string will determine if you are running the latest version note that the string shows the date
dbaastools_exa-1.0-1+21.4.1.1.0_220128.0941.x86_64 Mon 07 Feb 2022 02:09:32 PM UTC --->21.4.1.1.0_220128 --> version 21.4.1.1.0 --> Jan 01, 2022
3. Check if there are any latest cloud tooling updates available. Cloud tooling updates are cumulative. DBaaSCLI command retrieves patch list from the OSS container.
To list available DBaaS Tool (ExaCC Gen1)
# dbaascli patch tools list
Output Example: dbaascli patch tools list DBAAS CLI version 21.3.1.2.0 Executing command patch tools list Checking Current tools on all nodes DomU-Node1: Patchid : 21.3.1.2.0_211221.0941 Available Patches Patchid : 21.4.1.1.0_220128.0941(LATEST) Install tools patch using dbaascli admin updateStack --version LATEST DomU-Node2: Patchid : 21.3.1.2.0_211221.0941 Available Patches Patchid : 21.4.1.1.0_220128.0941(LATEST) Install tools patch using dbaascli admin updateStack --version LATEST All Nodes have the same tools version
# dbaascli admin showLatestStackVersion
DBAAS CLI version 24.1.1.0.0
Executing command admin showLatestStackVersion
Job id: 474fa258-b1f2-4ebb-9910-0f26d380829f
Session log: /var/opt/oracle/log/admin/showLatestStackVersion/dbaastools_2024-04-19_06-24-05-PM_143736.log
{
"description" : "dbaastools for Exadata cloud service EXACC",
"version" : "24.1.2.0.0_240327.2043",
"baseVersion" : "24.1.2.0.0"
}
Note:
If you don't see anything listed it may be due to /var/opt/oracle/exapatch/exadbcpatch.cfg having a missing property value for oss_container_url
It is important that for all new VM clusters to modify the oss_container_url to point to their OSS (unless it allows getting the information from the public cloud)
For ExaCC Gen2
oss_container_url="http://169.254.200.1:2080/dbaas_patch/shome"
For ExaCS - Public Cloud
oss_container_url=""
For ExaCC Gen1
oss_container_url="https://storage.<region_id>.ocm.<subscription_ID>.oraclecloudatcustomer.com/v1/Storage-idcs-cloudinfra-<region_id>/dbaas_patch/shome"
Important:
If there is a any newer version available, please upgrade it to latest version:
For ExaCS & ExaCC Gen2
Run following command from the First DomU only - Which is going to update DBaaS Tool on all DomUs
# dbaascli admin updateStack
For ExaCC Gen1
Run following command from the each DomU to update DBaaS Tool on all DomUs
# dbaascli patch tools apply --patchid LATEST
Look for the "complete successfully" to confirm DBaaS tool applied
5. Verify the installed version of Exadata cloud tooling :
# rpm -qa --last|grep -i dbaastools_exa
dbaastools_exa-1.0-1+21.4.1.1.0_220128.0941.x86_64 Mon 07 Feb 2022 02:09:32 PM UTC
6. If the cloud tooling update fails. Please open a Service request and attach log as per following MOS Note:
SRDC - Exadata Cloud Mandatory Data Collection for Database Life Cycle Issues (Doc ID 2683637.1)
Documentation:
https://docs.oracle.com/en-us/iaas/Content/Database/References/dbaascli_topic-tooling_log_collection.htm
Key Points:
Cloud tooling updates are cumulative
Update to the latest cloud tooling before any patches/upgrades.
All Exadata db nodes must have the same cloud tooling version.
Keep a backup of /var/opt/oracle/exapatch/exadbcpatch.cfg before the cloud tooling update.
This operation can be executed at any time without a performance impact.
Additional Information
- DBaaS Tools are generally released by Exadata Cloud Product development once or twice every month.
- The average size of DBaaS tool is between 500 - 800 MB.
- The current process includes Downloading of DBaaS Tool to Core Nodes & Staging them to OSS of customer OCC.
- The entire process of Downloading and Staging are automated.
- Automation takes care of approximately 70% of customers. These customers will have the latest version of DBaaS tools available within 2-3 days of release.
- The customer with automation failures are ones with connectivity issues. These are resolved manually by Cloud Operations engineers. The staging duration would depend on the type of issue encountered.
What is the significance of having the latest DBaaS Tool? Why should I try to keep the latest DBaaS Tool available in my environment?
DBaaS Tool is used by all of the DB Service related Cloud automation functions. This includes Creating and Deleting databases, Configuring Backup, Patching both and DB and GI using both Cloud UI or manually using dbaascli command. DBaaS Tool is released frequently (typically more than once per month) and generally contains new functionality as well as important bug fixes. Hence it is strongly recommended to keep the DBaaS Tooling updated on all nodes frequently and especially recommended to download the latest tooling prior to applying the latest updates.
Your feedback is important to us to improve our services, rate this document under "Was this document helpful?" (top right corner)
References
Uploading Attachments to Service Requests [ Video ] (Doc ID 1596914.1)
Oracle Support Training and Resources (Doc ID 1959163.2)
How to find the DB System OCI on Exadata Cloud Service (OCI) (Doc ID 2505850.1)
Updating the Cloud Tooling for Exadata Cloud Environment (DBaaS Tool a.k.a Cloud Tooling) (Doc ID 2495335.1)
