Tuesday, September 9, 2025

Exadata Database Service Software Versions

 

at No comments:
Labels:

Updating the Cloud Tooling for Exadata Cloud Environment (DBaaS Tool a.k.a Cloud Tooling)

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

    

     To list available DBaaS Tool (ExaCS & ExaCC Gen2)

        # 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:

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)

at No comments:
Labels: ,

How to Manage and Check Health of Exadata Cloud Related Services - ExaCS & ExaCC

How to Manage and Check Health of Exadata Cloud Related Services - ExaCS and ExaCC

Solution

A) Please check passwordless ssh - working for the OPC / GRID / ORACLE OS Users

Login as OPC user and run following command to check passwordless ssh (Please change the GRID Home Path for the olsnodes in following command)

for node in `sudo /u01/app/19.0.0.0/grid/bin/olsnodes`; do ssh -t -t -i /home/opc/.ssh/id_rsa -o StrictHostKeyChecking=no opc@$node 'hostname -s;date'; done

Login as OPC user and Switch User to GRID user and run following command to check passwordless ssh

sudo su -
su - grid
for node in `/u01/app/19.0.0.0/grid/bin/olsnodes`; do ssh -t -t -i /home/grid/.ssh/id_rsa -o StrictHostKeyChecking=no grid@$node 'hostname -s;date'; done

Login as OPC user and Switch User to ORACLE user and run following command to check 

sudo su -
su - oracle
for node in `/u01/app/19.0.0.0/grid/bin/olsnodes`; do ssh -t -t -i /home/oracle/.ssh/id_rsa -o StrictHostKeyChecking=no oracle@$node 'hostname -s;date'; done

 

B) Display Details About the Exadata Cloud System.

As a ROOT OS user, Please execute following commands and verify DBaaS Tool and DBCS Agent is latest 

/var/opt/oracle/misc/platforminfo

rpm -qa --last | egrep -i 'dbaastools_exa|dbcs'

 

C) Check Status, Stop and Start the DBCS Agent Services.

1. Check status for the DBCS Agent Service - Run following command as a ROOT OS User 

systemctl status dbcsagent

For Example - Output

● dbcsagent.service
   Loaded: loaded (/usr/lib/systemd/system/dbcsagent.service; enabled; vendor preset: disabled)
   Active: active (running) since Tue 2023-02-07 19:41:34 -04; 2h 10min ago
 Main PID: 24953 (bash)
    Tasks: 112
   Memory: 495.2M
   CGroup: /system.slice/dbcsagent.service
           ├─24953 /bin/bash -c umask 077; /bin/java -Xms100m -Xmx1024m -Doracle.security.jps.config=/opt/oracle/dcs/agent/jps-config.xml -jar  /opt/oracle/dcs/bin/dbcs-agent-*.jar server...
           └─24964 /bin/java -Xms100m -Xmx1024m -Doracle.security.jps.config=/opt/oracle/dcs/agent/jps-config.xml -jar /opt/oracle/dcs/bin/dbcs-agent-23.1.1.0.1_230119.0045.jar server /op...

2. To Stop and Start the DBCS Agent Service 

systemctl stop dbcsagent

systemctl start dbcsagent

3. Verify again status for the DBCS Agent and DBCS Admin Service 

systemctl status dbcsagent

 

D) Check Status, Stop and Start the DBCS Admin Services.

1. Check status for the DBCS Admin Service 

systemctl status dbcsadmin
 
 For Example - Output
 
● dbcsadmin.service
   Loaded: loaded (/usr/lib/systemd/system/dbcsadmin.service; enabled; vendor preset: disabled)
   Active: active (running) since Sat 2022-09-24 12:43:07 -04; 4 weeks 2 days ago
 Main PID: 304542 (sudo)
	Tasks: 0
   Memory: 1.6M
   CGroup: /system.slice/dbcsadmin.service
		   ‣ 304542 sudo -u opc /bin/bash -c umask 077; /bin/java -jar  /opt/oracle/dcs/bin/dbcs-admin-*.jar server /opt/oracle/dcs/conf/dcs-admin.json &amp;amp;amp;gt;/opt/oracle/dcs/log/dcsadmin-stdou...&amp;amp;nbsp;

2. To Stop and Start the DBCS Admin Service 

systemctl stop dbcsadmin

systemctl start dbcsadmin

3. Verify again status for the DBCS Admin Service 

systemctl status dbcsadmin

 

E) Reference Document

DBaaS Tools - Cloud Tooling RPM Release Notes (Doc ID 2404336.1)

Updating the Cloud Tooling for Exadata Cloud Environment (DBaaS Tool a.k.a Cloud Tooling) (Doc ID 2495335.1)

 

References

NOTE:2495335.1 - Updating the Cloud Tooling for Exadata Cloud Environment (DBaaS Tool a.k.a Cloud Tooling)

