Databases@Powered by Passion
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.
The RMAN database registration process encountered an error, specifically ORA-01403 (no data found), during its initial synchronization due to an existing restore point. Despite entering commands correctly, the registration failed because RMAN could not process the restore point metadata across the CDB. Upon identifying this issue through trace analysis, the restore point was deleted, allowing successful completion of the database registration process, highlighting the importance of internal procedures in troubleshooting.
This post explains how a Data Pump export in an Oracle RAC environment failed with misleading errors, including ORA-48128, related to symbolic links and file access. The actual cause was an NFS-mounted Data Pump directory that was accessible from only one RAC node. Adding CLUSTER=N resolved the issue by keeping all Data Pump workers on the local instance. Alternatively, mounting the NFS filesystem on all RAC nodes also resolves the problem.
The content discusses the role of Oracle Update Advisor in assisting DBAs with patch management decisions. While automation tools efficiently execute patches, they lack the capability to evaluate whether updates align with an organization’s needs. Oracle Update Advisor addresses this gap by providing status indicators and allowing customization of maintenance policies to better reflect operational realities.
The Oracle Fleet Patching and Provisioning (FPP) local mode, in 19c environments, mandates a Grid Infrastructure Management Repository (GIMR) for local automation. Users must configure GIMR when components are missing or when it was not initially installed. The MDBUtil tool assists with setting up GIMR, ensuring the environment is adequate for running FPP local mode. Additionally, commands for managing Cluster Health Monitor resources are outlined in this post.
Osman’s DBlog 