Databases@Powered by Passion
Before upgrading a 12c EBS database to 19c in an ExaCC environment, the DBMS_STATS.GATHER_FIXED_OBJECTS_STATS command resulted in an ORA-00600 error. The issue was resolved by correcting the ORA_NLS10 environment variable to point to the appropriate directory using srvctl setenv database. After restarting the database, the command executed successfully.
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.
This blog post details the steps for cloning an Oracle Database Home from an existing Oracle Home to another server, applicable to both RAC and Single Instance environments. Cloning is preferred over reinstalling, particularly for legacy systems with unique patches when original installation setups are unavailable. The process involves creating a tar file of the source, setting up the target, and executing cloning commands to ensure successful cloning and validation of the new Oracle Home.
This content discusses simulating tape backups using RMAN and a dummy SBT library (oracle.disksbt) to troubleshoot backup failures. The article details how to perform fake tape backups with Oracle’s disk-based SBT library, effectively isolating issues within the Oracle layer or the vendor’s Media Management Library (MML). It also introduces the sbttest tool for assessing media manager installation and its usage with Oracle Test Disk API.
The content explains various Oracle connectivity testing utilities: ping, tnsping, ociping, connping, and adbping. It honors Joel Kallman, a key figure in database development. The document details how each connectivity utility functions, emphasizing their roles in troubleshooting connection issues and measuring latency, providing practical examples and outcomes for effective database management and performance evaluation.
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.
Osman’s DBlog 