Databases@Powered by Passion
Oracle Data Pump is utilized for database migrations and backups. To automate daily exports, I have two Bash scripts: one for managing directories and notifications, and another for executing the Data Pump export with custom parameters. Features include automated directory creation, log management, and email alerts for failures.
This article provides a step-by-step guide to changing the DB_UNIQUE_NAME parameter in Oracle Database after cloning, migration, or environment refreshes. It explains how to relocate database files, including datafiles, tempfiles, redo logs, control files, SPFILE, and password files, to a new directory structure in ASM or filesystem storage, while also covering for pdb$seed and Oracle Clusterware configuration.
The RMAN backup error originated after upgrading an Oracle Database from version 19.26 to 19.32 while using Veritas NetBackup. The issue was identified as a version incompatibility between the RMAN recovery catalog (19.6) and the database environment. Testing showed that the backup worked without the recovery catalog, indicating that the catalog was the stumbling block. Upgrading the catalog resolved the issue, allowing successful backup operations to resume.
The post discusses an error encountered during a Data Pump export from an Oracle Database 19c, upgraded from 12c, specifically ORA-31642 and ORA-01031. Initially attributed to insufficient privileges, the problem was traced to lacking necessary rights. After granting required privileges and tablespace quotas, the export completed successfully.
The conference featured technical sessions with insights from various experts. Highlights included direct ASM file access via NFS, effective use of SQL tracing for diagnosing contention, and practical applications of SQLcl and AutoUpgrade. Presentations also covered transitioning to SaaS, PostgreSQL for Oracle DBAs, and lots of many things all about Oracle. Overall, the event fostered valuable networking and knowledge sharing among database professionals.
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.
