Category: Exadata

To register a manually created database on Exacc using dbaascli, a DBNAME.ini file must be created first. A specific command may fail due to a corrupted RPM database under /var/lib/rpm, showing a standard RPM-related error. To resolve this, the RPM database needs to be rebuilt by backing up and removing stale files. After rebuilding, the registration command should succeed and generate the necessary cloud registration file.

During an Oracle Database Appliance (ODA) patching process, a validation error (DCS-10045) occurred due to the absence of ‘Running’ databases. Although a physical standby database was running, ODA’s dcsagent failed to recognize it. The issue was resolved by adding the database using the srvctl command, and fixing missing ASM directory paths allowed the patching to complete successfully.

While working with an Oracle Database Appliance, an inconsistency arose between the management layer and the storage stack, leading to a disk reported as “FAILED” by odaadmcli. Further investigation revealed the disk was fully operational, with ASM actively using it. Troubleshooting involved validating multipath status, ASM state, and using the odaadmcli stordiag command. A file synchronization issue was discovered, which was resolved by restarting the OAK daemon, returning the disk to an “ONLINE” state.

The document details troubleshooting steps taken to resolve a grid release update(19.28) error on an Exadata Cloud system. The initial issue involved SSH connectivity, followed by problems with the Database Cloud Service (DBCS) agent. Key actions included checking SSH configurations, inspecting platform information, and managing package updates. Ultimately, updating the dbaascli tools resolved the precheck failures, simplifying the patching process.

The recent analysis of an Exachk report revealed a new check for Hardware Assisted Resilient Data (HARD) capability during the ASM Relocation (rebalance, resync, or resilver) process. HARD checks validate data integrity in Exadata storage servers, preventing corruption. Setting the content.check attribute of asm diskgroup to TRUE will enable Hardware Assisted Resilient Data (HARD) Validation During ASM Relocation. This change aligns with Exadata best practices for improved data protection.

This post outlines the steps to configure Cisco Management Network Switches with multiple uplinks for redundancy in Oracle Exadata environments. It emphasizes the importance of the Administration Network, which connects all Exadata components for management purposes. Detailed steps are provided for configuring a Cisco 9348 Ethernet Switch, including LACP setup for uplink ports and validating spanning tree settings to ensure stable and reliable connectivity