NOTE:2404336.1 - DBaaS Tools - Cloud Tooling RPM Release Notes

 How to Manage and Check Health of Exadata Cloud Related Services - ExaCS & ExaCC (Doc ID 2926648.1)

at No comments:
Labels: , , ,

Monday, September 8, 2025

Oracle EBS R12.2 Upgrade to Database 23ai on Exadata Cloud

 

  • Purpose: This Oracle Support note details the process for upgrading Oracle E-Business Suite (EBS) Release 12.2 from Oracle Database 19c to the newly certified Oracle Database 23ai, specifically for environments running on Exadata Database Service on dedicated infrastructure or Cloud@Customer.

  • Prerequisites:

    • EBS must be on at least Release 12.2.7 (Error Correction baseline).

    • Unified auditing must be enabled (traditional auditing is deprecated).

    • System Schema Migration is required to remove deprecated database dependencies

  • Deployment Context: This note applies to on-premises Exadata, specifically the Database Service on dedicated infrastructure or Cloud@Customer deployments, differentiating from the Base Database Service covered in another note.

  • Upgrade Utility: The recommended approach is using Oracle’s AutoUpgrade tool for seamless migration from DB 19c to DB 23ai. A newer tool, EDBPC (E-Business Suite Database Parameter Checker), is also introduced—helping validate initialization parameters for DB-23ai readiness

  • Key Enhancements with DB 23ai: Beyond the upgrade, the move to DB 23ai brings modern database innovations like AI-driven tuning, vector search, self-driving capabilities, scale improvements, rolling upgrades via Active Data Guard, and enhanced security features.


  • https://blogs.oracle.com/ebs/post/ebs-database-23ai-upgrade-migration-and-other-documents-revised-for-april-2025-ru-across-database-cloud-services?utm_source=chatgpt.com


    • at No comments:
    Labels: ,

    How to validate TDE Wallet Password

     Command syntax and usage

    The basic syntax for the command is:
    orapki wallet display -wallet <wallet_location>
    • orapki: The name of the Oracle PKI command-line utility.
    • wallet: The module or component to work with.
    • display: The specific action to perform on the wallet.
    • -wallet <wallet_location>: The full path to the directory containing the wallet files. For a password-protected PKCS#12 wallet (ewallet.p12), you will be prompted for the password unless it's an auto-login wallet (cwallet.sso). 
    Example of orapki wallet display
    After navigating to the location of the orapki tool (e.g., $ORACLE_HOME/bin), here is an example command and its output for a wallet located at /private/user/orapki_use/root:
    Rename the autologin wallet file.
    $ mv /private/user/orapki_use/root/cwallet.sso /private/user/orapki_use/root/cwallet.sso_tmp
    $ orapki wallet display -wallet /private/user/orapki_use/root

    at No comments:
    Labels: , , ,

    ewallet p12 vs cwallet sso

    The ewallet.p12 stores credentials and certificates protected by a user password, while cwallet.sso provides an obfuscated, random password for auto-login capabilities, allowing for passwordless wallet access. Both files are often used together in an Oracle auto-login wallet, where ewallet.p12 holds the sensitive data and cwallet.sso enables the wallet to open without requiring the user's password. 
    Key Differences
    • ewallet.p12
      • Function: Stores private keys, certificates, and credentials. 
      • Protection: Protected by a user-defined password, which is required to access and modify the wallet. 
      • Use Case: For password-protected wallets where the password is provided during connection or modification. 
    • cwallet.sso
      • Function: Enables "auto-login" functionality, allowing for passwordless access to the wallet. 
      • Protection: Uses an obfuscated, random password that is more secure than a simple user password for auto-login. 
      • Use Case: Bound to the specific host and user where it was created for increased security in auto-login environments. 
    Relationship in an Auto-Login Wallet
    • When you create an auto-login wallet using Oracle utilities, both ewallet.p12 and cwallet.sso files are generated. 
    • The ewallet.p12 file contains the essential credentials and certificates, while the cwallet.sso file contains the obfuscated password needed for the auto-login feature to work. 
    • The orapki utility can be used to modify the wallet, but it requires the wallet's original password, which was used to create the ewallet.p12 file. 

    In summary: Use ewallet.p12 when you need a password-protected wallet to store your security credentials and certificates, and use cwallet.sso when you need the wallet to open automatically and bypass password prompts on the host it was created on. 

    at No comments:
    Labels: ,
    Subscribe to: Posts (Atom)

    Upgrading Oracle E-Business Suite Release 12.2 with Oracle Database 19c to 23ai on Oracle Exadata Database Service on Dedicated Infrastructure or Cloud@Customer

      1.1 Carry Out Performance Evaluation in a Test Environment When upgrading your Oracle E-Business Suite database, it is essential to ensure...